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 3 Question 96 Discussion

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

Your MySQL environment has asynchronous position based-replication with one master and one slave.

The slave instance had a disk I/O problem, so it was stopped.

You determined that the slave relay log files were corrupted and unusable, but no other files are damaged.

You restart MySQL Server.

How can replication be restored?

Show Suggested Answer Hide Answer
Suggested Answer: B

Contribute your Thoughts:

Tiffiny
3 months ago
Oh man, corrupted relay logs? That's the worst! I bet the poor DBA is tearing their hair out right now. But hey, at least it's not a full server crash, right? Silver linings and all that.
upvoted 0 times
...
Charlene
3 months ago
This is a tricky one, but I think option C is the way to go. Deleting the corrupted logs and reconfiguring the replication settings should do the trick. Just gotta be careful not to mess up the file names, you know?
upvoted 0 times
Mona
2 months ago
Yeah, I think so too. It's better to be cautious and follow the proper steps to avoid any further issues.
upvoted 0 times
...
Alpha
2 months ago
I agree, option C seems like the safest choice. It's important to make sure the replication settings are correct.
upvoted 0 times
...
...
Thaddeus
3 months ago
I'm not sure, but I think we should use the relay logs from the master to replace the corrupted ones.
upvoted 0 times
...
Ronna
3 months ago
I agree with Mozelle. That seems like the right way to restore replication.
upvoted 0 times
...
Annamae
4 months ago
Hmm, deleting the slave's relay logs and adjusting the replication settings sounds like a lot of work. I'd probably just go with the backup option, D. It's the safest bet to ensure a clean restart.
upvoted 0 times
...
Jin
4 months ago
Ah, I see. The slave's relay logs are corrupted, but the master's logs are still intact. Sounds like option B is the way to go. Just need to copy those relay logs over to the slave, and we should be good to go!
upvoted 0 times
Myra
2 months ago
Great, let's go ahead and replace those logs and get the replication up and running again.
upvoted 0 times
...
Elza
3 months ago
Exactly. Once we do that, we can restart the replication and everything should be back on track.
upvoted 0 times
...
Annamae
3 months ago
That makes sense. We just need to replace the corrupted logs with the ones from the master.
upvoted 0 times
...
Jose
3 months ago
Option B) The relay logs from the master should be used to replace the corrupted relay logs.
upvoted 0 times
...
...
Mozelle
4 months ago
I think we should delete the slave relay logs and then execute START SLAVE.
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