Task Full load failed with error :[Microsoft][ODBC Driver 18 for SQL Server]TCP Provider: Error code 0x68 [1022502]

[adershb]

Hi @john_wang ,

Our Full load task failed with below errors  (source Oracle and target  Microsoft Azure SQL Database). 

03190811: 2023-08-18T06:39:56 [TARGET_LOAD ]E: RetCode: SQL_SUCCESS SqlState: 08S01 NativeError: 104 Message: [Microsoft][ODBC Driver 18 for SQL Server]TCP Provider: Error code 0x68 [1022502] (sqlserver_endpoint_imp.c:5528)
03190811: 2023-08-18T06:39:57 [TARGET_LOAD ]E: Begin bulk failed (sqlserver_endpoint_imp.c:4268)

Is it due to the keepalive mentioned in your post reply mentioned here ; Solved: Authentication token has expired. The user must a... - Qlik Community - 1841541

We could see on target end-point advanced settings there are some option for "Additional ODBC connection properties:" Could you please advise can we give some parameters here for keepalive ? Replicate on Linux (version - 2022.11.0.765). 

Regards,

Adersh

[Heinvandenheuvel]

>> Is it due to the keepalive mentioned in your post 

Very unlikely, if it is indeed an active full-load as the title and description suggests.

Keep-alive only comes into play with long duration idle connection which is inconsistent with active full-load. But please show us some timestamps on the log, what was it doing? What was the last activity? How long ago.

I suggest that you go forward assuming that Replicate is the victim here, nicely reporting an error.

This is a Network, or Source-DB issue, not Replicate 99.99% sure.

Just google "TCP Provider: Error code 0x68" orientate yourself using a few of the dozens (non Replicate) hit, and ask for help from your network staff. Be persistent. They can help.

Good luck,

Hein.