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: | |
| Category: | MySQL Server | Severity: | S1 (Critical) |
| Version: | 4.1 | OS: | Any (all) |
| Assigned to: | CPU Architecture: | Any |
[12 Feb 2003 16:14]
Georg Richter
[22 Feb 2003 5:35]
jocelyn fournier
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.
[22 Feb 2003 13:29]
jocelyn fournier
I've just figured out this problem also occurs in the latest 4.0.11 bk tree !
[22 Feb 2003 14:07]
Georg Richter
SHOW TABLE STATUS on these tables crashes server in 4.1
[25 Feb 2003 11:32]
Sergei Golubchik
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.
[25 Feb 2003 11:33]
Sergei Golubchik
Oops. This "Quick Fix" field added the first paragraph automatically. I didn't mean it :)
Portions of this website are copyright © 2001, 2002 The PHP Group
Page generated in 0.052 sec. using MySQL 8.4.7-u6-cloud
Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the
respective copyright holders.
It is not reviewed in advance
by Oracle and does not necessarily represent the opinion of
Oracle or any other party.