16.10 - ErrorTable - Parallel Transporter

Teradata Parallel Transporter Reference

Product
Parallel Transporter
Release Number
16.10
Published
July 2017
Content Type
Programming Reference
Publication ID
B035-2436-077K
Language
English (United States)

Update operations create two error tables for each target table. These error tables are similar to those used for the Load operator, but the Update error tables are typically named with the following suffixes to distinguish them.

Consider the following:

  • Names for error tables can be defaulted or they can be explicitly named using the VARCHAR ErrorTable attribute.
  • If a job generates no errors, the error tables will be empty. They are automatically dropped at the end of the job.
  • If errors are generated, the tables are retained at the end of the job so error conditions can be analyzed.
  • To rerun a job from the beginning, either delete the error tables, or rename them, otherwise an error message results, stating that error tables already exist.
  • Conversely, if you restart a job (not from the beginning), an error tables must already exist. In other words, do not delete error tables to restart an update job.

Errors are separated into two tables, as follows:

  • Error Table (ET) contains data errors that occur in the acquisition phase of the Update operator job.

    The following types of errors are captured:

    • Data conversion errors
    • Data errors with the primary index fields

      By default, this error table is assigned a name using the convention:

         Target_Tablename_ET
      The names in the Error Table (ET) ErrorField 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 Error Table (ET), the Teradata Database truncates any name that exceeds 120 characters.
  • Uniqueness Violations (UV) contains data errors that occur in the application phase of the Update operator job.

    The following types of errors are captured:

    • Uniqueness violations
    • Field overflow on columns other than primary index fields
    • Constraint errors

      By default, this error table is assigned a name using the following convention:

         Target_Tablename_UV