Quantcast
Channel: MySQL Forums - InnoDB
Viewing all articles
Browse latest Browse all 1957

Can't drop/replace lost table (no replies)

$
0
0
After cleanly restarting a MySQL 5.5.19 server, a few InnoDB tables could no longer be accessed with an error about missing data files in the log (there were no errors during the shutdown/startup). At first I tried setting innodb_file_per_table to 0 (I had enabled it previously but after most of the tables already existed), and some but not all of the previously innaccessible tables were accessible again. I decided to restore the remaining bad tables from a backup, but there is one that I can't seem to replace:

- I tried a simple "drop table" but I get an error saying that the table doesn't exist.
- I tried to check/repair the table, but I get the same error saying that it doesn't exist.
- I tried to delete the .frm file and create a new table in its place (after flushing tables) and I get an error saying the table already exists.
- I tried creating a dummy table and copying its .frm in place of the broken table, but after dropping the table I still can't create a new one with the same name.
- Tried recreating the table structure and copying that .frm in place of the existing one of the broken table, but I still get "table doesn't exist" when I try to access it.
- My last try was to delete the .frm and replace it with a dummy MyISAM table. I noticed that I could rename that table from and back to the broken table's name, but I still get the "table already exists" error if I drop the table and create an InnoDB table in its place or change the MyISAM table engine type to InnoDB.

Anyone have any other ideas?

Viewing all articles
Browse latest Browse all 1957

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>