Data Set Options for Relational Databases BL_BADFILE= Data Set Option 139
specifies that SAS performs the commit after processing the number of row that are
specified by using DBCOMMIT=, or the default number of rows if DBCOMMIT= is
not specified.
See Also
To assign this option to a group of relational DBMS tables or views, see the
LIBNAME option “AUTOCOMMIT= LIBNAME Option” on page 70.
BL_BADFILE= Data Set Option
Identifies a file containing records that were rejected during a bulk load
Valid in:
DATA and PROC steps (when accessing DBMS data using SAS/ACCESS
software)
DBMS Support:
Oracle
Default value:
creates a data file in the current directory or with the default file
specifications
Syntax
BL_BADFILE= path-and-filename
Syntax Description
path-and-filename
is an SQL*Loader file to which rejected rows of data are written. On most platforms,
the default file name takes the form BL_<table>_<unique-ID>.bad, where
table is the table name
unique-ID is 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.
Details
If you do not specify this option and a BAD file does not exist, a file is created in the
current directory (or with the default file specifications). If you do not specify this
option and a BAD file already exists, the Oracle bulk loader reuses the file, replacing
the contents with rejected rows from the new load.
Records can be rejected by either the SQL*Loader or by Oracle. For example, the
SQL*Loader can reject a record that contains invalid input, and Oracle can reject a
record because it does not contain a unique key. If no records are rejected, the BAD file
is not created.
On most operating systems, the BAD file is created in the same format as the DATA
file, so the rejected records can be loaded after corrections have been made.
Operating Environment Information: On OS/390 operating systems, the BAD file is
created with default DCB attributes. For information on how to overcome this, refer to