MEB Backup failed with error 'The slave SQL thread did not drop all temporary tables within 300 seconds' from 3.12.3/4.0 when backing up on SLAVE (Doc ID 2170246.1)

Last updated on JULY 26, 2017

Applies to:

MySQL Enterprise Backup - Version 3.12 and later
Information in this document applies to any platform.

Symptoms

MEB Backup failed with error 'The slave SQL thread did not drop all temporary tables within 300 seconds' from 3.12.3

 

Changes

 From MEB 3.12.3 and MEB 4.0.1 to avoid completing a backup of a slave server when temporary tables are still open on the slave, which will cause the restored slave server to be in an inconsistent replication state, mysqlbackup now has a new mechanism for ensuring that all temporary tables have already been closed before finishing a slave backup. See Temporary tables on statement-based replication (SBR) slave for details. A new option, --safe-slave-backup-timeout, has been created for specifying the time mysqlbackup will wait for all temporary tables to be closed before it times out. (Bug #19158516 )

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