Configure Openlog Replicator for Oracle¶

Overview¶

In addition to LogMiner-based replication, SynchDB supports Openlog Replicator (OLR) as a data source for Oracle connectors. This integration enables low-latency, redo log–based change data capture from Oracle databases via a standalone replication server.

This guide details the configuration steps necessary to associate an Oracle connector with an OLR endpoint using synchdb_add_olr_conninfo() and synchdb_del_olr_conninfo().

Requirements¶

Openlog Replicator Version: 1.3.0 (verified compatibility for Debezium 2.7.x)
Oracle instance with redo logs accessible to OLR
Openlog Replicator must be configured and running
An existing Oracle connector in SynchDB (created using synchdb_add_conninfo())

Refer to this external guide for details on deploying Openlog Replicator via Docker.

`synchdb_add_olr_conninfo()`¶

Registers an Openlog Replicator endpoint for an existing Oracle connector.

Signature:

synchdb_add_olr_conninfo(
    conn_name TEXT,     -- Name of the connector
    olr_host TEXT,      -- Hostname or IP of the OLR instance
    olr_port INT,       -- Port number exposed by OLR (typically 7070)
    olr_source TEXT     -- Oracle source name as configured in OLR
)

Example:

This instructs SynchDB to stream changes for the connector oracleconn from the Openlog Replicator instance running at 10.55.13.17:7070, using the Oracle source identifier ORACLE. Call synchdb_start_engine_bgw to start this connector.

SELECT synchdb_add_olr_conninfo('oracleconn', '10.55.13.17', 7070, 'ORACLE');

synchdb_del_olr_conninfo¶

Removes the OLR configuration for a specific connector, reverting it to use LogMiner.