Error in in managing safeguard policy.

[Naga_vivek]

Hi team,

We got an recoverable error recently in the Qlik replicate task where the error looks like

ERROR:

Problems in managing safeguard policy.
Failure in un-setting rear latch 'B' in safeguard_manager(...)
Failure in un-setting a safeguard latch for task '<ID>'
RetCode: SQL_ERROR SqlState: 08S01 NativeError: 10054 Message: [Microsoft][ODBC Driver 18 for SQL Server]TCP Provider: An existing connection was forcibly closed by the remote host.

Failed (retcode -1) to execute statement: commit transaction <ID>

So even after we got the error the task is in running state.

Note :

1. we are using Microsoft SQL server end point as source.

2.CSV file as target.

3.using Change processing mode (read changes from): Online Logs Only.

4.Internal parameters used

-------------------------------------- 

1.CDC timeout:3600

2.ignoreTxnCtxValidityCheck=true

3.TlogAccessMode=TlogOnly

4.additionalConnectionProperties

Please let me know why I am getting the error and what steps i can follow to resolve it.

[DesmondWOO]

Hi @Naga_vivek ,

Replicate opens two transactions so that unread changes will not be truncated from TLOG. Details can be found in the user guide.

Based on the error message, it appears that the connection was unexpectedly closed. I think the task should work again when you resume it.

Should the issue continue to occur, please submit a support case to our team.

Regards,
Desmond

[SushilKumar]

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

[Pranita123]

Hi @Naga_vivek ,

we are experiencing the same issue. has it been resolved on your end?

If so, how did you fix it? Your help with this matter would be greatly appreciated.

Thank You,

Pranita 

[DesmondWOO]

Hi @Naga_vivek ,

When the Replicate task encounters a connection issue, it should retry automatically. Did the problem resolve? If the Replicate task is functioning normally again, it may have just been a temporary network issue.

Regards,
Desmond