时间:2021-05-23
本文讲述了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: 0mysql> insert into t1 select * from t1;Query OK, 163328 rows affected (2.74 sec)Records: 163328 Duplicates: 0 Warnings: 0mysql> 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/ibdata1File information:ID of device containing file: 2049inode number: 1344553protection: 100660 (regular file)number of hard links: 1user ID of owner: 27group ID of owner: 27device ID (if special file): 0blocksize for filesystem I/O: 4096number of blocks allocated: 463312time of last access: 1440819443 Sat Aug 29 11:37:23 2015time of last modification: 1440819463 Sat Aug 29 11:37:43 2015time of last status change: 1440819463 Sat Aug 29 11:37:43 2015total size, in bytes: 236978176 (226.000 MiB)Size to process: 236978176 (226.000 MiB)Opening file: /var/lib/mysql/ibdata1File information:ID of device containing file: 2049inode number: 1344553protection: 100660 (regular file)number of hard links: 1user ID of owner: 27group ID of owner: 27device ID (if special file): 0blocksize for filesystem I/O: 4096number of blocks allocated: 463312Opening file: /var/lib/mysql/ibdata1File information:time of last access: 1440819443 Sat Aug 29 11:37:23 2015time of last modification: 1440819463 Sat Aug 29 11:37:43 2015ID of device containing file: 2049inode number: 1344553protection: 100660 time of last status change: 1440819463 Sat Aug 29 11:37:43 2015total size, in bytes: 236978176 (226.000 MiB)Size to process: 236978176 (226.000 MiB)Opening file: /var/lib/mysql/ibdata1File information:ID of device containing file: 2049inode number: 1344553protection: 100660 (regular file)number of hard links: 1user ID of owner: 27group ID of owner: 27device ID (if special file): 0blocksize for filesystem I/O: 4096number of blocks allocated: 463312time of last access: 1440819443 Sat Aug 29 11:37:23 2015time of last modification: 1440819463 Sat Aug 29 11:37:43 2015time of last status change: 1440819463 Sat Aug 29 11:37:43 2015total size, in bytes: 236978176 (226.000 MiB)Size to process: 236978176 (226.000 MiB)(regular file)number of hard links: 1user ID of owner: 27group ID of owner: 27device ID (if special file): 0blocksize for filesystem I/O: 4096number of blocks allocated: 463312time of last access: 1440819443 Sat Aug 29 11:37:23 2015time of last modification: 1440819463 Sat Aug 29 11:37:43 2015time of last status change: 1440819463 Sat Aug 29 11:37:43 2015total size, in bytes: 236978176 (226.000 MiB)Size to process: 236978176 (226.000 MiB)Opening file: /var/lib/mysql/ibdata1File information:ID of device containing file: 2049inode number: 1344553protection: 100660 (regular file)number of hard links: 1user ID of owner: 27group ID of owner: 27device ID (if special file): 0blocksize for filesystem I/O: 4096number of blocks allocated: 463312time of last access: 1440819443 Sat Aug 29 11:37:23 2015time of last modification: 1440819463 Sat Aug 29 11:37:43 2015time of last status change: 1440819463 Sat Aug 29 11:37:43 2015total size, in bytes: 236978176 (226.000 MiB)Size to process: 236978176 (226.000 MiB)Opening file: /var/lib/mysql/ibdata1File information:ID of device containing file: 2049inode number: 1344553protection: 100660 (regular file)number of hard links: 1user ID of owner: 27group ID of owner: 27device ID (if special file): 0blocksize for filesystem I/O: 4096number of blocks allocated: 463312time of last access: 1440819443 Sat Aug 29 11:37:23 2015time of last modification: 1440819463 Sat Aug 29 11:37:43 2015time of last status change: 1440819463 Sat Aug 29 11:37:43 2015Opening file: /var/lib/mysql/ibdata1File information:ID of device containing file: 2049inode number: 1344553protection: 100660 (regular file)number of hard links: 1user ID of owner: 27group ID of owner: 27device ID (if special file): 0blocksize for filesystem I/O: 4096number of blocks allocated: 463312total 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 2015time of last modification: 1440819463 Sat Aug 29 11:37:43 2015time of last status change: 1440819463 Sat Aug 29 11:37:43 2015total size, in bytes: 236978176 (226.000 MiB)Size to process: 236978176 (226.000 MiB)Opening file: /var/lib/mysql/ibdata1File information:ID of device containing file: 2049inode number: 1344553protection: 100660 (regular file)number of hard links: 1user ID of owner: 27group ID of owner: 27device ID (if special file): 0blocksize for filesystem I/O: 4096number of blocks allocated: 463312time of last access: 1440819465 Sat Aug 29 11:37:45 2015time of last modification: 1440819463 Sat Aug 29 11:37:43 2015time of last status change: 1440819463 Sat Aug 29 11:37:43 2015total 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... OKCreating test database ... OKCreating dictionary tables in database test:SYS_TABLES ... OKSYS_COLUMNS ... OKSYS_INDEXES ... OKSYS_FIELDS ... OKAll OKLoading dictionary tables data:SYS_TABLES ... 48 recs OKSYS_COLUMNS ... 397 recs OKSYS_INDEXES ... 67 recs OKSYS_FIELDS ... 89 recs OKAll 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 -l380731因为没有主键,使得恢复出来记录可能有一些重复,整体而言,可以较为完美的恢复数据
更多关于MySQL相关内容感兴趣的读者可查看本站专题:《MySQL日志操作技巧大全》、《MySQL事务操作技巧汇总》、《MySQL存储过程技巧大全》、《MySQL数据库锁相关技巧汇总》及《MySQL常用函数大汇总》
希望本文所述对大家MySQL数据库计有所帮助。
声明:本页内容来源网络,仅供用户参考;我单位不保证亦不表示资料全面及准确无误,也不保证亦不表示这些资料为最新信息,如因任何原因,本网内容或者用户因倚赖本网内容造成任何损失或损害,我单位将不会负任何法律责任。如涉及版权问题,请提交至online#300.cn邮箱联系删除。
1.大批量乱序数据导入InnoDB很慢如何解决?InnoDB因为主键聚集索引的关系,如果没有主键或者主键非序列的情况下,导入会越来越慢,如何快速的迁移数据到In
面试mysqldba的时候遇到一个题:描述msyqlreplication机制的实现原理,如何在不停掉mysql主库的情况下,恢复数据不一致的slave的数据库
在上一篇文章中我们提到热拷贝(MySQL备份与恢复之热拷贝),热拷贝也就是在MySQL或者其他数据库服务在运行的情况下使用mysqlhotcopy命令进行备份。
MySQLInnodb引擎优化,InnoDB给MySQL提供了具有提交,回滚和崩溃恢复能力的事务安全(ACID兼容)存储引擎。InnoDB锁定在行级并且也在SE
我们都知道当我们建立数据表(innodb或myisam)时,会生成相应的文件(如:MYD,MYI,frm)在这里,我们探讨下使用frm文件恢复innodb和my