15.10 - Error Recording - MultiLoad

Teradata MultiLoad Reference

prodname
MultiLoad
vrm_release
15.10
category
Programming Reference
featnum
B035-2409-035K

Error Recording

When Teradata MultiLoad encounters a data row that cannot be processed properly, it creates a row in one of the two error tables that are created for each target table in the Teradata MultiLoad job:

  • Acquisition error table
  • Application error table
  • Each error table row includes eight columns of information that can be used to determine the cause of the problem. Additionally, the acquisition error table includes the faulty record, and the application error table includes a mirror image of the target table.

    The target tables for the Teradata MultiLoad job cannot have column names that are the same as the error table column names because the application error table includes a mirror image of the target table, preceded by the error information. If the column names are duplicated, Teradata Database terminates the Teradata MultiLoad job and returns an Error 3861 message.

    Notes on recording errors:

  • The error limit that was set in the BEGIN MLOAD command pertains to the error threshold that limits the number of rejected records that can be written to the error tables during the acquisition phase of a Teradata MultiLoad import task.
  • When there are no expressions involved and at most one conversion required before loading the data into the target table, the data conversion takes place in the acquisition phase and the converted data is loaded into the worktable. This means that any errors with the data or with the conversion will be detected in the acquisition phase.
  • But, when expression(s) are involved or more than one level of conversion is required before inserting the data into the target table, expression evaluations or conversions on primary index fields are done in the acquisition phase and conversions on the rest of the fields are deferred until the application phase. Therefore, any errors with the primary index fields will be detected in the acquisition phase, and any errors with the rest of the fields will be detected in the application phase.
  • The user can define any column name they want (up to 128 characters), but if a row is placed in the error table, the DBS will truncate any column name that exceeds 120 characters.