MySQL 5.5 Replication Error when Restoring Slave from mysqldump Backup Using --single-transaction and --flush-log (Doc ID 1378033.1)

Last updated on MAY 01, 2017

Applies to:

MySQL Server - Version 5.5 and later
Information in this document applies to any platform.

Symptoms

When making a backup with mysqldump using both the options --single-transaction and --flush-log, the resulting backup dump is inconsistent. This causes a slave reloaded from the backup to break when replication is resumed.

Changes

This happens with MySQL version 5.5 and later.

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