Why didn't InnoDB table recover?

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.

Questions:
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--
Sam
SAbboushiAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Patrick BogersDatacenter platform engineer LindowsCommented:
Hi

1) there could be queries present in memory but not yet written to the database in time the machine crashed.
2) No there is not, chrashes while running an active DB surely can corrupt open databases.
3) From the error i read "ltbhouston"."sellers" is corrupted. The name implifies that this table stores a list of seller-contacts, how much can change in one day? I tend to believe not that much but off course i cannot look into the tables.

Else you could try to run innodb on the corrupted database and try to dump the sellers table to a file, just give it a chance. How to is described here.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
MySQL Server

From novice to tech pro — start learning today.