OpenLogReplicator
bersler.com
What it is
OpenLogReplicator is a free, open-source Oracle change data capture solution written in C++ for self-hosted Linux deployments. It reads transactions directly from Oracle binary redo logs and streams changes as JSON or Protobuf. Destinations include Kafka, flat files, plain TCP/IP or ZeroMQ network streams, and a discard output for testing. The log-based design is intended to minimize impact on the source database. Archived redo logs can be processed, including offline operation while the database is shut down, and actual DDL commands can be tracked. Basic DML filters can restrict processing, such as selecting INSERT operations for a table. Direct Prometheus metrics include DML counters that can carry schema-name tags. Oracle 23c is supported; binary XMLType support for Oracle 11.2 through 21c is experimental. Debezium use is supported with version 1.3.0 as the minimum and 1.9.0 recommended for Debezium 2.x and 3.x. The GPL v3 plan costs nothing.
Spec sheet
- Purpose
- OpenLogReplicator is an open-source Oracle database change data capture solution written in C++.Read 1 Oct 2026 · github.com
- Deployment
- The Docker quick-start tutorial documents running OpenLogReplicator on a Linux 64 machine.Read 1 Oct 2026 · bersler.com
- Support
- Production assistance and proof-of-concept help are available by contacting the author through the contact form.Read 1 Oct 2026 · bersler.com
- Data capture
- It reads transactions directly from Oracle binary redo log files and streams changes in JSON or Protobuf format.Read 1 Oct 2026 · github.com
- Data handling
- Support guidance asks users not to send redo logs containing actual customer or personal data because this could create GDPR or similar legal issues.Read 1 Oct 2026 · bersler.com
- Database impact
- The project is designed for log-based replication from Oracle Database with minimal impact on the source database.Read 1 Oct 2026 · bersler.com
- DDL replication
- OpenLogReplicator supports tracking actual DDL commands.Read 1 Oct 2026 · bersler.com
- Debezium
- OpenLogReplicator can be used with Debezium CDC as a replacement for the LogMiner reader; the repository lists version 1.3.0 as the minimum and 1.9.0 as the recommended version for Debezium 2.x and 3.x.Read 1 Oct 2026 · github.com
- Filtering
- Users can define basic DML filtering rules, such as processing only INSERT operations for a specified table.Read 1 Oct 2026 · bersler.com
- Integrity handling
- If an expected redo log record cannot be decoded, processing stops immediately by default; users can force invalid records to be skipped and continue.Read 1 Oct 2026 · bersler.com
- Offline operation
- It can operate from archived redo logs and can run in offline mode while the database is shut down.Read 1 Oct 2026 · bersler.com
- Oracle support
- The project announcement states that Oracle 23c is supported and that Oracle 11.2 through 21c have experimental binary XMLType support.Read 1 Oct 2026 · bersler.com
- Prometheus
- Version 1.5.0 added direct Prometheus metrics, including counters for DML operations that can be tagged with schema names.Read 1 Oct 2026 · bersler.com
- Targets
- Supported targets include Kafka, flat files, network streams using plain TCP/IP or ZeroMQ, and discard output for testing.Read 1 Oct 2026 · github.com
Plans and prices
Strong points and limits
Strong points
- Free GPL v3 plan
- Reads Oracle redo logs directly
- Supports Kafka and network outputs
- Offline archived-log processing
- Direct Prometheus metrics
Limits
- Linux self-hosted deployment
- Binary XMLType support is experimental
- Invalid records stop processing by default
- Oracle-focused CDC tool
Who it suits
OpenLogReplicator suits teams replicating Oracle changes on Linux through a self-hosted, log-based workflow. It fits users needing Kafka or file outputs, offline redo processing, DDL capture or Debezium compatibility.
Verdict
OpenLogReplicator provides Oracle redo-log capture with multiple destinations, offline operation and monitoring support. Its Linux self-hosted model and Oracle-specific scope define the deployment and database requirements.
Where Specifiction places it
- Change Data Capture Software#13 of 237.6