16.10 - Changing Maximum Sessions Per Gateway - 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

The number of supported sessions is based on the following:

  • The number of allotted Parsing Engines (PEs)
  • Usage (resources consumed)
  • Maximum number of sessions per gateway setting

If your site runs jobs that are CPU or I/O intensive, you might find that a lower session limit gives better performance. You cannot set the maximum sessions to a negative number.

To view the current maximum sessions, type:

gtwcontrol -d

To set the maximum sessions to 1000, type:

gtwcontrol -g 1 -s 1000

where 1 is the number of the host group, and 1000 is the desired maximum number of sessions.

The new limit is effective immediately.

If more sessions are active than the new maximum sessions limit allows, then no new sessions are started. No new sessions can log on until the number of sessions is below the maximum sessions limit.