IBM Support

IBM Content Collector: SQLSTATE 23505 returned when a unique value constraint is violated in Content Manager repository

Troubleshooting


Problem

When running an IBM Content Collector (ICC) task route, storing some documents in a Content Manager (CM) destination repository fails with an SQL State 23505 error in the ibm.ctms.cmv8.Connector-YYYY-MM-DD[(n)].log (CM Connector logs).

Symptom

ICC will write the following set of errors to the CM Connector logs, and the effected documents will be passed to the application blocklist after the maximum number of processing attempts have passed:

SQL0803N  One or more values in the INSERT statement, UPDATE statement, or foreign key update caused by a DELETE statement are not valid because the primary key, unique constraint or unique index identified by "4" constrains table "ICMADM.ICMUT01219001" from having duplicate values for the index key.
SQLSTATE=23505
SQLSTATE 23505: A violation of the constraint i
mposed by a unique index or a unique constraint occurred.

Cause

These errors are triggered by design when a document that is already present in CM is archived once again by ICC. This is validated on the CM side by using unique hash keys for each document. If an item is submitted for archival and CM finds that it has an identical hash value to one already in the repository, the item will not be stored and CM returns this message to indicate it is a duplicate of an already stored item.

Environment

IBM Content Collector

IBM Content Manager Repository

Diagnosing The Problem

The ibm.ctms.cmv8.Connector-YYYY-MM-DD[(n)].log file will contain the above mentioned error message and the failed document may be present in the blocklist if the maximum number of processing attempts has been surpassed for the document.

Resolving The Problem

This is by design; Content Manager is rejecting the effected document because it is a duplicate of an already stored mail. However, to prevent this from happening in the future, the ICC deduplication process can be configured in order to handle duplicate documents in a more graceful manner. See the below documentation for further details:

Configuring Content Collector: Deduplication

[{"Product":{"code":"SSAE9L","label":"Content Collector"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"--","Platform":[{"code":"PF033","label":"Windows"}],"Version":"4.0;3.0","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 June 2018

UID

swg21659318