David, Monday, September 23, 2002, 6:03:58 PM, you wrote: DP> We are having a problem which seems to have appeared recently with DP> replication on our mysql servers.
DP> - We have 3 servers set up with mysql 3.23.52 (they were running .49 but DP> we upgraded in an attempt to fix this problem, which did not work), set DP> up as a master and 2 slaves to the master. DP> - There is a large script that runs on the master server. This script DP> DROPs a large table, then recreates it. It is basically a DROP followed DP> by a CREATE and many INSERTs. DP> - Up until recently we have had no issues with this problem. Lately DP> however the slave servers are not updating. The error we see in the logs DP> is the table which it attempts to create already exists, therefore from DP> that point on the replication stops. We can't understand why suddenly DP> the DROP TABLE doesn't get replicated. David, does it happen every time when you drop the table or only sometimes? Is DROP TABLE statement present in binary logs? I tested on 3.23.52 and DROP TABLE replicated fine for me. -- For technical support contracts, goto https://order.mysql.com/?ref=ensita This email is sponsored by Ensita.net http://www.ensita.net/ __ ___ ___ ____ __ / |/ /_ __/ __/ __ \/ / Victoria Reznichenko / /|_/ / // /\ \/ /_/ / /__ [EMAIL PROTECTED] /_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net <___/ www.mysql.com --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
