Troubleshooting
Problem
When attempting to import a ReqIF (.reqifz) file exported from Siemens Polarion into IBM Engineering Requirements Management DOORS Next (DNG), the import process fails during the XML schema validation phase. This prevents the synchronization of requirements between the supplier and the client.
Symptom
The DNG import log or console displays a Schema Validation Error similar to the following:
Error Code:cvc-id.2
Message:ID value 'rmf-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' has occurred more than once.
Error Code:cvc-attribute.3
Message:In element 'SPEC-OBJECT', the value of attribute 'IDENTIFIER' does not match its type ID.
The import terminates abruptly, and no requirements are created or updated in the target module.
Cause
The root cause is a Violation of XML Unique ID Constraints.
The Polarion export engine has generated a ReqIF XML file where multiple <SPEC-OBJECT> elements share the exact same IDENTIFIER string.
According to the ReqIF standard and XML Schema definitions, every IDENTIFIER attribute must be globally unique within the document. When DNG detects two objects claiming the same ID, it rejects the file to prevent data corruption or ambiguous linking.
Environment
Source Tool:
Siemens Polarion (ReqIF Export Utility)
Target Tool:
IBM Engineering Requirements Management DOORS Next (DNG)
Diagnosing The Problem
To confirm the duplicates, perform the following steps:
Extract the Archive:
Unzip the .reqifz file to access the raw Requirements.reqif XML.
Inspect the XML:
Use a text editor (for example, VS Code or Notepad++) to search for the specific ID mentioned in the error log.
Verify Duplicates:
Count the occurrences of <SPEC-OBJECT IDENTIFIER="[ID_FROM_ERROR]">. If the count is greater than 1, the file is structurally invalid.
Check Timestamps:
Identify the LAST-CHANGE attribute for each duplicate entry to determine which is the most recent version of the requirement.
Resolving The Problem
Immediate Workaround (Automated Fix)
Identify all SPEC-OBJECT elements with clashing IDs.
1. Compare the LAST-CHANGE timestamps.
2. Keep the most recent ID as-is.
3. Append a suffix (for example, -OLD-0) to the IDENTIFIER of the earlier versions.
4. Ensure the output file maintains UTF-8 (No BOM) encoding and UNIX (LF) line endings, or DNG may reject the file based on encoding mismatches.
Permanent Resolution (Supplier Action)
Notify Supplier:
Provide the list of the 5 specific conflicting IDs to the Polarion technical team.
Review Export Configuration:
The supplier must investigate why their export utility is including redundant or historical versions of the same object in a single export package.
Update Export Logic:
Ensure that the export process performs a "latest-only" filter or generates unique UUIDs for every distinct entry in the ReqIF manifest.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
31 March 2026
UID
ibm17267274