EC
3199
MariaDBERRORCommonReplicationHIGH confidence

Replica requires full row image for this operation

Production Risk

Critical — replication stops until resolved.

Why it happens
  1. 1Primary is using binlog_row_image=MINIMAL or NOBLOB but the replica requires FULL.
  2. 2Row-based replication event missing columns needed by the replica.
How to reproduce
trigger — this will error
trigger — this will error
-- Occurs on replica when applying a row event with insufficient column data.

expected output

ERROR 3199 (HY000): Slave requires full row image to perform this operation.

Fix 1

Set binlog_row_image=FULL on the primary

Set binlog_row_image=FULL on the primary
SET GLOBAL binlog_row_image = 'FULL';

Why this works

FULL row image includes all columns, satisfying replica requirements.

Fix 2

Ensure matching schema on primary and replica

Ensure matching schema on primary and replica
-- Verify SHOW CREATE TABLE matches on both servers.

Why this works

Schema differences can cause partial image problems.

What not to do

✕

Sources
Official documentation ↗

MySQL 8.0 — 3199 ER_SLAVE_REQUIRE_FULL_IMAGE

Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev

← All MariaDB errors