'source change position (e.g. SCN or LSN)' Advanced Run option to start Log Stream tasks

[iti-attunity-sup]

I have some questions about using 'source change position (e.g. SCN or LSN)' Advanced Run option to start Log Stream tasks.

This is newly supported from v2023.05, according to the documentation below:

Qlik Help
https://help.qlik.com/en-US/replicate/May2023/Content/Replicate/Main/Release_Notes/features.htm

What's new?

Log Stream tasks now support the source change position (e.g. SCN or LSN) Advanced Run option
with the Oracle source endpoint.

I would like to know what kind of situation we will use this option. 

I'm assuming the following situation, is it appropriate?

Prerequisite:
Large number of updates to the tables not subject to CDC in the source database will occur in advance

1. Stop Log Stream tasks during the updates.
2. After all the unrelated updates are completed, check the current SCN.
3. Resume the Log Stream tasks using the current SCN confirmed at Step#2.

Are there any other cases where this option would be useful?
Or is there anything we should be careful about when using this option?

Regareds,

Kyoko Tajima

[DesmondWOO]

Hi Tajima san, @iti-attunity-sup ,

Thank you for reaching out to the Qlik Community.

Rather than starting the task from a specific date and time, you can resume it using SCN if you have the SCN position. Using a SCN provides a more precise position for starting the CDC.

For example, your step 3:

3. Resume the Log Stream tasks using the current SCN confirmed at Step#2.

You could also use date and time instead of SCN.

Regards,
Desmond