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.

Data Set Options <strong>for</strong> <strong>Relational</strong> <strong>Databases</strong> 4 MULTILOAD= Data Set Option 345run;3 If you used ML_LOG= in the run that failed, you can specify the same value <strong>for</strong>ML_LOG= on restart. There<strong>for</strong>e, you need not specify four data set options toidentify the temporary tables that MultiLoad uses.For example, assume that this is how the original run used ML_LOG=:data trlib.mlfloat(MultiLoad=yes ML_CHECKPOINT=1000 ML_LOG=MY_ERRORS);set work.testdata;run;If this DATA step fails with this error, the restart capability needs onlyML_LOG= to identify all necessary tables.ERROR: MultiLoad failed with DBS error 2644 after a checkpoint was taken <strong>for</strong>13000 records. Correct error and restart as an append process with data set optionsML_RESTART=<strong>SAS</strong>_ML_RS_1436199780, ML_ERROR1=<strong>SAS</strong>_ML_ET_1436199780,ML_ERROR2=<strong>SAS</strong>_ML_UT_1436199780, and ML_WORK=<strong>SAS</strong>_ML_WT_1436199780.If the first run used FIRSTOBS=n, then use the value (7278+n-1) <strong>for</strong> FIRSTOBSin the restart.Otherwise use FIRSTOBS=7278.Sometimes the FIRSTOBS value used on the restart can be an earlier positionthan the last checkpoint because restart is block-oriented and notrecord-oriented.proc append data=work.testdata(FIRSTOBS=7278)base=trlib.mlfloat(MultiLoad=YES ML_LOG=MY_ERRORS ML_CHECKPOINT=1000);run;3 If the MultiLoad process fails in the application phase, <strong>SAS</strong> has alreadytransferred all data to be loaded to Teradata. You must restart a MultiLoad joboutside of <strong>SAS</strong> using the script that is written to the <strong>SAS</strong> log. See your Teradatadocumentation on the MultiLoad utility <strong>for</strong> instructions on how to run MultiLoadscripts. Here is an example of a script that is written in the <strong>SAS</strong> log.=-=-= MultiLoad restart script starts here =-=-=.LOGTABLE MY_ERRORS_RS;.LOGON boom/mloaduser,********;.begin import mload tables "mlfloat" CHECKPOINT 0 WORKTABLESMY_ERRORS_WT ERRORTABLESMY_ERRORS_ET MY_ERRORS_UT/*TIFY HIGH EXIT <strong>SAS</strong>MLNE.DLL TEXT ’2180*/;.layout saslayout indicators;.FIELD "x" * FLOAT;.DML Label <strong>SAS</strong>DML;insert into "mlfloat".*;.IMPORT INFILE DUMMY/*SMOD <strong>SAS</strong>MLAM.DLL ’2180 2180 2180 */FORMAT UNFORMAT LAYOUT <strong>SAS</strong>LAYOUTAPPLY <strong>SAS</strong>DML;.END MLOAD;.LOGOFF;=-=-= MultiLoad restart script ends here =-=-=ERROR: MultiLoad failed with DBS error 2644 in the application phase.Run the MultiLoad restart script listed above outside of <strong>SAS</strong>to restart the job.

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

Saved successfully!

Ooh no, something went wrong!