Incremental Synchronization Error: timeout when get next file log, maybe has been deleted, please check it.
Scenarios
During an incremental synchronization with Oracle serving as the source, an error is reported, and the log information is as follows: service CAPTURE failed, cause by: get next Oracle log file error. The next file is: 1.log, errorcode = 'code': '01300', 'name': 'LOGS_NOT_EXIST', 'retry': false, 'reset': false, 'level': 3, message = timeout when get next file log, maybe has been deleted, please check it.
Possible Causes
- The source Oracle database is a physical standby database. The logs of the source database where the incremental startup position is located are not archived. As a result, DRS cannot obtain the logs.
- There are problems about nodes and logs in the source database. As a result, DRS fails to obtain logs and reports an error.
- The network is unstable, affecting the speed of obtaining logs from the source database. As a result, reading logs times out.
Solution
- After a DRS task is started, wait for about 10 minutes, click the task name, and check whether the error log is displayed on the Synchronization Logs page.
- If no, DRS has obtained logs.
- If yes, go to 2.
- If an error is reported for the LOGMANAGER process on the Synchronization Logs page, contact Huawei technical support.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot