Also, you may find that check table/repair table are able to fix the problem. See http://dev.mysql.com/doc/mysql/en/Table_maintenance.html for more information.
Greg On Thursday 12 January 2006 08:28, Greg Fortune wrote: > That looks a little odd. Do isam tables have a .myi file for each table > that stores the indexes? If so, yours appears to be missing. I would > suggest you use mysqldump to dump the table, change the ENGINE= section in > the resulting dump file, and then reload the table and data from that dump > file. > > When upgrading between major versions (4.0, 4.1, 5.0, 5.1, etc), it's > always wise to make a full backup of the data files and a full backup of > the database using mysqldump. The output from mysqldump is just SQL so it > is always the safest route if you run into problems. > > Greg Fortune > > On Wednesday 11 January 2006 13:39, Anne Ramey wrote: > > I have a problem. I had to upgrade to 4.1 yesterday for an application, > > and now I can't convert my old isam tables to myisam: > > ALTER TABLE codes TYPE = MYISAM; > > ERROR 1017 (HY000): Can't find file: 'codes.MYI' (errno: 2) > > and I can't use phpmyadmin because there are isam tables. Is there any > > way to save the data and fix this? I know it should have been done when > > upgrading to 4.0, but for some reason it wasn't. > > > > mysql 4.1, redhat ES3 > > -- > > Anne
pgpvBPtiiNNqf.pgp
Description: PGP signature
