RE: Index in Unusable State: Usual Suspects

Of course the table will have data in it but if it does not then the index would not be marked as
unusable(I think).

Rick

> -----Original Message-----
> From: Terrian, Thomas [SMTP:Thomas.Terrian_at_standardregister.com]
> Sent: Wednesday, January 10, 2001 7:41 AM
> To: Multiple recipients of list ORACLE-L
> Subject: RE: Index in Unusable State: Usual Suspects
>
> Yes, If you issue an "ALTER TABLE MOVE" command, the indexes will be
> marked unusable.
>
> Tom Terrian
>
> -----Original Message-----
> From: Koivu, Lisa [mailto:lkoivu_at_qode.com]
> Sent: Tuesday, January 09, 2001 2:42 PM
> To: Multiple recipients of list ORACLE-L
> Subject: Index in Unusable State: Usual Suspects
>
>
>
> Hi all,
>
> Has anyone ever seen an index rendered unusable when SQL*Loader is
> not involved?
> SQL*Loader populates a table that is used to populate a second
> table. One of the indexes on the second table somehow became unusable.
>
> The table is not partitioned and this is not a bitmap index.
>
> There are no savepoints being used, it's just an INSERT...SELECT
> statement from the first table. The SQL*Loader process was indeed
> complete before this statement ran.
>
> The client process did not die.
> And the database certainly did not experience instance failure! I
> would have known about that.
>
> I see that a unique index can become unusable if there are duplicate
> values, but that isn't the case here. The index was rebuilt with no
> incident. However, I need to chase down whatever it was that caused this.
>
>
> Thanks in advance for any suggestions.
>
> Lisa Rutland Koivu
> Oracle Database Administrator
> Qode.com
> 4850 North State Road 7
> Suite G104
> Fort Lauderdale, FL 33319
>
> V: 954.484.3191, x174
> F: 954.484.2933
> C: 954.658.5849
> <http://www.qode.com>
>
> "The information contained herein does not express the opinion or
> position of Qode.com and cannot be attributed to or made binding upon
Received on Wed Jan 10 2001 - 07:09:29 CST