How long do repotools -rebuildIndices take to run?

Chances are your 4001 upgrade install location just can't find the index locations of the previous installation.  We tried to provide information in the interactive upgrade guide that allowed you to be more cognizant of your existing index location prior to upgrade so such that during the upgrade, the indices would either 1) remain in their existing 'stable' locations and be accurately pointed at from the teamserver.properties or 2) be copied from their existing locations to a new location specified in the 'new' teamserver.properties file of the upgraded software. 

Just look for this line in both your JTS and <app-specific> teamserver.properties, where app is ccm or qm:
com.ibm.team.fulltext.indexLocation.

Here is an excerpt from the v4.0.1 infocenter on verifying your index locations prior to upgrading:

Before you start the upgrade, verify that the index locations in the application's properties files are pointing to absolute paths on the file system, rather than relative paths.

1. For Jazz Team Server, go to old_JTS_install_dir/server/conf/jts and open teamserver.properties file for editing.
2. For Change and Configuration Management application, go to old_CCM_install_dir/server/conf/ccm and open teamserver.properties file for editing.
3. Search for the com.ibm.team.fulltext.indexlocation line.
4. If the location is a relative path, the indices will be located relative to the WebSphere Application Server profile hosting the applications. Change the location to an absolute path:
   • For Jazz Team Server, enter com.ibm.team.fulltext.indexLocation=WAS_Install_Dir/appServer/profiles/Appsrv01/conf/jts/indices/workitemindex where WAS_Install_Dir is the WebSphere Application Server installation directory and Appsrv01 is the application server profile name.
   • For Change and Configuration Management application, enter com.ibm.team.fulltext.indexLocation=WAS_Install_Dir/appServer/profiles/Appsrv01/conf/ccm/indices/workitemindex where WAS_Install_Dir is the WebSphere Application Server installation directory and Appsrv01 is the application server profile name.
5. During the upgrade, after the properties are merged, the script opens the version 4.0.1 teamserver.properties file so that you can preview the properties. In the version 4.0.1 teamserver.properties file, change the location of the index files to an absolute path of a stable location on your drive. A stable location is a directory that will not be deleted when an application is uninstalled. The absolute stable location should look like this example:
   • com.ibm.team.fulltext.indexLocation=JTS_4.0.1_install_dir/server/conf/jts/indices/workitemindex where JTS_4.0_install_dir is the location where Jazz Team Server 4.0.1 application is installed.
   • com.ibm.team.fulltext.indexLocation=CCM_4.0.1_install_dir/server/conf/ccm/indices/workitemindex where CCM_4.0_install_dir is the location where Change and Configuration Management 4.0.1 application is installed.
   The script then copies the indexes from the previous installation location to the new version 4.0.1 stable directory.

I just did it a week ago.

On JTS:

• -renidex  9min50 sec
• -rebuildTextIndices  24sec (one NPE exception)
• -rebuildIndices  33sec

On CCM:

• -renidex  41sec
• -rebuildTextIndices  8h9min50sec
• -rebuildIndices  crashed (open PMR)
• -rebuildClosureTable  1h6min50sec

On QM:

• -renidex  31sec
• -rebuildTextIndices  1min5sec
• -rebuildIndices  3min50sec

Sizing info of my environemnt:

• JTS DB about 2GB (incl. RM)
• CCM DB about 4GB
• QM Db about 1GB
• Application Server:
• Windows2008-R2/64
• 24GB Ram
• 4 core
• DB Server
• Windows 2008R2/64
• DB29.7
• 24GB Ram
• 4Core
• 1GB Network between the two servers

Remark:

• The long time on CCM for the -rebuildTextIndices is suspect. This I will retry another weekend.
• open problems with NPW's on -rebuildIndices on CCM and JTS 

Hello
I'm involved in a RTC 4.0.6 migration project,
these are the times of the repotools commands:

Hardware specifications:
    WAS 8.5.5 + DB2 10.1 Server
        RHEL 6.5 / 64 bits
        8GB RAM
        2 CPU (4 cores) Pentium XEON 50110 1.6GHz

DD.BB Sizing:
    JTS DB about 11GB
    CCM DB about 48GB

On JTS:
    ./repotools-jts.sh -reindex                     --> 1 min.
    ./repotools-jts.sh -rebuildTextIndices   --> 30 sec.
    ./repotools-jts.sh -rebuildIndices          --> 30 sec.

On CCM:
    ./repotools-ccm.sh -reindex                    --> 55 min
    ./repotools-ccm.sh -rebuildTextIndices  --> 40 min.
    ./repotools-ccm.sh -rebuildIndices         --> 15 min.

Hi John,

please be careful which index command you run. One is creating the index on the database tables and typically not intended to be run by a user (I have been told). We are in the process of updating articles (the backup articles) and creating new content, based on recent information we gathered about the indexing story.

I can't give you an idea about how long it takes to recreate the indexes. I think you might have to try. It would be good if you measure how long it takes.

Here a summary of reindex commands with our latest information:

Recreate the Fulltext Index

You can recreate the Fulltext index files using the command:

repotools-${APP} -rebuildTextIndices

Recreate the JFS Index

You can recreate the JFS index files using the command:

repotools-${APP} -reindex all

My two cents - our RTC DB has about 35 GB data and rebuildIndices took about 30 mins. Because it is just creating DB indexes, it won't take as much time as rebuildTextIndices which usually took hours.