Re: controlling SQLLdr's commit operations

You might consider using utl_file in stead of sqlloader. using utl_file gives you the opportunity to validate your data from file and you can do your data/exception handling also straight from file. However, if you are going to import large amounts of data a staging table might be the best solution.

hth

Marc

"Menelaos Perdikeas" <mperdikeas_at_semantix.gr> wrote in message news:9sov0l$1dhc$1_at_ulysses.noc.ntua.gr...
> Hi,
>
> I need to import large amounts of data using the SQL loader tool and
> since I want this
> to be an atomic operation I was wondering if there is any way to
> configure SQL loader
> to do a commit only at the (successful) end of a large transaction.
> Setting the size of the
> bind array (as described in "Determining the size of the Bind Array"
> in Oracle's documentation) to a value large enough to hold all the
> rows, even if sth. like
> that were possible doesn't seem very deterministic to me. So, is there
> a pattern in dealing
> with this type of situation or does one have to write PLSQL or OCI
> calls oneself
> to do the importing in the intended way ??
>
> Thanks,
> Menelaos Perdikeas.
>
>
Received on Tue Nov 13 2001 - 10:55:34 CET