The first thing i did before start to analyse the database was to
disconnect all users and make a copy of database.

All error i reported happened when nobody was connect.

The only process that remained alive was 'fb_lock_mgr'.

After some random desperated tries, like 'gfix -mend -full', killing
'fb_lock_mgr', shuting down the server, i was able to make a backup of
the database, so now i am restoring it and it seems it is allright.

Did fb_lock_mgr need to be killed also to avoid this problem?

Regards,

Fabiano.

On Thu, May 15, 2008 at 9:32 AM, Vlad Khorsun
<hvlad@...> wrote:

>> I have a database (FB CS 2.0.4) that was left locked (nbackup -L) for
>> 4 days due to an error in a backup script.
>>
>> In this interval the users used it regularly.
>>
>> ###### Today, it started to show this error:
>>
>> [root@server1 firebird]# gfix -v -full romana.fdb
>> internal gds software consistency check (page in use during flush
>> (210), file: cch.cpp line: 3712)
>>
>> ###### If i try to unlock the database, i get this:
>>
>> [root@server1 firebird]# nbackup -N romana.fdb
>> [
>> PROBLEM ON "end backup".
>> internal gds software consistency check (can't continue after bugcheck)
>> SQLCODE:-902
>> ]
>> Failure: Database error
>> [
>> PROBLEM ON "rollback transaction".
>> internal gds software consistency check (can't continue after bugcheck)
>> SQLCODE:-902
>> ]
>> Failure: Database error
>>
>> ###### If i try to backup the database, i get this:
>>
>> gbak:readied database romana.fdb for backup
>> gbak:creating file /var/tmp/backup
>> gbak:starting transaction
>> gbak: ERROR:internal gds software consistency check (can't continue
>> after bugcheck)
>> gbak:Exiting before completion due to errors
>> gbak: ERROR:internal gds software consistency check (can't continue
>> after bugcheck)
>>
>> ###### Here is a sample of some errors i found in the log:
>>
>> server1.xxx.com.br Thu May 15 07:27:49 2008
>> Database: romana
>> internal gds software consistency check (decompression overran
>> buffer (179), file: sqz.cpp line: 223)
>>
>>
>> I neve saw this problem. Do someone have an advice on how should i proceed?
>
> Once you got "can't continue after bugcheck" message all you can do with database is
> shutdown (i.e. disconnect all users). When you ensure nobody is connected make copy
> of .fdb and .delta files and try to unlock database again.
>
> Also you may make files copy before disconnect. It is not guaranteed that you'll get correct
> image of .delta file, but it will not harm. I heard once about disappeared .delta file after full
> disconnect. Don't know if it was true but...
>
> Regards,
> Vlad
>
> ------------------------------------
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> Visit http://www.firebirdsql.org and click the Resources item
> on the main (top) menu. Try Knowledgebase and FAQ links !
>
> Also search the knowledgebases at http://www.ibphoenix.com
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> Yahoo! Groups Links
>
>
>
>