Operator-Specific Error Handling - Parallel Transporter

Teradata® Parallel Transporter User Guide

Product
Parallel Transporter
Release Number
16.20
Published
August 2020
Language
English (United States)
Last Update
2020-08-27
dita:mapPath
uah1527114222342.ditamap
dita:ditavalPath
Audience_PDF_product_tpt_userguide_include.ditaval
dita:id
B035-2445
lifecycle
previous
Product Category
Teradata Tools and Utilities

Teradata PT handles errors differently depending on the operator that detects the error and whether or not the operator has been directed, through one of its attributes, to ignore the error just detected.

The Load, Update and Stream operators, which typically process large numbers of data rows, have built-in tolerances for data application errors, which are specifiable through operator attributes. For detailed information the sections on these operators later in this section.

Other operators generally terminate for any error that occurs during their execution. The exceptions are:
  • DDL operator: Use the ErrorList attribute to specify one or more Teradata Database error codes that the operator will ignore, instead of causing the job to terminate, as would normally be the case.
  • DataConnector operator:
    • Use the RecordErrorFileName attribute (previously known as "RowErrFileName") to write erroneous source rows to a named file instead of terminating.
    • Use AcceptExcessColumns to ignore extra columns in its source rows instead of terminating.
    • Use AcceptMissingColumns to extend a short row to the correct number of columns instead of terminating.
    • Use TruncateColumnData to truncate a column that is too long instead of terminating.

For a list of obsolete syntax, which are supported but no longer documented, see "Deprecated Syntax" in Teradata® Parallel Transporter Reference, B035-2436.