Re: A real problem!

In addition to the other answers. I think you can rebuild the index while others can read the table, but not update it (use the command alter index rebuild). Because the rebuild command uses the old index, it is possible that this command do not work on the corrupt index.

Andreas Prusch

In article <6o2fqd$jmr$1_at_ash.prod.itd.earthlink.net>,   "Binoy James" <binoy.james_at_usa.net> wrote:
> Folks,
>
> We have a problem here that I would like some help/advice on:
>
> We have a 14 gb table with a primary unique index and three other indexes.
> When accessing that table on a delete operation, the user gets a ora-08102
> error (corrupt index - key not found). The problem we're running into is
> that we cannot determine which is the corrupt index? We are unable to do an
> analyze table since that would lock the table against any further updates
> till the analyze is complete and with a 14gb table....
>
> The problem is this is a 24x7 db and we have managed to get a 5hr downtime
> window to try and fix it. I am guessing it will take that amount of time to
> rebuild the bad index, but how do we narrow down which index is corrupt?
>
> Help!
> Jim.
>
> ps: I hope this is the right newsgroup for this post, if not please let me
> know which one is.
> Thanks in advance.
>
>

-----== Posted via Deja News, The Leader in Internet Discussion ==----- http://www.dejanews.com/rg_mkgrp.xp Create Your Own Free Member Forum Received on Fri Jul 10 1998 - 01:41:37 CDT