mysql innodb_file_per_table=1_对于innodb_file_per_table=off时，innodb引擎，误删除表的恢复...

最新推荐文章于 2024-01-12 15:24:55 发布
最新推荐文章于 2024-01-12 15:24:55 发布
阅读量220 收藏
点赞数
文章标签： mysql innodb_file_per_table=1
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_36212762/article/details/113429754
版权
本文介绍了在innodb_file_per_table=OFF的情况下，如何恢复误删除的InnoDB表。通过解析ibdata1文件并利用相关工具，可以恢复表结构和数据，包括表t1和t2。步骤包括使用stream_parser和c_parser等工具获取表定义、数据，并重建表。
摘要由CSDN通过智能技术生成

对于innodb_file_per_table=off时，innodb引擎，误删除表的恢复。

场景模拟：

mysql> show databases;

+--------------------+

| Database |

+--------------------+

| information_schema |

| d1 |

| mysql |

| performance_schema |

| song1 |

| song1_recover |

| t |

| test |

| ttt |

+--------------------+

9 rows in set (0.00 sec)

mysql> create database db_song;

Query OK, 1 row affected (0.01 sec)

mysql> use db_song;

Database changed

mysql> create table t1(id int);

Query OK, 0 rows affected (0.13 sec)

mysql> create table t2(id int primary key ,name

varchar(10));

Query OK, 0 rows affected (0.04 sec)

mysql> insert into t1 values

(1),(2),(3);

Query OK, 3 rows affected (0.00 sec)

Records: 3 Duplicates: 0 Warnings: 0

mysql> insert into t2 values

(1,'song'),(2,'zhi'),(3,'qinag');

Query OK, 3 rows affected (0.01 sec)

Records: 3 Duplicates: 0 Warnings: 0

mysql> show variables like '%per%';

+---------------------------------------------------+---------+

| Variable_name | Value |

+---------------------------------------------------+---------+

| innodb_file_per_table | OFF

mysql> drop table t1;

Query OK, 0 rows affected (0.00 sec)

mysql> drop table t2;

Query OK, 0 rows affected (0.00 sec)

把ibdata1文件放到/tmp目录后

[root@10-4-1-104 ]# ./stream_parser -f

/tmp/ibdata1

Opening file: /tmp/ibdata1

File information:

ID of device containing file: 64513

inode number: 655707

protection: 100640 (regular file)

number of hard links: 1

user ID of owner: 0

group ID of owner: 0

device ID (if special file): 0

blocksize for filesystem I/O: 4096

number of blocks allocated: 204800

Opening file: /tmp/ibdata1

File information:

ID of device containing file: 64513

inode number: 655707

protection: 100640 (regular file)

number of hard links: 1

user ID of owner: 0

group ID of owner: 0

device ID (if special file): 0

blocksize for filesystem I/O: 4096

number of blocks allocated: 204800

time of last access: 1437100833 Fri Jul 17 10:40:33

2015

time of last modification: 1437100833 Fri Jul 17 10:40:33

2015

time of last status change: 1437100833 Fri Jul 17 10:40:33

2015

Opening file: /tmp/ibdata1

total size, in bytes: 104857600 (100.000

MiB)

File information:

time of last access: 1437100833 Fri Jul 17 10:40:33

2015

Opening file: /tmp/ibdata1

ID of device containing file: 64513

Size to process: 104857600 (100.000

MiB)

inode number: 655707

File information:

protection: 100640 (regular file)

number of hard links: 1

user ID of owner: 0

ID of device containing file: 64513

time of last modification: 1437100833 Fri Jul 17 10:40:33

2015

inode number: 655707

protection: 100640 group ID of owner:

0

(regular file)

device ID (if special file): 0

number of hard links: 1

blocksize for filesystem I/O: 4096

user ID of owner: 0

number of blocks allocated: 204800

group ID of owner: 0

device ID (if special file): 0

blocksize for filesystem I/O: 4096

time of last status change: 1437100833 Fri Jul 17 10:40:33

2015

number of blocks allocated: 204800

total size, in bytes: 104857600 (100.000

MiB)

Size to process: 104857600 (100.000

MiB)

time of last access: 1437100833 Fri Jul 17 10:40:33

2015

time of last access: 1437100833 Fri Jul 17 10:40:33

2015

time of last modification: 1437100833 Fri Jul 17 10:40:33

2015

