mysqlbinlog With Verbose Outputs Corrupted Data or Crashes

(Doc ID 2024188.1)

Last updated on MARCH 08, 2017

Applies to:

MySQL Cluster - Version 6.3 to 7.3 [Release 6.3 to 7.3]
MySQL Server - Version 5.6 to 5.7 [Release 5.6 to 5.7]
Information in this document applies to any platform.


With binlog_row_image = MINIMAL (or in MySQL Cluster having ndb_log_updated_only enabled) the verbose output of mysqlbinlog is corrupted for changes were both of the following conditions are fulfilled:

The corruption can also cause mysqlbinlog to crash.

The issue can be reproduced using:

  • Created a table with nine or more columns.
  • Cause

    Sign In with your My Oracle Support account

    Don't have a My Oracle Support account? Click to get started

    My Oracle Support provides customers with access to over a
    Million Knowledge Articles and hundreds of Community platforms