Hello Ann,

>
> If memory serves, the bug shows up on an index where entries are made
> out of order (meaning not sorted by the index key as they are when
> the key is a timestamp or generator), and where key values are deleted
> (meaning that the record was deleted, or the key value updated) often.

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.

GBak takes about 20 minutes to get through a backup-restore on that
server, but I would rather minimise the downtime should this happen again.

If the corruption can be fixed using this method, is there any way of
identifying the offending index?

TIA

Adam