It's all about the answers!

Ask a question

How to perform a reindex for RELM database in LQE?


Pritesh Patel (12246) | asked Dec 17 '13, 8:59 p.m.
JAZZ DEVELOPER
edited Dec 03 '17, 6:11 p.m. by Fariz Saracevic (779613)

We have a client that is facing some "RELM TST Datasource indexing failures with Rollback detected errors". As a result of these, they have been advised to perform a REINDEX.

Does anyone have a documentation link or steps to perform a REINDEX?


Comments
Krzysztof Kaźmierczyk commented Dec 18 '13, 4:10 a.m.

Hi Pritesh,
We need a bit more information regarding your environment:
1. Where do you see the error message mentioned? Could you provide screen snapshot and error in the log?
2. What is the database Vendor?

Accepted answer


permanent link
John Carolan (71616) | answered Jan 08 '14, 11:27 a.m.
Just in case this crops up again... you need to edit the data source that you want to reindex in LQE, so typically that will be https://servername:9443/lqe/web and select Data Sources from the left pane.

Click on the pencil icon beside the data source to rebuild, and that will open its properties.
There are 3 options available: Reindex / Remove / Pause Indexing.
In this case, the first option would attempt to reindex the data source.

I hope that helps,

John
Pritesh Patel selected this answer as the correct answer

Comments
1
Pritesh Patel commented Jan 08 '14, 11:39 a.m.
JAZZ DEVELOPER

Thanks John, this is just what I was looking for. I also got the following:

Reindexing a data source :

1) Navigate to the admin UI (http://[server]:[port]/lqe/web/admin
2) select the data sources link
3) locate the data source that is a problem 
4) select the reindex action from the actions (note: depending on amount of data and data source response time(s) this can take a while)
  4a) edit the data source
  4b) select the reindex link

One other answer



permanent link
Pritesh Patel (12246) | answered Dec 23 '13, 8:52 p.m.
JAZZ DEVELOPER
Hi Krzysztof,

Thanks for your response. Here are some additional details:

a. OS for the severs:
Linux 2.6.18-238.el5

b. Focal Point:
6.5.2.3 Build ID FP6523-I20130618_0917

c. Database system and version:
Oracle Database 11g Release 11.1.0.0.0

d. App server (e.g. Websphere or Tomcat):
Apache Tomcat/6.0.35

The client sees the following exception in the Show Details screen on RELM GUI.

CRLQE0489E Rollback detected. Data source may have been rolled back.
Encountered an entry older than the last processed. Last Processed:
{Kind=CREATION; Identifier=urn:com.qctfp-tst.qualcomm.com:-1:2013-11-
22T00:14:27.576Z:1010127; Order=1385079267576; Changed=
https://qctfp-

tst.qualcomm.
com/fp/resources/workspaces/121/modules/327/elements/1010127}.
Encountered: {Kind=MODIFICATION; Identifier=urn:com.qctfp-tst.qualcomm.
com:-1:2013-11-22T00:10:37.761Z:1009834; Order=1385079037761;
Changed=
https://qctfp-tst.qualcomm.

com/fp/resources/workspaces/121/members/1009834}
com.ibm.team.jis.lqe.espresso.trsparser.RollbackDetectedException:
CRLQE0489E Rollback detected. Data source may have been rolled back.
Encountered an entry older than the last processed. Last Processed:
{Kind=CREATION; Identifier=urn:com.qctfp-tst.qualcomm.com:-1:2013-11-
22T00:14:27.576Z:1010127; Order=1385079267576; Changed=
https://qctfp-

tst.qualcomm.
com/fp/resources/workspaces/121/modules/327/elements/1010127}.
Encountered: {Kind=MODIFICATION; Identifier=urn:com.qctfp-tst.qualcomm.
com:-1:2013-11-22T00:10:37.761Z:1009834; Order=1385079037761;
Changed=
https://qctfp-tst.qualcomm.

com/fp/resources/workspaces/121/members/1009834}
 at com.ibm.team.jis.lqe.espresso.trsparser.TRS$ChangeLogHandle.
getChangeEntries(TRS.java:277)
 at com.ibm.team.jis.lqe.espresso.tasks.ChangeLogTask.call
(ChangeLogTask.java:152)
 at com.ibm.team.jis.lqe.espresso.tasks.ChangeLogTask.call
(ChangeLogTask.java:69)
 at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
 at java.util.concurrent.FutureTask.run(FutureTask.java:138)
 at java.util.concurrent.
ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301
(ScheduledThreadPoolExecutor.java:98)
 at java.util.concurrent.
ScheduledThreadPoolExecutor$ScheduledFutureTask.run
(ScheduledThreadPoolExecutor.java:206)
 at java.util.concurrent.ThreadPoolExecutor$Worker.runTask
(ThreadPoolExecutor.java:886)
 at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:908)
 at java.lang.Thread.run(Thread.java:736)

I cannot attach the image here but will send you an email.


The client was advised of the following steps:

Steps to copy data from the production environment to the non-production environment.
1) pause the RELM data source indexing.
2) Stop the Focal point services.
3) Complete the DB refresh on Focal point.
4) Bring up the Focal Point services.
5) Resume the RELM data source indexing. - if a rollback error is
encountered, a REINDEX will be required.

With regards to the above context, how can the cient perform a REINDEX in RELM as pointed out in step 5.

Many thanks,
Pritesh...




Comments
Krzysztof Kaźmierczyk commented Dec 30 '13, 5:05 a.m.

Hi Prmiesh,
Who recommended these steps for the client? Could the client ask the person who recommended that steps to elaboration them if you don't understand them?

Your answer


Register or to post your answer.