Skip to main content

Error classes

Generated from ErrorCode by ErrorClassesReferenceTest; do not edit by hand.

Every condition that stops a capture task has a stable code, an operator action and a runbook. Kafka Connect shows the task's error message in the task status in the form [CDC-2002] what happened Operator action: what to do Runbook: link, and the stop event on the ops topic carries the code, the action and the link as separate fields. Codes are never reused or renumbered.

Codes marked as retried are handled inside the task first: the engine reconnects or mines the same range again, and the task stops with the code only when retrying has not helped. Every other code stops the task at once. Nothing is skipped in either case: once the cause is fixed and the task restarted, it resumes from its last acknowledged position.

CodeNameRetriedWhat the connector sawRunbook
CDC-1001TRANSIENT_DATABASEyesThe connection or the instance became unavailable. The engine reconnects with backoff and stops only when cdc.retry.max.time.ms runs out, or at once for an ORA code it does not classify.transient-database
CDC-1002MINING_STEP_RETRYyesA LogMiner step failed with an error that mining the same range again fixes. The step is mined again; the task stops after more than 20 such failures in a row.mining-step-retry
CDC-2001LOG_GAPnoThe redo logs found for a thread do not cover the range to mine: a sequence is missing, or the first or last log falls inside the range.log-gap
CDC-2002LOG_PURGEDnoA redo log the connector still needs is marked deleted in the catalog, or cannot be read although the catalog lists it.log-purged
CDC-3001DECODEnoA row of a captured table could not be decoded with cdc.on.decode.error=fail, or a captured table cannot be keyed or read.decode
CDC-3002CORRUPTIONnoLogMiner reported MISSING_SCN, a spill file failed its integrity check, or the stored offset cannot be read.corruption
CDC-3003LOB_TOO_LARGEnoA committed LOB value was larger than cdc.lob.max.bytes with cdc.lob.oversize.action=fail.lob-too-large
CDC-4001BUFFER_EXHAUSTEDnoSpilled changes of open transactions exceeded cdc.buffer.spill.max.bytes, or writing to the spill directory failed.buffer-exhausted
CDC-4002JOURNAL_CORRUPTIONnoAt start, a journaled transaction is missing a chunk, or a journal record cannot be read with cdc.journal.converter.journal-corruption
CDC-4003MINING_STALLEDnoA mining step over a single redo log timed out at cdc.mining.query.timeout.ms three times in a row.mining-stalled
CDC-4004TRANSACTION_TOO_OLDnoA transaction stayed open longer than cdc.transaction.max.age.ms with cdc.transaction.max.age.action=fail.transaction-too-old
CDC-5001TOPOLOGYnoThe stored offset belongs to another database (DBID or RESETLOGS changed), no valid archive destination can be mined, or the database has more than one enabled redo thread (RAC), which this release does not capture.topology
CDC-5002PRIVILEGEnoThe database refused the connector user: a grant or a view is missing, or the login itself failed.privilege
CDC-6001DICTIONARY_UNAVAILABLEnoRows were written before a later DDL on their table, and no usable dictionary build in the redo or no exact schema version covers them.dictionary-unavailable
CDC-6002UNSUPPORTED_DDLnoA DDL statement on a captured table could not be classified.unsupported-ddl
CDC-6003SCHEMA_MISMATCHnoAt start, a schema version on the schema topic differs from the dictionary and no DDL ahead of the resume point explains it.schema-mismatch
CDC-6004NAME_COLLISIONnoTwo columns of a table adjust to the same field name under cdc.field.name.adjustment.mode, or two tables route to the same topic only because characters Kafka does not allow became underscores.name-collision
CDC-7001ORPHAN_RELEASE_VIOLATIONnoA COMMIT arrived for a transaction that orphan detection released or the age policy discarded.orphan-release-violation
CDC-7002ORPHAN_TRANSACTIONnoA buffered transaction is no longer known to the database and cdc.transaction.orphan.action=fail.orphan-transaction
CDC-7003RESUME_FLOOR_VIOLATIONnoA row or a COMMIT of a redo thread arrived at or before what an offset already handed to Kafka Connect covers on that thread, so a restart from that offset would skip it.resume-floor-violation
CDC-8001SNAPSHOT_TOO_OLDnoA snapshot chunk still met ORA-01555 or ORA-08181 at the smallest chunk size.snapshot-too-old