-
Bug
-
Resolution: Done
-
Major
-
3.0.GA, 3.1.3.Final, 3.2.0.Beta2
What Debezium connector do you use and what version?
Observed in Debezium 3.0.8, but code is still the same in 3.1/3.2/main
What is the captured database version and mode of deployment?
Captured Database is Oracle 19 EE, on-prem deployment. Using Logminer, unprivileged user on Oracle (not schema/table owner, user created along the lines of https://debezium.io/documentation/reference/3.1/connectors/oracle.html#creating-users-for-the-connector ). Access (SELECT, FLASHBACK) granted to specific tables (not ANY TABLE, as per "Description" in Table 15 of the documentation)
What behavior do you expect?
Connector does not hard-stop on decoding REVOKE FLASHBACK statement.
What behavior do you see?
Connector tells me to open a Jira ticket - here we are.
Do you see the same behaviour using the latest released Debezium version?
Verified that relevant code is unchanged in latest main. (Updating is hard, because this is a regulated environment and involves third-party plugins).
Do you have the connector logs, ideally from start till finish?
Full log captured, but providing detailed logs is difficult (regulated environment).
How to reproduce the issue using our tutorial deployment?
Capture Oracle database using unprivileged user. An erroneous "REVOKE SELECT, FLASHBACK ON (table)" has been issued on the Oracle side. The Debezium connector terminates the logmining session and itself (the fact that this revoke was issued is entirely on our side).
Relevant Log Excerpt: debezium_revoke_fail.txt
Implementation ideas (optional)
- depends on
-
DBZ-9302 Align Debezium Oracle DDL grammar with upstream
-
- Resolved
-