mysql binlog更新记录缺失_mysqlbinlog --处理二进制更新日志的工具

mysqlbinlog:Utility for Processing Binary Log Files

The binary log files that the server generates are written in binary format. To examine these files in text format, use the mysqlbinlog utility.

Invoke mysqlbinlog like this:shell> mysqlbinlog [options] log-file ...

For example, to display the contents of the binary log binlog.000003, use this command:shell> mysqlbinlog binlog.0000003

The output includes all statements contained in binlog.000003, together with other information such as the time each statement took, the thread ID of the client that issued it, the timestamp when it was issued, and so forth.

Normally, you use mysqlbinlog to read binary log files directly and apply them to the local MySQL server. It is also possible to read binary logs from a remote server by using the --read-from-remote-server option.

When you read remote binary logs, the connection parameter options can be given to indicate how to connect to the server, but they are ignored unless you also specify the --read-from-remote-server option. These options are --host, --password, --port, --protocol, --socket, and --user.

You can also use mysqlbinlog to read relay log files written by a slave server in a replication setup. Relay logs have the same format as binary log files.

The binary log is discussed further in Section 5.11.3, “The Binary Log”.

mysqlbinlog supports the following options:

--help, -?

Display a help message and exit.

--database=db_name, -d db_name

List entries for just this database (local log only).

--force-read, -f

With this option, if mysqlbinlog reads a binary log event that it does not recognize, it prints a warning, ignores the event, and continues. Without this option, mysqlbinlog stops if it reads such an event.

--hexdump, -H

Display a hex dump of the log in comments. This output can be helpful for replication debugging. This option was added in MySQL 5.0.16.

--host=host_name, -h host_name

Get the binary log from the MySQL server on the given host.

--local-load=path, -l path

Prepare local temporary files for LOAD DATA INFILE in the specified directory.

--offset=N, -o N

Skip the first N entries.

--password[=password], -p[password]

The password to use when connecting to the server. If you use the short option form (-p), you cannot have a space between the option and the password. If you omit the password value following the --password or -p option on the command line, you are prompted for one.

Specifying a password on the command line should be considered insecure. See Section 5.8.6, “Keeping Your Password Secure”.

--port=port_num, -P port_num

The TCP/IP port number to use for connecting to a remote server.

--position=N, -j N

Deprecated, use --start-position instead.

--protocol={TCP|SOCKET|PIPE|MEMORY}

The connection protocol to use.

--read-from-remote-server, -R

Read the binary log from a MySQL server. Any connection parameter options are ignored unless this option is given as well. These options are --host, --password, --port, --protocol, --socket, and --user.

--result-file=name, -r name

Direct output to the given file.

--short-form, -s

Display only the statements contained in the log, without any extra information.

--socket=path, -S path

For connections to localhost, the Unix socket file to use, or, on Windows, the name of the named pipe to use.

--start-datetime=datetime

Start reading the binary log at the first event having a datetime equal to or later than the datetime argument. The datetime value is relative to the local time zone on the machine where you run mysqlbinlog. The value should be in a format accepted for the DATETIME or TIMESTAMP data types. For example:shell> mysqlbinlog --start-datetime="2004-12-25 11:25:56" binlog.000003

This option is useful for point-in-time recovery.

--stop-datetime=datetime

Stop reading the binary log at the first event having a datetime equal or posterior to the datetime argument. See the description of the --start-datetime option for information about the datetime value. It is useful for point-in-time recovery.

--start-position=N

Start reading the binary log at the first event having a position equal to the N argument.

--stop-position=N

Stop reading the binary log at the first event having a position equal or greater than the N argument.

--to-last-log, -t

Do not stop at the end of the requested binary log of the MySQL server, but rather continue printing until the end of the last binary log. If you send the output to the same MySQL server, this may lead to an endless loop. This option requires --read-from-remote-server.

--disable-log-bin, -D

Disable binary logging. This is useful for avoiding an endless loop if you use the --to-last-log option and are sending the output to the same MySQL server. This option also is useful when restoring after a crash to avoid duplication of the statements you have logged. Note: This option requires that you have the SUPER privilege.

--user=user_name, -u user_name

The MySQL username to use when connecting to a remote server.

--version, -V

Display version information and exit.

You can also set the following variable by using --var_name=value syntax:

