Re: SQL*loader problem with SEQUENCE

In article <47lgvf$n1m_at_news.acns.nwu.edu>

           dma956_at_lulu.acns.nwu.edu "Dave Mausner" writes:
> In article <515310448wnr_at_istel-is.demon.co.uk>,
> Andy Hardy <AndyHard_at_istel-is.demon.co.uk> wrote:
> >I'm using SQLLOAD to append a large table. The key (UNIQUE INDEX) to this
> >table is generated using the SEQUENCE(COUNT) command in the ctl.
> >
> >However, on completion of a load I am getting 'Index in Direct Load
> >State' messages because of a constraint violation - and if I check I
> >can find a duplicate key.
> >
> >As SQL*load is generating the number for me, why is it creating
> >duplicates?
>
> this can happen in parallel direct mode because each instance of the
> load generates its sequence independently but not uniquely because
> when they start, the record count of the original data appears the
> same to each instance.
>
> you can load direct, but avoid parallel when using sequences based
> on count or max value.
Dave,

I don't recall running in parallel... and if I had then I'd have expected to see more than one duplicate.

However, it is something to bear in mind for the future,

Thanks,

Andy  

-- 
Andy Hardy (Internet: aph_at_ahardy.demon.co.uk, CIS: 100015,2603)
PGP key available on request
===============================================================
Don't assume - Check out the price at Tescos.