Hi, Apologies for not posting this in the 'replication' list, but that seems not very active...
I have setup replication between two 4.1.10 databases, and I noticed that the SLAVE THREAD had stopped because of an SQL error. The errorlog says: "Fix the problem and restart the slave SQL thread". But I'm not sure how to go about that, and would appreciate your feedback. I think I either have to edit the master binlog and remove the offending statement (but HOW, since it's a binary file?) or dump the binlog to a text file, edit the textfile and then pipe it into mysql. That would be really tedious, since the master is still writing to that binlog. To work around that, should I do the following: - stop the slave server - FLUSH LOGS on the master (to start a new binlog) - dump the binlog with the offending command, edit it and import it into the slave using the mysql client (taking care to remove the commands that were already issued /before/ replication stopped) - delete the master.info file - start the slave with --skip-slave-start option - execute the relevant CHANGE MASTER commands - start the slave I hope this doesn't happen often... Regards, Martijn -- The information contained in this communication and any attachments is confidential and may be privileged, and is for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify the sender immediately by replying to this message and destroy all copies of this message and any attachments. ASML is neither liable for the proper and complete transmission of the information contained in this communication, nor for any delay in its receipt. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
