Re: [firebird-support] Re: Error on Gfix

2015-10-01 Thread hv...@users.sourceforge.net [firebird-support]
> ---In firebird-support@yahoogroups.com,  wrote :
 > > Hi Vlad, thank for your e-mail!
 > 
 > I understood what you said, however, in the link 
 > http://www.firebirdsql.org/manual/gfix-dbverify.html 
 > http://www.firebirdsql.org/manual/gfix-dbverify.html I got the following 
 > information:
 > 
 > 
 > Full Validation
 > 
 > By default, validation works at page level. If no need to go deeper and 
 > validate at the record level as well, the command to do this is:
 > 
 > gfix -v[alidate] -full database_name
 > 
 > using this option will validate, report and update at both page and record 
 > level. Any corrupted structures etc will be fixed.
 > 
 > 
 > With the text above, I understood that the command gfix -v -full would fix 
 > both orphan page and record level error.
 > 
 > Is the text above wrong? 

  Yes, it is poorly worded and thus not correct. Note, validation process was 
always poorly documented, unfortunately.

A bit more info :
a) orphan record versions not fixed in any case, they just stay in database
b) hard corrupted records could be fixed by marking as "damaged" but only if 
-mend was specified.
  Such records stay in database and skipped by the engine.
c) orphan pages are fixed if and only if there was no other errors detected and 
-full was specified

Regards,
Vlad






[firebird-support] Re: Error on Gfix

2015-09-30 Thread hv...@users.sourceforge.net [firebird-support]
> ---In firebird-support@yahoogroups.com,  wrote :
 > > 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.

  gfix will correct orphan pages if and only if there were no other errors. 
Strongly speaking, "orphan pages"
is not error - in the sense that it not affect database operations. So, there 
is no strong need to fix it ASAP.


Regards,
Vlad

PS In fb3 we divided all inconsistencies detectable by validation (gfix) by 
"errors" and "warnings". 
All kind of "warnings" are not affect correctness of database operation






Re: [firebird-support] Re: Error on Gfix

2015-09-30 Thread Jeferson Sisto jsis...@gmail.com [firebird-support]
Hi Vlad, thank for your e-mail!

I understood what you said, however, in the link
http://www.firebirdsql.org/manual/gfix-dbverify.html I got the following
information:


Full Validation

By default, validation works at page level. If no need to go deeper and
validate at the record level as well, the command to do this is:

gfix -v[alidate] -full database_name

using this option will validate, report and update at both page and record
level. Any corrupted structures etc will be fixed.


With the text above, I understood that the command gfix -v -full would fix
both orphan page and record level error.

Is the text above wrong?


Thank you.

*Jeferson Sisto*
+55 (17) 98827-6685 (Oi - WhatsApp)
jsis...@gmail.com
jsis...@yahoo.com.br

2015-09-30 5:46 GMT-03:00 hv...@users.sourceforge.net [firebird-support] <
firebird-support@yahoogroups.com>:

>
>
> > ---In firebird-support@yahoogroups.com,  wrote :
> >
> > 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.
>
>   gfix will correct orphan pages if and only if there were no other
> errors. Strongly speaking, "orphan pages"
> is not error - in the sense that it not affect database operations. So,
> there is no strong need to fix it ASAP.
>
>
> Regards,
> Vlad
>
> PS In fb3 we divided all inconsistencies detectable by validation (gfix)
> by "errors" and "warnings".
> All kind of "warnings" are not affect correctness of database operation
>
> 
>