16.10 - When SQL is Not Recorded - Teradata Database

Teradata Database Administration

Product
Teradata Database
Release Number
16.10
Published
April 2018
Language
English (United States)
Last Update
2018-04-26
dita:mapPath
qjg1509413559832.ditamap
dita:ditavalPath
changebar_rev_16_10_exclude_audience_ie.ditaval
dita:id
ujp1472240543947

If a query encounters an error or is aborted, the data in the field SQLTextInfo might be:

  • Truncated
  • Set to Null (?)
  • Set to “Unavailable”

    The word “Unavailable” indicates that the system failed to translate correctly (for example, if the system must translate to UNICODE).

Also, in some cases, DBQL does not log the entire SQL statement. For example, DBQL logs the CREATE/REPLACE PROCEDURE statements including the arguments, but not the additional options nor statements making up the body of the stored procedure.