I use MySQL Workbench 6.0 for MySQL 5.6 running on my W7 64 pc.
I was altering a table when my pc crashed. After reboot, I got an error when I tried to run a query on the table that the table didn't exist. Looking in the system log, I found:
InnoDB: table ltbhouston/sellers contains 13 user defined columns in InnoDB, but 12 columns in MySQL. Please check INFORMATION_SCHEMA.INNODB_SYS_COLUMNS and http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how to resolve it
InnoDB: Cannot open table ltbhouston/sellers from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2014-01-10 21:13:10 1b34 InnoDB: table "ltbhouston"."sellers"is corrupted. Please drop the table and recreate
I see in the system log that it took steps to recover from the crash using the bin logs.
1) What could have caused the recovery to fail?
2) Is there something I can reconfigure to make recovery more bulletproof so it can recover the table to prior to the alter table operation (i.e. in the future should something like this happen again)?
3) How can I recover the table so I don't have to lose a day's work by restoring last night's backup? I reviewed the links referenced in the system log, but didn't see how I could use the info to try and recover the table
Thanks for your help--