r2 - 2015-05-27 - 16:57:29 - Main.sbagotYou are here: TWiki >  Deployment Web > DeploymentTroubleshooting > UpgradeTroubleshooting > CLMUpgradeTroubleshooting > RunStatistics

Run Database Statistics

Authors: UpgradeTroubleshootingTeam
Build basis: CLM 4.x, 5.x

This topic discusses running the database statistics prior to an upgrade.

Database Statistics

The upgrade documentation suggests that prior to any upgrade, you should update the database statistics for your CLM Deployment. Otherwise, the upgrade process may take significantly longer.

The following tables must contain up-to-date database statistics:

Running the Database Statistics

Work with your DBA to run the database statistics.

Common Issues

Below are some known issues which arise during the update configuration files step in the upgrade process

DB2: Runstats fails

Version: Upgrade to 4.x using DB2
Error During Upgrade: The default runstats, db2 runstats on table REPOSITORY.ITEM_STATES, command fails, it results in an error related to the INDEX-Dcom.ibm.team.repotools.rcp.allowInvalidBundles=true" is not properly formatted.
Resolution: Have your DBA run the following command:
db2 runstats on table REPOSITORY.ITEM_STATES on all columns and sampled detailed indexes all allow write access
Related topics:

External links:

  • None

Additional contributors: SusanWu

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r2 < r1 | More topic actions
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.