The first error table, called the acquisition error table, is specified with the ErrorTable1 attribute. It provides information about:
- All errors that occur during the acquisition phase of the Update operator job.
- Some errors that occur during the application phase if the Teradata Database cannot build a valid primary index.
The following table lists, in alphabetical order, the acquisition error table columns that can be specified.
|ApplySeq||Sequence number assigned to the DML group in which the error occurred (the same as DMLSeq). It can be ignored in error handling.|
|DMLSeq||Sequence number assigned to the DML statement within the DML group in which the error occurred.|
|ErrorCode||Code for the error.|
|ErrorField||Field name of the target table in which the error occurred.
This field may be blank if the system cannot determine which field caused the problem. Error 2677 (stack overflow) is an example of such a condition.
The names in this column have a maximum supported size of 120 characters. The names can be up to 128 characters, but if a row is inserted into the acquisition error table, the Teradata Database truncates any name that exceeds 120 characters.
|HostData||Client data being processed when the error occurred.|
|ImportSeq||Sequence number assigned to the input source in which the error occurred.|
|SourceSeq||Sequence number assigned to the row from the input source (the ImportSeq number) in which the error occurred.|
|STMTSeq||Sequence number of the DML statement within the DML group (as indicated by the previous column DMLSeq) being executed when the error occurred.|
You can use the Teradata PT Error Extractor command to extract the error information from the Update operator's acquisition phase error table when the schema for the Update operator job contains all VARCHAR columns.
For more information about the Teradata PT Error Table Extractor command, see "twbertbl" in the Terata in Teradata Parallel Transporter Reference (B035-2436).