3 hours Delay in the task, SQL Server to SQL Server

[ddb]

changes went to disk, the servers with the similar task setting and data flow do not have any delays.

[Dana_Baldwin · Accepted solution]

Hi @ddb Della,

I just responded to your support case. There are performance and/or other issues on the target database causing the task to repeatedly try to reconnect. There are timeout errors:

00016056: 2024-02-06T10:11:26 [TARGET_APPLY ]E: Failed to get table (null).attrep_changes1D2BF212A1954436 [1022502] (ar_odbc_conn.c:1060)

00016056: 2024-02-06T10:41:33 [TARGET_APPLY ]I: RetCode: SQL_ERROR SqlState: HYT00 NativeError: 0 Message: [Microsoft][ODBC Driver 18 for SQL Server]Query timeout expired [1022502] (ar_odbc_stmt.c:2828)

00008524: 2024-02-05T08:19:54 [TARGET_APPLY ]E: RetCode: SQL_ERROR SqlState: 42000 NativeError: 845 Message: [Microsoft][ODBC Driver 18 for SQL Server][SQL Server]Time-out occurred while waiting for buffer latch type 4 for page (1:12980142), database ID 18. Line: 1 Column: -1 [1022502] (ar_odbc_stmt.c:2828)

Please work with your target DBA and/or network team to root cause the issues.

To help work around these timeouts you can also increase the timeout parameters from their default in the internal parameters screen of your target endpoint:

cdcTimeout (default 600)
loadTimeout (default 1200)

You've already set and increased executeTimeout but it may need further increases.

Increasing timeout settings can help but isn't the root cause.

Thanks,

Dana

[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