SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

Data Set Options for Relational Databases 4 TPT_RESTART= Data Set Option 387See Also“Maximizing Teradata Load Performance” on page 804“Using the TPT API” on page 807“MULTISTMT= Data Set Option” on page 348“TPT= LIBNAME Option” on page 192“TPT= Data Set Option” on page 373“TPT_PACK= Data Set Option” on page 385TPT_RESTART= Data Set OptionSpecifies that a failed Fastload, MultiLoad, or Multi-Statement run that used the TPT API is beingrestarted.Default value: NOValid in: PROC steps (when accessing DBMS data using SAS/ACCESS software)DBMS support: TeradataSyntaxTPT_RESTART=YES | NOSyntax DescriptionYESspecifies that the load process is being restarted.NOspecifies that the load process is not being restarted.DetailsTo use this option, you must first set TPT=YES. This option is valid only when usingthe TPT API.SAS can restart from checkpoints any Fastload, MultiLoad, and Multi-Statementinsert that are run using the TPT API. The restart procedure varies: It depends onwhether checkpoints were recorded and in which phase the step failed during the loadprocess. The error message in the log is extremely important and contains instructionson how to restart.Here are the rules that govern restart.3 The TPT API does not return a checkpoint value when FastLoad records acheckpoint. Therefore, you need not set TPT_CHECKPOINT_VALUE= when youuse FastLoad. Set TPT_RESTART= instead.3 If the default error table name, work table name, or restart table name isoverridden, SAS must use the same name while restarting the load process.3 Teradata loads data in two phases: the acquisition phase and the applicationphase. In the acquisition phase, data transfers from SAS to Teradata. After thisphase, SAS has no more data to transfer to Teradata. If failure occurs after thisphase, set TPT_APPL_PHASE=YES while restarting. (Multi-Statement insert