Teradata Parallel Data Pump

Chapter 4: Troubleshooting
Reading Teradata TPump Error Tables
Table 29: Teradata TPump Error Conditions (continued)
Error
Description
7433 Invalid time.
7441 Date not corresponding to an existing era.
7442 Invalid era.
7451 Invalid timestamp.
7452 Invalid interval.
7453 Invalid field overflow.
7454 DateTime field overflow.
7455 Invalid time specified.
9102 Invalid CAST. The source character value must be valid for casting as PERIOD.
Reading Teradata TPump Error Tables
Teradata TPump error tables are a diagnostic device that help you locate and fix problems. For
more information, refer to the description of these tables in “BEGIN LOAD”.
Occasionally, Teradata TPump encounters rows that cannot be correctly processed. When this
happens, Teradata TPump creates a row in the error table that is produced for each target
table. Error tables are structured to provide enough information to reveal the cause of a
problem and allow correction.
In the case of missing, duplicate, or extra rows, these are noted in the error table only if the
DML command specifies that requirement with the MARK parameter, which is the default for
DML statements except for those participating in an upsert.
Three error codes relate specifically to the incidence of missing, duplicate, and extra rows:
• 2816: Failed to insert duplicate row into Teradata TPump target table.
This error occurs if MARK DUPLICATE INSERT/UPDATE ROWS is specified and a
duplicate row is detected.
• 2817: Activity count greater than one for Teradata TPump UPDATE/DELETE.
This error occurs if MARK EXTRA UPDATE/DELETE ROWS is specified and an activity
count greater than one resulted. In this case, the error table row is inserted, but the
corresponding UPDATE/DELETE also completes.
• 2818: Activity count zero for Teradata TPump UPDATE or DELETE.
This error occurs if MARK MISSING UPDATE/DELETE ROWS is specified and an
activity count of zero resulted.
Teradata Parallel Data Pump Reference 199