Skip to content

CONCEPT Cited by 1 source

Oracle LogMiner CDC

Definition

Oracle LogMiner CDC is the per-engine change-data-capture mechanism that consumes Oracle LogMiner — the Oracle Enterprise Edition redo-log-mining utility — to reconstruct row-level inserts, updates, and deletes from Oracle's redo log stream.

Sibling to the other per-engine CDC mechanisms canonicalised on the wiki:

Engine Per-engine CDC mechanism
PostgreSQL concepts/logical-replication (WAL at wal_level=logical)
MySQL concepts/binlog-replication
MongoDB concepts/mongodb-change-streams (oplog-backed)
Cloud Spanner concepts/spanner-change-stream
Oracle LogMiner on the redo log
SQL Server CDC change tables

Why it matters

Oracle's redo log is the sequential WAL that records every row- level change for crash recovery + physical replication. LogMiner provides the API surface for reading that log and reconstructing higher-level INSERT / UPDATE / DELETE semantics. Any CDC consumer wanting to ride Oracle's change stream is effectively a LogMiner client:

  • Redpanda Connect Oracle CDC (oracledb_cdc) — canonicalised on the wiki in the 2026-04-09 launch post.
  • Debezium Oracle connector — Kafka-Connect- hosted peer.
  • Oracle GoldenGate — Oracle's own commercial replication product (separately licensed).

Load-bearing canonical claim

Verbatim from the Redpanda Connect Oracle CDC launch:

"because it uses Oracle LogMiner, which ships with Oracle Enterprise Edition, there's no additional Oracle licensing required." (Source: sources/2026-04-09-redpanda-oracle-cdc-now-available-in-redpanda-connect)

The licensing claim is load-bearing: Oracle GoldenGate, the alternative commercial CDC path, carries its own six-figure licence. LogMiner-based CDC rides on the existing Enterprise Edition entitlement.

Structural properties

Typical snapshot + stream shape:

  • Snapshot phase — initial consistent snapshot of captured tables.
  • Streaming phase — tail the redo log from the snapshot- boundary SCN (System Change Number) forward, emit insert/update/delete events.

Canonical offset-durability class for LogMiner-based CDC: varies by consumer. Redpanda Connect's oracledb_cdc uses in-source checkpointing (a table inside Oracle itself). Debezium's Oracle connector uses Kafka Connect's offset topic. GoldenGate uses its own checkpoint trail file.

Prerequisites

  • Oracle Enterprise Edition required (Standard Edition does not ship LogMiner).
  • Supplemental logging must be enabled on captured tables (or database-wide) — otherwise the redo stream lacks the before-images necessary to reconstruct UPDATE/DELETE semantics. (Not walked by the 2026-04-09 launch post, but implicit in any LogMiner-based CDC deployment.)

Operational caveats (undisclosed in the 2026-04-09 post)

  • Supplemental logging configuration.
  • Archive-log retention sizing.
  • Continuous-mining mode deprecation in Oracle 19c.
  • LogMiner overhead on the source primary under OLTP load.

Seen in

Last updated · 470 distilled / 1,213 read