Bug #3280 | optimize table damaged innodb table! | ||
---|---|---|---|
Submitted: | 24 Mar 2004 4:21 | Modified: | 17 Sep 2004 12:29 |
Reporter: | [ name withheld ] | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Embedded Library ( libmysqld ) | Severity: | S2 (Serious) |
Version: | 4.0.16 | OS: | Linux (linux, 2.4) |
Assigned to: | CPU Architecture: | Any |
[24 Mar 2004 4:21]
[ name withheld ]
[24 Mar 2004 9:23]
Heikki Tuuri
Hi! What do you mean by 'optimize table'? For InnoDB, OPTIMIZE TABLE is essentially a null operation and only updates the table stats in the handle. Also, I think InnoDB does not give errors 28, but MyISAM does, if the table is corrupt. Are you sure your tables really are InnoDB type? Use SHOW CREATE TABLE ... to print the table type. Regards, Heikki
[17 Sep 2004 12:29]
Heikki Tuuri
Hi! No feedback in 6 months. Regards, Heikki