SQL*Loader: BAD file is empty?

From: Todd Owers <toddo_at_gcr1.com>
Date: 1998/12/08
Message-ID: <74jusd$ct1$1_at_nntp.gulfsouth.verio.net>#1/1

[Quoted] 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 Received on Tue Dec 08 1998 - 00:00:00 CET

This message: [ Message body ]
Next message: Idwi: "Re: Developer/2000: How to hide default toolbar?"
Previous message: SDG: "Re: Dev2K Install Crashes Win95"
Next in thread: mskoblar: "Re: SQL*Loader: BAD file is empty?"
Reply: Ernie Juanengo: "Re: SQL*Loader: BAD file is empty?"
Reply: mskoblar: "Re: SQL*Loader: BAD file is empty?"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message