Subject RE: [firebird-support] Fixing corrupted indexes without restoring
Author Maya Opperman
Ann wrote:
>there's no reason I can think of
>to deactivate and reactivate all indexes on a regular basis. If
>you're having problems with indexes, tell us what's going on so the
>problem can be fixed.

OK, here goes:

It has happened at a few of our sites. We mostly pick it up at year end,
since the system does not allow you to proceed to the new year, if it
thinks there is an imbalance.

We install Firebird 1.5.4 superserver by default (if there isn't already
a copy of firebird installed) so most of these would have been 1.5.4

We have moved the larger sites over to classic, and then some of them
further onto Firebird 2.1.3

So, it seems to be across all versions. We do not use Firebird 2.5, and
we don't use the new monitoring tables (which has a known bug, of
corrupting indexes)

I haven't managed to see a common denominator between all the sites
experiencing this :-(

It might be easiest though, if we just pick one site, and focus on that?

We have asked for the Firebird logs, and they all seem to contains a lot
of entries like this:

XYZAPPS Fri Mar 12 09:41:32 2010
INET/inet_error: read errno = 10054

XYZAPPS Fri Mar 12 09:41:32 2010
INET/inet_error: read errno = 10054

XYZAPPS Fri Mar 12 10:57:40 2010
INET/inet_error: read errno = 10054

We also managed to get a copy of one if these corrupted database on a
memory stick, and copied it here (since backup-restore resolves the
problem) and ran some tests on it.

Validation showed quite a few corrupt indexes. Dropping and recreating
the index affecting the total in particular I knew was out, also
resolved the problem. I have no idea of how to actually get a list of
exactly which indexes were corrupted. Is that possible?

Anyway, to try find and fix the source of the problem, what else do you
need from me?

Thanks in advance!