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

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!

Unable to resume Qlik Replicate tasks due to the error Start processing new RESETLOGS_ID 'xxxxxx' that does not still have archived Redo logs

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

Unable to resume Qlik Replicate tasks due to the error Start processing new RESETLOGS_ID 'xxxxxx' that does not still have archived Redo logs

Last Update:

Dec 21, 2023 3:49:25 AM

Updated By:

Sonja_Bauernfeind

Created date:

Dec 21, 2023 3:49:25 AM

Unable to resume Qlik Replicate tasks due to the error below:

00020080: 2023-08-16T13:55:07 [SOURCE_CAPTURE ]I: Start processing new RESETLOGS_ID 'xxxxxxxxx' that does not still have archived Redo logs (oradcdc_thread.c:430)

 

Resolution

The internal parameter supportResetLog is currently set to true. When a failover happens, the redo log ID will be reset to zero.

  • With supportResetLog set to true, Qlik Replicate will search from zero when it cannot find the next redo log.
  • With supportResetLog set to false, Qlik Replicate will keep searching for the next redo log until it appears or the task times out. This setting resolved the "Start processing new RESETLOGS_ID 'xxxxxxxxx' that does not still have archived Redo logs" error. 

To set the Internal Parameter:

  1. Go to the Oracle Source Endpoint
  2. Switch to the Advanced tab
  3. Click Internal Parameters
  4. Add:

    Parameter: supportResetLog
    Value: uncheck the box (set to false) 

    supportresetlog.png

    For more information on Internal Parameters, see Qlik Replicate: How to set Internal Parameters and what are they for?

  5. Save and exit. The change will take effect once the tasks using this endpoint are stopped and resumed.

 

 

Environment

  • Qlik Replicate
  • Oracle Database as a Source
Labels (1)
Comments
Jon_Donker
Creator
Creator

Once the issue is resolved - is it best practice to keep supportResetLog as false?  Or set it to true again 

Attunity_user
Creator
Creator

Hi Gerald_Uerald/

 

Once the issue is resolved - is it best practice to keep supportResetLog as false/ default value? Or set it to true again?

 

Thanks,

AU

Gerald_U
Support
Support

Once the issue is resolved, keep the supportResetLog parameter to false (uncheck the box).

Version history
Last update:
‎2023-12-21 03:49 AM
Updated by: