MySQL Bugs: #66: incorrect information in file host.frm

Bug #66	incorrect information in file host.frm
Submitted:	12 Feb 2003 16:14	Modified:	25 Feb 2003 11:33
Reporter:	Georg Richter	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	4.1	OS:	Any (all)
Assigned to:		CPU Architecture:	Any

Description:
After latest bk pull I can't start mysqld_safe

From err-file:

Fatal error: Can't open privilege tables: Incorrect information in file: './mysql/host.frm'

Also mysql_fix_privileges_table doesn't work anymore, cause you can't start mysqld.

How to repeat:

Suggested fix:
remove mysql db, run mysql_install_db and add all settings again :(

It seems the problem is due to the fact MySQL-4.1 doesn't support anymore the "old" FRM 4.0 file format :

e.g. :
SHOW CREATE TABLE forumconthardwarefr13;
ERROR 1033: Incorrect information in file:
'./forum_hardwarefr/forumconthardwarefr13.frm'

forumconthardwarefr13.frm uses the old FRM 4.0 file format.

After performing an "alter table forumconthardwarefr13 type=myisam" under mysql-4.0.11, the table uses now the new extended FRM 4.0 file format, and MySQL-4.1 is able to read the table again.

I've just figured out this problem also occurs in the latest 4.0.11 bk tree !

SHOW TABLE STATUS on these tables crashes server in 4.1

Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.mysql.com/documentation/ and the instructions on
how to report a bug at http://bugs.mysql.com/how-to-report.php

SHOW TABLE STATUS crash - it's ticket #93.

wrong frm format - these frm files (FRM_VER+2) were created in 4.1 - and in some intermediate version. Neither 4.0 nor 4.1-latest can generate these files. It's true that 4.0.9 can read these files, and 4.0.11 cannot. Still it's a non-issue.

Oops. This "Quick Fix" field added the first paragraph automatically. I didn't mean it :)