Re: Indexes going into DIRECT LOAD status

On Wed, 27 Jan 1999 18:32:08 +0100, david_neal_at_cantor.com wrote (in message <78niio$9mu$1_at_nnrp1.dejanews.com>):
>
> Hi all,
>
> I have a few indexes on an Oracle v7.3.2 database which are in a DIRECT
> LOAD status when queried from all_indexes but are fine from all_objects.
>
> 1. Which should I believe ? 2. Why does it go into this status and how can I

> prevent it ?
>
> I've gotten around it so far by alter index <index_name> rebuild but I'd
> like to know why it's happening and stop it.

Hi,

this happens when loader in directpath gets terminated before completing it's task.
There is also a bug. Any alter table that changes the max# of rows in a block makes indexes into directload status. Solved in 8.0.4. I think you should think of dba_objects contain the status of the definition of the index. In dba_indexes is the state of the index. Any way, I believe dba_indexes.

--

Ronald  -  Unix SA               http://home.wxs.nl/~ronr/professional.html

        -  Oracle DBA            http://www.tresco.nl  
        -  Middleware programmer/
                      designer   mailto:R.Rood_at_tresco.nl