很多時候因為 MySQL 數據庫不能啟動而造成數據無法訪問，但應用的數據通常沒有丟失，只是系統表空間等其它文件損壞了，或者遇到 MySQL 的 bug。

這個時候如果沒有備份，很多人就以為數據丟失了，但實際上大部分時候數據還是有救的。對于 MyISAM 引擎的表空間，直接把對應的數據文件拷貝到一個新的數據庫就行了，數據就可以恢復了。對于 InnoDB 引擎的數據庫表空間可以采用傳輸表空間的方式把數據救回來.前提是MySQL開啟了參數 innodb_file_per_table = 1 獨立表空間文件

當MySQL的數據表空間文件ibdata文件損壞或者是被無修改和刪除，導致MySQL服務重啟失敗。同時MySQL的數據又沒有及時備份，此時如何盡可能多的找回MySQL數據呢？？

for n in `mysql -e 'use db_bbs;show tables;'|sed ’1d’`;do echo $n; mysql -e 'use db_bbs;select count(*) from $n;';done >test.txt

確認MySQL故障前，庫中一共有多少張表：

一共是39張表：

[root@10-10-127-11 ~]# mysql -e 'use db_bbs;show tables;'|sed ’1d’|wc -l392.2、模擬刪除ibdata故障：

刪除ibdata文件（生產環境禁止這么干）

innodb_force_recovery =6 利用MySQL的強制啟動參數來啟動此時的MySQL服務，但是已經是無濟于事。由于是數據表空間文件ibdata文件被刪除了.所以啟動不了此時的MySQL服務。由于此MySQL采用的innodb引擎。而且開啟了獨立表空間參數 innodb_file_per_table = 1 。所以此時可以采用采用傳輸表空間的方式把數據救回來。

首先來創建已經丟失的表結構：

先要在故障的MySQL服務器上 安裝 mysql-utilities。

yum -y install mysql-utilities

使用 mysqlfrm 從 .frm 文件里面找回建表語句:

分析一個 .frm 文件生成建表的語句

mysqlfrm --diagnostic [root@test02 db_bbs]# mysqlfrm --diagnostic /data/mysql/data/db_bbs/t_admin.frm |grep -v '^#'CREATE TABLE `db_bbs`.`t_admin` ( `f_id` int(4) NOT NULL AUTO_INCREMENT, `f_type` tinyint(1) NOT NULL, `f_username` varchar(80) NOT NULL, `f_password` varchar(80) NOT NULL, `f_nick_name` varchar(80) NOT NULL, `f_real_name` varchar(80) NOT NULL, `f_create_time` bigint(4) NOT NULL, `f_update_time` bigint(4) NOT NULL, `f_last_login_time` bigint(4) DEFAULT NULL, `f_last_login_ip` varchar(80) DEFAULT NULL, `f_status` tinyint(1) NOT NULL, PRIMARY KEY `PRIMARY` (`f_id`) USING BTREE) ENGINE=InnoDB ROW_FORMAT = 2;

把全部的建表語句導入到/tmp/create.sql 文件：

[root@test02 ~]# cd /data/mysql/data/db_bbs/[root@test02 db_bbs]# for n in `ls -l /data/mysql/data/db_bbs/*.frm|awk -F ’/’ ’{print $NF}’|xargs -n 40`;do mysqlfrm --diagnostic $n|grep -v '^#' >>/tmp/create.sql;done

把生產的建表語句導入到新MySQL實例庫中:

[root@10-10-127-11 ~]# mysql db_bbs < create.sql ERROR 1064 (42000) at line 2: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ’5’ at line 10

原因是獲取到的建表sql中包含了ROW_FORMAT = 2 這樣的參數導致的###去掉建表語句中的包含ROW_FORMAT = 2, ROW_FORMAT = 5這些字符.重新導入建表語句###

批量替換命令如下:

cat /tmp/create.sql|sed -e ’s/ENGINE=InnoDB ROW_FORMAT = 2;/ENGINE=InnoDB ;/g’|grep ROW_FORMAT |uniq -ccat /tmp/create.sql|sed -e ’s/ENGINE=InnoDB ROW_FORMAT = 5;/ENGINE=InnoDB ;/g’|grep ROW_FORMAT |uniq -csed -i ’s/ENGINE=InnoDB ROW_FORMAT = 2;/ENGINE=InnoDB ;/g’ /tmp/create.sqlsed -i ’s/ENGINE=InnoDB ROW_FORMAT = 5;/ENGINE=InnoDB ;/g’ /tmp/create.sqlcat /tmp/create.sql|grep ROW_FORMAT |uniq -c

