MySQL Bugs: #16200: mysql_convert_table_format not working for one database

Bug #16200	mysql_convert_table_format not working for one database
Submitted:	4 Jan 2006 18:56	Modified:	6 Jan 2006 22:06
Reporter:	[ name withheld ]	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server	Severity:	S3 (Non-critical)
Version:	4.1.16	OS:	Linux (Red Hat Linux 9.0)
Assigned to:		CPU Architecture:	Any

Description:
I upgraded from 3.23.58 to 4.1 and MOST of my databases were able to be converted, but one particular one still gets an error

[root]# mysql_convert_table_format db4
Converting tables:
converting hits
Can't convert hits: Error Can't find file: 'hits' (errno: 2)

I cannot go into mysql and do the ALTER TABLE command either

mysql> use db4;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> alter table hits type=MyISAM;
ERROR 1017 (HY000): Can't find file: 'hits' (errno: 2)
mysql>

Help?

How to repeat:
Unknown how to repeat.
I can repeat it ad infinitum on my system.

Suggested fix:
Asking for suggestions.

> perror 2
OS error code   2:  No such file or directory

what type of table (myisam, innodb, bdb ...) was 'hits' in the original setup?

All tables were MySQL ISAM in database.

What is the result of SHOW CREATE TABLE hits statement? Have you tried to check this table in 3.23.58 with isamchk utility?

mysql> use db4;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A

Database changed
mysql> show create table hits;
ERROR 1017 (HY000): Can't find file: 'hits' (errno: 2)

I do not have 3.x on my system any longer, I have upgraded to 4.1.16. The isamchk utility is not on my system. A /usr/bin/myisamchk utility exists, but I'm reasonably sure that's not what you're asking about.

Do you remember something about that table? Column data types, number of rows etc.? Do you have error log from your previous 3.23.x server? 

Sorry for so many questions, but we need a repeatable sequence of steps to reproduce the problem to be able to fix it.

I went ahead and loaded a spare desktop with FC4, loaded old 3.23.58 binaries on it, FTP'd the tables from the db4 database over to the spare, ran the convert (which worked), and then FTP'd them back.

So, this bug report can be closed. 

Must have been just a freak of the system I was working on.