MySQL Bugs: #3692: Cross-Over Database Queries on master crashes slaves.

Bug #3692	Cross-Over Database Queries on master crashes slaves.
Submitted:	7 May 2004 23:24	Modified:	8 May 2004 12:59
Reporter:	Dimitrij HIlt	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S1 (Critical)
Version:	4.0.18-standard-log	OS:	Linux (Linux/Debian stable 2.4.21 ia32)
Assigned to:		CPU Architecture:	Any

Description:
If you have more than one database and replicate-do-do= on slaves, operations on excluded databases on master kann be replicated and crashes all slaves.

How to repeat:
On master:

1) On master: create databases replicate and notreplicate with table test in each database. Insert anything in table test in each database.
2) On master: create one user with rigths for both databases replicate and notreplicate
3) On slave: write replicate-do-db=replicate to configfile and start replication
4) On master: login in die database replicate and run 'delete from notreplicate.test' or similar.
5) On slave: you got Error:

Last_errno: 1146
Last_error: Error 'Table 'notreplicate.test' doesn't exist' on query 'delete from notreplicate.test'. Default database: 'replicate'

Hello,
This is expected behaviour of replicate-do-db, as explained here:
http://dev.mysql.com/doc/mysql/en/Replication_Options.html
You may want to use replicate-wild-do-table=replicate.% instead.

Guilhem