| Bug #15025 | LOAD DATA FROM MASTER attempts to load INFORMATION_SCHEMA | ||
|---|---|---|---|
| Submitted: | 17 Nov 2005 15:50 | Modified: | 30 Aug 2006 18:30 |
| Reporter: | Lukas Smith | Email Updates: | |
| Status: | Won't fix | Impact on me: | |
| Category: | MySQL Server: Replication | Severity: | S3 (Non-critical) |
| Version: | 5.0.15/5.0.17 BK | OS: | Linux (Linux) |
| Assigned to: | Andrei Elkin | CPU Architecture: | Any |
[17 Nov 2005 15:50]
Lukas Smith
[19 Nov 2005 14:00]
MySQL Verification Team
Are you using 5.0.15 servers for master and slave and could you please provide the my.ini/my.cnf files used in the servers configuration. Thanks in advance.
[27 Nov 2005 9:01]
Lukas Smith
I have been using 5.0.15 on both the master (windows) and the slave (linux).
[27 Nov 2005 9:04]
Lukas Smith
It seems I have already undone all the changes to my my.ini/my.cnf files. For the windows side. I will try to reconstruct things.
[27 Nov 2005 9:35]
Lukas Smith
Config file from the linux slave
Attachment: my.cnf (application/octet-stream, text), 4.07 KiB.
[27 Nov 2005 9:37]
Lukas Smith
Since I recently updated to mysql 5.0.16 I do not have the original my.ini from the windows server. It was a stock 5.0.15 install (developer, olap, latin1 charset) with the binary log enabled and server-id=1
[27 Nov 2005 14:53]
Pieter Verhaeghe
I have the same problem with a master on Win2003 server and a slave on WinXP Pro. The slave is configured with the wizard and server-id=2. The server had upgraded to MySQL 5 and configured with the wizard also. The server-id of the master = 1 and binary logs are enabled. So the bug is not only on Linux, but also on Windows.
[28 Nov 2005 15:30]
MySQL Verification Team
SuseLinux5017>LOAD DATA FROM MASTER; Query OK, 0 rows affected, 1 warning (0.01 sec) SuseLinux5017>show warnings\G *************************** 1. row *************************** Level: Error Code: 1007 Message: Can't create database 'information_schema'; database exists 1 row in set (0.00 sec)
[21 May 2006 11:54]
Lukas Smith
Looks like a duplicate bug report was marked as fixed in 5.1.10: Bug #18607
[30 Aug 2006 18:30]
Trudy Pelzer
Since the current implementation of LOAD DATA FROM MASTER and LOAD TABLE FROM MASTER is very limited, these statements are deprecated in versions 4.1, 5.0 and 5.1 of MySQL. We will introduce a more advanced technique (online backup) in a future (>5.1) version, that will have the added advantage of working with more storage engines. Due to the deprecated status of the statements, this bug will not be fixed. For 5.1 and earlier, the recommended alternative solution to usign LOAD DATA|TABLE FROM MASTER is mysqldump on the master piped (or output copied) to the mysql client on the slave. This also has the advantage of working for all storage engines. A deprecation warning will be added for these statements in 4.1, 5.0 and 5.1 shortly.
