Aborts any outstanding request or transaction of one or more sessions, and optionally logs those sessions off the Teradata system.
Syntax
ABORT SESSION {
hostid:sessionno |
hostid.username |
*.username |
hostid.* |
*.*
} [ LOGOFF ] [ LIST ] [ OVERRIDE ]
Syntax Elements
- 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 Vantage 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 Information
For more information about ABORT SESSION, see Teradata Vantage™ - Application Programming Reference, B035-1090.
For a complete description of error 3268, see Teradata Vantage™ - Database Messages, B035-1096.