Replication Breaks with Duplicate Entry error when using binlog_format=STATEMENT, Triggers and you insert into another table with an auto_increment column
Last updated on MARCH 09, 2015
Applies to:MySQL Server - Version 4.0 and later
Information in this document applies to any platform.
Your replication slave stops replicating with errors about "Duplicate Key" or "Duplicate Entry".
This situation can occur for an infinitely variable number of reasons, but this document addresses the situation where this occurs when you are
- Using Statement-based replication (binlog_format=STATEMENT)
- Insert into a table with both an auto_increment column and a trigger
- The trigger inserts an additional row into another table with an auto_increment column
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms