Recently, a customer's database got stealthily trashed by a flakey disk. By the time it got bad enough to notice, the database had some bad parts. Gfix and gbak eventually let us get this repaired, but in the process the inidices all got deactivated. I thought that a backup/restore cycle would take care of this, but evidently not.

We only noticed this because certain operations had become very slow.

I managed get them all reactivated, but it took a while; evidently the problem was that a row was missing from a master table as a result of the damage, so on of the FK indices couldn't be turned on.

My questions are:

1) Is there no quick, simple way to reactivate all indices? I did it by manipulating RDB$INDICES directly, but I would think there'd be a better way.

2) Was I wrong in thinking that a backup/restore cycle would reactivate indexes unless I told it not to, or was this not done because of the missing data which caused an error when activating that FK index?

Michael D. Spence
Mockingbird Data Systems, Inc.