--- In firebird-support@yahoogroups.com, "Ann W. Harrison"
<aharrison@...> wrote:

>
> Adam,
> > I had a report from a customer about a corrupt database, and I am
> > looking for any hints to determine what has actually occurred and
> > (hopefully) what may have caused it.
> >
> > Win 2003 Server, 1.5.5 Classic, from firebird.log:
> >
> > SERVER Tue Oct 28 14:30:04 2008
> > Database: E:\DATA\DATA.FDB
> > database file appears corrupt ()
> > wrong page type
> > page 195537 is of wrong type (expected 7, found 5)
> > internal gds software consistency check (error during savepoint
> > backout (290))
> >
> > This error occurs hundreds of times as different connections have hit
> > the corrupt page and crashed.
>

Hello Ann,

>
> A backup/restore will correct the problem, but the solution(*) is to
> move to a more recent version of Firebird.

By "correct the problem", I suppose you mean "correct the problem
until it happens again"?

By "more recent", I presume that this is a known issue in 1.5.x that
won't be fixed, and that 2.1 should (90%) be OK? We are still in
testing with this version, but if that is the fix, then I will ensure
that some focus is given to completing our testing of it.

> There was a bug in the
> index re-combination code that could, under heavy load, leave a
> pointer in a parent node to a page that had been a lower level index
> node, but had since been recombined, released, and reused as a
> data page.

That makes sense. This is a large customer database, although not our
largest or highest utilised database. The server has something like 16
cores so there would be a greater chance for concurrent database load
than the next largest server with 8 cores.

Adam