Oracle downstream database

9 views
Skip to first unread message

Alexei Rybalev

unread,
Jun 1, 2026, 11:42:35 PM (18 hours ago) Jun 1
to debezium
Hello, debezium team!
We have oracle downstream db and oracle connector version 3.5.
Snip of prop file

"connector.class": "io.debezium.connector.oracle.OracleConnector",

"database.hostname": "ds_host",

"database.user": "debezium",

"database.dbname": "ds_db",

"log.mining.strategy": "dictionary_from_file",

"internal.log.mining.read.only": "true",

"log.mining.read.only.hostname": "ds_host",

"log.mining.path.dictionary": "/torastg/dictionary.ora",

 When started we got error

io.debezium.DebeziumException: Cannot create read only connection, read only hostname is empty

        at io.debezium.connector.oracle.OracleConnectionFactory$ReadOnlyConnectionFactory.buildReadOnlyConfig(OracleConnectionFactory.java:84)


What we did wrong?

Thanks, best regards.

Chris Cranford

unread,
1:14 PM (5 hours ago) 1:14 PM
to debe...@googlegroups.com
Hi Alexei -

This post is a bit ironic, as I was just working fixing the bugs around read-only connections [1].

Suffice to say, mining from a downstream mining database is not currently supported. The requirements for downstream mining are significantly different for LogMiner, and the way the current code is designed, many of the sources for data points needed to capture changes are simply unavailable in the downstream system, as it acts solely as a replay machine, not actually applying the changes.

What is currently supported (once the fixes in the aforementioned PR are merged) will include:

    * LogMiner capture from a primary database in either write or read-only mode.
    * LogMiner capture from a physical or logical standby database.
    * XStream capture is not supported by Oracle from a standby system.
    
For downstream mining specifically (dbz#1848) [2]

    * XStream will be fully supported first (complexity here is lower with faster turn around)
    * A full LogMiner solution will take some time, perhaps available in 3.7 or 3.8 by end of year. 

So the short-answer is you aren't doing anything incorrectly. The documentation was simply a bit misleading unfortunately between physical standby vs downstream.

If you have any further questions, let us know.
-cc

[1] https://github.com/debezium/debezium/pull/7502
[2] https://github.com/debezium/dbz/issues/1868
--
You received this message because you are subscribed to the Google Groups "debezium" group.
To unsubscribe from this group and stop receiving emails from it, send an email to debezium+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/debezium/68154898-b039-4cd1-ab98-a8e87afec487n%40googlegroups.com.

Reply all
Reply to author
Forward
0 new messages