Cyber Monday 2024! 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 10 Question 88 Discussion

Actual exam question for Oracle's 1Z0-908 exam
Question #: 88
Topic #: 10
[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:

Bok
2 months ago
Deleting the relay logs and then starting the slave? Sounds like a recipe for disaster. I'd rather just throw the whole slave away and start fresh. Option D all the way!
upvoted 0 times
...
Ronald
2 months ago
But wouldn't it be safer to delete the slave relay logs, adjust the replication relay log file name, and then start the slave?
upvoted 0 times
...
William
2 months ago
The slave needs a backup, huh? Well, that's what they get for skipping backup day! I'm going with D, just to be on the safe side.
upvoted 0 times
Hollis
28 days ago
Great, let's get that backup restored and get the replication back up and running.
upvoted 0 times
...
Reed
1 months ago
I agree, it's better to be safe than sorry. Let's go ahead and restore from backup.
upvoted 0 times
...
Cristal
1 months ago
Yeah, that sounds like the safest option. We can't risk losing any data.
upvoted 0 times
...
Scot
2 months ago
I think we should go with option D and restore the slave from backup.
upvoted 0 times
...
...
Merissa
2 months ago
I disagree, I believe we should use the relay logs from the master to replace the corrupted ones.
upvoted 0 times
...
Sylvia
3 months ago
Hmm, I'm not too sure about B. Using the master's relay logs to replace the corrupted ones? Seems a bit risky to me. I'd go with C, it's the most straightforward approach.
upvoted 0 times
Alesia
2 months ago
Yeah, using the master's relay logs could introduce inconsistencies. C is definitely the way to go.
upvoted 0 times
...
Juan
2 months ago
I agree, starting the slave after deleting the corrupted logs seems like the right way to go.
upvoted 0 times
...
Raymon
2 months ago
I think C is the best option. It's safer to just delete the corrupted relay logs and adjust the replication relay log file name.
upvoted 0 times
...
...
Dong
3 months ago
Ah, so the slave's relay logs are corrupted! C definitely sounds like the way to go - delete those bad boys and then adjust the replication settings. Easy peasy!
upvoted 0 times
Daryl
2 months ago
Lajuana: Good point, let's make sure to restart the slave after executing the necessary commands.
upvoted 0 times
...
Amber
2 months ago
I think we should also restart the slave after making those changes.
upvoted 0 times
...
Lajuana
2 months ago
Agreed, deleting the corrupted relay logs and adjusting the replication settings should do the trick.
upvoted 0 times
...
Farrah
2 months ago
Yeah, C seems like the right choice.
upvoted 0 times
...
...
Ronald
3 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