Ok, running the gfix -sweep with everyone logged out did work and only took
about 5 minutes. I believe the issue came from me only trying to run the sweep
one time and a transaction being stuck. I never tried to run sweep AFTER
restarting the services. I also think there was confusion because
Last time I tried it, the gfix process hung and sat at 0% CPU for hours. I had
to terminate it. A backup only takes about 20 minutes, so I figured gfix
should take several hours.
I will try to run it again and get more detailed information to report back
here (with everyone logged out).
>You are wrong. Gbak does not do sweep, it runs snapshot transaction and reads
>all records in all tables - and, with some conditions, it can clear some
>garbage versions.
Ah I see - the documentation simply mentioned something like "garbage
collection maybe done during backup" - now I see
This is Classic, so yes, automatic sweep is disabled. My understanding is that
gbak does a sweep while doing a backup, which happens nightly, so sweep should
be happening then (if I understand it correctly that is). Also, running a
manual sweep hangs indefinitely.
As for the active transac
Using 2.5.2 64 bit on Windows - Super Classic model.
We have a large database around 20 gb that we have backup/restored
successfully several times now via gbak. After the restore, everything is good,
but over time, the transactions awaiting sweep starts to grow and never goes
back to zero.
