Bug #28645 MYSQL 4.1 tables "don't exist" under MYSQL 5.0.41
Submitted: 24 May 2007 10:15 Modified: 28 Jun 2007 12:52
Reporter: Fraser Ray Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Server: Backup Severity:S2 (Serious)
Version:5.0.41 OS:Microsoft Windows
Assigned to: CPU Architecture:Any

[24 May 2007 10:15] Fraser Ray
Description:
I backed up raw sql files (.frm etc)(mysql 4.1) before re installing windows.  I install MYSQL 5.0.41.  Using MYSQL Administrator, under backup, it says 'table *** doesnt exist'

SQL dump attached

How to repeat:
MYSQL Administrator, under backup
[24 May 2007 23:14] MySQL Verification Team
Thank you for the bug report. The dump file you have attached just has
the create/use database commands and some empty lines. I am able to
create backup files with MA and 5.0.41, please elaborate what are you
reporting.
[24 May 2007 23:29] MySQL Verification Team
You did a binary copy of the data files version 4.1 and then copied
them in the data directory of new 5.0.41 install?. If yes these tables
are MyISAM or InnoDB?. Thanks in advance.
[25 May 2007 4:47] Fraser Ray
Hey;

I copied the folder "data" using windows explorer through my lan.  I then installed mysql 5 and copied the data folder back.
[25 May 2007 6:18] Fraser Ray
this is what MYSQL Administrator says:

Attachment: mysql.JPG (image/pjpeg, text), 158.63 KiB.

[28 May 2007 12:52] MySQL Verification Team
Thank you for the feedback. Could you please read the below Manual's chapter:

http://dev.mysql.com/doc/refman/5.0/en/upgrading-from-4-1.html

The recommended way to upgrade from 4.1 to 5.0 is to create a backup file
of 4.1 using the tool mysqldump or MA and then restore it with 5.0.
Thanks in advance.
[28 Jun 2007 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".