Re: Rollback after sql load

Hi All,

Niall's suggestion is probably what I would recommend as well.

However, another option that might be appropriate would be to use a direct load with rows set to null. This will ensure a commit is only performed at the end (although you need to note the issues associated with direct load).

Cheers

Richard
"Niall Litchfield" <n-litchfield_at_audit-commission.gov.uk> wrote in message news:3d3d6845$0$225$ed9e5944_at_reading.news.pipex.net...
> "nn" <nn_at_n.com> wrote in message
> news:ahjot8$6mh$1_at_s1.read.news.oleane.net...
> > Thank you Richard
> > I've a critical table, and I would that sql loader's loading can be made
> > correctly. if for example, the sql loader exit with error because the
max
> > extent have been reached, the stuff loaded before error, have it been
> > committed?
>
> It depends. Generally sql*loader commits every 'n' records. Thus it is
> likely that some but not all of the data will have been committed.
>
> What I would do is to load into a staging table and only if this load is
> successful insert/update the production table from the staging table.
>
>
> --
> Niall Litchfield
> Oracle DBA
> Audit Commission UK
> *****************************************
> Please include version and platform
> and SQL where applicable
> It makes life easier and increases the
> likelihood of a good answer
>
> ******************************************
>
>
Received on Wed Jul 24 2002 - 03:42:17 CDT