mysqlbinlog
==========
The server's binary log consists of files containing “events” that describe modifications to database contents. The server writes these files in binary format. To display their contents in text format, use the mysqlbinlog utility. You can also use mysqlbinlog to display the contents of relay log files written by a slave server in a replication setup because relay logs have the same format as binary logs.
For statement-based logging, event information includes the SQL statement, the ID of the server on which it was executed, the timestamp when the statement was executed, how much time it took, and so forth. For row-based logging, the event indicates a row change rather than an SQL statement.
Parameters:
log-bin = /u03/mysqldata/$DB_NAME/logs/bin/mysql-bin
log_bin_index = /u03/mysqldata/$DB_NAME/logs/bin/mysql-bin.log.index
binlog_format=mixed
1>
The binary log files and its data are likely to be very huge, thus making it almost impossible to read anything on screen. However, you can pipe the output of mysqlbinlog into a file which can be open up for later browsing in text editor, by using the following command:
mysqlbinlog binlog.000001 > filename.txt
2> –start-datetime=datetime
Start reading the binary log at the first event having a timestamp 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:
mysqlbinlog --start-datetime="2005-12-25 11:25:56" binlog.000001
3> –stop-datetime=datetime
Stop reading the binary log at the first event having a timestamp equal or posterior to the datetime argument. This option is useful for point-in-time recovery. See the description of the –start-datetime option for information about the datetime value.
4> –start-position=N
Start reading the binary log at the first event having a position equal to the N argument. This option applies to the first log file named on the command line.
5> –stop-position=N
Stop reading the binary log at the first event having a position equal or greater than the N argument. This option applies to the last log file named on the command line.
6> --verbose::Reconstruct row events as SQL statements
Reconstruct row events and display them as commented SQL statements. If this option is given twice, the output includes comments to indicate column data types and some metadata.
mysqlbinlog -v log_file
mysqlbinlog -vv log_file
References:
https://dev.mysql.com/doc/refman/5.6/en/mysqlbinlog.html
==========
The server's binary log consists of files containing “events” that describe modifications to database contents. The server writes these files in binary format. To display their contents in text format, use the mysqlbinlog utility. You can also use mysqlbinlog to display the contents of relay log files written by a slave server in a replication setup because relay logs have the same format as binary logs.
For statement-based logging, event information includes the SQL statement, the ID of the server on which it was executed, the timestamp when the statement was executed, how much time it took, and so forth. For row-based logging, the event indicates a row change rather than an SQL statement.
Parameters:
log-bin = /u03/mysqldata/$DB_NAME/logs/bin/mysql-bin
log_bin_index = /u03/mysqldata/$DB_NAME/logs/bin/mysql-bin.log.index
binlog_format=mixed
1>
The binary log files and its data are likely to be very huge, thus making it almost impossible to read anything on screen. However, you can pipe the output of mysqlbinlog into a file which can be open up for later browsing in text editor, by using the following command:
mysqlbinlog binlog.000001 > filename.txt
2> –start-datetime=datetime
Start reading the binary log at the first event having a timestamp 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:
mysqlbinlog --start-datetime="2005-12-25 11:25:56" binlog.000001
3> –stop-datetime=datetime
Stop reading the binary log at the first event having a timestamp equal or posterior to the datetime argument. This option is useful for point-in-time recovery. See the description of the –start-datetime option for information about the datetime value.
4> –start-position=N
Start reading the binary log at the first event having a position equal to the N argument. This option applies to the first log file named on the command line.
5> –stop-position=N
Stop reading the binary log at the first event having a position equal or greater than the N argument. This option applies to the last log file named on the command line.
6> --verbose::Reconstruct row events as SQL statements
Reconstruct row events and display them as commented SQL statements. If this option is given twice, the output includes comments to indicate column data types and some metadata.
mysqlbinlog -v log_file
mysqlbinlog -vv log_file
References:
https://dev.mysql.com/doc/refman/5.6/en/mysqlbinlog.html
No comments:
Post a Comment