15.00 - Usage Considerations for the Error Table Columns - Teradata Database

Teradata Database SQL Data Definition Language Detailed Topics

Teradata Database
Programming Reference

Usage Considerations for the Error Table Columns

The following table supplies additional usage considerations for Error Table information beyond that listed in “System‑Defined Attribute Characteristics and Definitions for Error Table‑Specific Columns” on page 233.



Usage Notes


The system sets up a time-based query ID regardless of whether DBQL is enabled, and increments it for each new request.

You can use the column ETC_DBQL_QID to uniquely identify all error rows for a request.

The latter is less reliable because in a restart, the session numbers begin incrementing from the same base value. As a result, two different requests might have the same host, session, and request numbers if there are restarts.


You can use ETC_ErrSeq column to determine the order of row updates and inserts for a MERGE operation.

ETC_ErrSeq provides a numeric sequencing that is easier to refer to for error analysis and recovery purposes than the timestamps in ETC_TimeStamp.

If the data row size plus the fixed error table columns exceeds the system row size limit, an ANSI session mode request aborts and returns an error message to the requestor, while a Teradata session mode transaction containing the erring CREATE ERROR TABLE request aborts and returns an error message to the requestor.