Re: Index troubles with SQLLoader

It depends, if you are using the direct path loading option, Oracle disables all the constraints and loads the data directly into the datafiles. This is the reason that it runs quickly. There is an option to put at the end of the controlfile that is used to reenable the constraints and it is reenable constraints. However, you may encounter some problems with the indexes and you may have to rebuild them manually. You can check for the problem indexes by checking the dba_indexes table. BTW, direct path also doesn't perform any trigger fires so you have to contend with that issue as well.

The conventional load path keeps all of your data and applies the data to the indexes and also fires the triggers. You have the possibility of row contention and as such the conventional load path runs much slower. It used bind arrays to load the data and works very much like performing insert statements on the database.

Hope this helps.

Daniel Murray

x_at_x.com wrote:

> Ok, I done that for all my indexes that are not on the Primary Key
> (PK_THIRD).
> Nothing is changing.
> I guess the trouble is on my Pk_third index but I need drop my PK before
> (?).
> I can't do because I had old data in the THIRD table that have their PK used
> into others tables : I use SQLLoader in APPEND mode.
>
> Do I always recreate indexes when I load datas with SQLLoader ?
>
> Thanks for help.
>
> Chris Weiss a écrit dans le message <7if2j6$61m$1_at_msunews.cl.msu.edu>...
> >Drop and recreate your index before you perform the delete.
> >
> >Chris
> >
> >
Received on Mon Jun 28 1999 - 10:16:45 CDT