Bug #10799 | drop database exists on master cause replication error on slave | ||
---|---|---|---|
Submitted: | 23 May 2005 10:09 | Modified: | 23 May 2005 17:52 |
Reporter: | Sergey Frolovichev | Email Updates: | |
Status: | Can't repeat | Impact on me: | |
Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
Version: | 4.1.11-standard | OS: | Linux (SuSe Linux 9.3) |
Assigned to: | CPU Architecture: | Any |
[23 May 2005 10:09]
Sergey Frolovichev
[23 May 2005 15:23]
MySQL Verification Team
What is the error message are you getting?
[23 May 2005 15:30]
Sergey Frolovichev
SQL Running=No last err: Error 'Can't drop database 'Partner3'; database doesn't exist' on query. Default database: ''. Query: 'drop database Partner3'
[23 May 2005 17:04]
MySQL Verification Team
I was unable to repeat the behavior reported with current server built from BK source. not error showed after the create database and drop commands. Replicate_Do_Table: dbt.t1 Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0 Last_Error:
[23 May 2005 17:12]
Sergey Frolovichev
This table was in the same database you have created and dropped? In my case - not the same - replicated tables in Monamour2 and DROPED database which was no on SLAVE was Partner3. So like this - have Master with: Monamour2 and Partner3. After this starting slave with do-table=Monamour2.test On slave having Monamour2.tes and no Partner3. Then all i stsarted - cheking replication with executing some queries on Monamour2.test: insert into test (id) values (1); checking that replication working properly (this record apperiers on slave). Now making drop database Partner3 on master.
[23 May 2005 17:52]
MySQL Verification Team
Yes I did and repeated it like you wrote and still can't repeat.