Details

Type: Bug
Resolution: Unresolved
Priority: Major
Fix Version/s: 2.4-backlog
Affects Version/s: 2.2.0.Alpha1
Component/s: oracle-connector
Labels:
- connector
- oracle
- standby

Blocked:
False
Blocked Reason:
None
Ready:
False

Severity:
Important

SFDC Cases Counter:
SFDC Cases Links:

Description

In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.

Bug report

Related to https://issues.redhat.com/browse/DBZ-3866

this fix still doesn't work with read only physical stand by.

What Debezium connector do you use and what version?

Debezium V2.2.0 Alpha

What is the connector configuration?

We use the new parameter from V2.2.0 Alpha1 (Also documentation doesn't reflect the new parameter)

internal.log.mining.read.only=true

connector.class=io.debezium.connector.oracle.OracleConnector
database.hostname=dbhost
database.port=1521
database.dbname=dbname1
database.user=user
database.password=password
topic.prefix=dbname1
tasks.max=1
tombstones.on.delete=true
decimal.handling.mode=double
time.precision.mode=adaptive
snapshot.locking.mode=none
snapshot.mode=initial
internal.log.mining.read.only=true
schema.include.list=schema1
table.include.list=schema1.table1,schema1.table2
schema.history.internal.store.only.captured.tables.ddl=true
schema.history.internal.kafka.bootstrap.servers=kafka:9092
schema.history.internal.kafka.topic=dbhistory.dbname1

What is the captured database version and mode of depoyment?

(E.g. on-premises, with a specific cloud provider, etc.)

On-premises Oracle EE 19.0.0.0

What behaviour do you expect?

Able to extract the CDC from tables specified

What behaviour do you see?

Connector didn't capture any schemas in step 5. Waited for about 2 mins with no error messages and auto restarted connector after 5 mins at step 6.

Snapshot step 5 - Reading structure of captured tables (io.debezium.relational.RelationalSnapshotChangeEventSource:117)

Connector fails with oracle errors on Snapshot - Final stage

Snapshot step 6 - Persisting schema history (io.debezium.relational.RelationalSnapshotChangeEventSource:121)
 Capturing structure of table dbname1.schema1.table1 (io.debezium.connector.oracle.OracleSnapshotChangeEventSource:208)
Snapshot - Final stage (io.debezium.pipeline.source.AbstractSnapshotChangeEventSource:88)
 Snapshot was not completed successfully, it will be re-executed upon connector restart (io.debezium.pipeline.source.AbstractSnapshotChangeEventSource:97)
 Producer failure (io.debezium.pipeline.ErrorHandler:38)
 
io.debezium.DebeziumException: io.debezium.DebeziumException: java.sql.SQLException: ORA-16000: database or pluggable database open for read-only access
ORA-06512: at SYS.DBMS_LOCK, line 378
ORA-06512: at SYS.DBMS_LOCK, line 411
ORA-06512: at SYS.KUPU$UTILITIES_INT, line 1738
ORA-06512: at SYS.DBMS_METADATA, line 1216
ORA-06512: at SYS.DBMS_METADATA, line 8546
ORA-06512: at line 1
    at io.debezium.pipeline.source.AbstractSnapshotChangeEventSource.execute(AbstractSnapshotChangeEventSource.java:85)
    at io.debezium.pipeline.ChangeEventSourceCoordinator.doSnapshot(ChangeEventSourceCoordinator.java:155)
    at io.debezium.pipeline.ChangeEventSourceCoordinator.executeChangeEventSources(ChangeEventSourceCoordinator.java:137)
    at io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:109)
    at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
    at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
    at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
    at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
    at java.base/java.lang.Thread.run(Thread.java:829)

Do you see the same behaviour using the latest relesead Debezium version?

(Ideally, also verify with latest Alpha/Beta/CR version)

yes, V2.2.0 Alpha1

Do you have the connector logs, ideally from start till finish?

(You might be asked later to provide DEBUG/TRACE level log)

Attached above the relevant log

How to reproduce the issue using our tutorial deployment?

Need to setup the Oracle physical standby database to test this. Check the oracle website. I dont have that information.

Feature request or enhancement

For feature requests or enhancements, provide this information, please:

Which use case/requirement will be addressed by the proposed feature?

Allow reading from Oracle read-only physical Oracle

Implementation ideas (optional)

Attachments

Issue Links

impacts account

DBZ-3866 Allow reading from read-only Oracle standby disaster/recovery

Closed