Re: GridControlAgent on Debian
Date: Wed, 28 Jan 2009 13:41:56 -0600 (CST)
Off the original topic, my case was not the removal of the agent, but the repair of the OMS Repository that the agent may have caused.
In my case, Oracle Support recommended that I run 1700 queries *manually* to aid them. When I pointed out multiple times the multiple fallacies of this approach, I was directed to run the "repvfy" command from the EM Diag kit. The specific command I ran not only erased any trace of what may have caused my initial problem, but it also effectively wiped my metric history (I forget to what extent).
But thanks for the pointers! I'm sure I'll be needing to do that someday...
> if you accidentally added a target and want to remove it clean and
> seamlessly, consider involving "mgmt_admin.cleanup_agent".
> (For details, have a look here:
> This method is especially useful if the agent isn't reachable via network
> any more (or did never exist in this way).