Frm table structure using mysqlfrm recovery method

1, mysqlfrm installation

Since mysqlfrm tool is part of mysql-utilities, then we install mysql-utilities to download the corresponding good source packages, compile installation

shell> tar -xvzf mysql-utilities-1.6.4.tar.gz 

shell> cd mysql-utilities-1.6.4

shell> python ./setup.py build

shell> python ./setup.py install

After the installation is complete, in the corresponding python perform directory, you can execute mysqlfrm and other files.

2, mysqlfrm related parameters introduced

--basedir ：如 --basedir=/usr/local/percona-5.6.21

--server ： 如 --server=user:password@192.168.1.100:3306

--diagnostic ： 开启按字节模式来恢复frm结构

--user :启动MySQL用户，通过为mysql

3, mysqlfrm use

Use --basedir recovery mode:

[ 16:35:29-root@br3cy1sw:~ ]# mysqlfrm --basedir=/usr/local/percona-5.6.21/ /root/t1.frm --port=3434 --user=mysql --diagnostic

# WARNING The --port option is not used in the --diagnostic mode.

# WARNING: The --user option is only used for the default mode.

# WARNING: Cannot generate character set or collation names without the --server option.

# CAUTION: The diagnostic mode is a best-effort parse of the .frm file. As such, it may not identify all of the components of the table correctly. This is especially true for damaged files. It will also not read the default values for the columns and the resulting statement may not be syntactically correct.

# Reading .frm file for /root/t1.frm:

# The .frm file is a TABLE.

# CREATE TABLE Statement:

CREATE TABLE `root`.`t1` (

`a` int(11) NOT NULL,

`b` int(11) DEFAULT NULL,

`c` int(11) DEFAULT NULL,

`d` varchar(600) DEFAULT NULL,

PRIMARY KEY `PRIMARY` (`a`),

KEY `idx_t1_bc` (`b`,`c`)

) ENGINE=InnoDB;

    #...done.

Use --server recovery mode:

[ 16:35:10-root@br3cy1sw:~ ]#mysqlfrm --server=user:password@192.168.1.100:3306 /root/t1.frm --port=3434 --user=mysql --diagnostic

WARNING: Using a password on the command line interface can be insecure.

# WARNING The --port option is not used in the --diagnostic mode.

# WARNING: The --user option is only used for the default mode.

# Source on 192.168.1.100: ... connected.

# CAUTION: The diagnostic mode is a best-effort parse of the .frm file. As such, it may not identify all of the components of the table correctly. This is especially true for damaged files. It will also not read the default values for the columns and the resulting statement may not be syntactically correct.

# Reading .frm file for /root/t1.frm:

# The .frm file is a TABLE.

# CREATE TABLE Statement:

CREATE TABLE `root`.`t1` ( `a` int(11) NOT NULL, `b` int(11) DEFAULT NULL, `c` int(11) DEFAULT NULL,

`d` varchar(200) COLLATE `utf8_general_ci` DEFAULT NULL,

PRIMARY KEY `PRIMARY` (`a`),

KEY `idx_t1_bc` (`b`,`c`)

) ENGINE=InnoDB DEFAULT CHARSET=utf8;

    #...done.

We noticed that the use of recovered --basedir varchar turned out to be three times the --server mode; this should be mysqlfrm when using basedir mode and can not be caused due to the character code verification.