OpenLogReplicator is an open-source Oracle database Change Data Capture (CDC) solution written in C++.
It reads transactions directly from Oracle redo log files (by parsing binary redo logs) and streams changes in JSON or Protobuf format to various targets.
- Kafka
- Flat file
- Network stream (plain TCP/IP or ZeroMQ)
- Discard (for testing)
OpenLogReplicator processes mission-critical data streams where correctness is non-negotiable. While the source code is GPL, every official release is validated against a private, proprietary test suite with 1,000+ edge-case scenarios, including Oracle RAC, ASM, and multiple redo log versions. This internal validation is the only way to guarantee stability and prevent silent data corruption in production.
The Oracle Redo Log format is undocumented and extremely complex. Using AI-generated patches (for example, ChatGPT or GitHub Copilot) to modify the core parser, or maintaining private forks, is highly risky and can introduce undetectable corruption. Production deployments should use only officially signed binaries that have passed the full internal regression suite.
OpenLogReplicator is released under the GNU General Public License (GPL).
If you have received software that is based on OpenLogReplicator, you are legally entitled to obtain the full corresponding source code of that software.
For details, see the LICENSE file.
For a quick start, refer to the OpenLogReplicator tutorials repository.
- Introduction to OpenLogReplicator
- User Manual
- Reference Manual
- Configuration
- Installation Guide
- Release Notes
- Metrics
- Troubleshooting Guide
- Log Message Guide
- Experimental Features
Community discussion is available via Gitter chat.
OpenLogReplicator can be used together with Debezium CDC as a replacement for the LogMiner reader.
| Debezium | OLR minimal version | OLR recommended version |
|---|---|---|
| 2.x | 1.3.0 | 1.9.0 |
| 3.x | 1.3.0 | 1.9.0 |
OpenLogReplicator is primarily developed and maintained by its author.
Bug reports, feature requests, and discussions are welcome. Please note that ongoing development, maintenance, and support require significant time and effort.
- Issue reports are handled on a best-effort basis.
- Companies using OpenLogReplicator in production are encouraged to support its maintenance.
If OpenLogReplicator is critical to your systems, consider financially supporting the project or contributing improvements upstream instead of maintaining private forks.
Professional support, priority bug fixes, and feature development are available.
If you are:
- Running OpenLogReplicator in production
- Building commercial products or services on top of it
- Requiring guaranteed response times or roadmap influence
please consider the official support options at: https://www.bersler.com/openlogreplicator/support/
Our stability is powered by a dedicated hardware lab. Learn more about our testing infrastructure and how you can support it in SPONSORS.md. If you find OpenLogReplicator useful, consider supporting its development.
Your support directly helps ensure:
- Continued maintenance
- Faster bug fixes
- New features
- Long-term project sustainability
Any contribution is appreciated.
Enterprise collaboration is focused on risk mitigation and certified releases, not generic support. A Private Validation Service is available to test your configuration and workload against the internal regression suite and deliver certified results.
https://www.bersler.com/openlogreplicator/support/
Sponsorship funds maintain the dedicated Oracle testing lab, including servers, storage, and licensing required for full validation. This directly sustains reliable releases and long-term project continuity.
See SPONSORS.md for sponsorship tiers and enterprise options.
