Hi,

At November 24, 2003, 08:45, Martin Dew wrote:

> I cannot replicate or find how my apps are doing this but on occasions I
> have a header statistics from the database as follows;

> OT 566738
> OAT 566739
> NT 940551
> OS 564916

> Even if I log all applications out the transactions do not catch up with
> themselves.. So my question is I am seriously considering moving to FB
> 1.5 once it is in full release, is there a way that I can type in the
> oat and get rid of the transaction so that the Transactions all catch up
> ? I have tried with interbase to use the gfix -commit [trans number] and
> it just says that the transaction is active, even if I have no
> connections to interbase.

It could be a transaction in limbo! Because, what are those
statistics after a backup/restore? If the OAT is still the same, have
you tried gfix -rollback (instead of gfix -commit)?

> Wouldn't it be nice to have a command that you can run that just resets
> all transactions and memory allocations, so if you know that no-one on a
> site is connected and doing anything to your database you can just say
> right, lets set IB/FB as though we have done a backup and restore and
> start from the beginning again..

Have you tried gfix -sweep (it forces garbage collection)?
What is your sweep interval?
Do you have Forced Writes ON or OFF?

--
Best regards,
Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.filopto.com)