Re: Index troubles with SQLLoader

In article <7if2j6$61m$1_at_msunews.cl.msu.edu>, Chris Weiss <weisschr_at_pilot.msu.edu> writes
>Drop and recreate your index before you perform the delete.
>
>Chris
>
I'm sure there is a (re?) enable constraints clause you can put at the end of the control file.
If you are direct load mode, then I think I hit this bug myself a while back but I can't remember the details. try analyse table xx validate structure cascade and then tell support. I seem to remember it was an index left in direct load state but the system was still trying to use it and I had a big arg with support over whether it was a bug or a feature.
They were wrong ;-)
>
><x_at_x.com> wrote in message news:7if5np$eje$1_at_mars.worldonline.fr...
>> Hi,
>>
>> Well, my SQLLoader seems working well but it turns off all constraints on
>> the table I load.
>> I think it is right but I must enable these constraints manually (with
>> schema manager)
>> After that, if I try to delete the lines I have loaded, I get the
>following
>> message :
>>
>> SQL> delete third where id_ti > 1000;
>> delete third where id_ti > 1000
>> *
>> ERROR Line 1:
>> ORA-08102: index key not found, obj # 2697, dba 33578192 (2)
>>
>> Thanks for help.
>>
>>
>>
>
>

-- 
Please remove nospam from my address to Reply.