MySQL异常恢复之无主键情况下innodb数据恢复的方法
程序员文章站
2024-02-22 14:29:16
本文讲述了mysql异常恢复之无主键情况下innodb数据恢复的方法。分享给大家供大家参考，具体如下：
在mysql的innodb引擎的数据库异常恢复中,一般都要求有主键...
本文讲述了mysql异常恢复之无主键情况下innodb数据恢复的方法。分享给大家供大家参考，具体如下：
在mysql的innodb引擎的数据库异常恢复中,一般都要求有主键或者唯一index,其实这个不是必须的,当没有index信息之时,可以在整个表级别的index_id进行恢复
创建模拟表—无主键
mysql> create table `t1` ( -> `messageid` varchar(30) character set utf8 not null, -> `tokenid` varchar(20) character set utf8 not null, -> `mobile` varchar(14) character set utf8 default null, -> `msgformat` int(1) not null, -> `msgcontent` varchar(1000) character set utf8 default null, -> `scheduledate` timestamp not null default '0000-00-00 00:00:00', -> `deliverstate` int(1) default null, -> `deliverdtime` timestamp not null default '0000-00-00 00:00:00' -> ) engine=innodb default charset=utf8; query ok, 0 rows affected (0.00 sec) mysql> insert into t1 select * from sms_service.sms_send_record; query ok, 11 rows affected (0.00 sec) records: 11 duplicates: 0 warnings: 0 ………… mysql> insert into t1 select * from t1; query ok, 81664 rows affected (2.86 sec) records: 81664 duplicates: 0 warnings: 0 mysql> insert into t1 select * from t1; query ok, 163328 rows affected (2.74 sec) records: 163328 duplicates: 0 warnings: 0 mysql> select count(*) from t1; +----------+ | count(*) | +----------+ | 326656 | +----------+ 1 row in set (0.15 sec)
解析innodb文件
[root@web103 mysql_recovery]# rm -rf pages-ibdata1/ [root@web103 mysql_recovery]# ./stream_parser -f /var/lib/mysql/ibdata1 opening file: /var/lib/mysql/ibdata1 file information: id of device containing file: 2049 inode number: 1344553 protection: 100660 (regular file) number of hard links: 1 user id of owner: 27 group id of owner: 27 device id (if special file): 0 blocksize for filesystem i/o: 4096 number of blocks allocated: 463312 time of last access: 1440819443 sat aug 29 11:37:23 2015 time of last modification: 1440819463 sat aug 29 11:37:43 2015 time of last status change: 1440819463 sat aug 29 11:37:43 2015 total size, in bytes: 236978176 (226.000 mib) size to process: 236978176 (226.000 mib) opening file: /var/lib/mysql/ibdata1 file information: id of device containing file: 2049 inode number: 1344553 protection: 100660 (regular file) number of hard links: 1 user id of owner: 27 group id of owner: 27 device id (if special file): 0 blocksize for filesystem i/o: 4096 number of blocks allocated: 463312 opening file: /var/lib/mysql/ibdata1 file information: time of last access: 1440819443 sat aug 29 11:37:23 2015 time of last modification: 1440819463 sat aug 29 11:37:43 2015 id of device containing file: 2049 inode number: 1344553 protection: 100660 time of last status change: 1440819463 sat aug 29 11:37:43 2015 total size, in bytes: 236978176 (226.000 mib) size to process: 236978176 (226.000 mib) opening file: /var/lib/mysql/ibdata1 file information: id of device containing file: 2049 inode number: 1344553 protection: 100660 (regular file) number of hard links: 1 user id of owner: 27 group id of owner: 27 device id (if special file): 0 blocksize for filesystem i/o: 4096 number of blocks allocated: 463312 time of last access: 1440819443 sat aug 29 11:37:23 2015 time of last modification: 1440819463 sat aug 29 11:37:43 2015 time of last status change: 1440819463 sat aug 29 11:37:43 2015 total size, in bytes: 236978176 (226.000 mib) size to process: 236978176 (226.000 mib) (regular file) number of hard links: 1 user id of owner: 27 group id of owner: 27 device id (if special file): 0 blocksize for filesystem i/o: 4096 number of blocks allocated: 463312 time of last access: 1440819443 sat aug 29 11:37:23 2015 time of last modification: 1440819463 sat aug 29 11:37:43 2015 time of last status change: 1440819463 sat aug 29 11:37:43 2015 total size, in bytes: 236978176 (226.000 mib) size to process: 236978176 (226.000 mib) opening file: /var/lib/mysql/ibdata1 file information: id of device containing file: 2049 inode number: 1344553 protection: 100660 (regular file) number of hard links: 1 user id of owner: 27 group id of owner: 27 device id (if special file): 0 blocksize for filesystem i/o: 4096 number of blocks allocated: 463312 time of last access: 1440819443 sat aug 29 11:37:23 2015 time of last modification: 1440819463 sat aug 29 11:37:43 2015 time of last status change: 1440819463 sat aug 29 11:37:43 2015 total size, in bytes: 236978176 (226.000 mib) size to process: 236978176 (226.000 mib) opening file: /var/lib/mysql/ibdata1 file information: id of device containing file: 2049 inode number: 1344553 protection: 100660 (regular file) number of hard links: 1 user id of owner: 27 group id of owner: 27 device id (if special file): 0 blocksize for filesystem i/o: 4096 number of blocks allocated: 463312 time of last access: 1440819443 sat aug 29 11:37:23 2015 time of last modification: 1440819463 sat aug 29 11:37:43 2015 time of last status change: 1440819463 sat aug 29 11:37:43 2015 opening file: /var/lib/mysql/ibdata1 file information: id of device containing file: 2049 inode number: 1344553 protection: 100660 (regular file) number of hard links: 1 user id of owner: 27 group id of owner: 27 device id (if special file): 0 blocksize for filesystem i/o: 4096 number of blocks allocated: 463312 total size, in bytes: 236978176 (226.000 mib) size to process: 236978176 (226.000 mib) time of last access: 1440819443 sat aug 29 11:37:23 2015 time of last modification: 1440819463 sat aug 29 11:37:43 2015 time of last status change: 1440819463 sat aug 29 11:37:43 2015 total size, in bytes: 236978176 (226.000 mib) size to process: 236978176 (226.000 mib) opening file: /var/lib/mysql/ibdata1 file information: id of device containing file: 2049 inode number: 1344553 protection: 100660 (regular file) number of hard links: 1 user id of owner: 27 group id of owner: 27 device id (if special file): 0 blocksize for filesystem i/o: 4096 number of blocks allocated: 463312 time of last access: 1440819465 sat aug 29 11:37:45 2015 time of last modification: 1440819463 sat aug 29 11:37:43 2015 time of last status change: 1440819463 sat aug 29 11:37:43 2015 total size, in bytes: 236978176 (226.000 mib) size to process: 236978176 (226.000 mib) all workers finished in 0 sec
恢复数据字典
[root@web103 mysql_recovery]# ./recover_dictionary.sh generating dictionary tables dumps... ok creating test database ... ok creating dictionary tables in database test: sys_tables ... ok sys_columns ... ok sys_indexes ... ok sys_fields ... ok all ok loading dictionary tables data: sys_tables ... 48 recs ok sys_columns ... 397 recs ok sys_indexes ... 67 recs ok sys_fields ... 89 recs ok all ok
分析数据字典,找出来index_id
这里需要注意对于没有主键的表恢复,我们对应的类型是gen_clust_index
mysql> select * from sys_tables where name='test/t1'; +----------------------------------------+-----+-------------+------+--------+---------+--------------+-------+ | name | id | n_cols | type | mix_id | mix_len | cluster_name | space | +----------------------------------------+-----+-------------+------+--------+---------+--------------+-------+ | test/t1 | 100 | 8 | 1 | 0 | 0 | | 0 | +----------------------------------------+-----+-------------+------+--------+---------+--------------+-------+ 40 rows in set (0.00 sec) mysql> select * from sys_indexes where table_id=100; +----------+-----+------------------------------+----------+------+-------+------------+ | table_id | id | name | n_fields | type | space | page_no | +----------+-----+------------------------------+----------+------+-------+------------+ | 100 | 119 | gen_clust_index | 0 | 1 | 0 | 2951 | +----------+-----+------------------------------+----------+------+-------+------------+ 67 rows in set (0.00 sec)
恢复数据
root@web103 mysql_recovery]# ./c_parser -5f pages-ibdata1/fil_page_index/0000000000000119.page -t dictionary/t1.sql >/tmp/2.txt 2>2.sql [root@web103 mysql_recovery]# more /tmp/2.txt -- page id: 10848, format: compact, records list: valid, expected records: (73 73) 00000002141b 0000009924f2 80000027133548 t1 "82334502212106951" "sdk-bbx-010-18681" "13718311436" 8 "尊敬的用户您好：您的手机验证码为916515如非本人操作，请拨打奥 斯卡客服：400-620-7575。" "2010-01-01 00:00:00" 0 "1970-01-01 07:00:00" 00000002141c 0000009924f2 80000027133558 t1 "82339012756833423" "sdk-bbx-010-18681" "13718311436" 8 "尊敬的用户您好：您的手机验证码为396108如非本人操作，请拨打奥 斯卡客服：400-620-7575。" "2010-01-01 00:00:00" 0 "1970-01-01 07:00:00" 00000002141d 0000009924f2 80000027133568 t1 "8234322198577796" "sdk-bbx-010-18681" "13718311436" 8 "尊敬的用户您好：您的手机验证码为935297如非本人操作，请拨打奥 斯卡客服：400-620-7575。" "2010-01-01 00:00:00" 0 "1970-01-01 07:00:00" 00000002141e 0000009924f2 80000027133578 t1 "10235259536125650" "sdk-bbx-010-18681" "13718311436" 8 "尊敬的用户您好：您的手机验证码为474851如非本人操作，请拨打奥 斯卡客服：400-620-7575。" "2010-01-01 00:00:00" 0 "1970-01-01 07:00:00" 00000002141f 0000009924f2 80000027133588 t1 "10235353811295807" "sdk-bbx-010-18681" "13718311436" 8 "尊敬的用户您好：您的手机验证码为444632如非本人操作，请拨打奥 斯卡客服：400-620-7575。" "2010-01-01 00:00:00" 0 "1970-01-01 07:00:00" 000000021420 0000009924f2 80000027133598 t1 "102354211240398235" "sdk-bbx-010-18681" "13718311436" 8 "尊敬的用户您好：您的手机验证码为478503如非本人操作，请拨打奥 斯卡客服：400-620-7575。" "2010-01-01 00:00:00" 0 "1970-01-01 07:00:00" 000000021421 0000009924f2 800000271335a8 t1 "102354554052884567" "sdk-bbx-010-18681" "13718311436" 8 "尊敬的用户您好：您的手机验证码为216825如非本人操作，请拨打奥 斯卡客服：400-620-7575。" "2010-01-01 00:00:00" 0 "1970-01-01 07:00:00" 000000021422 0000009924f2 800000271335b8 t1 "132213454294519126" "sdk-bbx-010-18681" "13718311436" 8 "尊敬的用户您好：您的手机验证码为854812如非本人操作，请拨打奥 斯卡客服：400-620-7575。" "2010-01-01 00:00:00" 0 "1970-01-01 07:00:00" 000000021423 0000009924f2 800000271335c8 t1 "82329022242584577" "sdk-bbx-010-18681" "13718311436" 8 "尊敬的用户您好：您的手机验证码为253127如非本人操作，请拨打奥 斯卡客服：400-620-7575。" "2010-01-01 00:00:00" 0 "2015-08-26 22:02:17" ………… [root@web103 mysql_recovery]# cat /tmp/2.txt|grep -v "page id:"|wc -l 380731
因为没有主键,使得恢复出来记录可能有一些重复,整体而言,可以较为完美的恢复数据
更多关于mysql相关内容感兴趣的读者可查看本站专题：《mysql日志操作技巧大全》、《mysql事务操作技巧汇总》、《mysql存储过程技巧大全》、《mysql数据库锁相关技巧汇总》及《mysql常用函数大汇总》
希望本文所述对大家mysql数据库计有所帮助。