Teradata FastLoad Error Conditions - FastLoad

Teradata FastLoad Error Conditions

While processing a Teradata FastLoad job script, Teradata FastLoad tracks and records information about five types of error conditions that cause the Teradata Database to reject an input data record. Table 22 describes these error conditions.

Table 22: Error Conditions that Cause Teradata Database to Reject an Input Data Record 

Error Conditions	Description
Constraint violations	Records from the input file that do not comply with the range constraints that were specified in the CREATE TABLE statement.
Conversion errors	Records from the input file that fail a data type conversion that was specified in the DEFINE command.
Duplicate rows	Records from the input file that are exact duplicates of existing rows.
Unavailable AMP conditions	Records from the input file that are destined for a nonfallback table on an AMP that is down.
Unique primary index violations	Records from the input file that have a value for the unique primary index field that already exists, but is not a duplicate row.

Note: Teradata FastLoad does not store duplicate rows in an error table.

Additionally, when operating in batch mode, Teradata FastLoad returns the system error codes for error conditions encountered during Teradata FastLoad operations. (Teradata FastLoad does not return system error codes when operating in interactive mode.) This subsection describes the procedures for handling the five types of Teradata FastLoad error conditions.

See Messages (B035‑1096) for more information about system error messages.