1Z0-883 · Question #53
A simple master-to-slave replication is currently being used. The following information is extracted from the SHOW SLAVE STATUS output: Last_SQL_Error: Error 'Duplicate entry '8' for key 'PRIMARY' '…
The correct answer is E. SET GTID_NEXT="38f32e23480a7-32a1-c323f78067fd37821 : 9"; BEGIN; COMMIT. See the full explanation below for the reasoning.
Question
A simple master-to-slave replication is currently being used. The following information is extracted from the SHOW SLAVE STATUS output:
Last_SQL_Error: Error 'Duplicate entry '8' for key 'PRIMARY' ' on query. Default database: 'mydb'. Query: 'insert into mytable VALUES ('8' , 'George') ' Skip_Counter: 0 Retrieved _Gtid_Set: 38f32e23480a7-32a1-c323f78067fd37821: 1-8 Auto _Position: 1 You execute a "SHOW CREATE TABLE mytable" on the slave:
CREATE TABLE mytable' ( ID' int(11) NOT NULL DEFAULT 0', name' char(10) DEFAULT NULL, PRIMARY KEY (`ID') ) The table mytable on the slave contains the following:
You have issued a STOP SLAVE command. One or more statements are required before you can issue a START SLAVE command to resolve the duplicate key error. Which statement should be used?
Options
- ASET GLOBAL SQL_SKIP_SLAVE_COUNTER=1
- BSET GTID_NEXT="CONSISTENCY";
- CSET GLOBAL enforce_gtid_consistency=ON
- DSET GTID_EXECUTED="38f32e23480a7-32a1-c323f78067fd37821 : 9";
- ESET GTID_NEXT="38f32e23480a7-32a1-c323f78067fd37821 : 9"; BEGIN; COMMIT;
How the community answered
(20 responses)- A5% (1)
- B10% (2)
- C5% (1)
- E80% (16)
Community Discussion
No community discussion yet for this question.