Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now

Qlik Replicate Task Failure: Archived Redo Log Sequence Reported Missing Despite Being Present

100% helpful (1/1)
cancel
Showing results for 
Search instead for 
Did you mean: 
lilizou
Support
Support

Qlik Replicate Task Failure: Archived Redo Log Sequence Reported Missing Despite Being Present

Last Update:

Aug 21, 2025 9:35:15 AM

Updated By:

Sonja_Bauernfeind

Created date:

Aug 21, 2025 9:35:15 AM

Even if the archived redo logs are not deleted, the following error may still occur, causing task failure:

2025-06-19T15:20:29 [SOURCE_CAPTURE ]E: Archived Redo log with the sequence '188055' does not exist, thread 5 [1022318] (oradcdc_thread.c:711)

Two DEST_IDs exist.

ARCHIVED Log Status – Query Execution Results

SEQUENCE#,THREAD#,NAME,DEST_ID,FIRST_TIME,NEXT_TIME,DELETED,COMPLETION_TIME
188055,5,,1,2025-06-19 15:18:43,2025-06-19 15:20:28,YES,2025-06-19 15:20:28
188055,5,dg_osaka,2,2025-06-19 15:18:43,2025-06-19 15:20:28,NO,2025-06-19 15:20:28

 

Resolution

If multiple DEST_IDs exist, have the Oracle DBA check the configuration and set the correct values for the Archived and Alternate Redo Logs Destination IDs.

 

Cause

If multiple DEST_IDs exist and neither the archived redo logs location identifier nor the alternate archived redo logs destination ID is specified, the Qlik Replicate server will use the lowest existing DEST_ID.

As a result, Qlik Replicate will only use DEST_ID=1, which causes the issue.

 

Environment

  • Qlik Replicate
Labels (1)
Version history
Last update:
2 weeks ago
Updated by: