16.10 - ENABLE TRACE - Teradata Database

Teradata Database Utilities

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

Purpose

The ENABLE TRACE command turns on session tracing. The command records internal gateway events.

Syntax



Usage Notes

Session tracing may contain some of these elements:

Entries vary depending on the events and action taken.
  • Session number (if available)
  • Associated file description (if available)
  • Event
  • One or more of these events:
    • Assigned
    • Logged on
    • Logged off
    • Logoff forced (Teradata Database system killed session)
    • Logon failed (usually caused by invalid password)
    • Disconnected
    • Reassigned
    • Reconnected
  • Network address of the originating network-attached host

By default, tracing is disabled. After a Teradata Database system restart, tracing enabled earlier using the ENABLE TRACE command is continued.

If tracing has been enabled and you do not use the DISABLE TRACE command to turn it off, the file system may become full.

Before using the ENABLE TRACE command, you must select the host group from which the session is running using the SELECT HOST command. For information, see SELECT HOST.

The trace file is a text file, which can be viewed by any tool that displays text. The trace information is the same trace information controlled by Gateway Control, and is logged to the same files.

For additional information, see DISABLE TRACE. For information on the gateway log files, see Gateway Control (gtwcontrol).

Example: Enabling session event tracing

To turn on session event tracing, type:

enable trace