Sessions and Instances - Parallel Transporter

Teradata Parallel Transporter Reference

Product
Parallel Transporter
Release Number
15.00
Language
English (United States)
Last Update
2018-09-27
dita:id
B035-2436
lifecycle
previous
Product Category
Teradata Tools and Utilities

If the database that owns the Update target table, log table, error tables, or work table runs out of space, the Teradata Database returns an error message and the Update operator pauses the Update operator job. When this happens, you must allocate more space to the database before you can restart the job.Sessions and Instances

The values that you specify with the Update operator MinSessions and MaxSessions attributes are not the only factors that limit the number of sessions that the Update operator establishes with the Teradata Database. The other limiting factors are:

  • The Teradata Database limit of one session per available AMP
  • The platform limit on the maximum number of sessions per application.
  • On network-attached client systems for UNIX, Linux, and Windows systems, this value is defined in the COP Interface software file, clispb.dat, under the max_num_sess variable.
  • On mainframe-attached z/OS client systems, this value is defined in the HSHSPB parameter under the IBCSMAX setting.
  • On mainframe-attached z/OS client system, use the TDP SET MAXSESSIONS command to specify a platform limit.
  • The limit of the network protocol software on network-attached systems