领购物优惠券9块9包邮
首页 > 数据库 > MySQL教程

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

   2016-05-18 0
核心提示：这篇文章主要介绍了MySQL异常恢复之无主键情况下innodb数据恢复的方法,结合实例形式分析了针对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数据库计有所帮助。

 
标签： MySQL innodb 数据恢复
反对 0举报 0 评论 0
 

免责声明：本文仅代表作者个人观点，与乐学笔记（本网）无关。其原创性以及文中陈述文字和内容未经本站证实，对本文以及其中全部或者部分内容、文字的真实性、完整性、及时性本站不作任何保证或承诺，请读者仅作参考，并请自行核实相关内容。
    本网站有部分内容均转载自其它媒体，转载目的在于传递更多信息，并不代表本网赞同其观点和对其真实性负责，若因作品内容、知识产权、版权和其他问题，请及时提供相关证明等材料并与我们留言联系，本网站将在规定时间内给予删除等相关处理.

  • sql：mysql：函数：TIMESTAMPDIFF函数实现TimeStamp字段相减，求得时间差
    sql：mysql：函数：TIMESTAMPDIFF函数实现TimeS
     函数内指定是minute，则最终结果value值的单位是分钟，如果函数内指定为hours，则最终结果value值单位为小时。//UPLOAD_TIME 减去 CREATE_DTTM 求得时间差，以分钟数计时select avg(TIMESTAMPDIFF(MINUTE,CREATE_DTTM,UPLOAD_TIME)) value,LEFT(CREATE_DTTM
    03-08
  • mysql下如何执行sql脚本 执行SQL脚本
    1.编写sql脚本,假设内容如下:  create database dearabao;  use dearabao;  create table niuzi (name varchar(20));  保存脚本文件,假设我把它保存在F盘的hello world目录下,于是该文件的路径为:F:\hello world\niuzi.sql2.执行sql脚本,可以有2种方法: 
    02-10
  • MySQL 5.7版本sql_mode=only_full_group_by问题
    用到GROUP BY 语句查询时com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Expression #2 of SELECT list is not in GROUP BY clause and contains nonaggregated column 'col_user_6.a.START_TIME' which is not functionally dependent on colu
    02-10
  • Oracle迁移到MySQL性能下降的注意点 oracle数据
    背景：最近有较多的客户系统由原来由Oracle改造到MySQL后出现了性能问题CPU 100%，或是后台的CRM系统复杂SQL在业务高峰的时候出现堆积导致业务故障。在我的记忆里面淘宝最初从Oracle迁移到MySQL期间也遇到了很多SQL的性能问题，记忆最为深刻的子查询，当初的
    02-10
  • MySQL与Oracle 差异比较之六触发器
    触发器编号类别ORACLEMYSQL注释1创建触发器语句不同create or replace trigger TG_ES_FAC_UNIT  before insert or update or delete on ES_FAC_UNIT  for each rowcreate trigger `hs_esbs`.`TG_INSERT_ES_FAC_UNIT` BEFORE INSERT on `hs_esbs`.`es_fac_u
    02-10
  • mysql where条件：某时间字段为今天的sql语句
    1.查询：注册时间为今天的所有用户数：select count(*) from customer where TO_DAYS(createtime) = TO_DAYS(NOW())2.获取当前时间到凌晨24点还有多长时间：（Java中可用于判断某时间是否为今天）final Calendar cal = Calendar.getInstance();    ca
    02-10
  • mysql中的sql
    变量用户变量: 在用户变量前加@系统变量: 在系统变量前加@@运算符算术运算符有: +(加), -(减), * (乘), / (除) 和％ (求模) 五中运算位运算符有:(位于), | (位或), ^ (位异或), ~ (位取反),(位右移),(位左移)比较运算符有: = (等于),(大于),(小于), = (大
    02-10
  • mysql5.7配置文件修改sql_mode 重启无效解决方法。this is incompatible with sql_mode=only_full_group_by
    mysql5.7配置文件修改sql_mode 重启无效解决方
    whereis my.cnf找到配置路径：/etc/my.cnf找到[mysqld]，在下面添加sql_mode=STRICT_TRANS_TABLES,NO_ZERO_IN_DATE,NO_ZERO_DATE,ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION重要：如果没有[mysqld]，一定要先添加[mysqld]再在下
    02-10
  • mysql 8 查询报错(sql_mode=only_full_group_by)
    mysql 8 查询报错(sql_mode=only_full_group_by
    Expression #1 of ORDER BY clause is not in GROUP BY clause and contains nonaggregated column 'information_schema.PROFILING.SEQ' which is not functionally dependent on columns in GROUP BY clause; this is incompatible with sql_mode=only_full_
    02-10
  • Oracle、MySql、Sql Server比对
    MySql:廉价(部分免费)：当前，MySQL採用双重授权(DualLicensed)，他们是GPL和MySQLAB制定的商业许可协议。假设你在一个遵循GPL的***（开源）项目中使用MySQL，那么你能够遵循GPL协议免费使用MySQL。否则，你须要购买MySQLAB制定的那个商业许可协议。Windows $
    02-10
更多>MySQL教程
MySQL中表子查询与关联子查询的基础学习教程 CentOS系统下编译安装MySQL以及设置相关yum源的教程
更多>Oracle教程
Oracle数据库中表空间的基本管理操作小结 在Linux系统上同时监控多个Oracle数据库表空间的方法
更多>SQL Server
SQL SERVER修改函数名容易引发的问题分析 SQLSERVER分页查询关于使用Top方式和row_number()解析函数的不同
更多>MongoDB
教大家8天学通MongoDB——第一天 基础入门篇 MongoDB运行状态监控、性能分析工具mongostat详解
更多>PostgreSQL
PostgreSQL角色与用户管理介绍 Windows下PostgreSQL安装图解
点击排行
网站首页  |  关于我们  |  联系方式  |  使用协议  |  版权隐私  |  网站地图  |  网站留言  |  违规举报