r2 - 2013-09-25 - 20:45:00 - Main.sbagotYou are here: TWiki >  Deployment Web > DeploymentTroubleshooting > UpgradeTroubleshooting > CLMUpgradeTroubleshooting > ReindexingAfterUpgrade

new.png Upgrade troubleshooting

Authors: UpgradeTroubleshootingTeam
Build basis: CLM 3.x and later

This page is discusses reindexing the server after the upgrade, when testing proves that the upgrade may not have been successful.

Differences between re-index commands

There are three different re-index commands which can be run through repotools. Below, each command will be discussed.


This command is used to rebuild the Jazz Foundation Server (JFS) index. JFS indices are only used by JTS and are utilized by the dashboards and on RTC/z (EE) for a particular build app, otherwise they are not used on ccm nor qm. If the dashboards are failing then that would indicate a problem with the JFS index.


This command will rebuild the database indices.


This command will rebuild the workitem lucene indexer which is used by the workitems for text searches. If workitems or query search results are not accurate, that would indicate problem with workitem indexer and you may consider running this command to rebuild it.

Reindexing during the Upgrade

Reindex and RebuiltTextIndices repotools commands are run as part of the upgrade process, executed by the upgrade script. It is not mandatory that they are run seperately unless there is some indication that the indices are corrupt.

When to manually run the index commands

The following conditions may warrant running the reindex commands:
  • Indication of index corruption
  • Full Text queries are failing
  • Dashboard issues after the upgrade (where no dashboard migration occured)

How long will this command take to run?

The time to run the reindexing commands will depend on the size of the repository database and total workitems contained, and also the size of workitemindex folder.
Here is the benchmark we have for jazz.net:
  • Approx. total WIs in ccm: 248,000
  • ccm repository : 415 GB
  • jts repository: 15 GB
  • the workitemidex folder for ccm is approx. 1.5 GB

  • Time took to complete repotools-ccm -rebuildTextIndices: approx. 2.5 hours (this was to remove the old workitem indices and rebuild from scratch)
  • Time took to complete repotools-ccm -reindex: 15 minutes.

Where do I go from here?

If you are unable to resolve your issue using the available online resources, open a service request with IBM Rational Support. Refer to Additional troubleshooting resources for further details.

Related topics: None

External links:

  • None

Additional contributors: StephanieBagot, SusanWu, MichaelAfshar, WilliamChen, BrettBohnn

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.