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') '
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?
A. SET GLOBAL SQL_SKIP_SLAVE_COUNTER=1
B. SET GTID_NEXT="CONSISTENCY";
SET GTID_NEXT=" AUTOMATIC';
C. SET GLOBAL enforce_gtid_consistency=ON
D. SET GTID_EXECUTED="38f32e23480a7-32a1-c323f78067fd37821 : 9";
E. SET GTID_NEXT="38f32e23480a7-32a1-c323f78067fd37821 : 9"; BEGIN; COMMIT;
Consider the following statement on a RANGE partitioned table:
ALTER TABLE orders DROP PARTITION p1, p3;
What is the outcome of executing the above statement?
A. Only the first partition (p1) will be dropped as only one can be dropped at any time.
B. Al data in p1 and p3 partitions are removed, but the table definition remains unchanged.
C. A syntax error will result as you cannot specify more than one partition in the same
D. Al data in pi and p3 partitions are removed and the table definition is changed.