open_files_limit

Specify the number of open file descriptors to reserve.

It is also possible to set variables by using --set-variable=var_name=value or -O var_name=value syntax. This syntax is deprecated.

You can pipe the output of mysqlbinlog into a mysql client to execute the statements contained in the binary log. This is used to recover from a crash when you have an old backup (see Section 5.9.1, “Database Backups”):shell> mysqlbinlog hostname-bin.000001 | mysql

Or:shell> mysqlbinlog hostname-bin.[0-9]* | mysql

You can also redirect the output of mysqlbinlog to a text file instead, if you need to modify the statement log first (for example, to remove statements that you do not want to execute for some reason). After editing the file, execute the statements that it contains by using it as input to the mysql program.

mysqlbinlog has the --position option, which prints only those statements with an offset in the binary log greater than or equal to a given position (the given position must match the start of one event). It also has options to stop or start when it sees an event of a given date and time. This enables you to perform point-in-time recovery using the --stop-datetime option (to be able to say, for example, “roll forward my databases to how they were today at 10:30 AM”).

If you have more than one binary log to execute on the MySQL server, the safe method is to process them all using a single connection to the server. Here is an example that demonstrates what may be unsafe:shell> mysqlbinlog hostname-bin.000001 | mysql # DANGER!!

shell> mysqlbinlog hostname-bin.000002 | mysql # DANGER!!

Processing binary logs this way using different connections to the server causes problems if the first log file contains a CREATE TEMPORARY TABLE statement and the second log contains a statement that uses the temporary table. When the first mysql process terminates, the server drops the temporary table. When the second mysql process attempts to use the table, the server reports “unknown table.”

To avoid problems like this, use a single connection to execute the contents of all binary logs that you want to process. Here is one way to do this:shell> mysqlbinlog hostname-bin.000001 hostname-bin.000002 | mysql

Another approach is to do this:shell> mysqlbinlog hostname-bin.000001 > /tmp/statements.sql

shell> mysqlbinlog hostname-bin.000002 >> /tmp/statements.sql

shell> mysql -e "source /tmp/statements.sql"

mysqlbinlog can produce output that reproduces a LOAD DATA INFILE operation without the original data file. mysqlbinlog copies the data to a temporary file and writes a LOAD DATA LOCAL INFILE statement that refers to the file. The default location of the directory where these files are written is system-specific. To specify a directory explicitly, use the --local-load option.

Because mysqlbinlog converts LOAD DATA INFILE statements to LOAD DATA LOCAL INFILE statements (that is, it adds LOCAL), both the client and the server that you use to process the statements must be configured to allow LOCAL capability. See Section 5.6.4, “Security Issues with LOAD DATA LOCAL”.

Warning: The temporary files created for LOAD DATA LOCAL statements are not

Add 1:

关于mysql目录下个文件的作用，这里有一个比较简单的介绍，摘录部分如下：

libmysqld----嵌入式MySQL服务器，它不能独立运行，它是一个函数库，可嵌入到其它程序中，使程序具有MySQL服务器的功能。

myisamchk和isamchk----检查和修复数据表、分析键值的分布情况、禁止或启用数据表索引的工具。

myisampack和pack_isam----压缩数据表并生成只读数据表。

mysql----最常用的一个与服务器交互的命令行客户端程序。

mysqlaccess----一个用来测试数据库访问权限的脚本。

mysqladmin----一个用来执行各种系统维护和管理工作的工具。

mysqlbinlog----一个以ASCII格式显示二进制变更日志内容的工具。

mysqlbug----一个用来生成程序漏洞报告的脚本。

mysql_config----当准备编译基于MySQL的程序时，可以利用这个工具程序来确定该程序的编译选项和标志。

mysqld----MySQL服务器程序，MySQL数据的核心。

mysqld_multi----一个用来同时启动和关闭多个MySQL服务器的脚本。

mysql_safe----一个用来启动和监控MySQL服务器的脚本。

mysqldump----一个用来导出数据表内容的工具。

mysqlhotcopy----数据库备份工具。

mysqlimport----一个对数据表批量加载数据的工具。

mysql_install_db----一个初始化系统权限表和数据目录的脚本。

mysql.server----一个用来启动和关闭MySQL服务器的脚本。

mysqlshow----一个用来显示数据库中数据表的工具。