Re: Oracle SQL*Loader Duplicate record handling.

To get round this problem, I've written a utility which does a trial load of the first 100 records of a datafile. If no duplicates are found, then it loads the file using direct path.
Sounds like we were both doing the same VLDB data warehouse thing. This aspect of Oracle is completely awful from a technical stand point, but has at least encouraged us to look at data quality with a more critical eye before we load things.

Simon Riggs
Managing Consultant
Info Management Practice Group
OpenMIND Consulting
Voice: +44-1869 238080
http://www.open-mind.co.uk

Mark Gumbs <mgumbs_at_nospam.hotmail.com> wrote in message news:375d2741.0_at_145.227.194.253...
> Direct load loads the records directly into data files and does validation
> later.
> You have to use conventional path when loading for any validation to take
> place and for SQL*Loader to reject the record.
>
> Mark
>
>
> Ming wrote in message <7jj5dk$qq2_at_romeo.logica.co.uk>...
> >Dear all
> >
> >I'm currently using direct loader to load a large datafile into a fact
> table
> >with primary key and foreign key constraints. However whilst SQL*Loader
> >recognises that primary key constraints have been violated with dupicate
> >records it carries on loading them.
> >
> >Thus causing the primary key to go into a unstable state.
> >
> >Is there a way to trap these duplicate records within direct SQL*Loader
or
> a
> >t least terminate the loader so as not to load the file.
> >
> >
>
>
Received on Tue Jun 08 1999 - 18:32:17 CDT