UNDER CONSTRUCTION : Troubleshooting DOORS Next 7.0.x to 7.1/7.2 Upgrades

This article is to help troubleshoot ELM upgrades from V7.0.x to V7.1 or V7.2 and is a companion to Planning for upgrade to ELM 7.1

The importance of upgrade testing:

It is imperative that you test the upgrade:

• This is important to detect any data issues and will also provide you with accurate upgrade times.
• Use a staging area where the hardware is comparable with your production server.
• Testing with a copy of your production data is ideal Setting up a test staging environment with production data. If that is not possible use data as comparable to production as possible.
• Take accurate timings of the pre-upgrade tasks, upgrade tasks and post-upgrade tasks.

Use latest IFixes:

IBM recommend that you upgrade using the latest iFixes available for the release you are upgrading from/to.

If this is not possible then we highly recommend that you check the list of known issues that are fixed in the later Interim fixes to see if any could affect your upgrade or affect your users using the tool post upgrade.

• Interim fixes for Engineering Lifecycle Management 7.1
• Interim fixes for Engineering Lifecycle Management 7.2

The list shows the Known issues by Product and Component/area affected.

Critical Notes for Customers (Must Read):

Product LQE/RS

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

Known issues:

Product ETM

OSLC Migration Task

Problem: OSLC Migration Task performance is poor, it is running for days and shows no sign of completing.

What is OSLC migration:

OSLC migration is a background process that runs after an upgraded Engineering Test Management (ETM) server is started. The migration manages OSLC Migrators, which run a set of tasks on specific artifact types that publishes delete and create events in the Tracked Resource Set 2 (TRS2) feed for the artifacts that require them. The execution is asynchronous and does not prevent the server from working or users from performing normal activities (for example, creating or modifying test plans, test cases, etc.) while the migration is running.

Impact: Some features might not be displayed in Jazz Reporting Service until the migration is finished and LQE is up-to-date.

For example, ETM 7.0.3 / 7.1 introduced the advanced property mentioned in the below screenshot to include the archived approval groups to the REST and OSLC APIs, PDF, and JRS Reports.

The property is available under ETM Administration > Advanced Property.

Post upgrade to 7.0.3/7.1, one of the OSLC Migrators would update the archived approval details in the existing artifact schema. If the property is enabled before the task completes, the archived approvals will be visible in the report for only those artifacts which are updated / migrated.

In summary, while the task is in progress, the existing reports are expected to work the same way as before upgrade.

How to monitor the progress of OSLC Migration task?
Administrators can use the OSLC Migration Status page to monitor. The status page is available at the following location: =https://elm.host.name/<qm-context>/oslcMigrationStatus

How to resolve: This may be resource or database related and the time needed depends on the amount of data to be migrated post upgrade:

• Run the Database Must Gather and prove :
  • Oracle: Must-gather information for diagnosing long-running SQL statements on Oracle
    • Also Provide an AWR report for review.
  • DB2: Must-gather information for diagnosing long-running SQL statements on DB2
• Contact IBM Support for assistance.

External links:

• IBM

Additional contributors: TWikiUser, TWikiUser