time of last modification: 1437100833 Fri Jul 17 10:40:33

2015

time of last status change: 1437100833 Fri Jul 17 10:40:33

2015

total size, in bytes: 104857600 (100.000

MiB)

time of last status change: 1437100833 Fri Jul 17 10:40:33

2015

Size to process: 104857600 (100.000

MiB)

total size, in bytes: 104857600 (100.000

MiB)

Size to process: 104857600 (100.000

MiB)

All workers finished in 0 sec

先获得表的定义语句：

[root@10-4-1-104 ]# ./c_parser -4Df

pages-ibdata1/FIL_PAGE_INDEX/0000000000000001.page

\

> -t dictionary/SYS_TABLES.sql \

> > dumps/default/SYS_TABLES \

> 2>

dumps/default/SYS_TABLES.sql

[root@10-4-1-104 ]# ./c_parser -4Df

pages-ibdata1/FIL_PAGE_INDEX/0000000000000003.page

\

> -t dictionary/SYS_INDEXES.sql \

> > dumps/default/SYS_INDEXES \

> 2>

dumps/default/SYS_INDEXES.sql

[root@10-4-1-104 ]# ./c_parser -4Df

pages-ibdata1/FIL_PAGE_INDEX/0000000000000002.page

\

> -t dictionary/SYS_COLUMNS.sql \

> > dumps/default/SYS_COLUMNS \

> 2>

dumps/default/SYS_COLUMNS.sql

[root@10-4-1-104 ]# ./c_parser -4Df

pages-ibdata1/FIL_PAGE_INDEX/0000000000000004.page

\

> -t dictionary/SYS_FIELDS.sql \

> > dumps/default/SYS_FIELDS \

> 2>

dumps/default/SYS_FIELDS.sql

[root@10-4-1-104 ]#

[root@10-4-1-104 ]#

[root@10-4-1-104 ]# cat dictionary/SYS_* | mysql -u root

-ptest -S /data/mysqld.sock -D

db_song_recover

[root@10-4-1-104 ]# cat dumps/default/*.sql | mysql -u root

-ptest -S /data/mysqld.sock -D db_song_recover

--local-infile=1

[root@10-4-1-104 ]# make sys_parser

/opt/udb/program/mysql/mysql-5.5.24/bin/mysql_config

cc `mysql_config --cflags` `mysql_config --libs` -o sys_parser

sys_parser.c

[root@10-4-1-104 ]# ./sys_parser -u root -ptest -h10.4.1.104

-d db_song_recover db_song/t1

CREATE TABLE `t1`(

WARNING: Fields are not found for table 'db_song/t1' in

SYS_FIELDS

`id` INT) ENGINE=InnoDB;

[root@10-4-1-104 ]# ./sys_parser -u root -ptest -h10.4.1.104

-d db_song_recover db_song/t2

CREATE TABLE `t2`(

`id` INT NOT NULL,

`name` VARCHAR(10) CHARACTER SET 'utf8' COLLATE

'utf8_general_ci',

PRIMARY KEY (`id`)

) ENGINE=InnoDB;

存放表定义：

[root@10-4-1-104 ]# mkdir db_song

[root@10-4-1-104 ]# cd db_song

[root@10-4-1-104 db_song]# cat t1.sql

CREATE TABLE `t1`(

`id` INT) ENGINE=InnoDB;

[root@10-4-1-104 db_song]# cat t2.sql

CREATE TABLE `t2`(

`id` INT NOT NULL,

`name` VARCHAR(10) CHARACTER SET 'utf8' COLLATE

'utf8_general_ci',

PRIMARY KEY (`id`)

) ENGINE=InnoDB;

[root@10-4-1-104 db_song]# pwd

/tmp//db_song

先还原 t1表数据：

[root@10-4-1-104 ]# ./c_parser -4Df

pages-ibdata1/FIL_PAGE_INDEX/0000000000000001.page -t

dictionary/SYS_TABLES.sql | grep t1

00000005553D 3800000D0E0CB3 SYS_TABLES "db\_song/t1" 236 1 1 0

0 "" 0

00000005553D 3800000D0E0CB3 SYS_TABLES "db\_song/t1" 236 1 1 0

0 "" 0

SET FOREIGN_KEY_CHECKS=0;

LOAD DATA LOCAL INFILE '/tmp//dumps/default/SYS_TABLES'

