Key considerations and known issues when upgrading to ELM 7.2.0 (LQE relational store)

Release Notes

Abstract

This technote outlines the key considerations, limitations, and known issues associated with upgrading to IBM Engineering Lifecycle Management (ELM) 7.2.0, specifically focusing on the transition from the deprecated LQE Jena store to the required LQE relational store (LQE rs). Beginning in ELM 7.2.0, Jena-based storage is no longer supported, and organizations must fully migrate and validate all Jena-dependent reports using ELM 7.1.0 SR1 or later before upgrading. The document highlights performance variability observed in LQE rs, including regressions linked to complex queries, heavy enumeration usage, and the introduction of a stricter SQL parser designed for improved security but with potential performance impacts. It also summarizes the planned roadmap of fixes in upcoming 7.2.x and 7.3 releases and provides guidance on upgrade readiness across different customer scenarios. Customers already using LQE rs successfully may proceed with the upgrade, while those still dependent on Jena or experiencing LQE rs performance issues are advised to delay migration until further enhancements are delivered.

Content

Applies to: IBM Engineering Lifecycle Management (ELM) 7.2.0
Component: Report Builder (JRS)

Summary

Starting with ELM 7.2.0, LQE Jena-based storage is no longer supported. This release supports only the LQE relational store (LQE rs). If you are using LQE Jena in earlier versions, you must migrate your reports and usage to LQE rs before upgrading to ELM 7.2.0.

Important: Before upgrading to ELM 7.2.0, you must first upgrade to ELM 7.1.0 SR1 (or any later 7.1.0 iFix) to complete the migration and validation of your reports.

This technote documents the known limitations, performance considerations, and migration constraints identified in the ELM 7.2.0 release to help you assess readiness before upgrading.

Scope

This technote applies to the following upgrade paths:

Scenario	Upgrade Readiness	Notes
New customers (no existing LQE Jena reports)	✔ Recommended	You can proceed directly to the ELM 7.2 with LQE rs.
Existing customers using LQE rs successfully	✔ Recommended	Ensure that all reports execute without performance issues
Existing customers still using LQE Jena or facing LQE rs performance issues	⚠ Not recommended at this time	Stay on the ELM 7.1.0 (LQE Jena + LQE rs coexistence) until known issues are resolved

Key limitations and considerations

1. Mandatory migration from LQE Jena

LQE Jena is no longer supported in ELM 7.2.0. You must migrate all reports that depend on LQE Jena to the LQE relational store (LQE rs) before upgrading. Validate the migrated reports to ensure they run as expected.

Note: If you cannot complete migration or validation successfully, continue using ELM 7.1.0.

2. Performance variability with LQE rs reports

Performance regressions have been observed under certain query patterns when executing in ELM 7.2.0, especially compared to prior LQE rs releases (e.g., ELM 7.1.0 RC1).

3. Query structures with high enumeration usage

Queries involving multiple enumeration fields (2–3+) and large-value cardinality might result in severe slowdowns or timeouts.

Performance enhancement work for this problem is expected in the ELM 7.2.0 SR1 (Q2/Q3 2026) release and continues into ELM 7.3.0.

4. New SQL parser behavior

In ELM 7.2.0, a new secure SQL parser replaces the former one to address vulnerabilities, including unrestricted access and potential SQL injection risk paths.

While this brings required security compliance, it also has the following impacts:

Applies stricter version and syntax constraints
Possible changes in query execution paths
Some queries might run slower than in previous releases.

This parser change is also backported to ELM 7.0.3-iFix019 and ELM 7.1.0-iFix006, you may see similar behavior ahead of ELM 7.2.0.

Future fixes and roadmap

Release	Expected Improvements
ELM 7.2 GA (Current)	Usable for customers with validated LQE rs reports
Q1 2026 Fix Pack	Key performance fixes for SQL parser and enumeration-related queries
ELM 7.2 SR1 (Q2/Q3 2026)	Schema optimization and further query optimization

Recommendations

If you have no LQE Jena dependencies and your LQE rs reports perform well, you can upgrade to ELM 7.2.0.
If you rely on LQE Jena or have slow LQE rs reports, defer the upgrade and stay on ELM 7.1.0 until fixes are available.
Additional validation of report performance is strongly recommended before committing production workloads.

What to do next

If you are experiencing the following conditions during evaluation or upgrade preparation, share your feedback with IBM support:

LQE rs performance degradation
SQL parser regression scenarios
Meta-model refresh issues that cannot be reproduced internally

This information will help focus on future optimizations.

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSTU9C","label":"Jazz Reporting Service"},"ARM Category":[{"code":"a8m0z000000CbLWAA0","label":"Jazz Reporting Service"},{"code":"a8m0z000000CbLbAAK","label":"Jazz Reporting Service-\u003ELifecycle Query Engine"},{"code":"a8m3p0000008uFKAAY","label":"Jazz Reporting Service-\u003EPerformance"},{"code":"a8m0z000000CbLvAAK","label":"Jazz Reporting Service-\u003EReport Builder"},{"code":"a8m0z000000bpT8AAI","label":"Jazz Reporting Service-\u003EReport Builder-\u003EPerformance"},{"code":"a8m0z000000CbM5AAK","label":"Jazz Reporting Service-\u003EUpgrade"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"and future releases;7.1.0"}]

Tips