Resolve protected-table collisions automatically or manually - Connect_CDC - connect_cdc_mimix_share - 5 - 5.8

Connect CDC Advanced User Guide

Product type
Software
Portfolio
Integrate
Product family
Connect
Product
Connect > Connect CDC (MIMIX Share)
Version
5.8
Language
English
Product name
Connect CDC
Title
Connect CDC Advanced User Guide
Copyright
2023
First publish date
2003
ft:lastEdition
2023-09-27
ft:lastPublication
2023-09-27T18:12:55.651884

If a table is protected (defined with full collision resolution), all collisions are resolved before the distributed transaction is applied at the target. By default, the collision is automatically resolved, and the transaction is applied within the same transaction.

If automatic resolution is in effect, the Connect CDC component uses a “latest-update” algorithm to determine which of the two conflicting records is kept at the target table. One or more error messages is logged, but replication processing continues.

If manual resolution is selected collisions are still detected and their detailed information is retained, but transaction-error handling is invoked. In this case, the option you specify determines whether or not the transaction which contains the collision is rolled back so you can “manually” resolve the collision. See “Transaction error mode” .

If the colliding transaction is rolled back (and saved in the SQL metabase), you can use the shadow table records to help determine how to resolve the collision. You can reapply the transaction by doing one of the following after you examine and modify the colliding statement:

  • Stop and restart the Replication request.

  • Stop and restart the Connect CDC Kernel process on the target host using Connect CDC MonCon.

  • Update the source table with a suitable compensating statement to be replicated to the target.