Subject | wrong type (expected 7, found 5) |
---|---|
Author | Juan Pedro López |
Post date | 2008-08-21T11:41:31Z |
Hello,
I am using Firebird 2.0.3 SS amd64 on a Linux box.
My database had an error when I was doing a manual sweep with gfix. This
was shown in firebird.log:
database file appears corrupt ()
wrong page type
page 12547 is of wrong type (expected 7, found 5)
In this situation, no connections could be got from the database.
Just to test, I stopped the firebird server process and restarted it,
after stopping the hanged gfix process too.
That seemed to solve the problem because connections were available
again and I could successfuly execute the manual sweep.
Now everything seems to be working right.
Is it possible to have some indexes corrupted right now?
Should I run any other routine to completely fix the database?
Manual gfix that triggered the error is part of an automatic routine
executed every night, when the database is low loaded. This routine has
been working properly for three months util it failed for the first
time.
At first, some bulk deletes are done. After that the manual sweep is
performed. Finally a gbak is issued.
What could be the reason for the unexpected failure?
Thank you very much,
Juan Pedro López
I am using Firebird 2.0.3 SS amd64 on a Linux box.
My database had an error when I was doing a manual sweep with gfix. This
was shown in firebird.log:
database file appears corrupt ()
wrong page type
page 12547 is of wrong type (expected 7, found 5)
In this situation, no connections could be got from the database.
Just to test, I stopped the firebird server process and restarted it,
after stopping the hanged gfix process too.
That seemed to solve the problem because connections were available
again and I could successfuly execute the manual sweep.
Now everything seems to be working right.
Is it possible to have some indexes corrupted right now?
Should I run any other routine to completely fix the database?
Manual gfix that triggered the error is part of an automatic routine
executed every night, when the database is low loaded. This routine has
been working properly for three months util it failed for the first
time.
At first, some bulk deletes are done. After that the manual sweep is
performed. Finally a gbak is issued.
What could be the reason for the unexpected failure?
Thank you very much,
Juan Pedro López