-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
2.5.4.GA
-
True
-
-
False
-
High
-
-
-
-
-
Critical
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
Debezium 2.5.4
What is the connector configuration?
curl -i -X POST -H "Accept:application/json" -H "Content-Type:application/json" \
http://localhost:8083/connectors/ -d '{
"name": "debezium-ora-001",
"config":
}'
What is the captured database version and mode of deployment?
On-premises Oracle EE 19.0.0.0
What behavior do you expect?
it should work for STANDBY
What behavior do you see?
Connector Error during snapshot in step 3
[2024-05-23 16:26:45,532] INFO [debezium-ora-001|task-0] Snapshot step 3 - Locking captured tables [LOGSTBY.LOCAL.CUSTOMER_ORDER, LOGSTBY.LOCAL.CUSTOMER_ORDER_ITEM, LOGSTBY.LOCAL.REGIONS] (io.debezium.relational.RelationalSnapshotChangeEventSource:139)
[2024-05-23 16:26:46,690] ERROR [debezium-ora-001|task-0] Error during snapshot (io.debezium.relational.RelationalSnapshotChangeEventSource:179)
java.sql.SQLException: ORA-1622
java.sql.SQLException: ORA-16224: Database Guard is enabled
select guard_status from v$database;
GUARD_S
-------
STANDBY
Do you see the same behaviour using the latest relesead Debezium version?
Yes
Do you have the connector logs, ideally from start till finish?
(You might be asked later to provide DEBUG/TRACE level log)
yes
How to reproduce the issue using our tutorial deployment?
Feature request or enhancement
BUG
For feature requests or enhancements, provide this information, please:
Which use case/requirement will be addressed by the proposed feature?
With the LogMiner with read/write access with gaurd status set as "STANDBY" it is NOT working with Debezium 2.5.4