r16 - 2021-11-01 - 09:04:31 - PaulEllisYou are here: TWiki >  Deployment Web > DeploymentInstallingUpgradingAndMigrating > UnderstandingDOORSNextSizingsin6X > TroubleshootingDOORSNextUpgrades > DOORSNextUpgradeErrorCodes

DOORS Next 7.x upgrade Warning and Error codesuc.png

Authors: PaulEllis, MarkGoossen
Build basis: DOORS Next 7.x

This page is to explain the warning and error codes returned during the upgrade from DOORS Next Generation 6.x to DOORS Next 7.x.

This page will evolve constantly as new error and warning messages are encountered.

NOTE if you get any error codes shown in the summary at/near the end of migrationOutput.log then you must also check for database errors (in e.g. repotools_rm.log or, for 7.0.2, repotools_rm_error.log) and if any are found then you must resolve these first before (most likely) repeating the upgrade. See here for some assistance with DB2/Oracle errors during upgrade.

Error codes

CRRRS2094E Failure transforming state

This exception has multiple root causes, including:

These are both fixed in 7.0.2 GA, 7.0.1 ifix 1 and 7.0 ifix 4

Warning Codes

CRRRS2092W Unable to identify which folder this artifact belongs in

There are multiple causes for this warning. This is a warning that a folder bookmark could not be found for a resource. If a folder cannot be identified, the 7.x migration will place the artifact into the root folder. The list of issues per components are detailed in the MigrationOutput.log. For example:

 Component: MySystemRequirements(Requirements)  (1 issues) https://myuri.ibm.com/rm/cm/component/_EWJbEbPkbsAhRKeeoBN_Bg
            CRRRS2092W Unable to identify which folder this artifact belongs in
                Explanation: Unable to identify which folder the artifact belongs in. The artifact will not be available in any folder hierarchy.
                Recommendation: Orphan artifacts can be reclaimed using the FolderIntegrityCheck support tool to recover the orphaned artifacts into a LOST AND FOUND folder.
                Issues detected within:
                https://myuri.ibm.com/rm/cm/component/_EWJbEbPkbsAhRKeeoBN_Bg (Severity: Possible Issue)

As this warning message was also seen due to Defect 142084: 0.6 migration: exceptions when migrating requirements due to invalid parent folder. We recommend that you apply 7.0.2 ifix 8, when available.
To confirm that this defect was encountered, inspect the rm_upgrade.log for the following error: Caused by: java.lang.IllegalStateException: Unable to extract UUID from Id folders

If you encounter this issue, please contact IBM Support who will supply you with the Folder Integrity tool; and/or help you identify whether you have encountered defect 142084. This error may have to be fixed before upgrade,if so will have to revert, fix and re-run the upgrade. IBM Support will advise if this is necessary.

You do not have the required privileges for this operation. Missing privilege:create (com.ibm.rrs.team.saveFolder).

If when running the Folder Integrity Tool you encounter the message:

This message is telling us that we need to add Save Folder and Create Artifacts in the project area to our user/role.
a. Allocate permissions to Save Folder and Create Artifacts to your role.
b. If Change Management constraints are set in the stream (see Project Area > Administration > Manage Component and Configurations > Component > Stream > Details) create a change set in the stream
c. Depending on (b), execute the FolderIntegrityCheck tool either against the stream or against ChangeSet choosing the "Reparent Orphaned Artifacts and Folders" option.


CRRRS2096W Skipping binding because invalid state

"The artifact associated with binding may not be visible in the associated module because either the module was missing, the artifact was missing, or the binding was invalid."

This message is listed in DOORS Next some warnings during upgrade to 7.x must not be ignored and need to be investigated due to defect 0.6 migration: Bindings are not upgraded when the associated core artifact is missing the artifact format property in the latest version/revisions.
The CRRRS2096W warning is logged for a number of different reasons, but they all mean that the binding could not be created during upgrade. The reasons include:

  • the binding is missing the module property
  • the bound artifact is missing, this may be because the bound artifact was malformed (we have fixed several cases of this issue. IBM Support will send you an L3 tool, the bindingAndArtifactAnalyzer, which provides more detail on this)
  • the binding points to a bound artifact URI which is not a bound artifact

The original data being unusable can occur during a failed import, for example, via csv import or ReqIF. Prior to 7.0.2 ifix 8, defect 0.6 migration: Bindings are not upgraded when the associated core artifact is missing the artifact format property in the latest version/revisions, meant that upgrade could skip the last version of an artifact, resulting in "missing" data in 7.x when compared with the original data in DOORS Next 6.0.6.x.

