| Subject | RE: [firebird-support] Error on Gfix |
|---|---|
| Author | Neil Pickles |
| Post date | 2015-09-29T21:42:59Z |
I would have thought that at least steps 1 & 2 would be required, I thought it was the second step that actually ‘fixed’ things.
Cheers,
Neil Pickles - neil@...
From: firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com]
Sent: 29 September 2015 21:50
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] Error on Gfix
Ok, I know this full procedure about corrupt database.
But, when the unique problem about corrupt database is ORPHAN PAGE. In this especific situation, is necessary to execute all the steps, including the backup/restore?
Looking my situation, I'm having ONLY orphan page in a database that have 20~30 GB. In this database, the backup/restore procedure delay significative time...
2015-09-29 17:37 GMT-03:00 'Neil Pickles' neil.pickles@... [firebird-support] <firebird-support@yahoogroups.com>:
We have a 4 part fix process for fixing database, first two commands are gfix and the final two are gbak.
1. %gfix% -v -ignore -full -user SYSDBA -password masterkey %1
2. %gfix% -mend -ignore -user SYSDBA -password masterkey %1
3. %gbak% -b -g -ig -v -user SYSDBA -password masterkey %1 %2
4. %gbak% -c -v -p 8192 -user SYSDBA -password masterkey %1 %2
Sometimes it is necessary to add the –i switch to the 4th command line so that indexes aren’t reactivated upon restore where data is missing that causes the restore to fail. You then have to turn the indices back on individually and fix any data related issues until all indices and referential constraints are all resolved and reactivated successfully.
This process fixes most database corruption issues and has been gleaned from a variety of sources over the last few years, it works for v2.1 & v2.5.
Cheers,
Neil Pickles
From: firebird-support@yahoogroups.com [mailto:firebird-support@yahoogroups.com]
Sent: 29 September 2015 19:43
To: firebird-support@yahoogroups.com
Subject: Re: [firebird-support] Error on Gfix
Hi,
look into Firebird.log – there are more infos about corruptions recognized by gfix
regards,
Karol Bieniaszewski
Sent: Tuesday, September 29, 2015 2:53 PM
Subject: [firebird-support] Error on Gfix
Hi!
I'm using Firebird 2.5.x and the command gfix -v -full returned:
Summary of validation errors
Number of record level errors : 3
Number of database page errors : 1993
What I have to do in order to fix it, without a backup/restore? I read in "Firebird Documentation" that the command gfix -v -full will fix the orphan pages and record level erros, however, every time when i ran "gfix -v -full" is returned the error above.