Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
Thank you for the post to the QDI Forums. I would check the Change Processing Mode on the SQL Server Source as depending on how this is set will determine if the Task will read from the online TLOG or Backups or both. This would be first step and if support is needed a Support case with the SOURCE_CAPTURE set to TRACE and attach the Diagnostic Package to the case when opened to help expedite the case.
The SQL Server Source Advanced Tab:
Change processing mode: Choose one of the following change processing modes:
Prioritize Backup Logs - When this option is enabled, Replicate will first look for the changes in the backup transaction logs. This can improve performance when reading from the online transaction log is slow (e.g due to lock contention) or when using file-level access to access the backup transaction logs.
If the changes cannot be found in the backup transaction logs, it will look for them in the online transaction logs instead.
Thanks!
Bill
Thank you for this question.
The error you encountered appears when Replicate doesn’t find the LSN on TLOG/backup log.
In some cases, it takes some time for the logs to be presented, that’s why the endpoint returns a recoverable error.
Was the task able to recover and continue the CDC? If so, that's fine and you can ignore this error.
Hi MarinaEmbon,
We also encountering the same issue with our tasks, but our tasks go into failed state.
Hi,
Thank you for the post to the QDI Forums. I would check the Change Processing Mode on the SQL Server Source as depending on how this is set will determine if the Task will read from the online TLOG or Backups or both. This would be first step and if support is needed a Support case with the SOURCE_CAPTURE set to TRACE and attach the Diagnostic Package to the case when opened to help expedite the case.
The SQL Server Source Advanced Tab:
Change processing mode: Choose one of the following change processing modes:
Prioritize Backup Logs - When this option is enabled, Replicate will first look for the changes in the backup transaction logs. This can improve performance when reading from the online transaction log is slow (e.g due to lock contention) or when using file-level access to access the backup transaction logs.
If the changes cannot be found in the backup transaction logs, it will look for them in the online transaction logs instead.
Thanks!
Bill
Hi @missDBA,
If your Replicate has access to the backup logs then use the Prioritize Online logs option in Change Processing Mode so that if the LSN is not found in the .ldf file then Replicate tries to read it from the .trn backup file.
Thanks,
Swathi