IBM Support

LQE skipped resources after module configuration change

Troubleshooting


Problem

Lifecycle Query Engine (LQE) may report skipped resources when a DOORS module's configuration is changed from unset to a Global Configuration (GC) stream after objects have been created in the module.

Symptom

LQE shows skipped resources in the following scenario:
 

  1. The project is already added to the Working Set, and the database is not associated with the current
    configuration of a GC stream.
  2. We then add a module and create 3 objects in it.
  3. Entries are added to the trs.change_log table.
  4. Next, we associate the module with the current configuration of a GC stream.
  5. We add 2 more objects to the module.
  6. No entries are added to the trs.change_log table.
  7. As a result, LQE now contains some skipped resources.

Cause

The project is already added to the Working Set, and the module is not associated with the current configuration of a GC stream. So, When three objects were created, those three records also got inserted into the TRS feed. Then, when we associate the module with the current configuration of a GC stream, new modifications won't be inserted in the TRS feed (Known limitation - LQE can not index DOORS data associated with a GC stream).
So, previously added three records appear as skipped resources in LQE.

The root cause is a synchronization issue between the configuration change event and the TRS change log mechanism.

Resolving The Problem

Step 1: Open derby database console.

Run below “derby.run_ij.bat” from below DWA installed location.

C:\Program Files\IBM\Rational\DOORS Web Access\9.7.2.12\derby\scripts\derby.run_ij.bat


Step 2: Take the backup of trs.change_log table and truncate trs.change_log table by using following SQL queries. Update DDMMYYYY with current Date.

  1. CREATE TABLE trs.change_log_backup_DDMMYYYY AS SELECT * FROM trs.change_log WITH NO DATA;
  2. INSERT INTO trs.change_log_backup_DDMMYYYY SELECT * FROM trs.change_log;
  3. DELETE FROM trs.change_log;

Step 3: Trigger trs rebase

  1. Login into DWA in browser.
  2. Update your DWA_HOST in below URL and hit this HTTPS GET request in browser.

    https://DWA_HOST:8443/dwa/rm/trs-rebase

Step 4: Perform the Re-Index of the DOORS data provider from LQE.

Note: The above resolution is only possible with DWA 9.7.2.12.
 

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSKR2T","label":"IBM Engineering Requirements Management DOORS"},"ARM Category":[{"code":"a8m50000000L3D6AAK","label":"ERM DOORS"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7.2"}]

Document Information

Modified date:
30 June 2026

UID

ibm17277522