16.10 - ABORT SESSION - 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

Purpose

Aborts any outstanding request or transaction of one or more sessions, and optionally logs those sessions off the Teradata Database system.

Syntax



hostid
logical ID of a host (or client) with sessions logged on. A hostid of 0 identifies internal sessions or system console sessions. The range of values are 0 to 32767.
sessionno
session number. sessionno combined with hostid, represents a unique session ID. The range of values is 0 to 4,294,967,295.
username
user who is running the session. username can have a maximum length of 30 characters.
LOGOFF
indicator of whether or not to log the requested session off Teradata Database in addition to aborting them.
LIST
indicator of whether or not to display a list of sessions that meet criteria.
OVERRIDE
indicator of whether or not to override an ABORT SESSION failure.

Usage Notes

Aborting a session is useful when a session causes a production job to block other sessions waiting for locks, or when a session takes up so many resources that a critical application runs too slowly.

If an identified session cannot be aborted, the following occurs:

  • A 3268 error message returns.
  • Additional information is logged to the error log.
  • Processing of the request is terminated.

Retry the ABORT SESSION command at a later time after queued up abort requests complete.

You can issue the ABORT SESSION command on both mainframe-attached and workstation-attached clients.

Related Topics

For more information about ABORT SESSION, see Application Programming Reference.

For a complete description of error 3268, see Messages.