BL_EXCEPTION= Data Set Option

Specifies the exception table into which rows in error are copied.
Valid in: DATA and PROC steps (when accessing DBMS data using SAS/ACCESS software)
Default: none
Requirement: To specify this option, you must first set BULKLOAD=YES.
Data source: DB2 under UNIX and PC Hosts, Greenplum
See: BULKLOAD= data set option, Capturing Bulk-Load Statistics into Macro Variables

Syntax

BL_EXCEPTION=exception-table-name

Syntax Description

exception table-name
specifies the exception table into which rows in error are copied.

Details

DB2 under UNIX and PC Hosts: Any row that is in violation of a unique index or a primary key index is copied. DATALINK exceptions are also captured in the exception table. If you specify an unqualified table name, the table is qualified with the CURRENT SCHEMA. Information that is written to the exception table is not written to the dump file. In a partitioned database environment, you must define an exception table for those partitions on which the loading table is defined. However, the dump file contains rows that cannot be loaded because they are not valid or contain syntax errors.
Greenplum: Formatting errors are logged when running in single-row, error-isolation mode. You can then examine this error table to determine whether any error rows were not loaded. The specified error table is used if it already exists. Otherwise, it is generated automatically.
For more information about using this option with DB2 under UNIX and PC Hosts, see the FOR EXCEPTION parameter in the IBM DB2 Universal Database Data Movement Utilities Guide and Reference. For more information about the load exception table, see the load exception table topics in the IBM DB2 Universal Database Data Movement Utilities Guide and Reference and the IBM DB2 Universal Database SQL Reference, Volume 1.