Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi team,
Could you explain difference of Logstream Child Task lsn and Unidrectional Task lsn in qlik replicate.
Thanks,
Titus
Hello @Titus
Source change position (e.g. SCN or LSN): Specify the position in the log from where to resume change processing. The source change position format differs according to your source endpoint.
In Undirectional Task, we can Resume the Task using LSN/SCN But in Log stream Child Task we cannot resume task using LSN/SCN as there is a limitation
"The Source change position (e.g. SCN or LSN) Advanced Run option is only supported with the Oracle source endpoint"
Regards,
Suresh
Hello team,
If our response has been helpful, please consider clicking "Accept as Solution". This will assist other users in easily finding the answer.
Regards,
Sushil Kumar
Dear @Titus ,
Welcome and Thank you for reaching out to us on Qlik Community.
That's very interesting question you have posted. Please find some information related to Logstream Child Task LSN and Unidirectional Task LSN in Qlik Replicate.
Logstream Child Task LSN:
In a Logstream Child Task, the Log Sequence Number (LSN) is not used to resume the task. This is because a Logstream Child Task is part of a Log Stream, which is a dedicated Replicate task that saves data changes from the transaction log of a single source database and applies them to multiple targets. The Logstream Child Task inherits its position in the transaction log from the parent Log Stream. This means that the child task does not maintain its own position in the transaction log, but instead relies on the parent Log Stream for this information.
Unidirectional Task LSN:
In a Unidirectional Task, the LSN can be used to resume the task. This is because a Unidirectional Task directly reads from the transaction log of the source database. If the task is stopped for some reason, it can be resumed from the last known position in the transaction log, which is identified by the LSN. This means that the Unidirectional Task maintains its own position in the transaction log, independent of any other tasks.
I hope this helps! Let me know if you have any other queries.
If our response has been helpful, please consider clicking "Accept as Solution".
This will assist other users in easily finding the answer.
Best Regards,
Deepak Ahirwar