Resolving update-update conflict in peer-to-peer replication
Recently I had received a hand-off ticket which was about a replication issue. The system has been configured with the replication of Peer-to-Peer type. One of the subscribers was throwing an error which was reading like A conflict of type 'Update-Update' was detected at peer 4 between peer 100 (incoming), transaction id 0x000000000011a1c3 and peer 100 (on disk). While I was working on this issue and trying to resolve it, I noticed that it wasn't showing any records in msrepl_errors table or conflict_dbo_table.
![p2p1](https://static.hsstatic.net/BlogImporterAssetsUI/ex/missing-image.png)
![p2p2](https://static.hsstatic.net/BlogImporterAssetsUI/ex/missing-image.png)
Share this
You May Also Like
These Related Stories
Updating ASMLIB Driver Using "update-driver"
Updating ASMLIB Driver Using "update-driver"
Dec 10, 2010
1
min read
Simplify Oracle critical patch updates using simple configurations
Simplify Oracle critical patch updates using simple configurations
Nov 28, 2018
2
min read
News and updates from Google Cloud Platform
News and updates from Google Cloud Platform
Aug 2, 2018
4
min read
No Comments Yet
Let us know what you think