Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Oracle Exam 1Z0-908 Topic 4 Question 83 Discussion

Actual exam question for Oracle's 1Z0-908 exam
Question #: 83
Topic #: 4
[All 1Z0-908 Questions]

You have an InnoDB Cluster configured with three servers.

Examine this command, which executes successfully:

mysqldump -uroot -p -d mydatabase > mydatabase_backup.sql

Due to data loss, the cluster is initialized and a restore is attempted resulting in this error:

ERROR 13176 (HY000) at line 23: Cannot update GTID_PURGED with the Group Replication plugin running

Which two actions, either one of which, can fix this error and allow a successful restore of the cluster? (Choose two.)

Show Suggested Answer Hide Answer
Suggested Answer: D, E

Contribute your Thoughts:

Carmen
4 days ago
Wait, did they seriously ask us to choose two answers? That's just cruel. I'm going with B) and F) - can't be too careful with those GTID statements!
upvoted 0 times
...
Ruby
5 days ago
Ugh, Group Replication issues are the worst. I'd go with D) and remove the plugin before restoring. That way, you don't have to worry about that GTID_PURGED problem.
upvoted 0 times
...
Pearly
11 days ago
Hmm, this seems like a tricky one. I'm thinking B) or F) might do the trick, but I'm not 100% sure. Removing that GTID_PURGED statement could be the key to a successful restore.
upvoted 0 times
...
Leota
14 days ago
I'm not sure about option B. I think option C could also work by creating the backup with the --set-gtid-purged=OFF option.
upvoted 0 times
...
Tonette
15 days ago
I agree with Marguerita. Option B seems like the most logical solution to allow a successful restore of the cluster.
upvoted 0 times
...
Marguerita
16 days ago
I think option B is the right choice because removing the @@GLOBAL.gtid_purged statement from the dump file should fix the error.
upvoted 0 times
...
Gabriele
17 days ago
I'm not sure about option B. Maybe we should also consider option F, restoring with the --set-gtid-purged=OFF option.
upvoted 0 times
...
Linn
21 days ago
I agree with Rosalyn. Option B seems like the right choice to allow a successful restore of the cluster.
upvoted 0 times
...
Rosalyn
22 days ago
I think option B could fix the error because it involves removing the @@GLOBAL.gtid_purged statement.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77