REPLACE INTO TABLE `SYS_TABLES` FIELDS TERMINATED BY '\t'

OPTIONALLY ENCLOSED BY '"' LINES STARTING BY 'SYS_TABLES\t'

(`NAME`, `ID`, `N_COLS`, `TYPE`, `MIX_ID`, `MIX_LEN`,

`CLUSTER_NAME`, `SPACE`);

00000005553D 3800000D0E0CB3 SYS_TABLES "db\_song/t1" 236 1 1 0

0 "" 0

[root@10-4-1-104 ]# ./c_parser -4Df

pages-ibdata1/FIL_PAGE_INDEX/0000000000000003.page -t

dictionary/SYS_INDEXES.sql | grep 236

00000005553D 3800000D0E0C41 SYS_INDEXES 236 431

"GEN\_CLUST\_INDEX" 0 1 0 4294967295

SET FOREIGN_KEY_CHECKS=0;

LOAD DATA LOCAL INFILE '/tmp//dumps/default/SYS_INDEXES'

REPLACE INTO TABLE `SYS_INDEXES` FIELDS TERMINATED BY '\t'

OPTIONALLY ENCLOSED BY '"' LINES STARTING BY 'SYS_INDEXES\t'

(`TABLE_ID`, `ID`, `NAME`, `N_FIELDS`, `TYPE`, `SPACE`,

`PAGE_NO`);

00000005553D 3800000D0E0C41 SYS_INDEXES 236 431

"GEN\_CLUST\_INDEX" 0 1 0 4294967295

[root@10-4-1-104 ]# ./c_parser -6f

pages-ibdata1/FIL_PAGE_INDEX/0000000000000431.page -t

db_song/t1.sql

-- Page id: 600, Format: COMPACT, Records list: Valid,

Expected records: (3 3)

000000000803 00000005553B B6000001DC0110 t1

1

000000000804 00000005553B B6000001DC011F t1

2

000000000805 00000005553B B6000001DC012E t1

3

SET FOREIGN_KEY_CHECKS=0;

LOAD DATA LOCAL INFILE '/tmp//dumps/default/t1' REPLACE INTO

TABLE `t1` FIELDS TERMINATED BY '\t' OPTIONALLY ENCLOSED BY '"'

LINES STARTING BY 't1\t' (`id`);

-- Page id: 600, Found records: 3, Lost records: NO, Leaf

page: YES

[root@10-4-1-104 ]# ./c_parser -6f

pages-ibdata1/FIL_PAGE_INDEX/0000000000000431.page -t

db_song/t1.sql > dumps/default/t1 2>

dumps/default/t1_load.sql

mysql> use db_song_recover

Database changed

mysql> show tables;

Empty set (0.00 sec)

mysql> CREATE TABLE `t1`(

-> `id` INT) ENGINE=InnoDB;

Query OK, 0 rows affected (0.03 sec)

mysql> CREATE TABLE `t2`(

--顺手把t2也建上，一会就不会再建了

-> `id` INT NOT NULL,

-> `name` VARCHAR(10) CHARACTER SET 'utf8' COLLATE

'utf8_general_ci',

-> PRIMARY KEY (`id`)

-> ) ENGINE=InnoDB;

Query OK, 0 rows affected (0.04 sec)

mysql> source

/tmp//dumps/default/t1_load.sql

Query OK, 0 rows affected (0.00 sec)

ERROR 1148 (42000): The used command is not allowed with this

MySQL version

mysql> exit

Bye

[root@10-4-1-104 ~]# mysql -u root -ptest -S /data/mysqld.sock

--local-infile=1

Welcome to the MySQL monitor. Commands end with ; or

\g.

Your MySQL connection id is 10

Server version: 5.5.24-ucloudrel1-log Source

distribution

Copyright (c) 2000, 2011, Oracle and/or its affiliates. All

rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or

its

affiliates. Other names may be trademarks of their

respective

owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current

input statement.

mysql> source

/tmp//dumps/default/t1_load.sql

Query OK, 0 rows affected (0.00 sec)

ERROR 1046 (3D000): No database

selected

mysql> use db_song_recover

Reading table information for completion of table and column

names

You can turn off this feature to get a quicker startup with

-A

Database changed

mysql> source

/tmp//dumps/default/t1_load.sql

Query OK, 0 rows affected (0.00 sec)

Query OK, 3 rows affected (0.01 sec)

Records: 3 Deleted: 0 Skipped: 0 Warnings:

