On Wed, Jan 15, 2014 at 4:42 PM, rmcgi...@oceris.com wrote:
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
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
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
Are you sure gfix hangs? Maybe is a hdd slowdown in the process.
We had this same issue. Gbak does not clean all the mess on only one of our
clients.
The sollution is run a gfix and wait.
Em 07/01/2014 18:22, rmcgi...@oceris.com escreveu:
This is Classic, so yes, automatic sweep is disabled.
Hi Ryan,
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).
You are wrong. Gbak does not do sweep, it runs snapshot transaction and
reads all records in all tables - and, with some
I forget to say that you must disconnect all clients before run gfix
Em 07/01/2014 18:35, Alexey Kovyazin a...@ib-aid.com escreveu:
Hi Ryan,
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
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 that
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).
