Hi Christian, Christian Hammers <[EMAIL PROTECTED]> writes:
> On 2005-03-10 Marc Packenius wrote: >> After upgrading from 4.0.22 to 4.0.23 on a sarge, MySQL gave error >> messages like "Cannot open file '<tablename>.InnoDB' (error: 1)" when >> trying to access certain InnoDB tables. >> >> Upstream bug: >> http://lists.mysql.com/internals/22785 > The relevant code snippets do not exist in 4.0.23. Sure that this is > the right link? That's the fix in the 4.1 codebase. The InnoDB developers pointed to this when I asked about the problem with 4.0.22->4.0.23. I'm not sure how to find the fix for 4.0.23, but the problem is apparently the same. Here's the error message 4.0.23 will produce when it tries to access a table which can be opened fine with 4.0.22: mysqld[388]: 050309 0:02:27 /usr/sbin/mysqld: Kann Datei '<table name>.InnoDB' nicht oeffnen. (Fehler: 1) mysqld[388]: 050309 0:02:36 InnoDB: table <database name>/<table name> is in the new compact format mysqld[388]: InnoDB: of MySQL 5.0.3 or later mysqld[388]: 050309 0:02:36 InnoDB error: mysqld[388]: Cannot find table <database name>/<table name> from the internal data dictionary mysqld[388]: of InnoDB though the .frm file for the table exists. Maybe you mysqld[388]: have deleted and recreated InnoDB data files but have forgotten mysqld[388]: to delete the corresponding .frm files of InnoDB tables, or you mysqld[388]: have moved .frm files to another database? mysqld[388]: Look from section 15.1 of http://www.innodb.com/ibman.html mysqld[388]: how you can resolve the problem. Thanks for looking into this. -- Marc "Backlog" Packenius -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
