Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

The "triple live" index for private applications is ahead of the database (2013-02-23T16:06:07.334Z), shut down the server and run "repotools-jazz -reindex" to recover. The "text live" index for private applications is ahead of the database (2013-02-23T

We just restored one of our CLM instances onto our test server.  In the diagnostics sections of jts/admin, we are now getting

ERRORS:   The "triple live" index for private applications is ahead of the database (2013-02-23T16:06:07.334Z), shut down the server and run "repotools-jazz -reindex" to recover.   The "text live" index for private applications is ahead of the database (2013-02-23T16:06:07.334Z), shut down the server and run "repotools-jazz -reindex" to recover.

After running repotools-jazz.sh -reindex, we are still getting errors.  It seems like the reindex isn't working.  Also, every time we run "repotools-jazz.sh -reindex" we keep getting a pair these messages for "text live" and "triple live".  We now have 7 pairs of these messages after running "repotools-jazz -reindex" 7 times.  Any ideas why this is happening ?


2013-03-01 10:02:57,686 CRJZS5348I Indexing: resuming ...
2013-03-01 10:02:58,771 CRJZS5347I Indexing: resumed
2013-03-01 10:03:01,333 CRJZS5579I Reindexing : Deleting "text live" indices for private applications ...
2013-03-01 10:03:01,970 CRJZS5586I Reindexing : Finished processing "text live" indices for private applications in 640 ms
2013-03-01 10:03:01,979 CRJZS5579I Reindexing : Deleting "text live" indices for private applications ...
2013-03-01 10:03:02,391 CRJZS5586I Reindexing : Finished processing "text live" indices for private applications in 416 ms
2013-03-01 10:03:02,399 CRJZS5579I Reindexing : Deleting "text live" indices for private applications ...
2013-03-01 10:03:02,928 CRJZS5586I Reindexing : Finished processing "text live" indices for private applications in 532 ms
2013-03-01 10:03:02,936 CRJZS5579I Reindexing : Deleting "text live" indices for private applications ...
2013-03-01 10:03:03,394 CRJZS5586I Reindexing : Finished processing "text live" indices for private applications in 461 ms
2013-03-01 10:03:03,404 CRJZS5579I Reindexing : Deleting "text live" indices for private applications ...
2013-03-01 10:03:03,778 CRJZS5586I Reindexing : Finished processing "text live" indices for private applications in 378 ms
2013-03-01 10:03:03,785 CRJZS5579I Reindexing : Deleting "text live" indices for private applications ...
2013-03-01 10:03:04,223 CRJZS5586I Reindexing : Finished processing "text live" indices for private applications in 441 ms
2013-03-01 10:03:04,229 CRJZS5579I Reindexing : Deleting "text live" indices for private applications ...
2013-03-01 10:03:04,544 CRJZS5586I Reindexing : Finished processing "text live" indices for private applications in 316 ms
2013-03-01 10:03:05,585 CRJZS5579I Reindexing : Deleting "triple live" indices for private applications ...
2013-03-01 10:03:06,665 CRJZS5586I Reindexing : Finished processing "triple live" indices for private applications in 1082 ms
2013-03-01 10:03:06,673 CRJZS5579I Reindexing : Deleting "triple live" indices for private applications ...
2013-03-01 10:03:07,582 CRJZS5586I Reindexing : Finished processing "triple live" indices for private applications in 912 ms
2013-03-01 10:03:07,589 CRJZS5579I Reindexing : Deleting "triple live" indices for private applications ...
2013-03-01 10:03:08,389 CRJZS5586I Reindexing : Finished processing "triple live" indices for private applications in 802 ms
2013-03-01 10:03:08,395 CRJZS5579I Reindexing : Deleting "triple live" indices for private applications ...
2013-03-01 10:03:09,070 CRJZS5586I Reindexing : Finished processing "triple live" indices for private applications in 677 ms
2013-03-01 10:03:09,077 CRJZS5579I Reindexing : Deleting "triple live" indices for private applications ...
2013-03-01 10:03:09,732 CRJZS5586I Reindexing : Finished processing "triple live" indices for private applications in 657 ms
2013-03-01 10:03:09,739 CRJZS5579I Reindexing : Deleting "triple live" indices for private applications ...
2013-03-01 10:03:10,294 CRJZS5586I Reindexing : Finished processing "triple live" indices for private applications in 558 ms
2013-03-01 10:03:10,300 CRJZS5579I Reindexing : Deleting "triple live" indices for private applications ...
2013-03-01 10:03:10,898 CRJZS5586I Reindexing : Finished processing "triple live" indices for private applications in 600 ms
2013-03-01 10:03:11,270 The user "ADMIN" has logged out of the database "//hostname:60000/JAZZ:user=xxxxxxxx;password=xxxxxxxx;".
2013-03-01 10:03:11,741 CRJZS5652I Indexing services are being shut down ...
2013-03-01 10:03:12,451 CRJZS5651I Indexing services finished shutting down in 710 ms

0 votes

Comments

Database and RTC on same machine/vm/lpar ?  If not are the clocks in decent agreement ?

1 vote

Jeff
What version of CLM are you running? I have seen some issues reported in the Jazz Foundation project with this message. Some times reindex has gotten rid of the message, sometimes there has been a code fix, and sometimes it is a matter of this:  The original warning is supposed to be issued in the event an administrator did restore an older DB backup, but forgot to restore matching indexes (in which case the index is effectively ahead of the DB, and need to be recreated).

Have you tried a repotools-jazz -reindex -all?

When you did the restore, did you bring over the indices as well? The indices are located in the server\conf* directories.


Be the first one to answer this question!

Register or log in 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.

Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 7,495

Question asked: Mar 01 '13, 1:58 p.m.

Question was seen: 5,160 times

Last updated: Mar 04 '13, 10:35 a.m.

Confirmation Cancel Confirm