IBM Support

Replication fails with an error "Failed to update a row in table" for a table with no primary keys or unique indexes defined

Troubleshooting


Problem

Replication repeatedly fails with "Failed to update a row in table" error and affected table needs to be refreshed. This problem happens for a table that does not have any primary keys or unique indexes defined.

Symptom

Your target database is either DB2 LUW or SQL Server.

A row which CDC tries to update and fail is not present in the target table.

Both source and target tables have no primary keys or unique indexes defined.

In Management Console, in affected table-mapping settings, key is set to either "Use an index" -> "Auto Detect" or "Use all searchable columns".

[{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSX3HK","label":"InfoSphere Change Data Capture"},"ARM Category":[{"code":"a8m0z0000001gSjAAI","label":"CDC"},{"code":"a8m0z0000001gSjAAI","label":"CDC"},{"code":"a8m0z0000001gSjAAI","label":"CDC"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"11.3.0;11.4.0"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
26 February 2023

UID

swg21614463