Oracle
1Z0-883 · Question #110
A user has deleted the wrong row in a table and you are preparing a point-in-time recovery skipping the DELETE event. The server is configured with: You have identified that the DELETE statement to…
The correct answer is B. The server keeps track of which GTIDs have already been executed and skips those. See the full explanation below for the reasoning.
Question
A user has deleted the wrong row in a table and you are preparing a point-in-time recovery skipping the DELETE event. The server is configured with:
You have identified that the DELETE statement to skip has the Global Transaction Identifier (GTID) `dbbe7da-fe25-11e2-b6c7-0800274aa49e:5 and you replay the binary log with:
Mysqlbinlog ?exclude-gtides=' dbbe07da-fe25-11e2-b6c7-0800274aa49e:5' binlog.00000.2 | mysql However all events were skipped instead of just the one deleting the wrong row. What is the reason for this?
Options
- AMysqlbinlog ignores arguments to ?exclude-gtids-it means ignore all events with GTIDs.
- BThe server keeps track of which GTIDs have already been executed and skips those.
- CEnforce_gtid_consistency is set to ON.
- DGtid_mode must be set to AUTO during point in time recoveries.
How the community answered
(31 responses)- A6% (2)
- B77% (24)
- C3% (1)
- D13% (4)
Community Discussion
No community discussion yet for this question.