欧美bbbwbbbw肥妇,免费乱码人妻系列日韩,一级黄片

MySQL異?；謴?fù)之無(wú)主鍵情況下innodb數(shù)據(jù)恢復(fù)的方法

 更新時(shí)間：2016年04月26日 11:45:18   作者：OurMySQL  
這篇文章主要介紹了MySQL異?；謴?fù)之無(wú)主鍵情況下innodb數(shù)據(jù)恢復(fù)的方法,結(jié)合實(shí)例形式分析了針對(duì)innodb引擎無(wú)主鍵的情況下恢復(fù)數(shù)據(jù)的步驟與相關(guān)技巧,需要的朋友可以參考下

本文講述了MySQL異?；謴?fù)之無(wú)主鍵情況下innodb數(shù)據(jù)恢復(fù)的方法。分享給大家供大家參考，具體如下：

在mysql的innodb引擎的數(shù)據(jù)庫(kù)異?；謴?fù)中,一般都要求有主鍵或者唯一index,其實(shí)這個(gè)不是必須的,當(dāng)沒(méi)有index信息之時(shí),可以在整個(gè)表級(jí)別的index_id進(jìn)行恢復(fù)

創(chuàng)建模擬表—無(wú)主鍵

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

恢復(fù)數(shù)據(jù)字典

[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

分析數(shù)據(jù)字典,找出來(lái)index_id

這里需要注意對(duì)于沒(méi)有主鍵的表恢復(fù),我們對(duì)應(yīng)的類(lèi)型是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)

恢復(fù)數(shù)據(jù)

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    "尊敬的用戶(hù)您好：您的手機(jī)驗(yàn)證碼為916515如非本人操作，請(qǐng)撥打奧
斯卡客服：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    "尊敬的用戶(hù)您好：您的手機(jī)驗(yàn)證碼為396108如非本人操作，請(qǐng)撥打奧
斯卡客服：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    "尊敬的用戶(hù)您好：您的手機(jī)驗(yàn)證碼為935297如非本人操作，請(qǐng)撥打奧
斯卡客服：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    "尊敬的用戶(hù)您好：您的手機(jī)驗(yàn)證碼為474851如非本人操作，請(qǐng)撥打奧
斯卡客服：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    "尊敬的用戶(hù)您好：您的手機(jī)驗(yàn)證碼為444632如非本人操作，請(qǐng)撥打奧
斯卡客服：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    "尊敬的用戶(hù)您好：您的手機(jī)驗(yàn)證碼為478503如非本人操作，請(qǐng)撥打奧
斯卡客服：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    "尊敬的用戶(hù)您好：您的手機(jī)驗(yàn)證碼為216825如非本人操作，請(qǐng)撥打奧
斯卡客服：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    "尊敬的用戶(hù)您好：您的手機(jī)驗(yàn)證碼為854812如非本人操作，請(qǐng)撥打奧
斯卡客服：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    "尊敬的用戶(hù)您好：您的手機(jī)驗(yàn)證碼為253127如非本人操作，請(qǐng)撥打奧
斯卡客服：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

因?yàn)闆](méi)有主鍵,使得恢復(fù)出來(lái)記錄可能有一些重復(fù),整體而言,可以較為完美的恢復(fù)數(shù)據(jù)

更多關(guān)于MySQL相關(guān)內(nèi)容感興趣的讀者可查看本站專(zhuān)題：《MySQL日志操作技巧大全》、《MySQL事務(wù)操作技巧匯總》、《MySQL存儲(chǔ)過(guò)程技巧大全》、《MySQL數(shù)據(jù)庫(kù)鎖相關(guān)技巧匯總》及《MySQL常用函數(shù)大匯總》

希望本文所述對(duì)大家MySQL數(shù)據(jù)庫(kù)計(jì)有所幫助。

