BEGIN LOADING | Usage Notes | Teradata FastLoad - 17.00 - Usage Notes - FastLoad

Teradata® FastLoad Reference

Release Number
June 2020
English (United States)
Last Update

The following table describes the things to consider when using the BEGIN LOADING command.

Usage Note for BEGIN LOADING 
Topic Usage Notes
Required Privileges The user ID that is logged in to the Teradata FastLoad job must have:
  • SELECT and INSERT privileges on the Teradata FastLoad table
  • CREATE TABLE privilege on the database that owns the two error tables
Restart Log Table To run Teradata FastLoad, the following privileges must be available to user PUBLIC on the Teradata FastLoad restart log table (SYSADMIN.FASTLOG):
Error Tables Descriptions Teradata FastLoad creates two error tables when executing the BEGIN LOADING command:
  • The error table specified by errortname1 contains records that were rejected because of an error other than unique primary index or duplicate row violation.
  • The error table specified by errortname2 contains records that violated the unique primary index constraint.
Duplicate Records The database ignores duplicate records, which are not inserted in either error table.
Reusing Table Names If an error table has one or more rows, it is not dropped from the database at the end of a Teradata FastLoad job. To reuse the names specified for the error tables, use the DROP TABLE statement to remove the tables from the database.

For more information, see Error Recording.

Checkpoints The CHECKPOINT option defines points in a job where Teradata FastLoad pauses to record that the database has processed a specified number of input records. When checkpoints are used, the entire Teradata FastLoad job need not be run if it stops before completion. Teradata FastLoad uses the checkpoint information in the restart log table to determine the restart location.
When specifying the integer value for the CHECKPOINT option:
  • If zero is entered as the value, Teradata FastLoad processes the BEGIN LOADING command as if a CHECKPOINT value is not entered.
  • If a value is not entered, or if a value is entered that is not an integer, the database returns a syntax error.

For more information, see Checkpoint Tradeoffs.

Indicators Indicators are bits at the beginning of a record that identify the nulled fields in the record. When INDICATORS in the BEGIN LOADING command are specified, Teradata FastLoad expects the first bytes of the record to contain an indicator bit for each record field.

If the INDICATORS option is set but indicator bits are not entered at the beginning of the record, Teradata FastLoad assumes that the first field contains indicator bytes and loads the record incorrectly.

Indicator bits must be stored in a minimum of eight-bit bytes. For example, if a record contains from one to eight fields, one byte is required for the indicator bits. If a record contains from nine to 16 fields, two bytes are required for the indicator bits, and so on.

Set unused bits in indicator bytes to zero.

Indicator Bit Positions The positions of the indicator bits correspond to the record fields. The first bit in the byte is the indicator for the first field in the record.

If an indicator bit is set to 1, the database nulls the corresponding field when the record is loaded. If the indicator bit is set to zero, the database loads the data specified for that field.

The following figure shows a record containing indicators.

Example Record With Indicator Bits
See the following documents for more information about indicator bits and the INDICATORS option:
  • Teradata® Call-Level Interface Version 2 Reference for Mainframe-Attached Systems, B035-2417
  • Teradata® Call-Level Interface Version 2 Reference for Workstation-Attached Systems, B035-2418