Why did you receive this error?

ROW-based replication has stopped working. You investigate the error log file and find the
following entries: 2013-08-27 14:15:47 9056 [ERROR] Slave SQL: Could not execute
Delete_rows event on table test.t1; Can’t find record in ‘t1’, Error_code: 1032; handler error
HA_ERR_KEY_NOT_FOUND; the event’s master log 56_master-bin. 000003, end_log_pos
851, Error_code: 1032 2013-08-27 14:15:47 9056 [warning] Slave: Can’t find record in ‘t1’
Error_code: 1032 2013-08-27 14:15:47 9056 [ERROR] Error running query, slave SQL
thread aborted. Fix the problem, and restart the slave SQL thread with “SLAVE START”.
We stopped at log ‘56_masterbin. 000003’ position 684 Why did you receive this error?

ROW-based replication has stopped working. You investigate the error log file and find the
following entries: 2013-08-27 14:15:47 9056 [ERROR] Slave SQL: Could not execute
Delete_rows event on table test.t1; Can’t find record in ‘t1’, Error_code: 1032; handler error
HA_ERR_KEY_NOT_FOUND; the event’s master log 56_master-bin. 000003, end_log_pos
851, Error_code: 1032 2013-08-27 14:15:47 9056 [warning] Slave: Can’t find record in ‘t1’
Error_code: 1032 2013-08-27 14:15:47 9056 [ERROR] Error running query, slave SQL
thread aborted. Fix the problem, and restart the slave SQL thread with “SLAVE START”.
We stopped at log ‘56_masterbin. 000003’ position 684 Why did you receive this error?

A.
The slave SQL thread does not have DELETE privileges to execute on test.t1 table.s

B.
The table definition on the slave -litters from the master.

C.
Multi-threaded replication slaves can have temporary errors occurring for cross database
updates.

D.
The slave SQL thread attempted to remove a row from the test.t1 table, but the row did
not exist.



Leave a Reply 2

Your email address will not be published. Required fields are marked *