-
Bug
-
Resolution: Done
-
Major
-
3.2.3.Final, 3.2.4.Final, 3.3.0.Final, 3.3.1.Final
-
None
In order to make your issue reports as actionable as possible, please provide the following information, depending on the issue type.
Bug report
For bug reports, provide this information, please:
What Debezium connector do you use and what version?
Debezium Oracle connector on version 3.2 and 3.3
What is the connector configuration?
We are using debezium-server, so I will send the configuration in Yaml
source: connector: class: io.debezium.connector.oracle.OracleConnector offset: storage: ~: io.debezium.storage.jdbc.offset.JdbcOffsetBackingStore jdbc: table: name: table # connection: # url: <FROM_ENV> schema: include: list: schema history: internal: ~: io.debezium.storage.jdbc.history.JdbcSchemaHistory # We don't care about ddl, so set this to true on unparseable issues skip: unparseable: ddl: false jdbc: table: name: table # connection: # url: <FROM_ENV> store: only: captured: tables: ddl: true databases: ddl: true key: converter: schemas: enable: false value: converter: schemas: enable: false skip: messages: without: change: true include: schema: changes: false database: connection: adapter: logminer # hostname: <FROM_ENV> # port: <FROM_ENV> # user: <FROM_ENV> # password: <FROM_ENV> # dbname: <FROM_ENV> # pdb.name: <FROM_ENV> topic: prefix: 'prefix' snapshot: mode: no_data table: include: list: | tables column: include: list: | columns # Not using compaction, so we can set this to false tombstones: 'on': delete: false message: key: columns: | our columns log: mining: strategy: online_catalog query: filter: mode: in restart: connection: true flush: table: name: SOME_TABLE transaction: retention: ms: 300000
What is the captured database version and mode of deployment?
Oracle 19 running on OCI
What behavior do you expect?
We expect debezium to restart the connection and mining session every 15min or when a log switch occurs
What behavior do you see?
The mining session and connection are restarted every 5 seconds or so. This is a major issue as it severely impacts performance and floods the database with new sessions and connections.
Do you see the same behaviour using the latest released Debezium version?
(Ideally, also verify with latest Alpha/Beta/CR version)
The issue happens on 3.2.3+ and 3.3 currently, but previously, 3.2.2 works as intended
Do you have the connector logs, ideally from start till finish?
I will attach part of our logs here using a version that has this bug. As the debug logs are too big, I cannot attach the logs from start to finish.
Note that on 3.2.2, the restarts occur when there is a log switch or our session timeout ms runs out. I am pretty sure this is not a DB issue unless something changed in debezium that would require us to setup the database again. We also checked that no log switches happened on Oracle
How to reproduce the issue using our tutorial deployment?
As I am using debezium server, I don't know how to reproduce the issue on the tutorial deployment.
Feature request or enhancement
For feature requests or enhancements, provide this information, please:
Which use case/requirement will be addressed by the proposed feature?
<Your answer>
Implementation ideas (optional)
<Your answer>