Problem Note 20710: The BL_DEFAULT_DIR data set option enables you to override the default path for SQL*LOADER intermediate files when bulk loading to Oracle
 |  |  |  |  |
Often, when you use SAS® Marketing Automation or other SAS solutions to join SAS data with database tables, the SAS data is loaded into Oracle tables using the Oracle SQL*LOADER (SQLLDR). Oracle's bulk loader requires the use of intermediate files that are automatically created by SAS in the directory from which SAS was invoked. Because these files are generally large, you might encounter disk-space problems.
A new data set option, BL_DEFAULT_DIR, enables you to specify the location of all files (for example, .ctl, .dat, and .log files) that are created by the bulk loading process. The value specified for this option is pre-pended to the file name so it must include the complete, host-specific directory path.
Here is an example:
bl_delete_files=no);
c1=1;
run;
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | SAS Release | |
| Reported | Fixed* | |||
| SAS System | SAS/ACCESS Interface to Oracle | Microsoft Windows XP Professional | 9.1 TS1M3 SP4 | 9.2 TS1M0 |
| Windows Vista | 9.1 TS1M3 SP4 | 9.2 TS1M0 | ||
| Microsoft Windows NT Workstation | 9.1 TS1M3 SP4 | |||
| Microsoft Windows XP 64-bit Edition | 9.1 TS1M3 SP4 | 9.2 TS1M0 | ||
| Microsoft® Windows® for 64-Bit Itanium-based Systems | 9.1 TS1M3 SP4 | 9.2 TS1M0 | ||
| Microsoft Windows Server 2003 Standard Edition | 9.1 TS1M3 SP4 | 9.2 TS1M0 | ||
| Microsoft Windows Server 2003 Datacenter Edition | 9.1 TS1M3 SP4 | 9.2 TS1M0 | ||
| Microsoft Windows Server 2003 Enterprise Edition | 9.1 TS1M3 SP4 | 9.2 TS1M0 | ||
| Microsoft Windows 2000 Server | 9.1 TS1M3 SP4 | 9.2 TS1M0 | ||
| Microsoft Windows 2000 Advanced Server | 9.1 TS1M3 SP4 | 9.2 TS1M0 | ||
| Microsoft Windows 2000 Datacenter Server | 9.1 TS1M3 SP4 | 9.2 TS1M0 | ||
| Microsoft Windows 2000 Professional | 9.1 TS1M3 SP4 | 9.2 TS1M0 | ||
| Solaris for x64 | 9.1 TS1M3 SP4 | 9.2 TS1M0 | ||
| Linux | 9.1 TS1M3 SP4 | 9.2 TS1M0 | ||
| 64-bit Enabled Solaris | 9.1 TS1M3 SP4 | 9.2 TS1M0 | ||
| Linux on Itanium | 9.1 TS1M3 SP4 | 9.2 TS1M0 | ||
| HP-UX IPF | 9.1 TS1M3 SP4 | 9.2 TS1M0 | ||
| 64-bit Enabled AIX | 9.1 TS1M3 SP4 | 9.2 TS1M0 | ||
| 64-bit Enabled HP-UX | 9.1 TS1M3 SP4 | 9.2 TS1M0 | ||
| Tru64 UNIX | 9.1 TS1M3 SP4 | 9.2 TS1M0 | ||
A fix for SAS 9.1.3 (9.1 TS1M3) for this issue is available at:
http://www.sas.com/techsup/download/hotfix/e9_sbcs_prod_list.html#020710A fix for SAS 9.1.3 (9.1 TS1M3) with Asian Language Support (DBCS) for this issue is available at :
http://www.sas.com/techsup/download/hotfix/e9_dbcs_prod_list.html#020710| Type: | Problem Note |
| Priority: | high |
| Topic: | SAS Reference ==> LIBNAME Engines Data Management ==> Data Sources ==> External Databases ==> Oracle |
| Date Modified: | 2008-03-07 14:30:44 |
| Date Created: | 2007-08-01 09:13:03 |