16.10 - Bulk Load Sessions - Teradata Unity

Teradata Unity User Guide

Teradata Unity
Release Number
January 2018
English (United States)
Last Update

A bulk load job includes control sessions and data sessions.

Processing bulk load jobs in Unity differs from standard SQL processing. For example, the sequencer does not process bulk load data for other SQL clients. The sequencer and dispatcher processes are only involved with bulk load when processing the control session. The endpoint processes are the main components of the bulk load job and open the load data sessions to the database.

Bulk load data is temporarily stored on endpoint servers, under /data/processid . This data automatically deletes after the load data is completed on all systems. The load job fails if there is insufficient space available in this directory.

If you deactivate and reactivate all systems in the cluster, or individual tables that have stored bulk load data, the associated contents of the /data/processid directory are automatically deleted.
Process Bulk Load Job Role
Sequencer Manages load operations by processing SQL executed by control sessions, coordinating session distribution, monitoring the load progress on each system, and initiating load recovery as needed. Does not assist in processing data for loading.
Dispatcher Negotiates the initial logon and number of sessions to open the job on each system.
Endpoint Manages receiving data, storing data, and loading data to systems.