GWCHECK on individual user dbs works, but I'm concerned about the number
of these errors. Could this be a symptom of something larger? We have
tried recreating NGWGUARD but the problem still persists.
Any thoughts or directions would be greatly appreciated.
-- Geoff
Would it make sense to take the POA offline and rebuild the NGWGUARD and
post office databases? Also, would it make sense to clear out all
directories that get created automatically and let them get recreated as
the POA comes back up?
I'm looking for some sort of more comprehensive process for scrubbing
the databases. If anyone has got ideas, I'm all ears.
The number of [C022] errors has dropped significantly. We are not seeing
any in the current active POA logs, which is a welcome state. We were
getting a "duplicate request is running" error when running GWCHECK on a
specific user, so we followed TID 10077790 and deleted the NGWCHECK.DB
file. It recreated automatically upon running GWCHECK again.
Also, we have used the procedure in TID 10081351 to drop users from the
NGWGUARD database. This seems to work, but there has been at least 1
user that reported some information missing.
What I'm looking for is some sort of confirmation that what we've done
to this point is appropriate and could indeed reduce the amount of
[C022} errors. Does it make sense that there could have been bad entries
in NGWGUARD that could have caused the significant number of [C022]
errors? Is there anything else we should be exploring to make sure this
doesn't happen again?
Thanks in advance for any additional information.
-- Geoff
--
Danita
I don't know if there is any connection between the drop in errors and
the process of dropping user databases from the guardian database. I
wonder if there was a problem with the guardian database, and by
dropping problem users it fixed the issues with the guardian database.
Is this a possibility? I can see a correlation between the steps we took
and the reduction in the number of errors, but I'm trying to find the
cause so we can head off these errors in the future.
> I don't know if there is any connection between the drop in errors and the
> process of dropping user databases from the guardian database.
While unlikely, anything is possible I guess. I'm speculating here that
something hardware-wise happened (transport, IO, whatever) that caused
massive corruption, and it was just a matter of getting it all eventually
cleaned out. Occasional C022 errors are not that uncommon, and often the
POA just handles them itself without a lot of fanfare. It's when you get a
lot of them that you realize something's up. I'm not sure with the amount
of information we have though that we can really know what triggered this.
--
Danita
Novell Knowledge Partner
Time to upgrade to GW8!
http://www.caledonia.net/gw8upg.html
Thanks to all for their feedback and support info. As always, these
message forums are a huge help!
-- Geoff
> We have addressed all of these issues, and have not had
> any significant errors since.
>
> Thanks to all for their feedback and support info. As always, these
> message forums are a huge help!
I'm happy that the culprit was eventually located :)