The
automatic upgrade of Content Platform Engine data (Content Engine data
if you are upgrading FileNet® P8 from
a version prior to 5.2.0) includes the creation of a new index
on the IBM® Content Search Services index
requests table. However, if the table is too large, the automatic
upgrade cannot build the index. In which case you need to build it
manually.
About this task
The automatic upgrade of
Content Platform Engine drops an index on the
index request table and creates a new one. If there are too many entries
(500,000 by default) in the table, the automatic upgrade cannot create
the new index. Instead, it writes a message to the
p8_server_trace.log file
indicating that you must build the index manually.
Important: You
must create the index before you can upgrade IBM Content Search Services.
You
can find the
p8_server_trace.log file in one
of the following locations, depending on your application server type.
Table 1. Location of p8_server_trace.log fileApplication server type |
Path to p8_server_trace.log file |
WebSphere® Application
Server |
WEBSPHERE_HOME/profiles/profile_name/FileNet/server_Instance_name/p8_server_trace.log |
Oracle WebLogic Server |
WL_HOME/user_projects/domains/my_domain/FileNet/AdminServer/p8_server_trace.log |
JBoss Application Server |
JBOSS_HOME/jboss-as/bin/FileNet/server_instance_name/p8_server_trace.log |
WEBSPHERE_HOME,
WL_HOME,
and
JBOSS_HOME are the installation
locations of the application servers.
Procedure
To check for and build (as needed) the index on the index
requests table:
- Open the p8_server_trace.log file
on each server where you upgraded Content Platform Engine and check whether a
message similar to the following message is present: There
are more than 500000 rows in the IndexRequests table. Some index
creation has been skipped. You need to run the sql statement to create
the index MANUALLY after upgrade and prior to production.
- If the message is not present in the p8_server_trace.log file,
then the automatic upgrade created the index on the index requests
table and you can skip the remainder of this topic. If the message
is present, then complete the following substeps:
- Start the administration console for your database.
- Create the index on the index requests table by executing
the SQL statement that appears in the message in the p8_server_trace.log file.