BAD

Default: The name of the data file, with an extension of .bad

Purpose

Specifies the name or location, or both, of the bad file associated with the first data file specification.

Syntax and Description

BAD=[directory/][filename]

The bad file stores records that cause errors during insert or that are improperly formatted. If you specify the BAD parameter, you must supply either a directory or file name, or both. If there are rejected records, and you have not specified a name for the bad file, then the name defaults to the name of the data file with an extension or file type of .bad.

The directory parameter specifies a directory to which the bad file is written. The specification can include the name of a device or network node. The value of directory is determined as follows:

If the BAD parameter is not specified at all and a bad file is needed, then the default directory is the one in which the SQL*Loader control file resides.
If the BAD parameter is specified with a file name but no directory, then the directory defaults to the current directory.
If the BAD parameter is specified with a directory but no file name, then the specified directory is used and the default is used for the bad file name and extension.

The filename parameter specifies a file name recognized as valid on your platform. You must specify only a name (and extension, if one other than .bad is desired). Any spaces or punctuation marks in the file name must be enclosed in single quotation marks.

A bad file specified on the command line becomes the bad file associated with the first INFILE statement (if there is one) in the control file. The name of the bad file can also be specified in the SQL*Loader control file, using the BADFILE clause. If the bad file is specified in the control file, as well as on the command line, then the command-line value is used. If a bad file with that name already exists, then it is either overwritten or a new version is created, depending on your operating system