Why can't I search artifcats in RM?
David Sakoda (21●2●6)
| asked Jun 06 '16, 4:14 p.m.
edited Jun 07 '16, 1:01 a.m. by Geoffrey Clemm (30.1k●3●30●35)
I upgrade from 5.0.2 to 6.0.2.
I'm missing a bunch of collections and modules
I cannot create a new artifact, it hangs when trying to load artifact type.
I cannot search Artifacts in quick search.
I cannot browse artifact
But if i go to CM and find a workitem link with the RM link, it appears. so they're there somewhere.
Defect links from a work item in CM:
sorry, i don't have enough reps to upload a screenshot. i'll try and post them somwhere
I already tried reindexing RM db with repotools-jts.bat
2016-06-05 23:40:09,910 CRJZS5347I Indexing: resumed
2016-06-05 23:40:42,567 CRJZS5586I Reindexing : Finished processing "triple history" indices for private applications in 141 ms
2016-06-05 23:40:51,739 CRJZS5586I Reindexing : Finished processing "text history" indices for private applications in 16 ms
2016-06-05 23:40:56,317 CRJZS5579I Reindexing : Deleting "text live" indices for private applications ...
2016-06-05 23:40:57,177 CRJZS5579I Reindexing : Deleting "triple live" indices for private applications ...
2016-06-05 23:45:40,433 CRJZS0434W The root services document could not be fetched after 3 attempts.
2016-06-05 23:45:46,574 CRJZS0434W The root services document could not be fetched after 3 attempts.
2016-06-05 23:45:52,746 CRJZS0434W The root services document could not be fetched after 3 attempts.
2016-06-05 23:56:00,962 CRJZS0434W The root services document could not be fetched after 3 attempts.
2016-06-05 23:56:07,197 CRJZS0434W The root services document could not be fetched after 3 attempts.
2016-06-05 23:56:13,369 CRJZS0434W The root services document could not be fetched after 3 attempts.
2016-06-06 00:06:21,601 CRJZS0434W The root services document could not be fetched after 3 attempts.
2016-06-06 00:06:27,757 CRJZS0434W The root services document could not be fetched after 3 attempts.
2016-06-06 00:06:33,961 CRJZS0434W The root services document could not be fetched after 3 attempts.
2016-06-06 00:16:42,161 CRJZS0434W The root services document could not be fetched after 3 attempts.
2016-06-06 00:16:48,333 CRJZS0434W The root services document could not be fetched after 3 attempts.
2016-06-06 00:16:54,505 CRJZS0434W The root services document could not be fetched after 3 attempts.
2016-06-06 00:26:05,971 CRJZS5586I Reindexing : Finished processing "text live" indices for private applications in 2709654 ms
2016-06-06 00:26:06,252 CRJZS5586I Reindexing : Finished processing "triple live" indices for private applications in 2709075 ms
2016-06-06 00:26:24,768 CRJZS6109I Resources from database //db-server:50000/RM:user=xxxxxxxx;password=xxxxxxxx; were reindexed successfully.
2016-06-06 00:26:24,768 The user "ADMIN" has logged out of the database "/db-server:50000/RM:user=xxxxxxxx;password=xxxxxxxx;".
2016-06-06 00:26:25,237 CRJZS5652I Indexing services are being shut down ...
2016-06-06 00:26:32,174 CRJZS5651I Indexing services finished shutting down in 6937 ms
|
2 answers
There are some known issues with RM upgraded to 6.0.2. Please contact Support for more details.
|
|
Thanks Donald. I was getting so many different errors (db and app) I just redid the upgrade from scratch and it's working. The entire upgrade was large:
RTC 4.0.3 -> 5.0.2 -> 6.0.2
-for this step, i did apply all the ifixes for 5.0.2 that may have helped this second round.
DB2 9.7 -> 10.5
Win Serv 2k8 -> 2k12
Tomcat 6 -> 7
All is well now. thank you!
|
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.
Comments
here is a work item screen shot from CM showing the rm artifact link