Re: How to Fix Broken Replication
"Henry Chang" <[EMAIL PROTECTED]> wrote: > > I have MySQL replication setup between Master A and Slave B. > Everything was working fine, until one day replication was broken. > Status on the slave shows the following error message: > > Last_error: Error 'Can't drop database X. Database doesn't exist' > on query 'DROP DATABASE X. > > I suspect another admin probably deleted or moved the database from the > linux command line. At this point, how can I tell Slave B to jump over > this drop command and resume replication at the next command?? Or is > re-installing replication the only option on Slave B?? > > Any help would be greatly appreciated. > > Master A & Slave B > MySQL version 4.0.18 > Red Hat 9 SET GLOBAL SQL_SLAVE_SKIP_COUNTER command will help you: http://dev.mysql.com/doc/mysql/en/SET_GLOBAL_SQL_SLAVE_SKIP_COUNTER.html -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ __ / |/ /_ __/ __/ __ \/ /Egor Egorov / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: How to Fix Broken Replication
John...the skip-counter is perfect!! My Slave B is now back up and running again. Thanks again for your prompt help!! *** REPLY SEPARATOR *** On 6/14/2004 at 3:54 PM John McCaskey wrote: >Give the below a shot: > >slave stop; >set global sql_slave_skip_counter=1; >slave start; > >Good luck. > >John A. McCaskey > >-Original Message- >From: Henry Chang [mailto:[EMAIL PROTECTED] >Sent: Monday, June 14, 2004 3:34 PM >To: [EMAIL PROTECTED] >Subject: How to Fix Broken Replication > > > >I have MySQL replication setup between Master A and Slave B. Everything >was working fine, until one day replication was broken. Status on the >slave shows the following error message: > >Last_error: Error 'Can't drop database X. Database doesn't exist' >on query 'DROP DATABASE X. > >I suspect another admin probably deleted or moved the database from the >linux command line. At this point, how can I tell Slave B to jump over >this drop command and resume replication at the next command?? Or is >re-installing replication the only option on Slave B?? > >Any help would be greatly appreciated. > >Master A & Slave B >MySQL version 4.0.18 >Red Hat 9 > > >-- >MySQL General Mailing List >For list archives: http://lists.mysql.com/mysql >To unsubscribe: >http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
RE: How to Fix Broken Replication
Give the below a shot: slave stop; set global sql_slave_skip_counter=1; slave start; Good luck. John A. McCaskey -Original Message- From: Henry Chang [mailto:[EMAIL PROTECTED] Sent: Monday, June 14, 2004 3:34 PM To: [EMAIL PROTECTED] Subject: How to Fix Broken Replication I have MySQL replication setup between Master A and Slave B. Everything was working fine, until one day replication was broken. Status on the slave shows the following error message: Last_error: Error 'Can't drop database X. Database doesn't exist' on query 'DROP DATABASE X. I suspect another admin probably deleted or moved the database from the linux command line. At this point, how can I tell Slave B to jump over this drop command and resume replication at the next command?? Or is re-installing replication the only option on Slave B?? Any help would be greatly appreciated. Master A & Slave B MySQL version 4.0.18 Red Hat 9 -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
