1. Now, I am loster than before... :-)

2. There is no gargage collection from 04:00 through 22:00. At midnight, a cron job does backup and restore every day.

3. No. :-) Maybe, I wish firebird .conf would have an option that after one transaction were open for a long time, i.g. 15 minutes, it would be automatically commited or rolled back... When mon$ transactions are commited?

4. I have just made gstat, commit, select mon$, commit and gstat again, and the numbers are:

Mon Nov 10 10:39:34 BRST 2008

Oldest transaction 325
Oldest active 326
Oldest snapshot 326
Next transaction 21455
Attributes force write, no reserve
Sweep interval: 0

 

Select * From MON$TRANSACTIONS Where Mon$Transaction_ID = 326;
MON$TRANSACTION_ID = 326
MON$ATTACHMENT_ID = 8
MON$STATE = 1
MON$TIMESTAMP = '10.11.2008, 07:50:10.469'
MON$TOP_TRANSACTION = 326
MON$OLDEST_TRANSACTION = 234
MON$OLDEST_ACTIVE = 235
MON$ISOLATION_MODE = 2
MON$LOCK_TIMEOUT = -1
MON$READ_ONLY = 0
MON$AUTO_COMMIT = 0
MON$AUTO_UNDO = 1
MON$STAT_ID = 985
Select * From MON$STATEMENTS Where Mon$Transaction_ID = 326;
Nothing...

Mon Nov 10 10:42:49 BRST 2008
ODS version 11.1
Oldest transaction 325
Oldest active 326
Oldest snapshot 326
Attributes force write, no reserve
Sweep interval: 0

5. Why MON$TRANSACTIONS shows information about oat 326 and MON$STATEMENTS shows nothing?

 

Thanks,

 

Roberto Carlos

 


Em 01:41, Helen Borrie   escreveu:

At 12:55 PM 10/11/2008, you wrote:

>I am working on a Debian Linux, Etch, AMD 64 bits.
>FB SS 2.1.1.
>
>After all users have closed all systems (22:00), gstat says that my oldest active transaction (oat) is 191 and mon$ tables say that same oat is 21226. gstat reported as 191 during the whole day, but I could not find the command which generated this transaction.
>
>1. Which oat number is correct?

Probably both of them...

>2. I can not find transaction 191 via selecting mon$ tables. What select should I use for discovering the command (DDL, DML, DCL, TCL or DQL) which generated my last real oat (191 or 21226)?

Between the time when gstat stopped reading the header file and when the mon$ transaction started, the garbage collection thread committed and the transaction inventory page was updated. If you do another gstat after the mon$ transaction commits, you should see some nice clean numbers.

>3. FB 2.1.1 transactions have "time out"?

You have the option to set a timeout for WAIT transactions. I don't know whether this was the answer you wanted...

./heLen







[Non-text portions of this message have been removed]