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 8093 Data errors are logged in Teradata tables. Error recovery can be difficult if you donot TPT_CHECKPOINT_DATA= to enable restart from the last checkpoint. Tofind the error that corresponds to the code that is stored in the error table, seeyour Teradata documentation. You can restart a failed job <strong>for</strong> the last checkpointby following the instructions in the <strong>SAS</strong> error log.3 FastLoad does not load duplicate rows (those where all corresponding fieldscontain identical data) into a Teradata table. If your <strong>SAS</strong> data set containsduplicate rows, you can use other load methods.Starting FastLoad with the TPT APISee the <strong>SAS</strong> configuration document <strong>for</strong> instructions on setting up the environmentso that <strong>SAS</strong> can find the TPT API modules.You can use one of these options to start FastLoad in the<strong>SAS</strong>/<strong>ACCESS</strong> interfaceusing the TPT API:3 the TPT=YES data set option in a processing step that populates an emptyTeradata table3 the TPT=YES LIBNAME option on the destination libref (the Teradata DBMSlibrary where one or more tables are to be created and loaded)FastLoad with TPT API Data Set OptionsThese data set options are specific to FastLoad using the TPT API:3 TPT_BUFFER_SIZE=3 TPT_ERROR_TABLE_1=3 TPT_ERROR_TABLE_2=TPT API MultiLoad Supported Features and Restrictions<strong>SAS</strong>/<strong>ACCESS</strong> Interface to Teradata supports the TPT API <strong>for</strong> MultiLoad, also knownas the update driver. <strong>SAS</strong>/<strong>ACCESS</strong> works by interfacing with the update driverthrough the TPT API. This API then uses the Teradata Multiload protocol <strong>for</strong> loadingdata. See your Teradata documentation <strong>for</strong> more in<strong>for</strong>mation about the update driver.This is the default MultiLoad method. If <strong>SAS</strong> cannot find the Teradata modules thatare required <strong>for</strong> the TPT API or TPT=NO, then <strong>SAS</strong>/<strong>ACCESS</strong> uses the old method ofMultiLoad. <strong>SAS</strong>/<strong>ACCESS</strong> can restart Multiload from checkpoints when MultiLoad usesthe TPT API.The <strong>SAS</strong>/<strong>ACCESS</strong> MultiLoad facility loads both empty and existing Teradata tables.<strong>SAS</strong>/<strong>ACCESS</strong> supports only insert operations and loading only one target table at time.The <strong>SAS</strong>/<strong>ACCESS</strong> MultLoad facility using the TPT API is similar to the nativeTeradata MultiLoad utility. A common limitation that they share is that you must dropthese items on target tables be<strong>for</strong>e the load:3 unique secondary indexes3 <strong>for</strong>eign key references3 join indexesErrors are logged to Teradata tables. Error recovery can be difficult if you do not setTPT_CHECKPOINT_DATA= to enable restart from the last checkpoint. To find theerror that corresponds to the code that is stored in the error table, see your Teradatadocumentation. You can restart a failed job <strong>for</strong> the last checkpoint by following theinstructions in the <strong>SAS</strong> error log.

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

Saved successfully!

Ooh no, something went wrong!