Data Out of Sync Using Master-Master Active-Active Replication - Replication Error

(Doc ID 2321494.1)

Last updated on NOVEMBER 29, 2017

Applies to:

MySQL Server - Version 5.0 and later
Information in this document applies to any platform.

Symptoms

In a master-master replication setup where both/all MySQL instances are active, i.e. writes are allowed, the data on the MySQL instances become out of sync, and the replication will in most cases stop with errors. The errors will vary and may include:

Error NumberBinlog FormatError Definition StringExample Error TextDescription
1032 ROW HA_ERR_KEY_NOT_FOUND Could not execute Delete_rows event on table db1.t1; Can't find record in 't1' It was attempted to update/delete a row, but the row could not be found.
1032 ROW HA_ERR_END_OF_FILE Could not execute Update_rows event on table db1.t1; Can't find record in 't1' A row was not found by means of a table scan on a table without a primary key.
1062 ROW HA_ERR_FOUND_DUPP_KEY Could not execute Write_rows event on table db1.t1; Duplicate entry '1' for key 'PRIMARY' A duplicate key error. This can happen for both primary keys and unique indexes.
1062 STATEMENT   Error 'Duplicate entry '1' for key 'PRIMARY'' on query.  A duplicate key error. This can happen for both primary keys and unique indexes.

Cause

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