Help Center/ DataArts Studio/ FAQs/ DataArts Migration (Real-Time Jobs)/ What Should I Do If the Database Log Becomes Invalid During Incremental Reading from Oracle and Error Message "ORA-01292: no log file has been specified for the current LogMiner session" Is Displayed?
Updated on 2025-11-17 GMT+08:00
View PDF
Share

What Should I Do If the Database Log Becomes Invalid During Incremental Reading from Oracle and Error Message "ORA-01292: no log file has been specified for the current LogMiner session" Is Displayed?

Symptom

During incremental reading from Oracle, the database log becomes invalid, and the JobManager or TaskManager log contains error message "ORA-01292: no log file has been specified for the current LogMiner session".

Possible Causes

The log file for the Oracle database has been deleted. Confirm with the Oracle DBA about the startScn => '1963710021', endScn => '1963730021' log time to determine whether the log file has been deleted.

Solution

  • If the log file has been deleted, communicate with the DBA to change the log deletion mode and ensure that the log file is retained for at least three days.
  • If the log file has been retained for three days and has been deleted, you can perform a full and incremental migration again.