(r8) Troubleshooting70XTo7XUpgrades < Deployment

Engineering Lifecycle Management Wiki - Deployment
Community information and contribution guidelines
~~EditAttach~~Printable
TWiki > Deployment Web > DeploymentInstallingUpgradingAndMigrating > Troubleshooting70XTo7XUpgrades
Revision 8 - 2026-02-18 - 08:22:46 - WillChatham
<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%">
---+!! Troubleshooting IBM Engineering Lifecycle Management 7.0.x to 7.1/7.2 Upgrades  
%DKGRAY% Authors: Main.WillChatham, Main.BharathRao <br>
Last Updated: February 2026 | Applies to: ELM 7.0.x &#8594; 7.1, 7.2
%ENDCOLOR%</div></sticky>

<!-- Page contents top of page on right hand side in box -->
<sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;">
%TOC{title="Page contents"}%
</div></sticky>

<sticky><div style="margin:15px;"></sticky>

---+ Overview

This article helps troubleshoot ELM upgrades from V7.0.x to V7.1 or V7.2 and is a companion to [[https://www.ibm.com/support/pages/planning-upgrade-elm-71?view=full][Planning for upgrade to ELM 7.1]].

---++ Who Should Use This Guide

   * System administrators planning ELM upgrades
   * Technical teams troubleshooting upgrade issues
   * Anyone experiencing problems during 7.0.x to 7.1/7.2 migration

---+ Pre-Upgrade Checklist

<div style="border: 3px solid #FF6B6B; background-color: #FFE5E5; padding: 15px; margin: 20px 0;">
*%RED% &#9888;&#65039; CRITICAL: Complete These Steps Before Upgrading %ENDCOLOR%*

   1. *Test the upgrade in a staging environment*
   2. *Use latest iFixes for your source and target versions*
   3. *Review product-specific critical notes below*
   4. *Document baseline timings and system state*
</div>

---++ Step 1: Test Your Upgrade

<div style="background-color: #F0F8FF; border-left: 4px solid #4A90E2; padding: 15px; margin: 15px 0;">
*%BLUE% &#127919; UPGRADE TESTING REQUIREMENTS %ENDCOLOR%*

*Why Testing is Critical:*
   * Detects data issues before production impact
   * Provides accurate upgrade timing estimates
   * Validates compatibility with your environment

*Testing Environment Requirements:*
   * Hardware comparable to production (CPU, RAM, disk I/O)
   * Copy of production data (ideal) or comparable dataset
   * Network configuration similar to production

*What to Document:*
   * Pre-upgrade task duration: _____ hours.
   * Upgrade execution time: _____ hours.  
   * Post-upgrade task duration: _____ hours.
   * Any errors or warnings encountered.

*Reference:* [[https://www.ibm.com/docs/en/engineering-lifecycle-management-suite/lifecycle-management/7.1.0?topic=rename-scenario-setting-up-test-staging-environment][Setting up a test staging environment with production data]]
</div>

---++ Step 2: Use Latest iFixes

<div style="background-color: #FFF9E6; border-left: 4px solid #F5A623; padding: 15px; margin: 15px 0;">
*%ORANGE% &#128161; RECOMMENDATION: Latest iFixes %ENDCOLOR%*

IBM recommends upgrading using the latest iFixes for both source and target releases.

*If using older iFixes:* Review the known issues list to identify potential upgrade impacts.

*iFix Documentation:*
   * [[https://www.ibm.com/docs/en/engineering-lifecycle-management-suite/lifecycle-management/7.1.0?topic=system-interim-fixes-engineering-lifecycle-management-71][Interim fixes for ELM 7.1]]
   * [[https://www.ibm.com/docs/en/engineering-lifecycle-management-suite/lifecycle-management/7.2.0?topic=system-interim-fixes-engineering-lifecycle-management-72][Interim fixes for ELM 7.2]]

The lists show known issues organized by Product and Component/area.
</div>

---+ Critical Product-Specific Notes

<div style="border: 3px solid #FF6B6B; background-color: #FFE5E5; padding: 15px; margin: 20px 0;">
*%RED% &#9888;&#65039; MUST READ BEFORE UPGRADING %ENDCOLOR%*

Review the critical notes for products in your environment before proceeding.
</div>

---++ LQE/RS (Lifecycle Query Engine / Relational Store)

<div style="background-color: #FFE5E5; border-left: 4px solid #E74C3C; padding: 15px; margin: 15px 0;">
*%RED% &#9888;&#65039; CRITICAL CONSIDERATIONS %ENDCOLOR%*

*Key Issues and Considerations:*

Review the comprehensive guide before upgrading:
[[https://www.ibm.com/support/pages/key-considerations-and-known-issues-when-upgrading-elm-720-lqe-relational-store][Key considerations and known issues when upgrading to ELM 7.2.0 (LQE relational store)]]

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 document covers:
   * Known limitations.
   * Performance considerations.
   * Migration constraints identified.
</div>

---++ ETM (Engineering Test Management)

<div style="background-color: #E8F5E9; border-left: 4px solid #4CAF50; padding: 15px; margin: 15px 0;">
*%GREEN% &#128161; RECOMMENDED iFix: ETM 7.1 iFix008 or higher %ENDCOLOR%*

*Why iFix008 is Important:*

Contains critical TRS performance fixes that improve:
   * TRS Feed Validation speed
   * LQE indexing performance
   * LDX indexing efficiency

*Reference:* [[https://www.ibm.com/docs/en/engineering-lifecycle-management-suite/lifecycle-management/7.1.0?topic=71-interim-fix-8][Interim Fix 8 details for ELM 7.1]]
</div>

---+ Known Issues and Solutions

---++ ETM: OSLC Migration Task Performance

<div style="background-color: #FFF3CD; border: 2px solid #FFC107; padding: 15px; margin: 20px 0;">
*%ORANGE% &#128295; KNOWN ISSUE %ENDCOLOR%*

---+++ Problem Description

OSLC Migration Task shows poor performance, running for extended periods (days) with no indication of completion.

---+++ Background: What is OSLC Migration?

OSLC migration is a background process that runs after an upgraded ETM server starts:

*Key Characteristics:*
   * Manages OSLC Migrators for specific artifact types
   * Publishes delete and create events in TRS2 feed
   * Runs asynchronously (does not block server operations)
   * Users can continue normal activities during migration

*Typical Duration:* Varies based on data volume and system resources

---+++ Impact on Your System

<div style="background-color: #FFF9E6; padding: 10px; margin: 10px 0;">
*What Works:*
   * &#9989; Server remains fully functional
   * &#9989; Users can create and modify artifacts
   * &#9989; Normal ETM operations continue

*What's Delayed:*
   * &#9888;&#65039; Some JRS features unavailable until completion
   * &#9888;&#65039; Archived approval groups not visible in reports (if enabled)
   * &#9888;&#65039; New features dependent on migration incomplete
</div>

*Example Impact:*

ETM 7.0.3/7.1 introduced an advanced property to include archived approval groups in REST/OSLC APIs, PDF, and JRS Reports:

<img src="%ATTACHURLPATH%/ETMProperty.png" alt="ETM Advanced Property for Archived Approvals" width="1690" height="236" />

*Figure 1:* ETM Advanced Property (Administration > Advanced Property)

*Reference:* [[https://jazz.net/pub/new-noteworthy/etm/7.0.3/7.0.3/index.html#11][ETM 7.0.3 New & Noteworthy]]

Post-upgrade, an OSLC Migrator updates archived approval details in the artifact schema. If the property is enabled before migration completes, archived approvals appear only for migrated artifacts.

*Summary:* Existing reports work as before upgrade while migration is in progress.

---+++ Monitoring Migration Progress

*Status Page Location:*
=https://elm.host.name/<qm-context>/oslcMigrationStatus=

<img src="%ATTACHURLPATH%/oslcMigrationStatus.png" alt="OSLC Migration Status Page" width="1121" height="483" />

*Figure 2:* OSLC Migration Status Page showing progress

*What to Monitor:*
   * Overall completion percentage
   * Individual migrator status
   * Estimated time remaining
   * Any error messages

---+++ Resolution Steps

<div style="background-color: #E3F2FD; border-left: 4px solid #2196F3; padding: 15px; margin: 15px 0;">
*%BLUE% &#128203; TROUBLESHOOTING PROCEDURE %ENDCOLOR%*

*Step 1: Gather Database Diagnostics*

The migration time depends on data volume and database performance. Collect diagnostics:

*For Oracle:*
   1. Run [[https://jazz.net/wiki/bin/view/Deployment/OracleMustGather][Must-gather for long-running SQL statements on Oracle]]
   2. Generate AWR report for the migration period
   3. Document findings

*For DB2:*
   1. Run [[https://jazz.net/wiki/bin/view/Deployment/Db2MustGather][Must-gather for long-running SQL statements on DB2]]
   2. Document findings

*Step 2: Contact IBM Support*

Provide collected diagnostics to IBM Support for analysis.

*When to Escalate:*
   * Migration exceeds expected time-frame for your data volume
   * Status page shows errors
   * Migration appears stalled (no progress for extended period)
   * System performance severely degraded
</div>
</div>

---+ Additional Resources

---++ External Links

   * [[https://www.ibm.com][IBM Support Portal]]
   * [[https://www.ibm.com/docs/en/engineering-lifecycle-management-suite/lifecycle-management/7.1.0][ELM 7.1 Documentation]]
   * [[https://www.ibm.com/docs/en/engineering-lifecycle-management-suite/lifecycle-management/7.2.0][ELM 7.2 Documentation]]

---++ Contributors

*Authors:* Main.WillChatham, Main.BharathRao

*Additional Contributors:

---+ Feedback

<div style="background-color: #F5F5F5; border: 1px solid #CCCCCC; padding: 15px; margin: 20px 0;">
*Was this article helpful?*

Please provide feedback to help us improve this documentation:
   * Contact the authors with suggestions
   * Report issues or corrections
   * Share your upgrade experiences
</div>

<sticky></div></sticky>
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our Terms of Use. Please read the following disclaimer.
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.