Bug #18607 LOAD DATA FROM MASTER fails because of INFORMATION_SCHEMA database
Submitted: 29 Mar 2006 9:03 Modified: 3 May 2006 9:20
Reporter: Victoria Reznichenko Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Replication Severity:S3 (Non-critical)
Version:5.0 OS:Any (any)
Assigned to: Jim Winstead CPU Architecture:Any

[29 Mar 2006 9:03] Victoria Reznichenko
In 5.0 if you try to use LOAD DATA FROM MASTER, it tries to load INFORMATION_SCHEMA database as well and fails:

mysql> load data from master;
Query OK, 0 rows affected, 1 warning (0.04 sec)

mysql> show warnings;
| Level | Code | Message                                                     |
| Error | 1007 | Can't create database 'information_schema'; database exists |
1 row in set (0.01 sec)

If I add replicate-ignore-db=information_schema, it works fine.

INFORMATION_SCHEMA is a system database and I think it should not be copied at all during LOAD DATA FROM MASTER.

How to repeat:
1. setup replication between 5.0.X servers
2. run LOAD DATA FROM MASTER on the slave.
3. Check warnings.
[13 Apr 2006 19:30] Brad Brewer
I am having the same problem. However, adding "replicate-ignore-db=information_schema" to  my.cnf doesn't seem to help. 
Executing the "show slave status" command shows that there is now replication database defined. (Replicate_Do_DB: )

Operating System: CentOS 4.3
Slave: MySQL 5.0.19 community edition
Master: MySQL 5.0.18 pro
[13 Apr 2006 19:32] Brad Brewer
Sorry, that was supposed to be "NO replication database defined"
[22 Apr 2006 1:25] Bugs System
A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

[27 Apr 2006 13:41] Magnus BlÄudd
Looks ok to me(after seconds review).
[2 May 2006 18:27] Jim Winstead
Fixed in 5.0.22 and 5.1.10.
[3 May 2006 9:20] MC Brown
Documented in 5.0 and 5.1 changelog.

<literal>LOAD DATA FROM MASTER</literal> would fail when trying to load the <literal>INFORMATION_SCHEMA</literal> database from the master, because the <literal>INFORMATION_SCHEMA</literal> system database would already exist on the slave. (Bug #18607)