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

Bug report

Debezium-Springboot appllication is deployed on on-prem linux boxes. DB used is oracle to stream the events. One instance works fine without any issues which connects to Oracle-1, but second app same code connector goes down every 3 or 4 hours. No exception thrown when the connector goes down.

What Debezium connector do you use and what version?

io.debezium:debezium-connector-oracle:2.0.0.Final'

What is the connector configuration?

io.debezium.config.Configuration.create()
      .with("name", DbzConnectorName)
      .with("connector.class", DbzConnectorClass)
      .with("offset.storage", "org.apache.kafka.connect.storage.FileOffsetBackingStore")
      .with("offset.storage.file.filename", offsetStorageTempFile.getAbsolutePath())
      .with("offset.flush.interval.ms", "60000")
      .with("database.hostname", DbHost)
      .with("database.port", DbPort)
      .with("database.user", DbUsername)
      .with("database.password", DbPassword)
      .with("database.dbname", DbName)
      .with("schema.include.list", schemaList)
      .with("table.include.list", tableList)
      .with("include.schema.changes", "false")
      .with("topic.prefix", topicPrefix)
      .with("database.server.name", dbserverName)
      .with("snapshot.mode", snapshotMode)
      .with("converter.schemas.enable", "false")
      .with("decimal.handling.mode", "double")
      .with("schema.history.internal.kafka.topic", schemaTopic)
      .with("schema.history.internal.kafka.bootstrap.servers", schemaBootstrapServers)
      .with("schema.history.internal.consumer.security.protocol", schemaSecurityProtocol)
      .with("schema.history.internal.consumer.ssl.keystore.type", schemaSslKeyStoreType)
      .with("schema.history.internal.consumer.ssl.keystore.location", schemaSslKeystoreLocation)
      .with("schema.history.internal.consumer.ssl.keystore.password", schemaSslKeystorePassword)
      .with("schema.history.internal.consumer.ssl.truststore.type", schemaSslTrustStoreType)
      .with("schema.history.internal.consumer.ssl.truststore.location", schemaSslTruststoreLocation)
      .with("schema.history.internal.consumer.ssl.truststore.password", schemaSslTruststorePassword)
      .with("schema.history.internal.consumer.ssl.endpoint.identification.algorithm", sslEndpointAlgorithm)
      .with("schema.history.internal.producer.security.protocol", schemaSecurityProtocol)
      .with("schema.history.internal.producer.ssl.keystore.type", schemaSslKeyStoreType)
      .with("schema.history.internal.producer.ssl.keystore.location", schemaSslKeystoreLocation)
      .with("schema.history.internal.producer.ssl.keystore.password", schemaSslKeystorePassword)
      .with("schema.history.internal.producer.ssl.truststore.type", schemaSslTrustStoreType)
      .with("schema.history.internal.producer.ssl.truststore.location", schemaSslTruststoreLocation)
      .with("schema.history.internal.producer.ssl.truststore.password", schemaSslTruststorePassword)
      .with("schema.history.internal.producer.ssl.endpoint.identification.algorithm", sslEndpointAlgorithm)
      .with("bootstrap.servers", schemaBootstrapServers)
      .with("security.protocol", schemaSecurityProtocol)
      .with("ssl.keystore.location", schemaSslKeystoreLocation)
      .with("ssl.keystore.password", schemaSslKeystorePassword)
      .with("ssl.truststore.location", schemaSslTruststoreLocation)
      .with("ssl.truststore.password", schemaSslTruststorePassword)
      .with("ssl.endpoint.identification.algorithm", sslEndpointAlgorithm)
      .build();

What is the captured database version and mode of depoyment?

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

Oracle 19c

On-Prem

What behaviour do you expect?

App should run without connector downtime.

What behaviour do you see?

connector goes down every 3 or 4 hours

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

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

Not Tried.

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

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

No logs were emitted when app goes down.Just says stooping connector gracefully

How to reproduce the issue using our 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?

Implementation ideas (optional)