相關(guān)文章

  • MySQL數(shù)據(jù)庫(kù)遠(yuǎn)程連接很慢的解決方案

    MySQL數(shù)據(jù)庫(kù)遠(yuǎn)程連接很慢的解決方案

    本文給大家分享的是MySQL數(shù)據(jù)庫(kù)遠(yuǎn)程連接很慢的解決方法，簡(jiǎn)單的說(shuō)就是開(kāi)啟skip-name-resolve，非常的簡(jiǎn)單實(shí)用，有需要的小伙伴可以參考下
    2016-12-12
  • mysql快速插入大量數(shù)據(jù)的正確方法

    mysql快速插入大量數(shù)據(jù)的正確方法

    在處理大量數(shù)據(jù)時(shí)如果一條一條地插入會(huì)極大地影響效率,因此批量插入是一個(gè)更好的選擇,下面這篇文章主要給大家介紹了關(guān)于mysql快速插入大量數(shù)據(jù)的正確方法,需要的朋友可以參考下
    2024-01-01
  • SQL通用語(yǔ)法以及分類(lèi)圖文詳解

    SQL通用語(yǔ)法以及分類(lèi)圖文詳解

    本書(shū)從初學(xué)者的角度出發(fā),由淺入深,循序漸進(jìn)地介紹了SQL通用語(yǔ)法的相關(guān)知識(shí),下面這篇文章主要給大家介紹了關(guān)于SQL通用語(yǔ)法以及分類(lèi)的相關(guān)資料,需要的朋友可以參考下
    2022-12-12
  • MySQL中臨時(shí)表的基本創(chuàng)建與使用教程

    MySQL中臨時(shí)表的基本創(chuàng)建與使用教程

    這篇文章主要介紹了MySQL中臨時(shí)表的基本創(chuàng)建與使用教程,注意臨時(shí)表中數(shù)據(jù)的清空問(wèn)題,需要的朋友可以參考下
    2015-12-12
  • MySQL邏輯備份into?outfile

    MySQL邏輯備份into?outfile

    這篇文章主要介紹了MySQL?備份之?into?outfile，文章圍繞主題展開(kāi)詳細(xì)內(nèi)容介紹，具有一定的參考價(jià)值需要的小伙伴可以參考一下
    2022-05-05
  • 安裝和使用percona-toolkit來(lái)輔助操作MySQL的基本教程

    安裝和使用percona-toolkit來(lái)輔助操作MySQL的基本教程

    這篇文章主要介紹了安裝和使用percona-toolkit來(lái)輔助操作MySQL的基本教程,這里舉了五個(gè)最常見(jiàn)的命令用法,需要的朋友可以參考下
    2015-11-11
  • InnoDB 類(lèi)型MySql恢復(fù)表結(jié)構(gòu)與數(shù)據(jù)

    InnoDB 類(lèi)型MySql恢復(fù)表結(jié)構(gòu)與數(shù)據(jù)

    MySQL中.frm文件：保存了每個(gè)表的元數(shù)據(jù)，包括表結(jié)構(gòu)的定義等，該文件與數(shù)據(jù)庫(kù)引擎無(wú)關(guān)。MySQL中.ibd文件：InnoDB引擎開(kāi)啟了獨(dú)立表空間(my.ini中配置innodb_file_per_table = 1)產(chǎn)生的存放該表的數(shù)據(jù)和索引的文件。
    2018-01-01
  • 安裝Mysql時(shí)可能會(huì)遇到的一些疑難雜癥

    安裝Mysql時(shí)可能會(huì)遇到的一些疑難雜癥

    這篇文章主要給大家介紹了關(guān)于安裝Mysql時(shí)可能會(huì)遇到的一些疑難雜癥，文中通過(guò)示例代碼介紹的非常詳細(xì)，對(duì)大家的學(xué)習(xí)或者工作具有一定的參考學(xué)習(xí)價(jià)值，需要的朋友們下面隨著小編來(lái)一起學(xué)習(xí)學(xué)習(xí)吧
    2021-01-01
  • linux 下配置安裝mysql以及配置【經(jīng)驗(yàn)】

    linux 下配置安裝mysql以及配置【經(jīng)驗(yàn)】

    這篇文章主要介紹了linux 下配置安裝mysql以及配置【經(jīng)驗(yàn)】,需要的朋友可以參考下
    2016-05-05
  • MySQL對(duì)JSON數(shù)據(jù)進(jìn)行查詢(xún)實(shí)例代碼

    MySQL對(duì)JSON數(shù)據(jù)進(jìn)行查詢(xún)實(shí)例代碼

    這篇文章主要給大家介紹了關(guān)于MySQL對(duì)JSON數(shù)據(jù)進(jìn)行查詢(xún)的相關(guān)資料,MySQL支持使用JSON類(lèi)型存儲(chǔ)數(shù)據(jù),并提供了多種查詢(xún)JSON數(shù)據(jù)的方法,需要的朋友可以參考下
    2023-07-07

最新評(píng)論