Usage Information for Error Table Columns and Table Data | Teradata Vantage - Usage Considerations for the Error Table Columns - Analytics Database - Teradata Vantage

SQL Data Definition Language Detailed Topics

Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
VMware
Product
Analytics Database
Teradata Vantage
Release Number
17.20
Published
June 2022
Language
English (United States)
Last Update
2023-07-11
dita:mapPath
vuk1628111288877.ditamap
dita:ditavalPath
qkf1628213546010.ditaval
dita:id
B035-1184
lifecycle
latest
Product Category
Teradata Vantage™

The following table supplies additional usage considerations for Error Table information beyond that listed in System-Defined Attributes for Error Table-Specific Columns.

Column Usage Notes
ETC_DBQL_QID 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.

ETC_ErrSeq 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.