導出建表語句到新MySQL實例db_bbs庫報錯字段太長：

[root@10-10-127-11 ~]# mysql db_bbs -f < create.sql ERROR 1074 (42000) at line 232: Column length too big for column ’f_content’ (max = 16383); use BLOB or TEXT insteadERROR 1074 (42000) at line 299: Column length too big for column ’f_desc’ (max = 16383); use BLOB or TEXT insteadERROR 1074 (42000) at line 365: Column length too big for column ’f_body_image’ (max = 16383); use BLOB or TEXT insteadERROR 1074 (42000) at line 406: Column length too big for column ’f_content’ (max = 16383); use BLOB or TEXT insteadERROR 1074 (42000) at line 433: Column length too big for column ’f_summary’ (max = 16383); use BLOB or TEXT instead

修改完字段長度類型，重新導入建表sql到全新的MySQL庫中

[root@10-10-127-11 ~]# mysql db_bbs -f < create.sql [root@10-10-127-11 ~]# [root@10-10-127-11 ~]# [root@10-10-127-11 ~]# mysql -e 'use db_bbs;show tables;'|sed ’1d’|wc -l39

###將新建的MySQL實例的 沒有包括數據的 .ibd 文件拋棄掉，然后再導入故障數據庫的.idb文件###

拋棄掉新建庫的數據.ibd文件：

mysql -e 'show tables from db_bbs' | grep -v Tables_in_db_bbs| while read a; do mysql -e 'ALTER TABLE db_bbs.$a DISCARD TABLESPACE' ;done

[root@10-10-127-11 db_bbs]# ll *.ibd|wc -l39[root@10-10-127-11 db_bbs]# mysql -e 'show tables from db_bbs' | grep -v Tables_in_db_bbs| while read a; do mysql -e 'ALTER TABLE db_bbs.$a DISCARD TABLESPACE' ;done[root@10-10-127-11 db_bbs]# ll *.ibd|wc -lls: cannot access *.ibd: No such file or directory

*可以看到所有的 .idb 文件都已經被拋棄了。然后把舊的有數據的 .ibd 文件拷貝到這個新MySQL實例的 ./data/db_bbs/ 目錄下面，別忘了把屬主改過來：chown mysql. ，再把這些數據文件 import 到數據庫中**。

[root@test02 db_bbs]# scp *.ibd root@10.10.127.11:/data/mysql/data/db_bbs/root@10.10.127.11’s password: browse_record.ibd100% 100MB 50.0MB/s 00:02 t_admin.ibd ................

