--- In firebird-support@yahoogroups.com, Milan Babuskov <albis@e...>

> At the end, prehaps you are simply issuing some "heavy" query that

hogs

> the db. You could make a log file (simple txt file) where you would
> write every sql before executing it, and when the problem happens,

just

> read the last query from that file.

I don't know PHP but in my practice this is most often reason for
such a help calls. Or some query encountered deadly garbaged table
(millions of records were updated or deleted, even worse - one record
was updated million times). Or transaction of this process started
automatic sweep which collects large amount of garbage in entire
database. BTW, killing processes which perform garbage collection is
one of the reasons of database corruptions.

Best regards,
Alexander.