Replication Down: Last_Error: Could not execute Write_rows event on table (Doc ID 2029147.1)

Last updated on SEPTEMBER 01, 2015

Applies to:

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

Symptoms

In a Standard Master -> Slave Replication Environment, the replication has stopped giving an error 1114

  Last_Error: Could not execute Write_rows event on table data_
import.dp_specialty; The table 'table_name_here' is full, Error_code: 1114; handler
 error HA_ERR_RECORD_FILE_FULL; the event's master log BINLOG.000045, end
_log_pos 112428295


Changes

Consider if any changes have been made recently to the Master. In this simple example, a change to TEMP_TABLE_SIZE had been made on which doubled the size on the Master, but hadn't been enacted on the Slave.

 

 

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