Subject Re: [firebird-support] Re: Strange problem - database becomes unresponsive
Author Terry Johnson
Found the problem. On the same server another app running a separate
firebird database was leaking connections. Eventually when it got to 60
connections no more would be allocated, and it would just stall. Would
have been nice to terminate more gracefully, but now we know. Very
frustrating trying to find a bug in bug-free code though. Thanks for
your advice on dealing with corruption - we had this recently too.

Terry

tractaylor wrote:

>Hi Terry
>
>I had this problem a few weeks ago. My server would just hang on
>this one database. What I ended up finding is the database had
>become corrupt. I used the gfix stuff to validate and then try to
>fix the problem.
>
>I used the following commands and it seem to fix it.
>
>1) gfix -v -full YOUR_DATABASE_NAME.gdb //--this validates the
>database. If this says you have errors, go to step 2
>
>2) gfix -mend -full -ignore YOUR_DATABASE_NAME.gdb //--this is to fix
>any errors.
>
>3) gfix -v -full YOUR_DATABASE_NAME.gdb //-- run this again to see if
>any errors still exists. If there are still errors do Step 4
>
>4) gbak -backup -v -ignore YOUR_DATABASE_NAME.gdb
>YOUR_DATABASE_BACKUP.gbk. If this hangs, try the following command -
>gbak -backup -v -ignore -garbage YOUR_DATABASE_NAME.gdb
>YOUR_DATABASE_BACKUP.gbk
>
>5) Then restore it with the folling command -- gbak -replace -v
>YOUR_DATABASE_NAME.gbk YOUR_DATABASE_BACKUP.gdb
>
>
>This process helped me. Hopefully this helps you too. If it were me
>I would make some kind of backup to the file just make sure you will
>have a copy, just incase something goes wrong. I tried this same
>process on another database of ours, and I had to do the process
>twice to fix all the errors.
>
>Trac
>
>
>--- In firebird-support@yahoogroups.com, Terry Johnson <terry@s...>
>wrote:
>
>
>>I've been running a fairly simple database with FB 1.5 on Linux for
>>
>>
>some
>
>
>>time. During this time, no major changes to the DB, and it's been
>>consistently running well. Until last week. Now the DB runs for a
>>
>>
>bit,
>
>
>>and seems ok during this time, but within a short period it just
>>
>>
>hangs.
>
>
>>The firebird process can't be stopped in a normal manner, and
>>
>>
>connection
>
>
>>attempts with ISQL just hang too. We've been running Super Server
>>
>>
>and
>
>
>>tried changing to Classic, but it still behaves the same way. This
>>
>>
>DB is
>
>
>>under almost zero load, btw.
>>
>>The DB consists of about 15 tables, with each table keyed on a
>>
>>
>couple of
>
>
>>integers. There are a couple of triggers that only fire on deletes.
>>
>>
>A
>
>
>>few foreign key constraints. And the whole DB is only 70MB (mostly
>>graphic blobs). It is quite simple and undemanding. Probably the
>>
>>
>only
>
>
>>odd thing is the use of Varchar fields with CHARSET NONE for the
>>
>>
>storage
>
>
>>of some utf-8 encoded strings (but even there, there are none being
>>
>>
>used
>
>
>>as keys). The database seems to not be corrupt.
>>
>>Is there any way to find out what is going on?
>>
>>Terry
>>
>>
>
>
>
>
>
>Yahoo! Groups Links
>
>
>
>
>
>
>
>
>



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