If you upgraded prior to 7.0.2 ifix 8, follow the technote to identify if migrationOutput.log reported any of these error types. If any were reported, contact IBM Support, who will send you a tool to validate your data.

CRRRS2097W Skipping the artifact revision because it does not have a format (and is not a binding):

Skipping the artifact revision because it does not have a format (and is not a binding) Explanation: Skipping the artifact revision for artifact because it does not have a format (and is not a binding).

DOORS Next some warnings during upgrade to 7.x must not be ignored and need to be investigated

It is essential that you use the latest ifix when upgrading to DOORS Next 7.x. The minimum release levels that includes defect 141071: 0.6 migration: requirements which are missing an artifact format are not migrated (CRRRS2097W) are:

  • 7.0 iFix012
  • 7.0.1 iFix010
  • 7.0.2 iFix005

If you encounter this error code in the MigrationOutput.log then please contact IBM Support. IBM Support will send an additional validation tool "BindingAndArtifactAnalyzer" to ensure that this data migrated correctly - NOTE this will be run against 7.x rather than before the upgrade, i.e. no need to revert.

The CRRRS2096W and CRRRS2097W errors are still valid even when the latest Ifix is released, and will continue to be seen during upgrade. These will occur when all of the states of an artifact are invalid. 141071: 0.6 migration: requirements which are missing an artifact format are not migrated (CRRRS2097W) addresses an issue where the initial states of an artifact are invalid, and later states are valid.
For example, you could have requirement1 and requirement2:
requirement1.version1 -> invalid
requirement1.version2 -> invalid
requirement1.version3 -> *valid*

and

requirement2.version1 -> invalid
requirement2.version2 -> invalid
requirement2.version3 -> invalid

With the defect fix, we can now upgrade requirement1. With requirement2, you would still see the upgrade warning.

CRRRS2101W None of the states for a version of concept were upgraded. Skipping remaining versions of the concept.

This is stating that the artifact and all its versions in DOORS Next Generation 6.x were incomplete and unusable.
This is likely due to a failed import and the data's state would have been known (as unusable) at the time, but not deleted.

CRRRS2098W Artifact revision content reset because the XHTML/XML was invalid

The primary text or diagram XML is not valid according to the DNG XHTML schema.

CRRRS2102W Last revision for a version of concept were not upgraded. Skipping remaining versions of the concept

An error occurred while upgrading a revision of an artifact version. Subsequent revisions will be skipped.

CRRRS2104W Unable to determine link handle for subject URI

This is no longer in use in 7.0.3.

CRRRS2110W Ignore state due to missing model.

The artifact or link model content either does not exist or cannot be parsed. Subsequent states will be migrated.

CRRRS2112W An attribute definition could not be found. Artifact types and values will be affected.

The attribute definition that is referenced by an artifact type does not exist. The artifact type might have been archived. The artifact type will be migrated without the attribute definition.
If this message is unexpected, check the Component Properties to ensure that the artifact type does not exist.

CRRR2103W Ill-formed URI cannot be set on link

The data within the DOORS Next repository contains non-standard URIs, as defined by the Uniform Resource Identifiers(URI): Generic Syntax, for example: prefixes, or spaces within the URI. See How to identify ill-formed URIs in your data that cause links to break and upgrades to 7.x to fail on how to proceed.

CRRRS2116W Artifact revisions in JFS have inconsistent Wrapper/Text format.

Migrated data will be regularized to format Wrapper. An artifact has a text format, but its predecessor had a wrapper format. The artifact state will be migrated as a wrapper resource.

CRRRS2118W Link Title was truncated

The existing link title was too long and so the title was truncated.

CRRRS2119W Link URI was truncated

Explanation: The existing link URI was too long and so the URI was truncated.

See How to identify ill-formed URIs in your data that cause links to break and upgrades to 7.x to fail on how to proceed.

Related topics: Understanding DOORS Next sizings in ELM 6.x to estimate timings when upgrading to DOORS Next 7.x, Troubleshooting DOORS Next 6.x to 7.x Upgrades

External links:

Additional contributors: WillChatham, Main.Sudarshan

Edit | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r16 < r15 < r14 < r13 < r12 | More topic actions
 
This site is powered by the TWiki collaboration platformCopyright © by the 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.