Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
We are using Qlik replicate Version (May 2024 (2024.5.0.563) .
Source - Amazone RDS(For SQL Server )
Target – SQL Server 2019 Enterprise Edition
We are using CDC to replicate data from source to target.
While doing this we are facing issue like “Stream component 'st_0_xxxx_xx_SOURCE' terminated Stream component failed at subtask 0, component st_0_xxx_xx_SOURCE Error executing source loop” and “LSN '00006f2e:00001356:00a8' could not be found, neither in the transaction log nor in the backup log”
Please see attach screenshot for reference .
Hi @hrushikeshatre ,
As the error message states, Qlik Replicate cannot find the corresponding changes (LSN) from the transaction log or backup.
Based on the symptoms and Qlik documentation, this is likely caused by Amazon RDS for SQL Server moving the online logs to the backup location before Replicate has had a chance to read them. This typically happens when the allocated storage reaches its threshold or during high-volume transactions.
Reference: Qlik Help - AWS RDS SQL Server Limitations
Recommended Next Steps:
Increase Allocated Storage
If the LSN doesn't exist anymore, you may need to perform a Full Load (Reload Target) for this task to resync the data.
If you confirm that storage is not the cause, please raise a support ticket to us.
Regards,
Desmond
First and second is working appropriate i think we need to rasie support case.