IBM Support

Cannot upgrade user database after renaming a record type in ClearQuest

Troubleshooting


Problem

There is a problem with not being able to upgrade a user database after renaming a record types that has had packages applied to it using IBM Rational ClearQuest.

Symptom

When upgrading a ClearQuest database, the user is presented with the error:



    There is reference to an Object that doesn't exist
    Object Type: Entity
    Object: Defect

    The error was detected at ClearQuest Core:admetadatamgr.cpp:1135"

Resolving The Problem

This package upgrade issue was addressed as a defect in APAR PQ88070, and resolved in the 7.0.0 release. If you have changed the name of an record type (entity) that is referenced by a package query, ClearQuest 7.x will attempt to locate that entity by its name in the back-end. This second look-up will work for all entity types that are shipped as part of ClearQuest out-of-the-box schemas.

For more information on Naming Restrictions in ClearQuest 7.x, search on "Naming Restrictions" in the Rational ClearQuest Knowledge Center.


For ClearQuest versions prior to 7.x:

Renaming Record Types, breaks links to applied packages, as documented in the release notes. The work around is to check out the schema, revert to the original entity name, check in the schema, and upgrade the user database.

The ClearQuest 2003.06.13 release notes (GI11-4670-03) describe the restrictions on renaming a record type in Chapter 2. The following information can be found under restrictions and guidelines for using Rational ClearQuest:


    Renaming record types

    No entity to which a package has been previously applied should be renamed. Otherwise, attempts to upgrade the schema to a higher version of the package or to upgrade a user database will fail.

    For example, the upgrade fails with a returned error message if you do the following:

    1. Create SAMPL database using the Defect Tracking schema.
    2. Check out the schema.
    3. Rename the record type Defect to DefectA.
    4. Check in the new schema.
    5. Upgrade the user database.

    The work around is to check out the schema, revert to the original entity name, check in the schema, and upgrade the user database.

[{"Product":{"code":"SSSH5A","label":"Rational ClearQuest"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Designer - Packages","Platform":[{"code":"PF033","label":"Windows"}],"Version":"7.0;7.0.0.1;7.0.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
16 June 2018

UID

swg21202987

Page Feedback