Duplicate Documents Committed to UCM When Error Occurs After First Document in Batch
(Doc ID 953746.1)
Last updated on FEBRUARY 25, 2019
Applies to:Oracle WebCenter Capture 10g - Version 10.1.3.5.0 to 10.1.3.5.1 [Release 10gR3]
Information in this document applies to any platform.
Committing a batch through Commit Server (10.1.3.5.0) that has mixed date value delimiters (e.g. "/" vs "-") throughout the documents, it is possible to have multiple documents created in Content Server. Other data validation errors between Oracle Document Capture and UCM can cause this problem as well.
-- Steps To Reproduce:
- Create a commit profile that has a Capture index field mapped to a Content Server date field.
- Specify a valid date on the first document (e.g. 09/17/2009).
- Specify an invalid date value that Content Server doesn't accept on the second document (e.g. 09-17-2009).
- Commit the batch. The first document is committed, but not removed from the batch, while the second document errors out.
If Commit Server were processing this batch, you would have many duplicate items within the batch.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document