CRJZS5758E JFS Index Error in RM Application , CLM 5.0.2
ERRORS:
CRJZS5758E The information in the index for private applications might be incorrect because the timestamp (2013-10-11T14:54:45.712Z) of the "triple live" index is ahead of the timestamp (2013-10-11T14:14:54.152Z) of the database. Stop the server and either restore the index that corresponds to the database or run the following command: "repotools-rm -reindex" to recover the correct index. For more details, open the help system and search for CRJZS5758E.
CRJZS5758E The information in the index for private applications might be incorrect because the timestamp (2013-10-11T14:54:45.712Z) of the "text live" index is ahead of the timestamp (2013-10-11T14:14:54.152Z) of the database. Stop the server and either restore the index that corresponds to the database or run the following command: "repotools-rm -reindex" to recover the correct index. For more details, open the help system and search for CRJZS5758E.
So As I understand what I need to do is to rebuild the index by following the actions
Wile running repotools-rm -reindex all command i am getting following error
Loading configuration from "file:teamserver.properties".
CRJAZ1093I Service failed to activate.
CRJAZ0520I Failed to create the connection pool.
The server is running - The connectionPoolService is locked by another Process.
2 answers
https://www.ibm.com/support/knowledgecenter/SSYMRC_5.0.2/com.ibm.jazz.install.doc/topics/r_repotools_reindex.html
The index error that you got is usually caused by restoring a database backup without the associated index backup.
Comments
But in my case i am using db connections via WebSphere Application server Data Sources , means i am creating J2EE connection in JTS Setup.
If i stop the server repotools will not be able to communicate with the DB.
I have also found this on forum : https://jazz.net/forum/questions/114234/crjaz0527i-failed-to-lookup-datasource-when-running-repotools-with-a-j2ee-data-source
In this case, you will have to follow the workaround mentioned in the other post. Still, you need to stop the server for repotools to run.
Even i also encountered the below error in the RM Diagnostics Page after the upgrade from 6.0.6 to 6.0.6.1
Running the repotools-rm -reindex all against the RM application resolved the issue.
https://jazz.net/help-dev/clm/ <wbr> index.jsp?topic=%2Fcom.ibm.jaz <wbr> z.install.doc%2Ftopics%2Fr_rep <wbr> otools_reindex.html