Types of conflicts in DXRE and how they are resolved in a Multi-Site environment |
Summary: What are the various types of conflicts that can arise in DXRE, and how can they be resolved? Solution: There are 4 types of conflicts: Type 1 - record updated at both sites since current cutoff date - Newer record is replicated. To resolve a conflict where updates to the same data have occurred at multiple sites since the last replication session, the sites must choose one update and discard the other. By default, the Replication Engine resolves conflicts by keeping the update with the most recent time stamp. A fragment time stamp records the absolute time when a fragment was updated in Coordinated Universal Time (UTC). If the timestamps are identical but the updates conflict, the Replication Engine cannot resolve the conflict. Refer to the Replication Engine logs for indications and details of conflicts. Conflicts are designated by lines beginning with C.
Example of Type VI conflict (Update - Delete):
Note: to create this error, had to delete a record at both sites, and recreate at one site with identical PK You can also specify whether the Replication Engine resolves conflicts that occur during a sites initial replication session. The Replication Engine cannot resolve Type V starter data conflicts using fragment time stamps because any data that is present in the database prior to activation is assigned the same time stamp. You can enable the Replication Engine to resolve starter data conflicts using the dsetting keyword or the Designer database setting PD_RESOLVE_TYPEV_CONFLICT. |
Posted - November 1, 2022. This article has been viewed 360 times. |
Online URL: https://counterpoint.knowledgebase.co/article.php?id=1361 |
Powered by PHPKB (Knowledge Base Software)