Database index is not created when you start IBM Content Navigator after upgrading

When you start IBM® Content Navigator after you upgraded your IBM Content Navigator deployment, you see an error in the web application server log file.

Symptoms

In most instances, the indexes on your database are automatically updated when you start IBM Content Navigator after you upgrade your deployment. However, in some instances, when you start IBM Content Navigator, you see an error in the web application server log file. The error indicates that an index could not be created in your database.

Resolving the problem

Your database administrator must run the script that is displayed in the log file to build the index.
To determine if there are any indexes that were not created, review the appropriate log for your web application server:
  • For WebSphere® Application Server, open the Systemout.log file. By default, this log file is in the WAS_profile_location/logs/server/ subdirectory of the WebSphere Application Server installation directory.
  • For Oracle WebLogic Server, open the AdminServer.log file. By default, this log file is in the Oracle/Middleware/user_projects/domains/base_domain/servers/AdminServer/logs directory.
If you find an error in the log file stating that index creation failed, complete the following steps:
  1. Stop the IBM Content Navigator web application server.
  2. Have your database administrator run the script from the log file on your IBM Content Navigator configuration database.
  3. Restart the IBM Content Navigator web application server.