Data Sessions | Teradata Business Continuity Manager - Data Sessions - Teradata Business Continuity Manager

Teradata® Business Continuity Manager User Guide

Product
Teradata Business Continuity Manager
Release Number
1.0
Published
January 2022
Language
English (United States)
Last Update
2022-01-27
dita:mapPath
otc1639627713801.ditamap
dita:ditavalPath
ft:empty
dita:id
B035-2550
lifecycle
previous
Product Category
Analytical Ecosystem

The Bulk Load client uses Communications Processor (COP) discovery to open multiple data sessions to Business Continuity Manager across multiple endpoint processes. The client opens one set of sessions at a time to Business Continuity Manager. Business Continuity Manager returns an error if it is unable to open any additional sessions with the client.

The following tables lists the factors that open sessions. Business Continuity Manager uses the lowest number of sessions required between factors.

Connection Factors
Client to Business Continuity Manager Number of sessions requested by the client.
Maximum number of sessions opened to each Teradata Database system managed by Business Continuity Manager.
Business Continuity Manager to Teradata system Number of AMPs in the Teradata system. Business Continuity Manager forces 16 sessions if the Teradata Database system has at least 16 AMPs. The LoadNumSessions sequencer configuration parameter defines 16 load sessions by default to use from Business Continuity Manager to the Teradata Database. Set LoadNumSessions to 0 disable it.
Session limit assigned by TASM.
Number of sessions requested by the client.
You can modify the BCMLoadSessions query band setting to override an individual load job. Set BCMLoadSessions to 0 to disable it.
If TASM is installed on Teradata systems, set the LoadMaxJobs parameter to 0 to avoid contention between TASM and Business Continuity Manager.