Debezium Error Reference

The most common Debezium connector errors with root causes and step-by-step fixes. Click any error for details.

Error signal	Connectors	Severity
Replication
`ERROR: replication slot "debezium" already exists`	PostgreSQL	high	Details →
`ERROR: replication slot "debezium" is active for PID ...`	PostgreSQL	high	Details →
`FATAL: could not write to file "pg_wal/..." — disk full (no Debezium error, PostgreSQL-side symptom)`	PostgreSQL	high	Details →
`Creation of replication slot failed; query to create replication slot timed out — make sure there are no long-running queries on the database`	PostgreSQL	high	Details →
Offset
`Saved offset is before replication slot's confirmed_flush_lsn; streaming will start from the confirmed_flush_lsn`	PostgreSQL	high	Details →
`The connector is trying to read binlog starting at binlog file 'mysql-bin.000003', pos=..., but this is no longer available on the server`	MySQL MariaDB	high	Details →
`Command failed with error 286 (ChangeStreamHistoryLost) / error 280 (ChangeStreamFatalError): resume point was not found in the oplog`	MongoDB	high	Details →
`No previous offset found — starting new snapshot`	PostgreSQL MySQL SQL Server MongoDB MariaDB	high	Details →
Setup
`ERROR: publication "dbz_publication" does not exist`	PostgreSQL	high	Details →
`ERROR: must be superuser to create FOR ALL TABLES publication`	PostgreSQL	high	Details →
`ERROR: logical decoding requires wal_level >= logical`	PostgreSQL	high	Details →
`The MySQL server is not configured to use a ROW binlog_format, which is required for this connector to work properly`	MySQL MariaDB	high	Details →
`Access denied for user 'debezium'@'%' (using password: YES) — REPLICATION CLIENT command denied`	MySQL MariaDB	high	Details →
`This database (mydb) does not have CDC enabled`	SQL Server	high	Details →
`No maximum LSN recorded in the database; SQL Server Agent is not running`	SQL Server	high	Details →
`Invalid object name 'cdc.fn_cdc_get_all_changes_dbo_customers'`	SQL Server	high	Details →
Configuration
`FATAL: number of requested standby connections exceeds max_wal_senders (currently N)`	PostgreSQL	high	Details →
`Cannot replicate anonymous transaction when AUTO_POSITION = 1`	MySQL	high	Details →
`ConnectException: Error configuring an instance of KafkaSchemaHistory; check the logs for details`	SQL Server MySQL MariaDB	high	Details →
`ConnectException: snapshot.mode.custom.name is not set but snapshot.mode=custom`	PostgreSQL MySQL SQL Server MongoDB MariaDB	high	Details →
Schema History
`Encountered change event for table db.table_name whose schema isn't known to this connector`	MySQL MariaDB	high	Details →
`io.debezium.text.ParsingException: DDL statement couldn't be parsed`	MySQL MariaDB	high	Details →
`The db history topic or its content is fully or partially missing. Please check database schema history topic configuration and re-execute the snapshot.`	MySQL MariaDB SQL Server	high	Details →
Resources
`org.apache.kafka.common.errors.RecordTooLargeException: The message is N bytes when serialized which is larger than 1048576`	PostgreSQL MySQL SQL Server MongoDB MariaDB	high	Details →
`java.lang.OutOfMemoryError: Java heap space`	PostgreSQL MySQL SQL Server MongoDB MariaDB	high	Details →