Rebuilding workitemindex?
We recently migrated from RTC 1.0.1.1 to RTC 2.0.0.2. In the migration instructions it mentions that you should copy the workitemindex folder over prior to migration. I was unable to find this folder and skipped this step.
Now full text searches that worked previously don't seem to work any longer.
Is the search issue related to the workitemindex? If so, is there a way to rebuild the workitemindex?
Thanks!
Now full text searches that worked previously don't seem to work any longer.
Is the search issue related to the workitemindex? If so, is there a way to rebuild the workitemindex?
Thanks!
3 answers
We recently migrated from RTC 1.0.1.1 to RTC 2.0.0.2. In the migration
instructions it mentions that you should copy the workitemindex folder
over prior to migration. I was unable to find this folder and skipped
this step.
Now full text searches that worked previously don't seem to work any
longer.
Is the search issue related to the workitemindex? If so, is there a
way to rebuild the workitemindex?
Please run the following command:
repotools -rebuildTextIndices
This can be done while the server is running.
--
Regards,
Patrick
Jazz Work Item Team
We recently migrated from RTC 1.0.1.1 to RTC 2.0.0.2. In the migration
instructions it mentions that you should copy the workitemindex folder
over prior to migration. I was unable to find this folder and skipped
this step.
Now full text searches that worked previously don't seem to work any
longer.
Is the search issue related to the workitemindex? If so, is there a
way to rebuild the workitemindex?
Please run the following command:
repotools -rebuildTextIndices
This can be done while the server is running.
--
Regards,
Patrick
Jazz Work Item Team
Patrick,
I don't know how I missed that from the docs.
BTW, I tried to run repotools -rebuildTextIndices while the server was running and it didn't work. I got the following message:
CRJAZ1238I Jazz has detected another server process is connected to the repository database location "db2:/localhost:50000/JAZZ20". The server must not be running when running repotools data commands. Check that only one process is connecting to the database.
I'll try it with the server down tonight.
Thanks!