Skip to main content

Record conflict detection

Maintaining sync between source and target record


FairCom replication checks for record conflicts on update.

FairCom replication checks for record conflicts on update. This is significant because it validates that a target record image has not changed from the underlying assumption that the data is absolutely in sync between the source and target. This check ensures that the target server is not unexpectedly updated or not in sync with source data.

When a record is applied for update, the original source record (before update) is compared to the current target record image. This check is performed for both update and delete operations. If these differ a REPCNF_ERR (1105) error is returned as logged to the exception log along with the old and new record images as well as the index keys.

For specific use cases, it may be acceptable for the target to allow updates to selected record fields.


Changing the primary key field used for replication could result in the record not being found on the target.

This option can be disabled in Replication Manager while creating your plan. From the Advanced Options panel, by unchecking the Conflict Detection checkbox.

Figure 1. Advanced option tab
Advanced option tab

This is analogous to the Replication Agent check_update configuration.

Data conflict management

There is no automatic conflict management in bidirectional replication, where the target node can be updated and replication conflicts should be assumed to occur. Refer to Replication Agent Extensions Library for the FairCom replication callback SDK to implement advanced conflict management solutions.