Hi,

one of our databases can no longer be backed up. We always get the following error:

ERROR: internal gds software consistency check (index inconsistent (204), file: btr.cpp line: 4555)

FBFirstAID, GFIX and GBAK do not seem to help in fixing this corruption. In this case, we are using Firebird 2.0.3.

What can we defer from the following errors that GFIX produced in firebird.log:

NIVANT2 (Server) Tue Oct 07 22:10:44 2008
Database: C:\METADATA.FDB
Index 3 is corrupt on page 101 level 1. File: \fb2\dev\fb2R2_0_3\firebird2\src\jrd\validation.cpp, line: 1656
in table RDB$RELATION_FIELDS (5)

NIVANT2 (Server) Tue Oct 07 22:10:44 2008
Database: C:\METADATA.FDB
Index 3 is corrupt on page 101 level 1. File: \fb2\dev\fb2R2_0_3\firebird2\src\jrd\validation.cpp, line: 1532
in table RDB$RELATION_FIELDS (5)

NIVANT2 (Server) Tue Oct 07 22:10:44 2008
Database: C:\METADATA.FDB
Index 3 is corrupt on page 101 level 1. File: \fb2\dev\fb2R2_0_3\firebird2\src\jrd\validation.cpp, line: 1646
in table RDB$RELATION_FIELDS (5)

NIVANT2 (Server) Tue Oct 07 22:10:44 2008
Database: C:\METADATA.FDB
Index 3 is corrupt on page 101 level 1. File: \fb2\dev\fb2R2_0_3\firebird2\src\jrd\validation.cpp, line: 1671
in table RDB$RELATION_FIELDS (5)

These are the only errors. How could we fix this database? It seems that the corruption is minor (one database page only), but the tools we have don't seem to be able to fix it.

Best regards,
Antti Nivala

------------------------------------------

Motive Systems
http://www.motivesys.com