It's all about the answers!

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

×6,037
×5,941

question asked: Sep 02 '15, 7:32 a.m.
question was seen: 3,748 times
last updated: Dec 16 '15, 1:15 a.m.

Related questions

After the server renaming RM diagnostics got JFS index has a warning

0
Kanagasabapathi R (17●3●14) | asked Sep 02 '15, 7:32 a.m.
Hello

I had renamed the server from 5.0.2 to a staging environment after the successful renaming found a JFS Index warning in RM application diagnostics page with:

WARNINGS:
   CRJZS5763W The indexing backlog of the "triple history" indexer for private applications is high. As a result, the server might run slowly.
   CRJZS5763W The indexing backlog of the "text history" indexer for private applications is high. As a result, the server might run slowly.

Can anyone help here ?

Thanks.
Saba

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Diane Everitt (278●3●5) | answered Sep 02 '15, 12:39 p.m.

Hello Saba,

Did you try running the reindex all command? 

http://www.ibm.com/support/knowledgecenter/SSYMRC_5.0.2/com.ibm.jazz.install.doc/topics/r_repotools_reindex.html

I hope this helps.

Regards,

Diane

0
permanent link
anoop mc (748●11●200●221) | answered Dec 16 '15, 1:15 a.m.
 Hi,

We have recieved a similar error after migrating the application server from Apache Tomcat to WAS 8.5.5.7.

The end-user were -  generating baselines. The module baseline became inaccessible after creation.

Workaround:    Restarting the server fixed the issue.

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.