Re: How to best handle a Replication collision.
Posted by:
Irfan Ali
Date: August 19, 2012 04:37PM
>> I also agree that removing the autoincrement might resolve the problem, but then I would end up with double-posting in that table on the slave.
Removing auto_increment column from TABLE B will not end up double entry on slave because on master it's only writing auto_increment id for TABLE B in binary log not the entire query for TABLE B.
You can examine master binary log to confirm. I still believe removing auto_increment column from TABLE B will resolve the issue.
Or you can reproduce the issue on test table to confirm.
Subject
Views
Written By
Posted
2669
August 17, 2012 02:39PM
1319
August 18, 2012 09:46PM
1007
August 18, 2012 09:58PM
1040
August 19, 2012 03:40PM
1211
August 19, 2012 04:27PM
Re: How to best handle a Replication collision.
1117
August 19, 2012 04:37PM
952
August 19, 2012 04:46PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.