Subject | Committing forgotten transactions? |
---|---|
Author | Matthias Hanft |
Post date | 2009-04-29T17:13:54Z |
Hello,
I'm using some FB 2.0.3 databases on a Linux server. The clients
were (up to now) only self-programmed Delphi software, and because
I ever had kept an eye on closing transactions, I always had good
"gstat -h" like this:
Oldest transaction 4180420
Oldest active 4180421
Oldest snapshot 4180421
Next transaction 4180422
Perfect, isn't it? But now, I do some experiments with PHP as client,
and it seems that there has been some unclosed transaction during my
testing; "gstat -h" now shows like this:
Oldest transaction 4180420
Oldest active 4180421
Oldest snapshot 4180421
Next transaction 4180538
The 3 "Oldest" fields remain the same, but the "Next" field increases
with every new database access. I think it will be _really_bad_ if I
leave the database alone in that condition?!
I have already tried "gfix -commit all": with no error message, but with
no effect either!
Is there any command to revert the database into the "good condition" it
had before? Hopefully without shutting it down and/or backup/restore?
Since I will continue to develop some PHP scripts, I'm pretty sure this
problem will arise more often from now on...
Thank you,
Matt
I'm using some FB 2.0.3 databases on a Linux server. The clients
were (up to now) only self-programmed Delphi software, and because
I ever had kept an eye on closing transactions, I always had good
"gstat -h" like this:
Oldest transaction 4180420
Oldest active 4180421
Oldest snapshot 4180421
Next transaction 4180422
Perfect, isn't it? But now, I do some experiments with PHP as client,
and it seems that there has been some unclosed transaction during my
testing; "gstat -h" now shows like this:
Oldest transaction 4180420
Oldest active 4180421
Oldest snapshot 4180421
Next transaction 4180538
The 3 "Oldest" fields remain the same, but the "Next" field increases
with every new database access. I think it will be _really_bad_ if I
leave the database alone in that condition?!
I have already tried "gfix -commit all": with no error message, but with
no effect either!
Is there any command to revert the database into the "good condition" it
had before? Hopefully without shutting it down and/or backup/restore?
Since I will continue to develop some PHP scripts, I'm pretty sure this
problem will arise more often from now on...
Thank you,
Matt