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

SAS/ACCESS Interface to Oracle 4 Overview 725Passing Joins to OracleBefore a join can pass to Oracle, all of these components of the LIBNAME statementsmust match exactly:3 user ID (USER=)3 password (PASSWORD=)3 path (PATH=)For more information about when and how SAS/ACCESS passes joins to the DBMS,see “Passing Joins to the DBMS” on page 43.Bulk Loading for OracleOverviewSAS/ACCESS Interface to Oracle can call the Oracle SQL*Loader (SQLLDR) whenyou set the data set option BULKLOAD=YES. The Oracle bulk loader provides superiorload performance, so you can rapidly move data from a SAS file into an Oracle table.Future releases of SAS/ACCESS software will continue to use powerful Oracle tools toimprove load performance. An Oracle bulk-load example is available.Here are the Oracle bulk-load data set options. For detailed information about theseoptions, see Chapter 11, “Data Set Options for Relational Databases,” on page 203.3 BL_BADFILE=3 BL_CONTROL=3 BL_DATAFILE=3 BL_DELETE_DATAFILE=3 BL_DIRECT_PATH=3 BL_DISCARDFILE=3 BL_INDEX_OPTIONS=3 BL_LOAD_METHOD=3 BL_LOG=3 BL_OPTIONS=3 BL_PARFILE=3 BL_PRESERVE_BLANKS=3 BL_RECOVERABLE=3 BL_RETURN_WARNINGS_AS_ERRORS=3 BL_SQLLDR_PATH=3 BL_SUPPRESS_NULLIF=3 BULKLOAD=BULKLOAD= calls the Oracle bulk loader so that the Oracle engine can move datafrom a SAS file into an Oracle table using SQL*Loader (SQLLDR).Note: SQL*Loader direct-path load has a number of limitations. See your Oracleutilities documentation for details, including tips to boost performance. You can alsoview the SQL*Loader log file instead of the SAS log for information about the loadwhen you use bulk load. 4