A MySQL replication slave is set up as follows: User all InnoDB tables Receives ROW-based binary logs Has the read-only option The replication slave has been found in an error state. You check the MySQL error log file and find the following entries: 2013-08-27 13:55:44 9056 [ERROR] Slave SQL: Could not execute Write_rows event on table test.tl; Duplicate entry ‘3’ for key’PRIMARY’ , Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event’s master log 56_master-bin.000003, end_log_pas 653, Error_code: 1062 2013-08-27 13:55:44 9056 [Warning] Salve: Duplicate entry ‘3’ for key ‘PRIMARY’ Error_code: 1062 2013-08-27 13:55:44 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 496 What are two possible causes for this error to occur?（）A.The slave was created with mysqldump –u root –p – skip-lock-table—all-databases > /data/data.sqlB.The slave user does have INSERT, UPDATE, or DELETE permission and cannot execute the write_rows functionC.For tables with UNIQUE keys, statement-based replication must be used maintain integrityD.The root user on the slave has executed FLUSH LOGS, causing the relay-log to doublewriteE.The applications have the SUPER privilege, which allows them to update rows

多项选择题

A MySQL replication slave is set up as follows: User all InnoDB tables
Receives ROW-based binary logs Has the read-only option
The replication slave has been found in an error state.
You check the MySQL error log file and find the following entries:
2013-08-27 13:55:44 9056 [ERROR] Slave SQL: Could not execute Write_rows event on table test.tl; Duplicate entry ‘3’ for key’PRIMARY’ , Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event’s master log 56_master-bin.000003, end_log_pas 653, Error_code: 1062
2013-08-27 13:55:44 9056 [Warning] Salve: Duplicate entry ‘3’ for key ‘PRIMARY’
Error_code: 1062
2013-08-27 13:55:44 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 496 What are two possible causes for this error to occur?（）

A.The slave was created with mysqldump –u root –p – skip-lock-table—all-databases > /data/data.sql
B.The slave user does have INSERT, UPDATE, or DELETE permission and cannot execute the write_rows function
C.For tables with UNIQUE keys, statement-based replication must be used maintain integrity
D.The root user on the slave has executed FLUSH LOGS, causing the relay-log to doublewrite
E.The applications have the SUPER privilege, which allows them to update rows

1z0-883