Subject | Re: [ib-support] Corrupt Database |
---|---|
Author | Ann W. Harrison |
Post date | 2002-11-01T15:17:19Z |
At 12:38 AM 11/1/2002 +0100, Pete Clark wrote:
causing the byte-offset value to roll over. The result is that
something has written an index page (7) on page 0 which should
be the header page (1). The header page then got written back
over the index page - it gets written a lot. Gbak was following
an index and discovered the error.
Gbak uses only system indexes - indexes on system tables. Since
it reads all of every data table, it uses only natural scans of
user data. So, you've had the bad luck to corrupt a system index.
The tools distributed won't fix that. With luck you've got a recent
backup and can move forward from it. Otherwise contact IBSurgeon
or me.
Regards,
Ann
www.ibphoenix.com
We have answers.
>I am getting errors whilst trying to backup the Interbase Version WI-It sounds as if your database has exceeded 4Gb in a single file,
>V5.5.0.742 database. So I used Interbase Server, Maintenance, Database
>Validation, founds some errors, told the program to fix them, then
>backup again. But I still get some errors:
>
>gbak: ERROR: database file appears corrupt ()
>gbak: ERROR: wrong page type
>gbak: ERROR: page 0 is of wrong type (expected 7, found 1)
>gbak: ERROR: gds_$receive failed
>gbak: Exiting before completion due to errors
causing the byte-offset value to roll over. The result is that
something has written an index page (7) on page 0 which should
be the header page (1). The header page then got written back
over the index page - it gets written a lot. Gbak was following
an index and discovered the error.
Gbak uses only system indexes - indexes on system tables. Since
it reads all of every data table, it uses only natural scans of
user data. So, you've had the bad luck to corrupt a system index.
The tools distributed won't fix that. With luck you've got a recent
backup and can move forward from it. Otherwise contact IBSurgeon
or me.
Regards,
Ann
www.ibphoenix.com
We have answers.