sqlloader errors

Hello,

Env: Oracle 8.1.6.0.0 on Solaris 2.7

Does anyone know what controls sqlloader behaviour regarding the number of records it rejects when an error is encountered?

We have a number of daily sqlldr processes; this morning, one sqlldr process rejected 7 records because of unique constraint violations. We are certain that only 1 record really had a violation, and the other 6 did not.

The records rejected were all consecutive in the .dat file, and the .log file indicates that sqlloader is using 7 records in each batch commit.
(Space allocated for bind array: 57792 bytes(7 rows))

Our conclusion is that sqlloader rejected all records in the same batch because 1 of them had an error.

What is puzzling is that we have several other similar sqlloader processes, using multiple records in each batch, but all others only reject individual records with errors, not all records in the same array. The .ctl files for all of these processes are very similar, and contain mostly the same options: ROWS=1024, ERRORS=50 The default bindsize on this machine is 64K.

Thanks to any responders.

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Bill Becker
  INET: beckerb_at_mfldclin.edu

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L


(or the name of mailing list you want to be removed from).  You may

also send the HELP command for other information (like subscribing).