slider

MySQL starts with innodb_force_recovery, but tables are still not accessible

  1. Backup and Data Recovery for MySQL
  2. MySQL starts with innodb_force_recovery, but tables are still not accessible
0
0

On behalf of a user:

“My DB started while giving force recovery but i can only see table names not data. Can you please help me?”

  • You must to post comments
0
0
  1. First of all, make sure you try to start MySQL with all values of innodb_force_recovery. From 1 till 6.
  2. If MySQL starts it’s better to dump tables one by one. Write small script that iterates over database and  table names. Then dump each table with `mysqldump –skip-lock-tables $database $table`. If MySQL crashes on some table, fear not. Start it again and go on with rest other tables.
  3. By now you should have dumps of some tables. Some table cannot be dumped because MySQL creases when you access them. In this case grab *.ibd and .*frm files and go to https://recovery.twindb.com/
  4. First, you need to recover schema. Archive all .frm tables into a .zip or .tar.gz archive and upload it on “Recover Structure” -> “from .frm file”. You will get the structure back.Screenshot 2016-07-05 00.44.09
  5. Once you have the structure you can recover tables from .ibd files. Go to “Recover table” -> “corrupted .ibd file” and upload one .ibd file. Paste its structure as well. Don’t forget to specify MySQL version, it’s important.Screenshot 2016-07-05 00.47.53
  6. The system will try to recover the table and will show you result. If you happy with it you can download the dump. Please note this service is not free. Check our prices on https://recovery.twindb.com

 

 

  • You must to post comments
Showing 1 result
Your Answer

Please first to submit.