Flashes (Alerts)
Abstract
Report Builder in Engineering Lifecycle Manager 7.x supports a new feature to report on Link Validity using Lifecycle Query Engine. This feature doesn't exist in earlier releases.
A defect in the upgrade process prevent reports working properly for Link Validity data migrated from an earlier release.
If you intend to use this feature in 7.x, we strongly advise patching this defect before proceeding with the upgrade.
Content
The following defect is known to impact reports against Link Validity Data when upgrading from 6.x to 7.x:
You will be impacted by this defect if all the following are true:
1) You have upgraded RM (DOORS Next) from 6.x to 7.x
2) There are links involving RM requirements that also have validity assertions
3) Report builder queries reporting on the validity status of the links on RM requirements are used after upgrade (it doesn't matter when or how the report was created).
2) There are links involving RM requirements that also have validity assertions
3) Report builder queries reporting on the validity status of the links on RM requirements are used after upgrade (it doesn't matter when or how the report was created).
Run this SQL query to check if you are might be impacted by this defect:
##### ORACLE ######
SELECT COUNT(version) FROM JTSUSER.VLDTMDL_CNTNT_HSH_T_VRSN_MPPNG
WHERE version LIKE '%versionedResources%';
WHERE version LIKE '%versionedResources%';
#################
NOTE: Please specify the correct user or schema name for JTSUSER in the ORACLE query above.
######## DB2 ######
SELECT COUNT(version)
FROM VALIDITYMODEL.CONTENT_HASH_TO_VERSION_MAPPING
WHERE version LIKE '%versionedResources%';
FROM VALIDITYMODEL.CONTENT_HASH_TO_VERSION_MAPPING
WHERE version LIKE '%versionedResources%';
#################
When running the SQL query please login to the correct JTS database using the same credentials as JTS uses for the connection.
If you are using a multi-JTS configuration, you will need to identify the correct JTS server database to query as follows:
Check the value of the advanced admin property, Shared Validity Provider URL.
If this specifies a JTS server, then you should query the database used by that JTS server.
If no URL is specified, then query the database of the JTS that RM is registered with.
If the query returns a nonzero number and you might use report builder and LQE in the future for queries involving link validity data, then you would be affected by this defect.
This defect is fixed in DOORS Next 7.0.2 and will be backported in iFixes for both 7.0.1 and 7.0 shortly.
Check the ELM maintenance schedule for further details.
If you have already upgraded DOORS Next from 6.x to 7.x without applying this patch then Report builder queries will not report the correct link validity status for associated RM requirements. Please contact IBM Support if you are impacted. You may use the same SQL query above to check if you are impacted after the upgrade is complete.
If you have not yet upgraded from DOORS Next 6.x to 7.x then you are advised to wait for this defect to be patched before proceeding.
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSTU9C","label":"Jazz Reporting Service"},"ARM Category":[{"code":"a8m0z000000CbMyAAK","label":"Jazz Reporting Service->Report Builder->LQE DataSource Based"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.0;7.0.1","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Product Synonym
LQE;ELM;DNG
Was this topic helpful?
Document Information
Modified date:
07 July 2020
UID
ibm16243870