Application Error Table - MultiLoad

Teradata® MultiLoad Reference - 20.00

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
MultiLoad
Release Number
20.00
Published
October 2023
Language
English (United States)
Last Update
2024-03-18
dita:mapPath
lji1691576359330.ditamap
dita:ditavalPath
kju1619195148891.ditaval
dita:id
sga1478609868891
Product Category
Teradata Tools and Utilities
The second error table, called the application error table, is the one specified as tname4 (default UV_tname1) in the BEGIN MLOAD command. It provides information about:
  • Uniqueness violations
  • Field overflow on columns other than primary index fields
  • Constraint errors

The following table shows the format of the application error table.

A copy (or mirror) of the target table columns precedes the ImportSeq column in the application error table. If the target table is a VIEW, then only those eight fields are specified. The following table is added into the application error table (UV_table).
Application Error Table Format 
Column Contains
ApplySeq Sequence number of the APPLY clause that was executing when the error occurred
DBCErrorCode Code for the error
DBCErrorField 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.

DMLSeq Sequence number assigned to the DML statement in which the error occurred
ImportSeq Sequence number assigned to the IMPORT command in which the error occurred
SourceSeq Data row number in the client file that the database was building when the error occurred
SMTSeq Sequence number of the statement that was being executed when the error occurred
Uniqueness Value that prevents duplicate row errors in the error table

It can be ignored in error handling.