debezium / debezium/dbz

LogMiner session stopped due to an error

Open
#1,607 4 comments 0 reactions 0 assignees View on GitHub
component/oracle-connector type/bug
Dominant language
HTML
Stars
6
Forks
8
Avg merge
2d 19h
Merged PRs (30d)
1

Description

## Bug report

**What Debezium connector do you use and what version?**

`3.3.2.Final`

---

**What is the connector configuration?**

```
apiVersion: kafka.strimzi.io/v1beta2
kind: KafkaConnect
metadata:
name: debezium-connect-cluster
namespace: kafka
annotations:
strimzi.io/use-connector-resources: "true"
spec:
version: 3.7.1
image: /debezium-connect:3.3.2-strimzi-0.42.0-kafka-3.7.1
replicas: 1
bootstrapServers: debezium-poc-kafka-kafka-bootstrap:9092
config:
config.providers: secrets,configmaps
config.providers.secrets.class: io.strimzi.kafka.KubernetesSecretConfigProvider
config.providers.configmaps.class: io.strimzi.kafka.KubernetesConfigMapConfigProvider
group.id: debezium-poc-kafka
offset.storage.topic: debezium-poc-kafka-offsets
config.storage.topic: debezium-poc-kafka-configs
status.storage.topic: debezium-poc-kafka-status
# -1 means it will use the default replication factor configured in the broker
config.storage.replication.factor: -1
offset.storage.replication.factor: -1
status.storage.replication.factor: -1
```

---

**What is the captured database version and mode of deployment?**

_E.g. on-premises, with a specific cloud provider, etc._

`Oracle 19`

---

**What behavior do you expect?**

`The process might fail, but it must restart itself, not just remain "broken" and waiting for a restart`

---

**What behavior do you see?**

```
The tasks crashes and it not restarted, leading to a database that is past its redo log retention and unrecoverable by debezium.
```

---

**Do you see the same behaviour using the latest released Debezium version?**

_Ideally, also verify with the latest Alpha/Beta/CR version._

`Were not able to test this`

---

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

_You might be asked later to provide [DEBUG/TRACE](https://debezium.io/documentation/reference/stable/operations/logging.html) level log._

```
2025-11-13 20:34:05,917 ERROR [debezium-poc-oracle-cintmcn1-dbintmbr2|task-0] LogMiner session stopped due to an error. (io.debezium.connector.oracle.logminer.AbstractLogMinerStreamingChangeEventSource) [debezium-oracleconnector-server1-change-event-source-coordinator]
2025-11-13 20:34:05,921 ERROR [debezium-poc-oracle-cintmcn1-dbintmbr2|task-0] Producer failure (io.debezium.pipeline.ErrorHandler) [debezium-oracleconnector-server1-change-event-source-coordinator]
2025-11-13 20:34:18,132 ERROR [debezium-poc-oracle-cintmcn1-dbintmbr2|task-0] WorkerSourceTask{id=debezium-poc-oracle-cintmcn1-dbintmbr2-0} Task threw an uncaught and unrecoverable exception. Task is being killed and will not recover until manually restarted (org.apache.kafka.connect.runtime.WorkerTask) [task-thread-debezium-poc-oracle-cintmcn1-dbintmbr2-0]
```

---

**How to reproduce the issue using our [tutorial](https://github.com/debezium/debezium-examples/tree/main/tutorial) deployment?**

`The issue just occurs on its own. After a few days, the tasks crashes and that is that. The Database was a test DB and there was not a lot of activity on the DB, maybe this is an important piece of the puzzle.`

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.