If you're using InnoDB tables, replication stops the slaves from
running. Heikki said he'd try to get this fixed for 3.23.52.
--Pete
On Mon, Aug 12, 2002 at 04:05:11PM +0200, Lutz Maibach wrote:
> Hi,
>
> today I noticed a strange behaviour in MySQL 3.23.49a-Replication I can't explain.
> A perl-script which controls whether master- and replication-tables are equal showed
> me, that a master-table was missing on both slaves (two backups are better than one
> :-) )
>
> When I controlled the master update-log I saw that the master-table was renamed with
> the following command:
> ALTER TABLE ad_429_t RENAME adprj_7;
>
> This command was missing in the slave-updatelogs. The sql-statements before and
> right after the missing one were present and no error was written down in the
> mysql-error-log.
>
> Trying to find out whether the Rename-Statement works right or not I did some tests
> with renaming a table but all actions were performed on the slaves too.
>
> Has someone experienced the same? I'm now a bit unsure whether the replication is
> working right.
>
> Greetings from Germany
>
> Lutz Maibach
>
>
>
> ---------------------------------------------------------------------
> 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 <mysql-thread116863@stripped>
> To unsubscribe, e-mail
> <mysql-unsubscribe-harlan=artselect.com@stripped>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
