topic Suspended tables - run from backdated time in Qlik Replicate

Suspended tables - run from backdated time

amitw — Thu, 01 Aug 2024 06:29:51 GMT

Hi Team,

Should we need to consider source and target latency when we are running the job from timestamp for suspended tables to avoid data loss.

For e.g.

If we get suspended tables in the job at 11 am UTC and the job has source or target latency of 5 hours when the table got suspended, should we run the job from 6 AM UTC time to avoid data loss

Thanks,

Amit

Re: Suspended tables - run from backdated time

john_wang — Thu, 01 Aug 2024 06:51:48 GMT

Hello @amitw ,

Thanks for reaching out to Qlik Community!

If only a specific table status go to 'suspended' , then you might want to:

1- Unsuspend the table;

2- Reload the selected table rather than reload the whole task.

More detailed information can be found in Reloading Tables.

Hope this helps.

John.

Re: Suspended tables - run from backdated time

amitw — Thu, 01 Aug 2024 11:06:02 GMT

Thanks @john_wang for your response. If the suspended table is huge and we want to avoid reload of it , can you please suggest if we need to run the task from backdated time by considering the latency values to be added in as well .

Re: Suspended tables - run from backdated time

sureshkumar — Thu, 01 Aug 2024 13:26:56 GMT

Hello @amitw

I would suggest

Perform a full reload on the suspended tables. OR
Define another task with the affected tables and use the “Start from timestamp” Run option and with the time or SCN when the table was suspended.

Regards,

Suresh