Peer-to-Peer replication (P2P) allows users on multiple databases to make changes concurrently to the same data, while SharePlex replication keeps all of the databases synchronized. Peer-to-Peer replication is not appropriate for all replication environments as it requires a major commitment on the application and database design that may not be practical when packaged applications are in use. Before the latest SharePlex 8.6.4 version, P2P required custom PL/SQL conflict resolution procedures to resolve the conflict when more than one user changed the same record at, or near, the same time. In SharePlex 8.6.4, pre-built conflict resolutions with host based priority and time-based priority are available for customers to use in P2P environment.
Peer-to-peer replication represents unique challenges not found in single-direction replication such as replication for reporting purposes. In those configurations, users are not allowed on the secondary system to perform DML changes on replicated objects. In peer-to-peer replication, however, different users all make DML changes to copies of the same tables in different databases, usually on different systems, while SharePlex keeps them all current through replication. Conflict can occur for many reasons in a Peer-to-Peer environment.
A conflict is defined as an out-of-sync condition and conflict resolution routines are called upon by SharePlex post process to resolve the conflict.
Conflict can occur for following reasons:
To successfully deploy SharePlex in a peer-to-peer configuration, you must be able to:
For simple conflict resolution requirement
Logging for details on default conflict resolution is now available in SharePlex 8.6.6. If you have more complex conflict resolution requirement, please contact your account representative to engage professional services consulting services to create customized conflict resolution procedures.