13.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>SAS</strong>/<strong>ACCESS</strong> Interface to Teradata 4 Using the TPT API 807MY_LOAD_RS. Errors are logged in tables MY_LOAD_ET and MY_LOAD_UT. The worktable is named MY_LOAD_WT.3 ML_RESTART= lets the user name the log table that MultiLoad uses <strong>for</strong> trackingcheckpoint in<strong>for</strong>mation. By default, the log table is named <strong>SAS</strong>_ML_RS_randnumwhere randnum is a random number. When restarting a failed MultiLoad job, youneed to specify the same log table from the earlier run so that the MultiLoad jobcan restart correctly. Note that the same error tables and work table must also bespecified upon restarting the job, using ML_ERROR1, ML_ERROR2, andML_WORK data set options. ML_RESTART and ML_LOG are mutually exclusiveand cannot be specified together.3 ML_WORK= lets the user name the work table that MultiLoad uses <strong>for</strong> loadingthe target table. See the Teradata MultiLoad reference <strong>for</strong> more in<strong>for</strong>mation aboutwhat is stored in this table. By default, the work table is named<strong>SAS</strong>_ML_WT_randnum where randnum is a random number. When restarting afailed MultiLoad job, you need to specify the same work table from the earlier runso that the MultiLoad job can restart correctly. Note that the same log table,acquisition error table and application error table must also be specified uponrestarting the job using ML_RESTART, ML_ERROR1, and ML_ERROR2 data setoptions. ML_WORK and ML_LOG are mutually exclusive and cannot be specifiedtogether.3 SLEEP= specifies the number of minutes that MultiLoad waits be<strong>for</strong>e it retries alogon operation when the maximum number of utilities are already running on theTeradata database. The default value is 6. SLEEP= functions very much like theSLEEP run-time option of the native Teradata MultiLoad utility.3 TENACITY= specifies the number of hours that MultiLoad tries to log on whenthe maximum number of utilities are already running on the Teradata database.The default value is 4. TENACITY= functions very much like the TENACITYrun-time option of the native Teradata MultiLoad utility.Be aware that these options are disabled while you are using the <strong>SAS</strong>/<strong>ACCESS</strong>MultiLoad facility.3 The DBCOMMIT= LIBNAME and data set options are disabled becauseDBCOMMIT= functions very differently from CHECKPOINT of the nativeTeradata MultiLoad utility.3 The ERRLIMIT= data set option is disabled because the number of errors is notknown until all records have been sent to MultiLoad. The default value ofERRLIMIT=1 is not honored.To see whether threaded reads are actually generated, turn on <strong>SAS</strong> tracing by settingOPTIONS <strong>SAS</strong>TRACE=”,,,d” in your program.Using the TPT APITPT API Supported Features and Restrictions<strong>SAS</strong>/<strong>ACCESS</strong> Interface to Teradata supports the TPT API <strong>for</strong> loading data. The TPTAPI provides a consistent interface <strong>for</strong> Fastload, MultiLoad, and Multi-Statementinsert. TPT API documentation refers to Fastload as the load driver, MultiLoad as theupdate driver, and Multi-Statement insert as the stream driver. <strong>SAS</strong> supports all threeload methods and can restart loading from checkpoints when you use the TPT API withany of them.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!