Hello Vlad,

>> We have moved to FB 2.1 64 bits on windows 3 weeks ago, and we are
>> experiencing a strange issue, the oldest transations remains low,
>> while the next transaction keeps growing, and the database sweep does
>> not fix the issue. The database is onlyne 24x7, and it use to work
>> fine under FB 2.0
>> Also the Bumped transaction = 1 never dissappears, even after backup
>> and restare.
>>
>> The following is the copy from Statistics:
>>
>> Flags 0
>> Checksum 12345
>> Generation 14501
>> Page size 16384
>> ODS version 11.1
>> Oldest transaction 1506
>> Oldest active 1507
>> Oldest snapshot 1507
>
> Use MON$xxx tables and search for attachment of tx 1507. Look at application which
> holds it and fix it to not hold transaction too long.

The application name is a bit of a problem if the application does not
use the Firebird client library from 2.1, e.g. when using Jaybird.

Is there probably a way how Roman could make the application name
available in the monitoring tables?

Possibly, the same applies to the .NET data provider as well.

Thanks.


--
Best Regards,
Thomas Steinmaurer
LogManager Series - Logging/Auditing Suites supporting
InterBase, Firebird, Advantage Database, MS SQL Server and
NexusDB V2
Upscene Productions
http://www.upscene.com