Hello Experts

Our customer has upgraded v2022.05 to v2023.11 and encountered the problem below:

In 2022.05, when the following warning occurred, CDC task continued without any errors.

[TARGET_LOAD ]I: Load finished for table 'ADM'.'XXXXX' (Id = 1). 85627944 rows received. 0 rows skipped. Volume transferred 98611582288. (streamcomponent.c:3976)
[TARGET_LOAD ]I: TPT statistics for table 'REP.YYYYY': Operator=LOAD, CPU time=1115.296875, Received Rows=85627944, Sent Rows=85627944, Applied Rows=85627917 (teradata_tpt_engine.cpp:778)
[TARGET_LOAD ]W: Not all rows have been loaded successfully for 'REP'.'YYYYY' due to possible 'TPT LOAD' errors. Consult Target 'xxxx_E?' / 'xxxx_L?' Error / Log tables contents. (teradata_tpt_engine.cpp:786)
[TARGET_LOAD ]I: teradata_terminate_tpt(...) successfully applied conn->Terminate() method for task identified by UUID '74a9fd96-8335-5944-bb67-6aaa83fb3782' (teradata_tpt_engine.cpp:839)
[TASK_MANAGER ]I: Loading finished for table 'ADM'.'XXXXX' (Id = 1) by subtask 1. 85627944 records transferred. (replicationtask.c:3012)
[TARGET_LOAD ]I: teradata_stop_imp(...) stopping task identified by UUID '74a9fd96-8335-5944-bb67-6aaa83fb3782' (teradata_endpoint_imp.c:857)
[TARGET_LOAD ]I: teradata_free(...) freeing resources for task identified by UUID '74a9fd96-8335-5944-bb67-6aaa83fb3782' (teradata_endpoint_imp.c:878)
[TARGET_LOAD ]I: teradata_disconnect(...) disconnecting for task identified by UUID '74a9fd96-8335-5944-bb67-6aaa83fb3782' (teradata_endpoint_imp.c:92)
[TARGET_LOAD ]I: teradata_disconnect(...) disconnecting Data Connection succeeded for task identified by '74a9fd96-8335-5944-bb67-6aaa83fb3782' (teradata_endpoint_imp.c:104)
[TARGET_LOAD ]I: teradata_disconnect(...) No active Lookup Connection to disconnect from was detected for task identified by '74a9fd96-8335-5944-bb67-6aaa83fb3782' (teradata_endpoint_imp.c:122)
[TASK_MANAGER ]I: Subtask #1 ended (replicationtask_util.c:591)

However the behavior has changed after upgrading to v2023.11.
After the same warning occurred, it is detected as an error and the table is suspended.

[TARGET_LOAD ]I: Load finished for table 'ADM'.'XXXXX' (Id = 1). 85986652 rows received. 0 rows skipped. Volume transferred 99014228864. (streamcomponent.c:4076)
[TARGET_LOAD ]I: TPT statistics for table 'REP.YYYYY': Operator=LOAD, CPU time=1126.937500, Received Rows=85986652, Sent Rows=85986652, Applied Rows=85986625 (teradata_tpt_engine.cpp:781)
[TARGET_LOAD ]W: Not all rows have been loaded successfully for 'REP'.'YYYYY' due to possible 'TPT LOAD' errors. Consult Target 'xxxx_E?' / 'xxxx_L?' Error / Log tables contents. (teradata_tpt_engine.cpp:789)
[TARGET_LOAD ]I: teradata_terminate_tpt(...) successfully applied conn->Terminate() method for task identified by UUID '74a9fd96-8335-5944-bb67-6aaa83fb3782' (teradata_tpt_engine.cpp:846)
[TARGET_LOAD ]E: TPT data acquisition failed [1020403] (teradata_endpoint_imp.c:1480)
[TARGET_LOAD ]E: Handling End of table 'REP'.'YYYYY' loading failed by subtask 1 thread 1 [1025000] (endpointshell.c:3069)
[TASK_MANAGER ]W: Table 'ADM'.'XXXXX' (subtask 1 thread 1) is suspended. TPT data acquisition failed; Handling End of table 'REP'.'YYYYY' loading failed by subtask 1 thread 1 (replicationtask.c:3208)

Is there any options to ignore the warnings/errors and continue the task like v2022.05?

Any advice would be appreciated.

Regards,
Kyoko Tajima

Hi,

I am wondering when I have a source lookup on a column in a table, then I also have a filter on the table. What comes first? Are the records filtered then the source lookup occurs? or does the source lookup occur then the rows are filtered?

Regards,

Mo