[Oracle] Debezium stops when no archive logs available – how to keep connector running until logs are archived?

[HUY TRỊNH VĂN]

Hi everyone,

I'm using Debezium 2.7 with Oracle 19c.  
I have configured the connector to only use archived logs with the setting:

"log.mining.archive.log.only.mode": "true"

In my environment, the Oracle DBA runs the archive job only once per day at midnight.
During the day, there are no new archived logs available.

The problem is:
When Debezium starts and reaches a SCN not yet archived, it logs messages like:

No logs available yet (attempt 4)...

And then the connector stops automatically after a few retries.

My question is:

How can I configure Debezium to stay alive and keep retrying until archived logs are available, without stopping the connector?

I want to avoid having to restart the connector manually every day.

Any recommended workaround or configuration is greatly appreciated.
Thank you!

[Chris Cranford]

Hi, that appears to be a bug, could you please raise a Jira issue?

Thanks,
-cc

--
You received this message because you are subscribed to the Google Groups "debezium" group.
To unsubscribe from this group and stop receiving emails from it, send an email to debezium+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/debezium/80ca6419-119f-4567-93fa-27827e8941e8n%40googlegroups.com.