相思资源网 Design By www.200059.com

本文讲述了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数据库计有所帮助。

标签:
MySQL,无主键,innodb,数据恢复

相思资源网 Design By www.200059.com
广告合作:本站广告合作请联系QQ:858582 申请时备注:广告合作(否则不回)
免责声明:本站文章均来自网站采集或用户投稿,网站不提供任何软件下载或自行开发的软件! 如有用户或公司发现本站内容信息存在侵权行为,请邮件告知! 858582#qq.com
相思资源网 Design By www.200059.com

评论“MySQL异常恢复之无主键情况下innodb数据恢复的方法”

暂无MySQL异常恢复之无主键情况下innodb数据恢复的方法的评论...

《魔兽世界》大逃杀!60人新游玩模式《强袭风暴》3月21日上线

暴雪近日发布了《魔兽世界》10.2.6 更新内容,新游玩模式《强袭风暴》即将于3月21 日在亚服上线,届时玩家将前往阿拉希高地展开一场 60 人大逃杀对战。

艾泽拉斯的冒险者已经征服了艾泽拉斯的大地及遥远的彼岸。他们在对抗世界上最致命的敌人时展现出过人的手腕,并且成功阻止终结宇宙等级的威胁。当他们在为即将于《魔兽世界》资料片《地心之战》中来袭的萨拉塔斯势力做战斗准备时,他们还需要在熟悉的阿拉希高地面对一个全新的敌人──那就是彼此。在《巨龙崛起》10.2.6 更新的《强袭风暴》中,玩家将会进入一个全新的海盗主题大逃杀式限时活动,其中包含极高的风险和史诗级的奖励。

《强袭风暴》不是普通的战场,作为一个独立于主游戏之外的活动,玩家可以用大逃杀的风格来体验《魔兽世界》,不分职业、不分装备(除了你在赛局中捡到的),光是技巧和战略的强弱之分就能决定出谁才是能坚持到最后的赢家。本次活动将会开放单人和双人模式,玩家在加入海盗主题的预赛大厅区域前,可以从强袭风暴角色画面新增好友。游玩游戏将可以累计名望轨迹,《巨龙崛起》和《魔兽世界:巫妖王之怒 经典版》的玩家都可以获得奖励。