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?

Oracle connector running on Debezium 3.2.1

What is the connector configuration?

Here's a snippet of the LogMiner + heartbeat configuration:

"internal.log.mining.use.cte.query": "true",
"query.fetch.size": "50000",
"heartbeat.action.query": "MERGE INTO DBZUSER.DEBEZIUM_HEARTBEAT h USING (SELECT 1 id, SYSTIMESTAMP ts FROM dual) s ON (h.id = s.id) WHEN MATCHED THEN UPDATE SET h.updated_at = s.ts WHEN NOT MATCHED THEN INSERT (id, updated_at) VALUES (s.id, s.ts)",
"heartbeat.interval.ms": "1000",
"log.mining.batch.size.increment": "50000",
"log.mining.batch.size.max": "100000", 

What is the captured database version and mode of deployment?

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

On premise Oracle 11g

What behavior do you expect?

Heartbeat query runs consistently according to the heartbeat interval to keep the low watermark SCN moving when there are periods of no changes the connector is interested in

What behavior do you see?

Heartbeat stops running and the low watermark SCN gets stuck, see Zulip discussion here:

#community-oracle > Performance degradation after connector setup change @ 💬

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

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

We've tried an alpha release of 3.3.0 and had the same behaviour

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

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

Unfortunately not! In dev, we see the "Generating heartbeat event" message followed by "Executed heartbeat action query" until the heartbeat stops

How to reproduce the issue using our tutorial deployment?

Should be possible using the connector config snippet above - Requires the heartbeat table to be created + configured in Oracle