It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,877
×10,962
×7,469
×5,939
×4,318
×3,954
×2,351

question asked: May 06 '15, 4:10 a.m.
question was seen: 4,533 times
last updated: May 06 '15, 8:52 a.m.

Related questions

Rebuild All Indexes

0
Kurtulus YILDIRIM (68●11●22) | asked May 06 '15, 4:10 a.m.
 Hi,
My customer has a CLM server which RTC, RRC and RQM 4.0.6 installed on it. Now, they want to split products into a different servers. Also they will change Operating System (Windows to Linux) so I need to rebuild all indexes. Can I rebuild indexes while current / Windows server running? I mean users will continue their daily usage while I run rebuild indexes in new server?
Thank you.

Accepted answer

0
permanent link
Ralph Schoon (63.5k●3●36●46) | answered May 06 '15, 4:21 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
edited May 06 '15, 4:23 a.m.
It is not true that you necessarily have to rebuild any index to do so.
  • The Text Indexes are stored in files. You can and should move the indexes to some fast network access storage or copy the files over to the new server while it is down. If the path to the index location is set correctly in the teamserver.properties and the files can be read and written by the user context that runs the server, there should be no need to recreate those files; you should use an absolute path to the index files and also include them in your backups
  • The database indexes don't have to be changed if the database remains the same. If not it depends if the DBMS vendor allows to move the DB to a different system using backup/restore this should keep the indexes untouched. If not and you need to do a DB export and re-import, the indexes should be recreated in that process as far as I know

For additional information see https://jazz.net/library/article/1271 https://jazz.net/library/article/1272 and check the repotools commands. Also see https://jazz.net/wiki/bin/view/Deployment/BackupCLM


I think most of the index related commands require the server to be down.

Kurtulus YILDIRIM selected this answer as the correct answer
Comments
Kurtulus YILDIRIM commented May 06 '15, 4:36 a.m. | edited May 06 '15, 4:39 a.m.

 Hi Ralph,

Thank you for your reply but in the link below, it says I need to rebuild Text indices if I switch the OS. https://jazz.net/wiki/bin/view/Deployment/MigratingCLMToANewEnvironment
So my question is still there. Can I run rebuild indexes command while current PROD server is running.

Database will remain same so we don't need to do anything about it as you suggested.

Ralph Schoon commented May 06 '15, 4:44 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

It says pretty much what I have said

5. Copy or Rebuild Indexes

The index files are referenced in the teamserver.properties file with relative path locations (e.g. com.ibm.team.fulltext.indexLocation=conf/qm/indices/workitemindex, com.ibm.team.jfs.index.root.directory=indices). So these entries should not have to change when you create new install areas. But after a new installation, the index files under these directories would not match. So you must copy these files from the source to the target. If the operating systems are different, you should rebuild the indexes with repotools commands. This will take longer and must be done with the database running and the server shut down.

It is not precise on the files on if you have to though. It says you should. I am not sure about the rationale. The content should be the same. I think I have  used Derby/Tomcat setups and moved the backups between OS's without seeing issues. However since this is a production setup you might want to make sure and rebuild the text indexes.

It says that the server needs to be down.

Kurtulus YILDIRIM commented May 06 '15, 8:48 a.m. | edited May 06 '15, 8:52 a.m.

So, Can I run rebuild indexes command while current PROD server is running? to make shortest blackout time.

Thank you.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.