Hello Adam,

>
>
> Our customer raised a good question. If this problem is an index
> corruption, could it not be repaired by simply dropping and recreating
> the index (or constraint). You mention that it won't be a generator
> populated field, which means it will not be one of our primary keys.
> This means (in our case) that there are no dependencies to worry about.

Yes, that's right. One way to find the index is to get the plan for
a statement that causes the error. Or have a few test statements that
use specific indexes - you need a statement that touches the broken
part of the index, so a sequence of ranges might work. Another clue
is that it's an active index, so one where the field is changed often
would be a place to look.


Good luck,


Ann

>