Skip to content
Go to Customer Portal
  • There are no suggestions because the search field is empty.

OPA publish fails with an IX_XDS_ENTITY unique-key violation on XDS_DOCUMENT

An OPA project may fail to publish with an IX_XDS_ENTITY unique-key violation on XDS_DOCUMENT. 

 Symptoms
  • Project publishing fails with an IX_XDS_ENTITY unique-key violation on XDS_DOCUMENT.
  • The related error reports that a document of type Case Management Event already exists at a lifecycle/case-model location.
  • In the reported case, the document was identified as Event (14).
Cause

Not confirmed. OpenText requested investigation of potential duplicate activity names or document-name conflicts and details of recent lifecycle changes. These were investigative leads, not a verified diagnosis.

Troubleshooting already performed

The following sequence was performed in the reported case:

  1. Run Clean Build Output.
  2. Synchronize the project.
  3. Validate the workspace.
  4. Attempt to publish the project again.

Observed result: Publishing still failed with the previously reported error. Do not present this sequence as a confirmed fix.

Additional checks requested by OpenText

The vendor requested the following information and tests; the reviewed activity does not confirm their completion or effectiveness:

  • Confirm whether the project was developed in the same environment and whether it is part of CAP.
  • Determine whether the issue also occurs after synchronizing or rebuilding the project in a new organization.
  • Describe the exact lifecycle changes made before the failure.
  • Check the location named in the error for duplicate activity or document names. If a conflict is found, coordinate any renaming with OpenText.
  • Confirm whether SVN or another version-control system is in use.

SVN/workspace recovery proposal — vendor supervision required

If SVN is in use, OpenText proposed reverting to a previous version, committing it, creating a new workspace synchronized with SVN, validating that workspace, removing the old workspace, and restarting the CAP service container.

Caution: This proposal was not validated as a fix in the reviewed activity. Before attempting it, preserve current work and backups, confirm the intended revision and rollback plan with OpenText, and obtain approval for workspace removal or service interruption. Do not remove the existing workspace before confirming recovery requirements with the vendor.