Bug report

A DB query didn't return for a very long time. Debezium process was waiting there all the time without neither further mining nor any exception.

Please check the 0420_pub.log.zip.  "java.sql.SQLException: ORA-01291" happened and caused a restarting. Before stops, it called "LogMinerDatabaseStateWriter" to log some database info. But in "SELECT * FROM V$LOGMNR_LOGS" step, the query operation was stuck without timeout for several hours. 

You can see in "0420_pub2.log", when I tried to restart connector several hours later, there was an exception. 

During this period, the connector status was OK. No Kafka failure happened either. Debezium metrics "CommitThroughput" still had values. 

This kind of DB issue happens occasionally. (Not just Oralce. I've seen it in other kind of DB). But Debezium is better to be prepared for it.

What Debezium connector do you use and what version?

Oracle

What is the connector configuration?

configuration.json

What is the captured database version and mode of depoyment?

19c, rac

What behaviour do you expect?

Debezium raises exception when DB operation timeout.

What behaviour do you see?

Debezium did not do anything but waiting. The mining work was actually stopped.

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

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

Yes

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

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

Yes

How to reproduce the issue using our tutorial deployment?

It's difficult to reproduce. But easy to understand.

Feature request or enhancement

N/A

Which use case/requirement will be addressed by the proposed feature?

N/A

Implementation ideas (optional)

Maybe we should add timeout checking to DB operations and 
raise exception if DB operation doesn't return in time threshold.