Re: [firebird-support] Error on Gfix
On Tue, Sep 29, 2015 at 4:50 PM, Jeferson Sisto jsis...@gmail.com [firebird-support]wrote: > > > 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... > Orphan pages are just lost space. If you've only got three or four (at 16KB per page) in a 20 GB database by all means ignore it. Orphan record versions are the same, but even less significant. Both those errors can occur when the database shuts down without writing out its cache completely. They're totally benign. For those who care deeply, here's the situation. Firebird uses careful write to maintain on-disk consistency. That translates to writing the thing pointed to before the pointer when creating objects and removing the pointer before the object when releasing objects. Consider the case of allocating a new page to a table. 1) the page number is released from the free page list, so it can't be allocated twice and the free page list is written. 2) the page is formatted to look like a data page for that table and written to the database. 3) the page number is entered into the list of page that belong to the table and that list is written to the database. If the database stops between 1 and 2 or 2 and 3, that page is neither free nor associated with a table, index, or internal structure. But it doesn't cause any problems either. It just sits there, wasting a small amount of space until gfix removes it or the database is restored from a backup. Similarly when Firebird garbage collects an old record version, it first clears the pointer to the version in the next newer version, then clears the entry on the data page that locates the actual record. Last, it removes index entries that are no longer valid. If there's a failure between clearing the record pointer and the entry on the data page, that record version sits there until gfix removes it or the database is restored. Good luck, Ann
RE: [firebird-support] Error on Gfix
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 - n...@csy.co.uk 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... Obrigado. Jeferson Sisto (17) 98827-6685 (Oi - WhatsApp) <mailto:jsis...@gmail.com> jsis...@gmail.com jsis...@yahoo.com.br 2015-09-29 17:37 GMT-03:00 'Neil Pickles' neil.pick...@csy.co.uk [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 From: mailto:firebird-support@yahoogroups.com Sent: Tuesday, September 29, 2015 2:53 PM To: firebird-support@yahoogroups.com 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. Thank you Jeferson Sisto +55 (17) 98827-6685 <tel:%2B55%20%2817%29%2098827-6685> (Oi - WhatsApp) <mailto:jsis...@gmail.com> jsis...@gmail.com jsis...@yahoo.com.br
RE: [firebird-support] Error on Gfix
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 From: mailto:firebird-support@yahoogroups.com Sent: Tuesday, September 29, 2015 2:53 PM To: firebird-support@yahoogroups.com 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. Thank you Jeferson Sisto +55 (17) 98827-6685 (Oi - WhatsApp) <mailto:jsis...@gmail.com> jsis...@gmail.com jsis...@yahoo.com.br
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... Obrigado. *Jeferson Sisto* (17) 98827-6685 (Oi - WhatsApp) jsis...@gmail.com jsis...@yahoo.com.br 2015-09-29 17:37 GMT-03:00 'Neil Pickles' neil.pick...@csy.co.uk [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 > > > > *From:* mailto:firebird-support@yahoogroups.com > <firebird-support@yahoogroups.com> > > *Sent:* Tuesday, September 29, 2015 2:53 PM > > *To:* firebird-support@yahoogroups.com > > *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. > > > > > > Thank you > > > > > > *Jeferson Sisto* > > +55 (17) 98827-6685 (Oi - WhatsApp) > > jsis...@gmail.com > > jsis...@yahoo.com.br > > >
Re: [firebird-support] Error on Gfix
Hi, look into Firebird.log – there are more infos about corruptions recognized by gfix regards, Karol Bieniaszewski From: mailto:firebird-support@yahoogroups.com Sent: Tuesday, September 29, 2015 2:53 PM To: firebird-support@yahoogroups.com 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. Thank you Jeferson Sisto +55 (17) 98827-6685 (Oi - WhatsApp) jsis...@gmail.com jsis...@yahoo.com.br
Re: [firebird-support] Error on Gfix
Hi! I know Firebird.log and its informations... also, this information are very helpful. However, always when we detect a corrupt database, our team run a backup/restore. It can be a problem when a database has 20, 30 GB. I read that gfix can fix orphan pages, and our corrupt is about orphan pages. I ran the command gfix -v -full but I don't if it works because ALWAYS returns the result below. May someone else help us? Obrigado. *Jeferson Sisto* (17) 98827-6685 (Oi - WhatsApp) jsis...@gmail.com jsis...@yahoo.com.br 2015-09-29 15:43 GMT-03:00 liviusliv...@poczta.onet.pl [firebird-support] < firebird-support@yahoogroups.com>: > > > Hi, > > look into Firebird.log – there are more infos about corruptions recognized > by gfix > > > regards, > Karol Bieniaszewski > > *From:* mailto:firebird-support@yahoogroups.com >> *Sent:* Tuesday, September 29, 2015 2:53 PM > *To:* firebird-support@yahoogroups.com > *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. > > > Thank you > > > *Jeferson Sisto* > +55 (17) 98827-6685 (Oi - WhatsApp) > jsis...@gmail.com > jsis...@yahoo.com.br > > >