I was using the following to which tranactions were still hanging out there.
C:\EDSS\PRO-TECH+\Source>FSQL PRODATA.FDB
SQL> show transactions;
Transaction - oldest = 36516
Transaction - oldest active = 36517
Transaction - oldest snapshot = 36517
Transaction - Next = 36529
Live transaction and HUNG TRANSACTION HERE HERE (n,n,n,n,etc)
The example above is clean database.


What will gstat -h show me? here's a good database stats for reference not the database stats where I got the issue to occur. I am not a point where I can recreate the issue due to time constraints.
Flags 0
Checksum 12345
Generation 36535
Page size 8192
ODS version 10.1
Oldest transaction 36516
Oldest active 36517
Oldest snapshot 36517
Next transaction 36529
Bumped transaction 1
Sequence number 0
Next attachment ID 134
Implementation ID 16
Shadow count 0
Page buffers 0
Next header page 0
Database dialect 3
Creation date Feb 17, 2011 7:27:41
Attributes force write

Variable header data:
Sweep interval: 20000

--- In firebird-support@yahoogroups.com, Thomas Steinmaurer <ts@...> wrote:
>
> >> If I look at the log at this time before firebird is restarted, the log>appears to be ok. When I restart firebird, the log shows the>inconsistency database corruption error. If I look at the transactions>with FSQL, it indeed shows many transaction out there where it only>showed the end users log in transaction to begin with.
> >
> > The log also said something about to many save points.
>
> Might be the result of calling commit/rollback retaining too often. Any
> chance that you are doing a commit/rollback yourself or by using some
> kind of auto commit mode in your application?
>
> How does gstat -h look like?
>
>
> --
> With regards,
>
> Thomas Steinmaurer
> Upscene Productions
> http://www.upscene.com
> http://blog.upscene.com/thomas/
>
> Download LogManager Series, FB TraceManager today!
> Continuous Database Monitoring Solutions supporting
> Firebird, InterBase, Advantage Database, MS SQL Server
> and NexusDB!
>