An attempt to import a document that is marked for deletion in the destination domain
returns the uniqueness constraint error DB_NOT_UNIQUE.
The contents of recovery bins are ignored by
FileNet® Deployment Manager. If you
are importing a document that was marked for deletion on the destination domain, the uniqueness
constraint error
DB_NOT_UNIQUE is returned. If an error occurs, take one of the
following actions to resolve the problem:
- Remove the document that is in the recovery bin from the export manifest and run the import
procedure again.
- Remove the document from the recovery bin by reinstating the document and running the import
procedure again. This action causes the document at the destination to be updated by the import
process.
- Delete the document from the recovery bin and import the document again.