Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
Last night we ran into an issue with one of our customers. We received a fatal error on one of their tasks. See error below.
File 'M:\LogStreams\4x_prodr4x_rez_ver_oltp_ls_sc\LOG_STREAM\audit_service\20240109184846409694\139' already purged, position does not exist.
Failed to read CDC channel
There is a gap in the audit files, expecting file number 140, found file number 143
What would cause this gap in audit files? Any best priactice in recovering from this error?
Thanks,
Paul
Hi @pmaclell ,
Thank you for using Qlik community platform to raise this concern.
The following error means the below audit file is purged based on the retention period:
File 'M:\LogStreams\4x_prodr4x_rez_ver_oltp_ls_sc\LOG_STREAM\audit_service\20240109184846409694\139' already purged, position does not exist.
To avoid purging the logs, Ensure to maintain a better retention policy.
To resolve the issue please start your Parent task and child task with back in time to capture the missed changes (or) perform a reload of the target tables on all the replication/child tasks, to make sure we are in sync with the source.
Best Regards,
Geetha
Hi @pmaclell ,
Thank you for using Qlik community platform to raise this concern.
The following error means the below audit file is purged based on the retention period:
File 'M:\LogStreams\4x_prodr4x_rez_ver_oltp_ls_sc\LOG_STREAM\audit_service\20240109184846409694\139' already purged, position does not exist.
To avoid purging the logs, Ensure to maintain a better retention policy.
To resolve the issue please start your Parent task and child task with back in time to capture the missed changes (or) perform a reload of the target tables on all the replication/child tasks, to make sure we are in sync with the source.
Best Regards,
Geetha
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