Data Set Options for Relational Databases

ML_RESTART= Data Set Option

Specifies the name of a temporary table that MultiLoad uses to track checkpoint information.

Default value:	none
Valid in:	DATA and PROC steps (when creating and appending to DBMS tables using SAS/ACCESS software)
DBMS support:	Teradata

Syntax
Syntax Description
Details
See Also

Syntax

ML_RESTART=temporary-table-name

Syntax Description

temporary-table-name: specifies the name of the temporary table that the Teradata MultiLoad utility uses to track checkpoint information.

Details

To specify this option, you must first set MULTILOAD=YES.

Use this option to specify the name of a table to store checkpoint information. Upon restart, ML_RESTART= is used to specify the name of the log table that you used for tracking checkpoint information in the earlier failed run.

Note: Do not use ML_RESTART= with ML_LOG=, which provides a common prefix for all temporary tables that the Teradata MultiLoad utility uses. [cautionend]

For more information about the temporary table names that the Teradata MultiLoad utility uses, see the Teradata documentation on the MultiLoad utility.

Use this option to specify the name of a table to use for tracking errors that were generated during the application phase of the MultiLoad bulk-load operation. By default, the application error table is named SAS_ML_UT_randnum, where randnum is a random number.

When you restart a failed MultiLoad job, you must specify the same application table from the earlier run so that the MultiLoad job can restart correctly. Using ML_RESTART=, ML_ERROR1=, and ML_WORK=, you must also specify the same log table, acquisition error table, and work table upon restarting.

Note: Do not use ML_ERROR2 with ML_LOG=, which provides a common prefix for all temporary tables that the Teradata MultiLoad utility uses. [cautionend]

For more information about temporary table names that the Teradata MultiLoad utility uses and what is stored in each, see the Teradata MultiLoad reference.