0

mysql> select * from t1; --t1表数据恢复了

+------+

| id |

+------+

| 1 |

| 2 |

| 3 |

+------+

3 rows in set (0.00 sec)

再恢复 t2：

[root@10-4-1-104 ]# ./c_parser -4Df

pages-ibdata1/FIL_PAGE_INDEX/0000000000000001.page -t

dictionary/SYS_TABLES.sql | grep t2

00000005553F 3900000D100D1D SYS_TABLES "db\_song/t2" 237 2 1 0

0 "" 0

00000005553F 3900000D100D1D SYS_TABLES "db\_song/t2" 237 2 1 0

0 "" 0

SET FOREIGN_KEY_CHECKS=0;

LOAD DATA LOCAL INFILE '/tmp//dumps/default/SYS_TABLES'

REPLACE INTO TABLE `SYS_TABLES` FIELDS TERMINATED BY '\t'

OPTIONALLY ENCLOSED BY '"' LINES STARTING BY 'SYS_TABLES\t'

(`NAME`, `ID`, `N_COLS`, `TYPE`, `MIX_ID`, `MIX_LEN`,

`CLUSTER_NAME`, `SPACE`);

00000005553F 3900000D100D1D SYS_TABLES "db\_song/t2" 237 2 1 0

0 "" 0

[root@10-4-1-104 ]# ./c_parser -4Df

pages-ibdata1/FIL_PAGE_INDEX/0000000000000003.page -t

dictionary/SYS_INDEXES.sql | grep 237

00000005553F 3900000D100C76 SYS_INDEXES 237 432 "PRIMARY" 1 3

0 4294967295

SET FOREIGN_KEY_CHECKS=0;

LOAD DATA LOCAL INFILE '/tmp//dumps/default/SYS_INDEXES'

REPLACE INTO TABLE `SYS_INDEXES` FIELDS TERMINATED BY '\t'

OPTIONALLY ENCLOSED BY '"' LINES STARTING BY 'SYS_INDEXES\t'

(`TABLE_ID`, `ID`, `NAME`, `N_FIELDS`, `TYPE`, `SPACE`,

`PAGE_NO`);

00000005553F 3900000D100C76 SYS_INDEXES 237 432 "PRIMARY" 1 3

0 4294967295

[root@10-4-1-104 ]# ./c_parser -6f

pages-ibdata1/FIL_PAGE_INDEX/0000000000000432.page -t

db_song/t2.sql

-- Page id: 615, Format: COMPACT, Records list: Valid,

Expected records: (3 3)

00000005553C B7000001DE0110 t2 1

"song"

00000005553C B7000001DE011D t2 2 "zhi"

00000005553C B7000001DE012A t2 3

"qinag"

-- Page id: 615, Found records: 3, Lost records: NO, Leaf

page: YES

-- Page id: 615, Format: COMPACT, Records list: Valid,

Expected records: (0 0)

-- Page id: 615, Found records: 0, Lost records: NO, Leaf

page: YES

-- Page id: 615, Format: COMPACT, Records list: Valid,

Expected records: (3 3)

00000005553C B7000001DE0110 t2 1

"song"

00000005553C B7000001DE011D t2 2 "zhi"

00000005553C B7000001DE012A t2 3

"qinag"

SET FOREIGN_KEY_CHECKS=0;

LOAD DATA LOCAL INFILE '/tmp//dumps/default/t2' REPLACE INTO

TABLE `t2` FIELDS TERMINATED BY '\t' OPTIONALLY ENCLOSED BY '"'

LINES STARTING BY 't2\t' (`id`, `name`);

-- Page id: 615, Found records: 3, Lost records: NO, Leaf

page: YES

[root@10-4-1-104 ]# ./c_parser -6f

pages-ibdata1/FIL_PAGE_INDEX/0000000000000432.page -t

db_song/t2.sql > dumps/default/t2 2>

dumps/default/t2_load.sql

mysql> source

/tmp//dumps/default/t2_load.sql

Query OK, 0 rows affected (0.00 sec)

Query OK, 6 rows affected (0.01 sec)

Records: 6 Deleted: 0 Skipped: 0 Warnings:

0

mysql> select * from t2;

--t2表的数据也恢复了

+----+-------+

| id | name |

+----+-------+

| 1 | song |

| 2 | zhi |

| 3 | qinag |

+----+-------+

