Tell me more ×
Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

My MySQL database server crashed but I managed to recover copies of the ibdata1 and .frm files.

I have followed instructions, including some from this site, that say to do a clean install and overwrite the new ibdata1 and .frm files with the old ones.

I have also tried forcing InnoDB recovery with innodb_force_recovery=6 but no success yet. I am guessing that my ibdata1 file is corrupt. The most recent backup I have is like a month old and no good for my purposes.

Anymore ideas on how I could recover my database(s)?

Here's the important part of my error log:

130322 11:41:15 [Note] Plugin 'FEDERATED' is disabled.
130322 11:41:15 InnoDB: The InnoDB memory heap is disabled
130322 11:41:15 InnoDB: Mutexes and rw_locks use Windows interlocked functions
130322 11:41:15 InnoDB: Compressed tables use zlib 1.2.3
130322 11:41:15 InnoDB: Initializing buffer pool, size = 44.0M
130322 11:41:15 InnoDB: Completed initialization of buffer pool
130322 11:41:15  InnoDB: Log file .\ib_logfile0 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile0 size to 22 MB
InnoDB: Database physically writes the file full: wait...
130322 11:41:15  InnoDB: Log file .\ib_logfile1 did not exist: new to be created
InnoDB: Setting log file .\ib_logfile1 size to 22 MB
InnoDB: Database physically writes the file full: wait...
130322 11:41:16 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
130322 11:41:17  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
130322 11:41:17  InnoDB: Error: page 7 log sequence number 2452699171
InnoDB: is in the future! Current system log sequence number 2452696588.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: for more information.

The "page x log sequence number" part repeats through out the log file for different pages.

share|improve this question
I think posting the relevant parts of the log files & the error messages you're getting (if any) would help people figure out what your exact problem is. Please edit your post with whatever additional details you can give. – Mat Mar 16 at 15:21

migrated from stackoverflow.com Mar 16 at 9:02

Know someone who can answer? Share a link to this question via email, Google+, Twitter, or Facebook.

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.