[root@10-10-127-11 db_bbs]# ll *.ibd|wc -l39[root@10-10-127-11 db_bbs]# ll *.ibd-rw-r----- 1 root root 104857600 Mar 14 21:56 browse_record.ibd-rw-r----- 1 root root 98304 Mar 14 21:56 t_admin.ibd-rw-r----- 1 root root 98304 Mar 14 21:56 t_anonymous_code.ibd-rw-r----- 1 root root 98304 Mar 14 21:56 t_apply.ibd-rw-r----- 1 root root 9437184 Mar 14 21:56 t_attach.ibd-rw-r----- 1 root root 147456 Mar 14 21:56 t_banner.ibd-rw-r----- 1 root root 163840 Mar 14 21:56 t_banner_log.ibd-rw-r----- 1 root root 114688 Mar 14 21:56 t_black_ip.ibd-rw-r----- 1 root root 98304 Mar 14 21:56 t_black_user.ibd-rw-r----- 1 root root 98304 Mar 14 21:56 t_block_userbaseinfo.ibd-rw-r----- 1 root root 98304 Mar 14 21:56 t_collect.ibd-rw-r----- 1 root root 98304 Mar 14 21:56 t_country_code.ibd-rw-r----- 1 root root 163840 Mar 14 21:56 t_ct_goods.ibd-rw-r----- 1 root root 131072 Mar 14 21:56 t_ct_goods_record.ibd-rw-r----- 1 root root 9437184 Mar 14 21:56 t_ct_integral.ibd-rw-r----- 1 root root 46137344 Mar 14 21:56 t_ct_integral_record.ibd-rw-r----- 1 root root 27262976 Mar 14 21:56 t_ct_news.ibd-rw-r----- 1 root root 9437184 Mar 14 21:56 t_ct_order.ibd-rw-r----- 1 root root 98304 Mar 14 21:56 t_feedback.ibd-rw-r----- 1 root root 98304 Mar 14 21:56 t_lexicon.ibd-rw-r----- 1 root root 327680 Mar 14 21:56 t_logs.ibd-rw-r----- 1 root root 98304 Mar 14 21:56 t_manage.ibd-rw-r----- 1 root root 98304 Mar 14 21:56 t_module.ibd-rw-r----- 1 root root 9437184 Mar 14 21:56 t_post_extend.ibd-rw-r----- 1 root root 12582912 Mar 14 21:56 t_post.ibd-rw-r----- 1 root root 98304 Mar 14 21:56 t_post_video.ibd-rw-r----- 1 root root 98304 Mar 14 21:56 t_realtime_message.ibd-rw-r----- 1 root root 98304 Mar 14 21:56 t_recommend.ibd-rw-r----- 1 root root 46137344 Mar 14 21:56 t_reply.ibd-rw-r----- 1 root root 98304 Mar 14 21:56 t_reward.ibd-rw-r----- 1 root root 196608 Mar 14 21:56 t_sensitive_word.ibd-rw-r----- 1 root root 98304 Mar 14 21:56 t_system_message.ibd-rw-r----- 1 root root 9437184 Mar 14 21:56 t_userbaseinfo.ibd-rw-r----- 1 root root 344064 Mar 14 21:56 t_userextendinfo.ibd-rw-r----- 1 root root 12582912 Mar 14 21:56 t_user_health.ibd-rw-r----- 1 root root 98304 Mar 14 21:56 t_user_message.ibd-rw-r----- 1 root root 442368 Mar 14 21:56 t_user_read_module_log.ibd-rw-r----- 1 root root 17825792 Mar 14 21:56 t_viewpoint.ibd-rw-r----- 1 root root 114688 Mar 14 21:56 t_white_ip.ibd[root@10-10-127-11 db_bbs]# chown mysql.mysql *.ibdmysql -e 'show tables from db_bbs' | grep -v Tables_in_db_bbs| while read a; do mysql -e 'ALTER TABLE db_bbs.$a import TABLESPACE' ;done

導入每個表的表空間時，出現個別表報錯：

[root@10-10-127-11 db_bbs]# mysql -e 'show tables from db_bbs' | grep -v Tables_in_db_bbs| while read a; do mysql -e 'ALTER TABLE db_bbs.$a import TABLESPACE' ;done ERROR 1808 (HY000) at line 1: Schema mismatch (Table has ROW_TYPE_DYNAMIC row format, .ibd file has ROW_TYPE_COMPACT row format.)

校驗表文件，發現只有browse_record表導入獨立表表空間時報錯導致此表恢復數據失敗

[root@10-10-127-11 db_bbs]# mysqlcheck -c db_bbsdb_bbs.browse_recordWarning : InnoDB: Tablespace has been discarded for table ’browse_record’Error : Tablespace has been discarded for table ’browse_record’error : Corruptdb_bbs.t_admin OKdb_bbs.t_anonymous_code OKdb_bbs.t_apply OKdb_bbs.t_attach OKdb_bbs.t_banner OKdb_bbs.t_banner_logOKdb_bbs.t_black_ip OKdb_bbs.t_black_userOKdb_bbs.t_block_userbaseinfo OKdb_bbs.t_collect OKdb_bbs.t_country_code OKdb_bbs.t_ct_goods OKdb_bbs.t_ct_goods_record OKdb_bbs.t_ct_integralOKdb_bbs.t_ct_integral_record OKdb_bbs.t_ct_news OKdb_bbs.t_ct_order OKdb_bbs.t_feedback OKdb_bbs.t_lexicon OKdb_bbs.t_logs OKdb_bbs.t_manage OKdb_bbs.t_module OKdb_bbs.t_post OKdb_bbs.t_post_extendOKdb_bbs.t_post_videoOKdb_bbs.t_realtime_message OKdb_bbs.t_recommend OKdb_bbs.t_reply OKdb_bbs.t_reward OKdb_bbs.t_sensitive_word OKdb_bbs.t_system_message OKdb_bbs.t_user_healthOKdb_bbs.t_user_message OKdb_bbs.t_user_read_module_log OKdb_bbs.t_userbaseinfo OKdb_bbs.t_userextendinfo OKdb_bbs.t_viewpoint OKdb_bbs.t_white_ip OK

