MySQL Bugs: #25384: Backup Fails to restore cross platform using mysqldump, mysqladministrator

Bug #25384	Backup Fails to restore cross platform using mysqldump, mysqladministrator
Submitted:	3 Jan 2007 12:40	Modified:	4 Jan 2007 10:02
Reporter:	Charlie Farrow	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Backup	Severity:	S3 (Non-critical)
Version:	5.0.27 - Community	OS:	Windows (Win / Fedora 6)
Assigned to:	MySQL Verification Team	CPU Architecture:	Any
Tags:	administrator, Backup, linux, mysqldunp, restore, windows

Description:
I currently have a windows box running mysql. 

Simply for the fact that windows is not very stable (not the mysql software, windows itself) and we keep having problems, I am trying to port my installation to Fedora Linux.

I have the 5.0.27 - Community server set up on both the Fedora and Windows boxes.

I am using mysql administrator on both boxes.

I cannot restore either a mysqldump backup or a administrator backup from the windows box to the Fedora box.

It is only my database 'wellandpowerdb' that seems to have an issue, not the other databases. I have checked the database for errors and have found none.

I *think* but am not sure that it might relate to the triggers/stored procs.

mysqldump on restore in a terminal window gives the error:

[root@workshop2 ~]# mysql -u root -p < '/test.sql' 
Enter password: 
ERROR 1054 (42S22) at line 6854: Unknown column 'cl.COMPONENT_ID' in 'field list'

if i sun in the console, using the source command, I do not get a fatal error, but the server is unable to read the database wellandpowerdb, all the others restore correctly.

With mysqladministrator i get:

Error during backup.
Table 'columns_priv' already exists

Please find attached mysqldump file and 'test.sql' and administrator backup file

How to repeat:
Please try to restore

Suggested fix:
I am not sure.

Files for this bug are too large. They have been uploaded (or are being at this second) to the FTP space.

File name is bug 25384.tar.gz

Hope this helps

Thank you for the bug report. I was unable to extract your tar.gz file
anyway please verify if you don't have a mix of letter case in the tables
and columns names; I recommend you to use on Windows lowercase and then
backup and restore on Linux. Also avoid to backup the information_schema.
Thanks in advance

Hi,

The problem was related to the backup of the proceedures and it was related to case, I was working on it last night.

Basically the backup had different references to tables in different cases. I edited the SQL file and changed the cases (it only happned in a couple of places). I would therefore think that you can colse this bug, it is probably not important enough to warrant time and/or is not a bug.