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,
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
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
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
Jeferson said:
I already try to do it, but when a connection from a client (another
machine) is ended abnormally (for example, turn off the machine or
disconnect the cable of network), this connection still stay on system
table MON$ATTACHMENT.
Dmitry said:
It's because the connection is still
Hello!
May I use the system table MON$ATTACHMENT in order to get the connected
users in moment?
I already try to do it, but when a connection from a client (another
machine) is ended abnormally (for example, turn off the machine or
disconnect the cable of network), this connection still stay