上面的browse_record 表恢復失敗 報錯解決辦法如下：

參考：https://blog.csdn.net/weixin_30607659/article/details/94987901

刪除導入到新MySQL實例的表browse_record，然后執行下面的建表語句，新建browse_record表：

CREATE TABLE `browse_record` ( `id` int(4) unsigned NOT NULL AUTO_INCREMENT, `post_id` int(4) unsigned NOT NULL, `user_id` int(4) unsigned NOT NULL, `status` tinyint(1) unsigned NOT NULL, `update_time` bigint(4) unsigned NOT NULL, `create_time` bigint(4) unsigned NOT NULL, PRIMARY KEY (`id`) USING BTREE, KEY `browse` (`post_id`,`user_id`) USING BTREE) ENGINE=InnoDB DEFAULT CHARSET=utf8mb4 row_format=compact;

提示：如果在新MySQL實例單獨刪除表browse_record，刪除失敗的話，那就直接drop掉新MySQL實例上的db_bbs庫，重新導入db_bbs所有表的建表語句，然后再執行下面的命令：

mysql -e 'show tables from db_bbs' | grep -v Tables_in_db_bbs| while read a; do mysql -e 'ALTER TABLE db_bbs.$a DISCARD TABLESPACE' ;done

重新導入表空間到新實例MySQL中:

[root@10-10-127-11 db_bbs]# mysql -e 'show tables from db_bbs' | grep -v Tables_in_db_bbs| while read a; do mysql -e 'ALTER TABLE db_bbs.$a import TABLESPACE' ;done[root@10-10-127-11 db_bbs]#

到此處數據修復完成

校驗MySQL db_bbs庫中的表：

[root@10-10-127-11 db_bbs]# mysqlcheck -c db_bbsdb_bbs.browse_recordOKdb_bbs.t_admin OKdb_bbs.t_anonymous_code OKdb_bbs.t_apply OKdb_bbs.t_attach OKdb_bbs.t_banner OKdb_bbs.t_banner_logOKdb_bbs.t_black_ip OKdb_bbs.t_black_userOKdb_bbs.t_block_userbaseinfo OKdb_bbs.t_collect OKdb_bbs.t_country_code OKdb_bbs.t_ct_goods OKdb_bbs.t_ct_goods_record OKdb_bbs.t_ct_integralOKdb_bbs.t_ct_integral_record OKdb_bbs.t_ct_news OKdb_bbs.t_ct_order OKdb_bbs.t_feedback OKdb_bbs.t_lexicon OKdb_bbs.t_logs OKdb_bbs.t_manage OKdb_bbs.t_module OKdb_bbs.t_post OKdb_bbs.t_post_extendOKdb_bbs.t_post_videoOKdb_bbs.t_realtime_message OKdb_bbs.t_recommend OKdb_bbs.t_reply OKdb_bbs.t_reward OKdb_bbs.t_sensitive_word OKdb_bbs.t_system_message OKdb_bbs.t_user_healthOKdb_bbs.t_user_message OKdb_bbs.t_user_read_module_log OKdb_bbs.t_userbaseinfo OKdb_bbs.t_userextendinfo OKdb_bbs.t_viewpoint OKdb_bbs.t_white_ip OK2.4、獲取導入到新MySQL實例db_bbs庫中表記錄和和原來的庫test.txt表記錄文件對比

[root@10-10-127-11 ~]# for n in `mysql -e 'use db_bbs;show tables;'|sed ’1d’`;do echo $n; mysql -e 'use db_bbs;select count(*) from $n;';done >test.txt11

和原來的庫test.txt表記錄文件對比。

[root@test02 ~]# vimdiff test.txt11 test.txt

表記錄完全一致到此處MySQL的數據修復完畢

參考資料：https://mp.weixin.qq.com/s/r3KTPsFay292JnO0lgTLUghttps://www.cnblogs.com/jiangxu67/p/4744283.htmlhttps://blog.csdn.net/Sonny_alice/article/details/80198200https://www.cnblogs.com/jiangxu67/p/4744283.html

到此這篇關于mysql5.7.33誤刪除ibdata文件找回數據的方法的文章就介紹到這了,更多相關mysql誤刪ibdata內容請搜索好吧啦網以前的文章或繼續瀏覽下面的相關文章希望大家以后多多支持好吧啦網！