Subject | RE: [firebird-support] Can't run GFix |
---|---|
Author | Helen Borrie |
Post date | 2007-12-11T08:28:25Z |
At 06:48 PM 11/12/2007, you wrote:
Also read this How-to:
http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_db_corr
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
>I did not run it so I did not see it (the Error message, I'll ask the dudes,You mean the database is online? Then what makes you think it is corrupted?
>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).
>gfix requires exclusive access for some of its functions. Database repair is one of them.
>Because dude on my left thisks he gotr DB in use, or similar, error message
>Why don't you study the gfix section of the IB 6 Operations Guide? You can google for OpGuide.pdf.
>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.
Also read this How-to:
http://www.ibphoenix.com/main.nfs?a=ibphoenix&page=ibp_db_corr
>btw... any ideas where to look, because this particular DB has corruptedHow do you know it is corrupted? (Looking for error messages here, possibly firebird.log messages too).
>couple of times at very short period of time.
>Is it possible that db getsThe 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.
>corrupted by incoming selects/updates/inserts while Backup is runnign (gpak
>if I recall)...
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