IBM Support

Best Practice: Upgrading to Content Platform Engine V5.5.9 or higher.

Troubleshooting


Problem

Due to the metadata removal process included in the v5.5.9 and higher upgrade, the time required for upgrading any object store could be significantly longer than normal. 

Symptom

You may experience an object store upgrade process seemingly hang on the "31.1.3_DeleteObsoleteClasses" phase. 

Cause

Upgrading to CPE 5.5.9 or higher from a prior release includes automated steps that remove metadata related to the Publishing and DITA Publishing add-ons.
 
In addition, if you are upgrading from a version earlier than 5.5.2, the upgrade process also removes metadata related to multiple IBM Connections extensions, and the Social Collaboration Notification Extensions for Content Navigator.
 

Resolving The Problem

Prior to upgrading any object store to V5.5.9 or higher,  IBM recommends that you take the following actions:
 
1.  There are several upgrade-related fixes in 5.5.9.0-P8CPE-IF002, 5.5.10.0-P8CPE-IF003, 5.5.11.0-P8CPE-IF001, 5.5.12.0-P8CPE-IF002, and 5.6.0-P8CPE. Upgrade your P8 domain using one of these release versions at minimum.
 
2.  Remove as many object store artifacts of the obsolete pre-5.5.3 add-ons as possible prior to upgrade, if you are concerned about the time required.
 
3.  If the UT_ClbActivityStreamQueueEnt table or UT_ClbSeedlistEntry table exists in the object store database, count the table rows. If either table contains more than 10,000 rows, truncate the table contents.
 
4. Count the table rows in the SweepResults table.  If the table contains more than 100,000 rows, consider truncating the table contents.  This table contains the results of individual sweeps, and you will need to evaluate whether the sweep result history is important to your business requirements.
 
5. If there are any rows in the object store PublishRequest table, truncate the table contents.
 
6.  Create these indexes in each object store database to help general database performance during the obsolete object deletions.  Remove the indexes when you are finished with the upgrade.
 
Composite index on DOCVERSION (object_class_id, object_id)
Composite index on EVENT (object_class_id, object_id)
 
7. In ACCE, search for and delete any documents that are of the following classes:
 
ACCE > [object store] > Search - Class: [as below], ID: Is Not Null
DitaBase
DitaMap
DitaBookMap
DitaTask
DitaGlossEntry
DitaConcept
DitaReference
DitaTopic
DitaVal
 
8.  Increase your upgrade timeout and transaction timeout values by configuring the following JVM parameters to initially give the upgrade code plenty of time to complete:
 
-Dcom.filenet.engine.upgrade.TransactionTimeout=16000
-Dcom.filenet.engine.minServerManagedTimeout=16000
-Dcom.filenet.engine.maxServerManagedTimeout=16000
-Dcom.filenet.engine.recommendedTimeoutIncrement=16000
 
9.  If you have many CPE instances in your cluster, assign each CPE instance to upgrade a few specific object stores by using the object store symbolic names in the following JVM parameter.  This configuration provides greater control from a status monitoring perspective via the servlet and CPE trace logs.
 
"-Dcom.filenet.engine.upgrade.ObjectStores=os1,os2,My object store name"
 
10. Verify that you have recently updated the database statistics on the Event and QueueItem tables on your object store databases.  If the statistics are out of date or stale, queries on these tables could take much longer than when the statistics are up to date.
 

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSNVNV","label":"IBM FileNet Content Manager"},"ARM Category":[{"code":"a8m0z0000001kJMAAY","label":"Upgrade"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.5.9;and future releases"}]

Document Information

Modified date:
20 July 2026

UID

ibm17150032

Page Feedback