Subject Corrupted primary key
Author Alec Swan

We just ran into a problem (in production) where a corrupted primary key
caused the query to return incorrect results. We rebuilt statistics on all
indexes in the database, but that didn't fix the problem. We had to drop and
re-create the primary key to fix the problem.

Our maintenance plans "set statistics" as Ann suggested in this thread (
However, this new problem requires us to drop and recreate primary keys.

My understanding is that the original problem reported in ( was
caused by "bad memory chip" or maybe some other hardware failure. Has there
been any work done in the recent Firebird releases to protect or recover
from this kind of problems? If not, how can we reduce the likelihood of
these problems occurring in the future, e.g. flush to disk more often?



[Non-text portions of this message have been removed]