>> I just want to double check that the following is safe to do, and

won't

>> result in users being able to post duplicate keys, if something goes
>> wrong with reactivating an index for some odd reason:

> It isn't safe and it isn't necessary. Rebuild only corrupted

indexes.

>For the rest SET STATISTICS is enough.
> Use IBAnalyst or FBDataGuard to watch your DB.

Is there a SQL statement, or a call to GFIX that will tell me which
indexes are corrupt?

All I know is my totals don't add up properly till a backup restore, and
validating the database shows me X number of indexes are corrupt.

This is happening at about 5 sites that I know of, at east once a year,
sometimes once a week at the busy sites, both FB 1.5, and FB 2.1

It might be due to network disconnections - looking at their logs, that
has been happening.

I plan to try get some of the more problematic sites on to FB2.5, but I
see from a post here in the past month, that FB2.5 still has some
unexplained index corruptions... so I'm sticking to the devil I know
just a little bit longer...