Hi,
Did you started sweep manually? Or you wait for automatic sweep?
Regards,
Karol Bieniaszewski
- Reply message -
Od: soprano...@yahoo.com.ar
Do:
Temat: [firebird-support] Re: I dont know why sweep is not doing clean
Data: śr., mar 19, 2014 23:00
Thanks for all answers!
I'm
Thanks for all answers!
I'm still with this problem, I would like to revisit the issue.
I've checked transactions in mon$ tables and I can't find the transaction in
order to kill it.
For example, right now I have:
Oldest transaction 963037
Oldest active transaction 1552161
Oldest snapshot 1552161
On Fri, Dec 6, 2013 at 2:44 PM, wrote:
> Hi Vlad, gstat -h result:
>
> Oldest transaction 371932
>
> Oldest active1906983
> Oldest snapshot 1906983
> Next transaction 2696106
>
>
Only record versions created before transaction three hu
Hello, sopranoeli!
Friday, December 6, 2013, 11:44:31 PM, you wrote:
syca> I do not mind the difference between "Oldest active" and "Next
syca> transaction".
why? you have some transaction (not read only read_committed) running for 2
days.
Why auto-sweep is not running - this is another story
Hi Vlad, gstat -h result:
Database header page information:
Flags 0
Checksum12345
Generation 2834816
Page size 8192
ODS version 11.2
Oldest transaction 371932
Ol
> Thank you for your help. I dont understand why sweep is not doing clean.
> I use Super Server 2.5. I try also to run sweep manually and it ends
> immediatelly without doing clean.
Make sure your database is not shutdown. Show us gstat -h output.
Regards,
Vlad
PS And consider to remove "r