3 rows in set (0.00 sec)

转载请注明源出处

QQ 273002188  欢迎一起学习

房导航
关注
mysql innodb_file_per_table=1_mysql-5.7 innodb_file_per_table 详解
weixin_39908588的博客
01-27 1381
一、innodb_file_per_table 的简要说明：在很久很久以前也就是说还没有innodb_file_per_table 的那个年代，所有的innodb表的数据都是保存在innodb系统表空间中的，在有了innodb_file_per_table参数后innodb可以把每个表的数据单独保存。单独保存有两方面的优势一个是方便管理，二个是提长性能。二、用一个例子直观的来感受一下innodb_...
mysql通用配置表设计_mysql-通用优化配置详解
weixin_32056343的博客
01-20 2024
mysql-通用优化配置详解此处只是将通用优化配置项进行解释说明，再具体的优化需要根据自己业务需求进行相应配置transaction_isolation = READ-COMMITTED解读：事务隔离级别：Oracle、SQL Server等商业数据库默认级别为READ-COMMITTED，MySQL默认为REPEATABLE-READ，它利用自身独有的Gap Lock解决了"幻读"，但也因次相比...
mysql innodb_file_per_table=1_MySQL单独存放表空间Innodb_file_per_table参数详解
weixin_42367148的博客
01-21 1392
在mysql中Innodb_file_per_table参数的作用是什么呢，其实许多的朋友是不知道的，今天我们来看这篇MySQL单独存放表空间Innodb_file_per_table参数详解之后你就懂了哦。MySQL可使用多种引擎，当我们选择使用InnoDB引擎的时候，ibdata1这个文件会随着时间的推移变得越来越大，占据大量的磁盘空间。那么，ibdata1里保存了哪些东西，为什么会变得越来越...
对于innodb_file_per_table=off时，innodb引擎，误删除表的恢复
cuiyangshua0551的博客
07-17 239
对于innodb_file_per_table=off时，innodb引擎，误删除表的恢复。 场景模拟： mysql> show databases; +--------------------+ | ...
mysql innodb_file_per_table=1_mysql ibdata1文件的如何缩小 利用innodb_file_per_table=1
weixin_35992471的博客
01-21 151
参考链接http://www.xpcmd.cn/post/658.htmlhttp://www.mysqlsupport.cn/innodb%E5%85%B1%E4%BA%AB%E8%A1%A8%E7%A9%BA%E9%97%B4vs%E7%8B%AC%E7%AB%8B%E8%A1%A8%E7%A9%BA%E9%97%B4/1备份数据库 停止mysql服务2在/etc/my.cnf中添加innod...
MySQL巡检分享_20180817_徐晨亮1
08-03
3. **事务日志相关参数**：如innodb_flush_log_at_trx_commit、innodb_log_file_size等，需根据业务需求调整以保证数据安全性。 4. **其他参数**：包括innodb_open_files、innodb_data_home_dir、innodb_flush_...
mysql 误删除ibdata1之后的恢复方法
09-10
MySQL数据库的InnoDB存储引擎使用一个名为`ibdata1`的数据文件来存储表数据和索引，以及系统表空间信息。当这个文件被意外删除时，可能会引发严重的数据丢失问题，尤其是在没有最近备份的情况下。然而，如果MySQL...
mysql 误删 恢复_MySQL误删除数据，如何恢复
weixin_35826751的博客
01-18 373
展开全部每个 DBA 是不是都有过删库的经历？删库了没有备份怎么办？备份恢复32313133353236313431303231363533e58685e5aeb931333433626437后无法启动服务什么情况？表定义损坏数据无法读取怎么办？我曾遇到某初创互联网企业，因维护人员不规范的备份恢复操作，导致系统表空间文件被初始化，上万张表无法读取，花了数小时才抢救回来。当你发现数据无法读取时，也许...
mysql truncate恢复_求一个恢复truncate或drop table的完整案例
weixin_29630465的博客
01-19 1004
这两天自己找资料实现了上面的流程,详细步骤如下:1. 锁定当前误操作表->改名->解锁2. 创建新实例,恢复操作在新实例上进行3. 先还原备份-->恢复备份到误操作之前的业务-->恢复误操作之后的业务4. 确认恢复之后的表5. 导入到生产库1. 确认log_bin是否打开mysql> show global variables like 'log_bin';+----...
MySQL5.6开始可以使用独立表空间， innodb_file_per_table=1
cov61598的博客
10-20 711
MySQL5.6开始可以使用独立表空间： MySQL5.6 innodb_file_per_table=1#使用独立表空间，动态参数。（5.6默认OFF...
innodb_file_per_table - 转换为InnoDB
aecuhty88306453的博客
12-31 173
共享InnoDB / var / lib / mysql / ibdata1存储的问题InnoDB表当前将数据和索引存储到共享表空间（/ var / lib / mysql / ibdata1）。由于共享表空间，一个InnoDB表的数据损坏可能导致MySQL无法在整个计算机上启动。修复InnoDB损坏可能非常难以执行，并且可能导致在修复过程中最初未损坏的表的数据丢失。由于MySQL 5....
mysql ibdata1文件的如何缩小 利用innodb_file_per_table=1
weixin_34018202的博客
03-19 391
参考链接 http://www.xpcmd.cn/post/658.html http://www.mysqlsupport.cn/innodb%E5%85%B1%E4%BA%AB%E8%A1%A8%E7%A9%BA%E9%97%B4vs%E7%8B%AC%E7%AB%8B%E8%A1%A8%E7%A9%BA%E9%97%B4/ 1备份数据库 停止mysql服务 2在...
mysql innodb_file_per_table=1_mysql-如何将现有数据库的“ innodb_file_per_table”参数从“ OFF”更改为“ 1”？...
weixin_35633340的博客
02-26 344
从MyISAM切换到InnoBD时,我使用了默认设置.阅读优化技巧后,我意识到每个表在单独的文件中会更好.在每种表格模式下,如何将表格从一个文件转移到单独的文件中？解决方法:如果您使用的是MariaDB 10.x,则innodb_file_per_table = 1是此处的默认设置,因此,只要您使用默认值,新的InnoDB表以及从MyISAM转换为InnoDB的表均已具有单独的表空间.如果您使用的...
Innodb innodb_file_per_table mysql数据分文件储存操作
Lyndon的专栏
05-17 1854
1.备份现有的数据库。 mysqldump -q -uroot -p111111 --add-drop-table --all-databases > C:\ar\all.sql 2.停止mysql，删除原来的ibdata1文件及日志文件ib_logfile*，在mysql.ini中添加： innodb_file_per_table=1 3.还原 mysql  -uroot
mysql innodb_file_per_table=1_ibdata1在innodb_file_per_table=1时增加的快，可能是因为undo[转]...
weixin_28950015的博客
01-27 103
In this DocumentAPPLIES TO:MySQL Server - Version 4.0 and laterInformation in this document applies to any platform.SYMPTOMSIn spite of usinginnodb_file_per_tablethe shared tablespace (ibdata1) keep...
InnoDB 引擎独立表空间 innodb_file_per_table
写代码的小孩
10-15 821
起因：zabbix数据所在的mysql server上有个文件在不断的增大m
mysql单独表空间默认文件大小_MySQL单独存放表空间Innodb_file_per_table
weixin_30301989的博客
02-11 233
mysqldump -u root -p --all-database > /tmp/all-database.dump2) 删除数据库中数据#mysql -u root -pmysql> drop database dbname;3) 停止MySQL#service mysqld stop4) 删除ibdata1文件#mv /var/lib/mysql/ibdata1 /tmp#mv...
MySQL 参数- Innodb_File_Per_Table（独立表空间）
最新发布
csdn_life18的博客
01-12 737
如果启用了innodb_file_per_talbe参数，需要注意的是每张表的表空间内存放的只是数据、索引和插入缓冲Bitmap页，其他数据如：回滚信息、插入缓冲索引页、系统事物信息、二次写缓冲（Double write buffer）等还是放在原来的共享表空间内。**缺点：**所有的数据和索引存放到一个文件中，虽然可以把一个大文件分成多个小文件，但是多个表及索引在表空间中混合存储，这样对于一个表做了大量删除操作后表空间中将会有大量的空隙，特别是对于统计分析，日值系统这类应用最不适合用共享表空间。
MySQL InnoDB数据恢复实战：innodb-tools工具详解
当面临意外删除表、误操作或数据损坏等情况时，这些工具可以帮助用户从数据文件中恢复丢失的信息。 在开始恢复前，需要了解以下关键点： 1. innodb-tools适用于InnoDB和XtraDB存储引擎的表，不支持MyISAM表的恢复...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值