Solved

Why didn't InnoDB table recover?

Posted on 2014-01-10
1
640 Views
Last Modified: 2014-01-11
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
0
Comment
Question by:SAbboushi
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
1 Comment
 
LVL 22

Accepted Solution

by:
Patrick Bogers earned 500 total points
ID: 39773192
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.
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Popularity Can Be Measured Sometimes we deal with questions of popularity, and we need a way to collect opinions from our clients.  This article shows a simple teaching example of how we might elect a favorite color by letting our clients vote for …
Introduction This article is intended for those who are new to PHP error handling (https://www.experts-exchange.com/articles/11769/And-by-the-way-I-am-New-to-PHP.html).  It addresses one of the most common problems that plague beginning PHP develop…
The Email Laundry PDF encryption service allows companies to send confidential encrypted  emails to anybody. The PDF document can also contain attachments that are embedded in the encrypted PDF. The password is randomly generated by The Email Laundr…
How to Install VMware Tools in Red Hat Enterprise Linux 6.4 (RHEL 6.4) Step-by-Step Tutorial

696 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question