Subject | Rolling back old transactions |
---|---|
Author | Rick Debay |
Post date | 2005-04-19T15:04:08Z |
We had some long running transactions that we were unable to commit
because the client was rebooted.
Looking at the statistics, there is a gap and no one is attached.
Gfix -l doesn't return anything. Sweep doesn't change anything. We
ended up restarting the server. Is there any way to close the
transaction gap besides bouncing the server?
Database header page information:
Flags 0
Checksum 12345
Generation 284039
Page size 8192
ODS version 10.1
Oldest transaction 284008
Oldest active 284009
Oldest snapshot 284009
Next transaction 284038
Bumped transaction 1
Sequence number 0
Next attachment ID 0
Implementation ID 19
Shadow count 0
Page buffers 0
Next header page 0
Database dialect 3
Creation date Apr 18, 2005 12:12:29
because the client was rebooted.
Looking at the statistics, there is a gap and no one is attached.
Gfix -l doesn't return anything. Sweep doesn't change anything. We
ended up restarting the server. Is there any way to close the
transaction gap besides bouncing the server?
Database header page information:
Flags 0
Checksum 12345
Generation 284039
Page size 8192
ODS version 10.1
Oldest transaction 284008
Oldest active 284009
Oldest snapshot 284009
Next transaction 284038
Bumped transaction 1
Sequence number 0
Next attachment ID 0
Implementation ID 19
Shadow count 0
Page buffers 0
Next header page 0
Database dialect 3
Creation date Apr 18, 2005 12:12:29