Teradata Database error message regarding errors that can be fixed and resubmitted are 2631, 2639, 2641, 2834, 2835, 3110, 3111, 3120, 3127, 3178, 3598, 3603, and 8024.
Teradata TPump ignores errors on Teradata SQL statements outside of the Teradata TPump task; that is, before the BEGIN LOAD command or after the END LOAD command. The Teradata TPump job continues and no return code is returned, although Teradata Database error messages are displayed.
When Teradata TPump encounters errors caused by a Teradata Database failure, it neither terminates the job nor produces a return code. When Teradata Database recovers, Teradata TPump restarts the job and continues without user intervention. Teradata Database failure messages are 2825, 2826, 2827, 2828, 3897, and 8018.
When one of these errors occur, a row is inserted into Teradata TPump’s error table for the statement or data record in question. If the error occurs for one of the statements in a multiple‑statement request, the remaining statements are re‑driven.
The retry-able errors are automatically retried up to 16 times if retry times are not specified. For the complete text and explanation of error messages, see Messages (B035‑1096).
A row is inserted into Teradata TPump’s error table for the statement in error. If the error occurs for one of the statements in a multiple‑statement request, then the remaining statements are re‑driven.
Teradata TPump obtains the retry-able error codes list from database view SYSLIB.DBSRetryableErrors and displays those error codes as retry-able.