Data Set Options for Relational Databases

BL_LOG= Data Set Option

Identifies a log file that contains information for bulk load, such as statistics and errors.

Default value:	DBMS-specific
Valid in:	DATA and PROC steps (when accessing DBMS data using SAS/ACCESS software)
DBMS support:	DB2 under UNIX and PC Hosts, Oracle, Teradata

Syntax
Syntax Description
Details
See Also

Syntax

BL_LOG=path-and-log-filename

Syntax Description

path-and-log-filename: is a file to which information about the loading process is written.

Details

To specify this option, you must first set BULKLOAD=YES. See the reference section for your SAS/ACCESS interface for additional details.

When the DBMS bulk-load facility is invoked, it creates a log file. The contents of the log file are DBMS-specific. The BL_ prefix distinguishes this log file from the one created by the SAS log. If BL_LOG= is specified with the same path and filename as an existing log, the new log replaces the existing log.

Oracle: When the SQL*Loader is invoked, it creates a log file. This file contains a detailed summary of the load, including a description of any errors. If SQL*Loader cannot create a log file, execution of the bulk load terminates. If a log file does not already exist, it is created in the current directory or with the default file specifications. If a log file does already exist, the Oracle bulk loader reuses the file, replacing the contents with information from the new load. On most platforms, the default filename takes the form BL_<table>_<unique-ID>.log:

table	specifies the table name
unique-ID	specifies a number that is used to prevent collisions in the event of two or more simultaneous bulk loads of a particular table. The SAS/ACCESS engine generates the number.

DB2 under UNIX and PC Hosts: If BL_LOG= is not specified, the log file is deleted automatically after a successful operation. For more information, see the bulk-load topic in the DB2 under UNIX and PC Hosts bulk loading section.

Teradata: For more information, see the bulk-load topic in the Teradata section interface.