《MYSQL教程MySQL數(shù)據(jù)庫(kù)InnoDB數(shù)據(jù)恢復(fù)工具的使用小結(jié)詳解》要點(diǎn)：
本文介紹了MYSQL教程MySQL數(shù)據(jù)庫(kù)InnoDB數(shù)據(jù)恢復(fù)工具的使用小結(jié)詳解，希望對(duì)您有用。如果有疑問(wèn)，可以聯(lián)系我們。
本文從實(shí)際使用經(jīng)驗(yàn)出發(fā),介紹一款開(kāi)源的MySQL數(shù)據(jù)庫(kù)InnoDB數(shù)據(jù)恢復(fù)工具：innodb-tools,它通過(guò)從原始數(shù)據(jù)文件中提取表的行記錄,實(shí)現(xiàn)從丟失的或者被毀壞的MySQL表中恢復(fù)數(shù)據(jù).例如,當(dāng)你不小心執(zhí)行DROP TABLE、TRUNCATE TABLE或者DROP DATABASE之后,可以通過(guò)以下方式恢復(fù)數(shù)據(jù).
以下內(nèi)容大部分參考自：Percona Data Recovery Tool for InnoDB,文檔是英文的,而且寫(xiě)的比較晦澀,這里是個(gè)人的實(shí)戰(zhàn)經(jīng)驗(yàn)總結(jié),供大家參考學(xué)習(xí).
在介紹innodb-tools工具進(jìn)行數(shù)據(jù)恢復(fù)之前,首先明確以下幾點(diǎn)：
1、這個(gè)工具只能對(duì)InnoDB/XtraDB表有效,而無(wú)法恢復(fù)MyISAM表(注： Percona號(hào)稱(chēng)有一套用于恢復(fù)MyISAM表的工具,但是本人未做嘗試).
2、這個(gè)工具是以保存的MySQL數(shù)據(jù)文件進(jìn)行恢復(fù)的,而不用MySQL Server運(yùn)行.
3、不能保證數(shù)據(jù)總一定可被恢復(fù).例如,被重寫(xiě)的數(shù)據(jù)不能被恢復(fù),這種情況下可能需要針對(duì)系統(tǒng)或物理的方式來(lái)恢復(fù),不屬于本工具的范疇.
4、恢復(fù)的最好時(shí)機(jī)是當(dāng)你發(fā)現(xiàn)數(shù)據(jù)丟失時(shí),盡快備份MySQL數(shù)據(jù)文件.
5、使用這個(gè)工具需要手動(dòng)做一些工作,并不是全自動(dòng)完成的.
6、恢復(fù)過(guò)程依賴于你對(duì)丟失數(shù)據(jù)的了解程度,在恢復(fù)過(guò)程中可能需要在不同版本的數(shù)據(jù)之間做出選擇.那么如果你越了解自己的數(shù)據(jù),恢復(fù)的可能性就越大.
接下來(lái),下面通過(guò)一個(gè)例子來(lái)介紹如何通過(guò)這個(gè)工具進(jìn)行恢復(fù).
1. 前提條件
首先,需要理解的是innodb-tools工具不是通過(guò)連接到在線的database進(jìn)行數(shù)據(jù)恢復(fù),而是通過(guò)離線拷貝數(shù)據(jù)的方式進(jìn)行的.注意：不要在MySQL運(yùn)行的時(shí)候,直接拷貝InnoDB文件,這樣是不安全的,會(huì)影響數(shù)據(jù)恢復(fù)過(guò)程.
為了完成數(shù)據(jù)恢復(fù),必須知道將要被恢復(fù)的表結(jié)構(gòu)(列名、數(shù)據(jù)類(lèi)型).最簡(jiǎn)單的方式就是SHOW CREATE TABLE,當(dāng)然后續(xù)會(huì)介紹幾種可替代的方式.因此,如果有一個(gè)MySQL server作為備份,即使數(shù)據(jù)是很早的甚至表中沒(méi)有記錄,可以有助于使用innodb-tools工具進(jìn)行恢復(fù).不過(guò)這個(gè)不是必須的.
2. 簡(jiǎn)單例子
代碼如下:
mysql> TRUNCATE TABLE customer;
3. 構(gòu)建工具
為了構(gòu)建innodb-tools工具,需要依賴于C編譯器、make工具等.
1、下載解壓innodb-tools工具源碼：
代碼如下:
wget https://launchpad.net/percona-data-recovery-tool-for-innodb/trunk/release-0.5/+download/percona-data-recovery-tool-for-innodb-0.5.tar.gztar -zxvf percona-data-recovery-tool-for-innodb-0.5.tar.gz
2、進(jìn)入解壓后根目錄下的mysql-source目錄,運(yùn)行配置命令(注：不運(yùn)行make命令)：
代碼如下:
cd percona-data-recovery-tool-for-innodb-0.5/mysql-source
./configure
3、完成配置步驟后,回到解壓后的根目錄,運(yùn)行make命令,編譯生成page_parser和constraints_parser工具：
代碼如下:
cd ..
make
page_parser工具將根據(jù)InnoDB的底層實(shí)現(xiàn)原理,解析表的頁(yè)和行結(jié)構(gòu).constraints_parser工具暫時(shí)不使用,后續(xù)還需要在定義表結(jié)構(gòu)之后,重新編譯生成它.
如果編譯過(guò)程中出現(xiàn)問(wèn)題,點(diǎn)擊這里.本文使用過(guò)程中沒(méi)有出現(xiàn)問(wèn)題,故不再一一列舉.
4. 提取需要的頁(yè)
InnoDB頁(yè)的默認(rèn)大小是16K,每個(gè)頁(yè)屬于一個(gè)特定表中的一個(gè)特定的index.page_parser工具通過(guò)讀取數(shù)據(jù)文件,根據(jù)頁(yè)頭中的index ID,拷貝每個(gè)頁(yè)到一個(gè)單獨(dú)的文件中.
如果你的MySQL server被配置為innodb_file_per_table=1,那么系統(tǒng)已經(jīng)幫你實(shí)現(xiàn)上述過(guò)程.所有需要的頁(yè)都在.ibd文件,而且通常你不需要再切分它.然而,如果.ibd文件中可能包含多個(gè)index,那么將頁(yè)單獨(dú)切分開(kāi)還是有必要的.如果MySQL server沒(méi)有配置innodb_file_per_table,那么數(shù)據(jù)會(huì)被保存在一個(gè)全局的表命名空間(通常是一個(gè)名為ibdata1的文件,本文屬于這種情況),這時(shí)候就需要按頁(yè)對(duì)文件進(jìn)行切分.
4.1 切分頁(yè)
運(yùn)行page_parser工具進(jìn)行切分：
?如果MySQL是5.0之前的版本,InnoDB采取的是REDUNDANT格式,運(yùn)行以下命令：
代碼如下:
./page_parser -4 -f /path/to/ibdata1
?如果MySQL是5.0版本,InnoDB采取的是COMPACT格式,運(yùn)行以下命令：
代碼如下:
./page_parser -5 -f /path/to/ibdata1
運(yùn)行后,page_parser工具會(huì)創(chuàng)建一個(gè)pages-<TIMESTAMP>的目錄,其中TIMESTAMP是UNIX系統(tǒng)時(shí)間戳.在這個(gè)目錄下,為每個(gè)index ID,以頁(yè)的index ID創(chuàng)建一個(gè)子目錄.例如：
代碼如下:
pages-1330842944/FIL_PAGE_INDEX/0-1/1-00000008.page
pages-1330842944/FIL_PAGE_INDEX/0-1/6-00000008.page
4.2 選擇需要的Index ID
一般來(lái)說(shuō),我們需要根據(jù)表的主鍵(PRIMARY index)進(jìn)行恢復(fù),主鍵中包含了所有的行.以下是一些可以實(shí)現(xiàn)的步驟：
如果數(shù)據(jù)庫(kù)仍處于運(yùn)行狀態(tài),并且表沒(méi)有被drop掉,那么可以啟動(dòng)InnoDB Tablespace Monitor,輸出所有表和indexes,index IDs到MySQL server的錯(cuò)誤日志文件.創(chuàng)建innodb_table_monitor表用于收集innodb存儲(chǔ)引擎表及其索引的存儲(chǔ)方式：
代碼如下:
mysql> CREATE TABLE innodb_table_monitor (id int) ENGINE=InnoDB;
如果innodb_table_monitor已經(jīng)存在,drop表然后重新create表.等MySQL錯(cuò)誤日志輸出后,可以drop掉這張表以停止打印輸出更多的監(jiān)控.一個(gè)輸出的例子如下：
代碼如下:
TABLE: name sakila/customer, id 0 142, columns 13, indexes 4, appr.rows 0
? COLUMNS: customer_id: DATA_INT len 2 prec 0; store_id: DATA_INT len 1 prec 0; first_name: type 12 len 135 prec 0; last_name: type 12 len 135 prec 0; email:
?type 12 len 150 prec 0; address_id: DATA_INT len 2 prec 0; active: DATA_INT len 1 prec 0; create_date: DATA_INT len 8 prec 0; last_update: DATA_INT len 4 pr
ec 0; DB_ROW_ID: DATA_SYS prtype 256 len 6 prec 0; DB_TRX_ID: DATA_SYS prtype 257 len 6 prec 0; DB_ROLL_PTR: DATA_SYS prtype 258 len 7 prec 0;
? INDEX: name PRIMARY, id 0 286, fields 1/11, type 3
?? root page 50, appr.key vals 0, leaf pages 1, size pages 1
?? FIELDS:? customer_id DB_TRX_ID DB_ROLL_PTR store_id first_name last_name email address_id active create_date last_update
? INDEX: name idx_fk_store_id, id 0 287, fields 1/2, type 0
?? root page 56, appr.key vals 0, leaf pages 1, size pages 1
?? FIELDS:? store_id customer_id
? INDEX: name idx_fk_address_id, id 0 288, fields 1/2, type 0
?? root page 63, appr.key vals 0, leaf pages 1, size pages 1
?? FIELDS:? address_id customer_id
? INDEX: name idx_last_name, id 0 289, fields 1/2, type 0
?? root page 1493, appr.key vals 0, leaf pages 1, size pages 1
?? FIELDS:? last_name customer_id
這里,我們恢復(fù)的是sakila庫(kù)下的customer表,從上面可以獲取其主鍵信息：
代碼如下:
INDEX: name PRIMARY, id 0 286, fields 1/11, type 3
Index ID是0 256,因此我們需要恢復(fù)的InnoDB頁(yè)位于0-256子目錄下.
備注：參考文檔原文中之描述了以上這種獲取表的index ID的方法,本文在實(shí)際操作中,采取了更簡(jiǎn)單的一種方式,即直接恢復(fù)page_parser生成的所有InnoDB頁(yè).實(shí)踐證明這種方法也是可行的：)
5. 生成表定義
步驟4中,我們已經(jīng)找到了需要的數(shù)據(jù),接下來(lái)需要找到表結(jié)構(gòu),創(chuàng)建表定義,將其編譯到constraints_parser中,然后使用這個(gè)工具從InnoDB頁(yè)中提取表中的行.
表定義包含了表中的列、列順序、數(shù)據(jù)類(lèi)型.如果MySQL server仍處于運(yùn)行且表未被drop掉,那么簡(jiǎn)單實(shí)用SHOW CREATE TABLE就可以收集到這些信息.接下來(lái)將使用這些表結(jié)構(gòu)信息來(lái)創(chuàng)建一個(gè)C結(jié)構(gòu)體標(biāo)識(shí)的表定義,然后編譯到constraints_parser工具.C結(jié)構(gòu)體的定義存放在include/table_defs.h中.
最簡(jiǎn)單的方式是create_defs.pl Perl 腳本,連接到MySQL server,讀取SHOW CREATE TABLE的結(jié)果,輸出生成的表定義到標(biāo)準(zhǔn)輸出.下面是個(gè)例子,其中直接將結(jié)果重定向到了include/table_defs.h中：
If possible, the easiest way to create the table definition is with the create_defs.pl Perl script. It connects to the MySQL server and reads SHOW CREATE TABLE output, and prints the generated definition to its standard output. Here is an example:
代碼如下:
$ ./create_defs.pl --host=localhost --user=root --password=123456 --db=sakila --table=customer > include/table_defs.h
下面是例子中的表結(jié)構(gòu)：
代碼如下:
CREATE TABLE `customer` (
? `customer_id` smallint(5) UNSIGNED NOT NULL AUTO_INCREMENT,
? `store_id` tinyint(3) UNSIGNED NOT NULL,
? `first_name` varchar(45) NOT NULL,
? `last_name` varchar(45) NOT NULL,
? `email` varchar(50) DEFAULT NULL,
? `address_id` smallint(5) UNSIGNED NOT NULL,
? `active` tinyint(1) NOT NULL DEFAULT '1',
? `create_date` datetime NOT NULL,
? `last_update` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP,
? PRIMARY KEY? (`customer_id`),
? KEY `idx_fk_store_id` (`store_id`),
? KEY `idx_fk_address_id` (`address_id`),
? KEY `idx_last_name` (`last_name`),
? CONSTRAINT `fk_customer_address` FOREIGN KEY (`address_id`) REFERENCES `address` (`address_id`) ON UPDATE CASCADE,
? CONSTRAINT `fk_customer_store` FOREIGN KEY (`store_id`) REFERENCES `store` (`store_id`) ON UPDATE CASCADE
) ENGINE=InnoDB DEFAULT CHARSET=utf8
下面是生成的表定義：
代碼如下:
#ifndef table_defs_h
#define table_defs_h
// Table definitions
table_def_t table_definitions[] = {
??????? {
??????????????? name: "customer",
??????????????? {
??????????????????????? { /* smallint(5) unsigned */
??????????????????????????????? name: "customer_id",
??????????????????????????????? type: FT_UINT,
??????????????????????????????? fixed_length: 2,
??????????????????????????????? has_limits: TRUE,
??????????????????????????????? limits: {
??????????????????????????????????????? can_be_null: FALSE,
??????????????????????????????????????? uint_min_val: 0,
??????????????????????????????????????? uint_max_val: 65535
??????????????????????????????? },
??????????????????????????????? can_be_null: FALSE
??????????????????????? },
??????????????????????? { /* Innodb's internally used field */
??????????????????????????????? name: "DB_TRX_ID",
??????????????????????????????? type: FT_INTERNAL,
??????????????????????????????? fixed_length: 6,
??????????????????????????????? can_be_null: FALSE
??????????????????????? },
??????????????????????? { /* Innodb's internally used field */
??????????????????????????????? name: "DB_ROLL_PTR",
??????????????????????????????? type: FT_INTERNAL,
??????????????????????????????? fixed_length: 7,
??????????????????????????????? can_be_null: FALSE
??????????????????????? },
??????????????????????? { /* tinyint(3) unsigned */
??????????????????????????????? name: "store_id",
??????????????????????????????? type: FT_UINT,
??????????????????????????????? fixed_length: 1,
??????????????????????????????? has_limits: TRUE,
??????????????????????????????? limits: {
??????????????????????????????????????? can_be_null: FALSE,
??????????????????????????????????????? uint_min_val: 0,
??????????????????????????????????????? uint_max_val: 255
??????????????????????????????? },
??????????????????????????????? can_be_null: FALSE
??????????????????????? },
??????????????????????? { /* varchar(45) */
??????????????????????????????? name: "first_name",
??????????????????????????????? type: FT_CHAR,
??????????????????????????????? min_length: 0,
??????????????????????????????? max_length: 45,
??????????????????????????????? has_limits: TRUE,
??????????????????????????????? limits: {
??????????????????????????????????????? can_be_null: FALSE,
??????????????????????????????????????? char_min_len: 0,
??????????????????????????????????????? char_max_len: 45,
??????????????????????????????????????? char_ascii_only: TRUE
??????????????????????????????? },
??????????????????????????????? can_be_null: FALSE
??????????????????????? },
??????????????????????? { /* varchar(45) */
??????????????????????????????? name: "last_name",
??????????????????????????????? type: FT_CHAR,
??????????????????????????????? min_length: 0,
??????????????????????????????? max_length: 45,
??????????????????????????????? has_limits: TRUE,
??????????????????????????????? limits: {
??????????????????????????????????????? can_be_null: FALSE,
??????????????????????????????????????? char_min_len: 0,
??????????????????????????????????????? char_max_len: 45,
??????????????????????????????????????? char_ascii_only: TRUE
??????????????????????????????? },
??????????????????????????????? can_be_null: FALSE
??????????????????????? },
??????????????????????? { /* varchar(50) */
??????????????????????????????? name: "email",
??????????????????????????????? type: FT_CHAR,
??????????????????????????????? min_length: 0,
??????????????????????????????? max_length: 50,
??????????????????????????????? has_limits: TRUE,
??????????????????????????????? limits: {
??????????????????????????????????????? can_be_null: TRUE,
??????????????????????????????????????? char_min_len: 0,
??????????????????????????????????????? char_max_len: 50,
??????????????????????????????????????? char_ascii_only: TRUE
??????????????????????????????? },
??????????????????????????????? can_be_null: TRUE
??????????????????????? },
??????????????????????? { /* smallint(5) unsigned */
??????????????????????????????? name: "address_id",
??????????????????????????????? type: FT_UINT,
??????????????????????????????? fixed_length: 2,
??????????????????????????????? has_limits: TRUE,
??????????????????????????????? limits: {
??????????????????????????????????????? can_be_null: FALSE,
??????????????????????????????????????? uint_min_val: 0,
??????????????????????????????????????? uint_max_val: 65535
??????????????????????????????? },
??????????????????????????????? can_be_null: FALSE
??????????????????????? },
??????????????????????? { /* tinyint(1) */
??????????????????????????????? name: "active",
??????????????????????????????? type: FT_INT,
??????????????????????????????? fixed_length: 1,
??????????????????????????????? can_be_null: FALSE
??????????????????????? },
??????????????????????? { /* datetime */
??????????????????????????????? name: "create_date",
??????????????????????????????? type: FT_DATETIME,
??????????????????????????????? fixed_length: 8,
??????????????????????????????? can_be_null: FALSE
??????????????????????? },
??????????????????????? { /* timestamp */
??????????????????????????????? name: "last_update",
??????????????????????????????? type: FT_UINT,
??????????????????????????????? fixed_length: 4,
??????????????????????????????? can_be_null: FALSE
??????????????????????? },
??????????????????????? { type: FT_NONE }
??????????????? }
??????? },
};
#endif
如果需要,可以根據(jù)需要編輯修改include/table_defs.h；然后根據(jù)include/table_defs.h,重新編譯
constraints_parser工具：
代碼如下:
$ make
gcc -DHAVE_OFFSET64_T -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE=1 -D_LARGEFILE_SOURCE=1 -g -I include -I mysql-source/include -I mysql-source/innobase/include -c tables_dict.c -o lib/tables_dict.o
gcc -DHAVE_OFFSET64_T -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE=1 -D_LARGEFILE_SOURCE=1 -g -I include -I mysql-source/include -I mysql-source/innobase/include -o constraints_parser constraints_parser.c lib/tables_dict.o lib/print_data.o lib/check_data.o lib/libut.a lib/libmystrings.a
gcc -DHAVE_OFFSET64_T -D_FILE_OFFSET_BITS=64 -D_LARGEFILE64_SOURCE=1 -D_LARGEFILE_SOURCE=1 -g -I include -I mysql-source/include -I mysql-source/innobase/include -o page_parser page_parser.c lib/tables_dict.o lib/libut.a
6. 從頁(yè)中提取行記錄
6.1 合并頁(yè)到一個(gè)文件
前面已經(jīng)提到,我們需要恢復(fù)的index ID 0 286,包含數(shù)據(jù)的頁(yè)位于pages-1246363747/0-286/ 目錄.
代碼如下:
total 120
-rw-r--r-- 1 root root 16384 Jun 30 05:09 1254-00001254.page
-rw-r--r-- 1 root root 16384 Jun 30 05:09 1255-00001255.page
-rw-r--r-- 1 root root 16384 Jun 30 05:09 1256-00001256.page
-rw-r--r-- 1 root root 16384 Jun 30 05:09 1257-00001257.page
-rw-r--r-- 1 root root 16384 Jun 30 05:09 50-00000050.page
-rw-r--r-- 1 root root 16384 Jun 30 05:09 74-00000050.page
輸入以下命令進(jìn)行合并頁(yè)：
代碼如下:
$ find pages-1246363747/0-286/ -type f -name '*.page' | sort -n | xargs cat > pages-1246363747/0-286/customer_pages_concatenated
生成的結(jié)果文件：pages-1246363747/0-286/customer_pages_concatenated,將作為constraints_parser工具的輸入.
6.2 運(yùn)行constraints_parser工具
下面到恢復(fù)數(shù)據(jù)最核心的步驟――運(yùn)行constraints_parser工具以提取行記錄.和page_parser工具一樣,需要通過(guò)-5或-4參數(shù)指定InnoDB頁(yè)格式(COMPACT/REDUNDANT),-f指定輸入文件.
回到例子中,我們可以這樣運(yùn)行constraints_parser工具(下面的命令是恢復(fù)一個(gè)單一的頁(yè),也可以直接恢復(fù)經(jīng)過(guò)6.1步驟合并所有頁(yè)之后的文件)：
代碼如下:
$ ./constraints_parser -5 -f pages-1246363747/0-286/50-00000050.page
輸出結(jié)果中每行包含表名以及表中的各個(gè)列.備注：其中可能有正確的行記錄,也可能有不正確的行記錄.官方文檔中這個(gè)章節(jié)給出了如何調(diào)整表定義獲取盡可能多的有效數(shù)據(jù),同時(shí)過(guò)濾掉垃圾行,這里不再詳細(xì)描述.
代碼如下:
customer??????? 0?????? 120???? ""????? ""????? ""????? 32770?? 0?????? "0000-00-00 00:12:80"?? 0
customer??????? 0?????? 0?????? ""????? ""????? ""????? 0?????? 0?????? "9120-22-48 29:44:00"?? 2
customer??????? 61953?? 0?????? ""????? ""????? ""????? 2816??? 0?????? "7952-32-67 11:43:49"?? 0
customer??????? 0?????? 0?????? ""????? ""????? ""????? 0?????? 0?????? "0000-00-00 00:00:00"?? 0
... snip ...
customer??????? 0?????? 0?????? ""????? ""????? ""????? 0?????? 0?????? "0000-00-00 00:00:00"?? 16777728
customer??????? 28262?? 114???? ""????? ""????? NULL??? 25965?? 117???? "4603-91-96 76:21:28"?? 5111809
customer??????? 0?????? 82????? ""????? ""????? ""????? 22867?? 77????? "2775-94-58 03:19:18"?? 1397573972
customer??????? 2?????? 1?????? "PATRICIA"????? "JOHNSON"?????? "PATRICIA.JOHNSON@sakilacustomer.org"?? 6?????? 1?????? "2006-02-14 22:04:36"?? 1140008240
customer??????? 3?????? 1?????? "LINDA" "WILLIAMS"????? "LINDA.WILLIAMS@sakilacustomer.org"???? 7?????? 1?????? "2006-02-14 22:04:36"?? 1140008240
customer??????? 4?????? 2?????? "BARBARA"?????? "JONES" "BARBARA.JONES@sakilacustomer.org"????? 8?????? 1?????? "2006-02-14 22:04:36"?? 1140008240
customer??????? 5?????? 1?????? "ELIZABETH"???? "BROWN" "ELIZABETH.BROWN@sakilacustomer.org"??? 9?????? 1?????? "2006-02-14 22:04:36"?? 1140008240
customer??????? 6?????? 2?????? "JENNIFER"????? "DAVIS" "JENNIFER.DAVIS@sakilacustomer.org"???? 10????? 1?????? "2006-02-14 22:04:36"?? 1140008240
customer??????? 7?????? 1?????? "MARIA" "MILLER"??????? "MARIA.MILLER@sakilacustomer.org"?????? 11????? 1?????? "2006-02-14 22:04:36"?? 1140008240
customer??????? 8?????? 2?????? "SUSAN" "WILSON"??????? "SUSAN.WILSON@sakilacustomer.org"?????? 12????? 1?????? "2006-02-14 22:04:36"?? 1140008240
customer??????? 9?????? 2?????? "MARGARET"????? "MOORE" "MARGARET.MOORE@sakilacustomer.org"???? 13????? 1?????? "2006-02-14 22:04:36"?? 1140008240
... snip ...
customer??????? 0?????? 0?????? ""????? ""????? ""????? 0?????? 0?????? "0000-00-00 00:00:00"?? 0
customer??????? 0?????? 0?????? ""????? ""????? ""????? 0?????? 0?????? "7679-35-98 86:44:53"?? 720578985
7. 導(dǎo)入數(shù)據(jù)到數(shù)據(jù)庫(kù)中
最后,為了完成數(shù)據(jù)恢復(fù),需要將步驟6中constraints_parser工具的輸出結(jié)果,使用LOAD DATA INFILE命令導(dǎo)入到數(shù)據(jù)庫(kù)中.命令如下：
代碼如下:
LOAD DATA INFILE '/tmp/customer_data.tsv'
REPLACE INTO TABLE customer
FIELDS TERMINATED BY '\t'
OPTIONALLY ENCLOSED BY '"'
LINES STARTING BY 'customer\t'
(customer_id, store_id, first_name, last_name, email,
?? address_id, active, create_date, @last_update)
SET last_update = FROM_UNIXTIME(@last_update);
至此,完成了數(shù)據(jù)的恢復(fù)和導(dǎo)入過(guò)程.希望大家不會(huì)有機(jī)會(huì)去實(shí)踐這篇文章介紹的方法.
轉(zhuǎn)載請(qǐng)注明本頁(yè)網(wǎng)址：
http://www.fzlkiss.com/jiaocheng/1083.html
