It is corrupted because Backup fails and can't take metadata with
IBOConsole. always when we have had corruptions there are this kind of
errors (with Firebird). It seems to work, but backup fails or some queries
fails very mysteriously with some situations.

99% working but not working. This happens also that can't take metadata out
of DB. Db (in our customers) never has corruped in a way that everything
stops working (or I can't remember that FB-db on our system ever refuced to
work at all. It always works almost perfectly).

-TP-




_____

From: firebird-support@yahoogroups.com
[mailto:firebird-support@yahoogroups.com] On Behalf Of Helen Borrie
Sent: 11. joulukuuta 2007 10:28
To: firebird-support@yahoogroups.com
Subject: RE: [firebird-support] Can't run GFix



At 06:48 PM 11/12/2007, you wrote:

>I did not run it so I did not see it (the Error message, I'll ask the

dudes,

>wait a Sec :) ).
>
>I remember trying to run it a year back and never got it right.
>
>do we need to take DB offline first (there was GFix command s for that
>also).

You mean the database is online? Then what makes you think it is corrupted?

>
>Because dude on my left thisks he gotr DB in use, or similar, error message

gfix requires exclusive access for some of its functions. Database repair is
one of them.

>
>I suggest that, if this is this difficult (Gfix don't give too much help,

in

>case of error and gfix /? don't give exact examples how to use it), could
>some make small GUI frontend to do all this for us.

Why don't you study the gfix section of the IB 6 Operations Guide? You can
google for OpGuide.pdf.

Also read this How-to:
http://www.ibphoeni
<http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_db_corr>
x.com/main.nfs?a=ibphoenix&page=ibp_db_corr

>btw... any ideas where to look, because this particular DB has corrupted
>couple of times at very short period of time.

How do you know it is corrupted? (Looking for error messages here, possibly
firebird.log messages too).

>Is it possible that db gets
>corrupted by incoming selects/updates/inserts while Backup is runnign (gpak
>if I recall)...

The program is gbak. No, a DB can't get corrupted by incoming
selects/updates/insert during a backup. It can, however, get corrupted by
running a gbak -r[eplace_database] (destructive restore) and allowing users
to log in before it completes.

You have to do a better job with your problem description. Tell us what OS
the database is running on. Tell us what error messages you have seen that
make you think the database is corrupted. And, for heaven's sake, if the DB
really is corrupted, don't try to use it!

./heLen






[Non-text portions of this message have been removed]