It's all about the answers!

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

×6,020
×4,304
×864

question asked: Mar 31 '14, 10:27 a.m.
question was seen: 4,280 times
last updated: Aug 19 '14, 8:53 a.m.

Related questions

CRJZS5806E while reindexing design manager DB

1
Tomas Juknevicius (41●1●3) | asked Mar 31 '14, 10:27 a.m.
edited Mar 31 '14, 10:29 a.m.
 Hello,
I am having a problem with rebuilding design manager indices.
I have probably shut down the server incorrectly and now Rhapsody does not allow me to connect to DM (giving error CRJZS5787E). I've looked it up and according https://jazz.net/library/article/1160 it seems that my indices are corrupt.
Per that recommendation I have tried to reindex (stop the server, then use command "repotools-XXX.bat -reindex").
The jts, vvc, qm and ccm reindexed OK (in that order), but the "repotools-dm.bat -reindex" starts normally, but later on finishes with the following error:
CRJZS5652I Indexing services are being shut down ...
CRJZS5806E An unexpected problem occurred while processing a transactional model read activity
CRJZS5651I Indexing services finished shutting down in 4736 ms
How can I fix that? Googling for CRJZS5806E did not give me any useful pointers.

Any help would be greatly appreciated. Thanks in advance.
--
Tomas J.


Comments
Ralph Schoon commented Apr 02 '14, 5:34 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

I would check if there are more errors in the log files (in the .log file in the .metadata folder in the workspace folder) and in the server logs (server/logs folder).
I would check if there are errors in the Database e.g. if you use an enterprise database.

Otherwise, I would contact customer support. I was unable to find anything related to this error message, so I am not sure what is going on.

Accepted answer

1
permanent link
Tomas Juknevicius (41●1●3) | answered Apr 02 '14, 6:34 a.m.
 Hello Ralph,
I managed to fix it myself. Just nuked (deleted) the index  directory completely and then the reindexing command ran without a hitch.

BTW no this was not enterprise DB - just a simple demo/trial install of DM running on top of the built in Derby DB.

Sincerely,


Ralph Schoon selected this answer as the correct answer
Comments
Ralph Schoon commented Apr 02 '14, 6:44 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Glad you were able to fix it. Re-indexing is a bit confusing, because there are several indexes and only one is on the DB.

Alastair Beadle commented Aug 19 '14, 8:53 a.m.

Excellent - fixed my problem too.
In my case I was wondering initially what you meant by deleting the index directory - so for reference I stopped the server, deleted all files under:

...server/conf/rm/indices
and then reran the reindex command from the server directory, in my case:
repotools-rm -reindex all
Then restarted the server.

(obviously change rm as applicable if the problem is with another app).

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.