Re: Recovering InnoDB database from ibdata1 ib_logfile0 ib_logfile1 and frm files
Hi Harutyun Martirosyan,
The relevant information is this one:
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 2.
Somehow page 2 (and ff. ?) got corrupted. Page 2 is most probably the "file segment inode" page in the data dictionary. This does not just affect a block of a table but a block of the database data dictionary. So most probably InnoDB cannot read the database at all...
"FILE SEGMENT INODE: Segment inode which is created for each segment in a tablespace."
The solution is /are:
* Do what is written here:
InnoDB: You may have to recover from a backup.
* If your database does not crash and you can dump with innodb_force_recovery > 0, dump your data and reload in a newly created database.
* If this is not possible or if you do not have a backup you can try with some special tools from the web (innodb recovery tools) to rescue your data from the innodb database files...
If you want to send me your innodb files I can try and have a look...
Best regards,
Oli
--
FromDual - Independent and neutral MySQL consulting
Subject
Views
Written By
Posted
10896
March 17, 2010 12:07PM
Re: Recovering InnoDB database from ibdata1 ib_logfile0 ib_logfile1 and frm files
8360
March 17, 2010 05:49PM
5314
March 18, 2010 03:06PM
5420
March 26, 2010 12:53PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.