Re: SQL*Loader: BAD file is empty?

In article <74jusd$ct1$1_at_nntp.gulfsouth.verio.net>, toddo_at_gcr1.com says...
> I'm experiencing a problem with SQL*Loader version 7.3.2.3.2 on a VMS
> system. The LOG file tells me that 5 rows of the data file were not loaded
> because of a unique constraint violation. But the BAD file is empty; it
> does not contain the 5 rows that failed. The BAD file has the same
> date/time stamp as the LOG file, so it appears that it is getting created,
> but it is empty. Shouldn't rows that are rejected due to Oracle errors be
> written to the BAD file?
>
> Does anyone know of any reasons why the BAD file would be empty in this
> situation? Thanks in advance.
>
> Todd Owers
> toddo_at_gcr1.com
>

Maybe you have empty rows in your data file. You can check BAD file if it has five emty rows (just <LF> or <CR> in it). Received on Wed Dec 09 1998 - 00:00:00 CET