Help Center/ DataArts Studio/ FAQs/ DataArts Migration (Real-Time Jobs)/ What Should I Do If Incremental Synchronization from Oracle Fails to Start and Error Message "oracle.jdbc.OracleDatabaseException: ORA-44609: CONTINOUS_MINE is desupported for use with DBMS_LOGMNR.START_LOGMNR" Is Displayed?
Updated on 2025-11-17 GMT+08:00

What Should I Do If Incremental Synchronization from Oracle Fails to Start and Error Message "oracle.jdbc.OracleDatabaseException: ORA-44609: CONTINOUS_MINE is desupported for use with DBMS_LOGMNR.START_LOGMNR" Is Displayed?

Symptom

Incremental synchronization from Oracle fails to start. The JobManager or TaskManager log contains error message "oracle.jdbc.OracleDatabaseException: ORA-44609: CONTINOUS_MINE is desupported for use with DBMS_LOGMNR.START_LOGMNR".

ORA-06512: at "SYS.DBMS_LOGMNR", line 72ORA-06512: at line 1    at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:509) ~[blob_p-ae195b90d37a40e645add451c65120a442900059-4727c0614178dd3ac7cfd9e4530f3d8b:?]    at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:461) ~[blob_p-ae195b90d37a40e645add451c65120a442900059-4727c0614178dd3ac7cfd9e4530f3d8b:?]    at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1104) ~[blob_p-ae195b90d37a40e645add451c65120a442900059-4727c0614178dd3ac7cfd9e4530f3d8b:?]    at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:550) ~[blob_p-ae195b90d37a40e645add451c65120a442900059-4727c0614178dd3ac7cfd9e4530f3d8b:?]    at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:268) ~[blob_p-ae195b90d37a40e645add451c65120a442900059-4727c0614178dd3ac7cfd9e4530f3d8b:?]    at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:655) ~[blob_p-ae195b90d37a40e645add451c65120a442900059-4727c0614178dd3ac7cfd9e4530f3d8b:?]    at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:229) ~[blob_p-ae195b90d37a40e645add451c65120a442900059-4727c0614178dd3ac7cfd9e4530f3d8b:?]    at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:41) ~[blob_p-ae195b90d37a40e645add451c65120a442900059-4727c0614178dd3ac7cfd9e4530f3d8b:?]    at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:928) ~[blob_p-ae195b90d37a40e645add451c65120a442900059-4727c0614178dd3ac7cfd9e4530f3d8b:?]    at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1205) ~[blob_p-ae195b90d37a40e645add451c65120a442900059-4727c0614178dd3ac7cfd9e4530f3d8b:?]    at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1823) ~[blob_p-ae195b90d37a40e645add451c65120a442900059-4727c0614178dd3ac7cfd9e4530f3d8b:?]    at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1778) ~[blob_p-ae195b90d37a40e645add451c65120a442900059-4727c0614178dd3ac7cfd9e4530f3d8b:?]    at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:303) ~[blob_p-ae195b90d37a40e645add451c65120a442900059-4727c0614178dd3ac7cfd9e4530f3d8b:?]    at org.apache.inlong.sort.cdc.oracle.shaded.io.debezium.jdbc.JdbcConnection.executeWithoutCommitting(JdbcConnection.java:1446) ~[blob_p-ae195b90d37a40e645add451c65120a442900059-4727c0614178dd3ac7cfd9e4530f3d8b:?]    at org.apache.inlong.sort.cdc.oracle.shaded.io.debezium.connector.oracle.logminer.LogMinerStreamingChangeEventSource.startMiningSession(LogMinerStreamingChangeEventSource.java:678) ~[blob_p-ae195b90d37a40e645add451c65120a442900059-4727c0614178dd3ac7cfd9e4530f3d8b:?]    at org.apache.inlong.sort.cdc.oracle.shaded.io.debezium.connector.oracle.logminer.LogMinerStreamingChangeEventSource.execute(LogMinerStreamingChangeEventSource.java:240) ~[blob_p-ae195b90d37a40e645add451c65120a442900059-4727c0614178dd3ac7cfd9e4530f3d8b:?]    at org.apache.inlong.sort.cdc.oracle.source.reader.fetch.OracleStreamFetchTask$RedoLogSplitReadTask.execute(OracleStreamFetchTask.java:136) ~[blob_p-ae195b90d37a40e645add451c65120a442900059-4727c0614178dd3ac7cfd9e4530f3d8b:?]    at org.apache.inlong.sort.cdc.oracle.source.reader.fetch.OracleStreamFetchTask.execute(OracleStreamFetchTask.java:74) ~[blob_p-ae195b90d37a40e645add451c65120a442900059-4727c0614178dd3ac7cfd9e4530f3d8b:?]    at org.apache.inlong.sort.cdc.oracle.shaded.org.apache.inlong.sort.cdc.base.source.reader.external.IncrementalSourceStreamFetcher.lambda$submitTask$0(IncrementalSourceStreamFetcher.java:86) ~[blob_p-ae195b90d37a40e645add451c65120a442900059-4727c0614178dd3ac7cfd9e4530f3d8b:?]    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [?:1.8.0_412]    at java.util.concurrent.FutureTask.run(FutureTask.java:266) [?:1.8.0_412]    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) [?:1.8.0_412]    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) [?:1.8.0_412]    at java.lang.Thread.run(Thread.java:750) [?:1.8.0_412]Caused by: oracle.jdbc.OracleDatabaseException: ORA-44609: CONTINOUS_MINE is desupported for use with DBMS_LOGMNR.START_LOGMNR.ORA-06512: at "SYS.DBMS_LOGMNR", line 72ORA-06512: at line 1     at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:513) ~[blob_p-ae195b90d37a40e645add451c65120a442900059-4727c0614178dd3ac7cfd9e4530f3d8b:?]    ... 23 more

Possible Causes

Oracle 19c does not support the CONTINOUS_MINE option for reading logs. This option is used by logimner to automatically load new logs when reading logs.

Solution

Set CONTINOUS_MINE to false in the custom configuration of the job:

debezium.log.mining.continuous.mine         false