Subject AW: [firebird-support] firebird 2.1 questions
Author Olaf Kluge
Hi,

has no one the same problem with the monitoring tables?


Hello,

I have installed firebird 2.1 this weekend, there was a firebird 2.0
installation before.

After the restore I have executed the metadata update.

We have transaction problems with one application connected to our firebird
database. It was developed by an other developer. All other applications are
clean, but the one developed dll does not commit the transactions.

Now I can see the transaction problem in the monitoring tables.

But:
After I have restored the database, the follow sql statement returns a true
result (details of the last saved transaction):

select
md.mon$oldest_active,
mt.mon$transaction_id,
ma.mon$remote_address,
ma.mon$remote_process,
ma.mon$attachment_name,
ms.mon$timestamp,
ms.mon$sql_text
from mon$database md
join mon$transactions mt on mt.mon$transaction_id=md.mon$oldest_active
left join mon$attachments ma on ma.mon$attachment_id=mt.mon$attachment_id
left join mon$statements ms on ms.mon$transaction_id=md.mon$oldest_active

But after a few hours, the statement returns a blank result. Is the last
saved transaction in the database-monitoring-table not present in
transactions-monitoring-table? (md.mon$oldest_active =
mt.mon$transaction_id) What is wrong?

This code does work: (returns all transactions)

select
mt.mon$transaction_id,
ma.mon$remote_address,
ma.mon$remote_process,
ma.mon$attachment_name,
ms.mon$timestamp,
ms.mon$sql_text
from mon$transactions mt
left join mon$attachments ma on ma.mon$attachment_id=mt.mon$attachment_id
left join mon$statements ms on ms.mon$transaction_id=mt.mon$attachment_id

My second question, should something not work tomorrow, can I easily
fallback to the old firebird version? I have made the metadata update, is
this a problem to fallback?

A big Thanks to all the firebird developers and newsgroup members for the
good work, and thanks for your help.

With best regards.

Olaf Kluge