Re: 12c agent problem
- From: David Barbour <david.barbour1@xxxxxxxxx>
- To: Andrew Kerber <andrew.kerber@xxxxxxxxx>
- Date: Wed, 18 Sep 2013 13:31:47 -0500
Andrew,
I don't have any experience with 12c Grid Control, but with 11g at least,
I've run into a similar situation and had to delete the agent from the grid
repository database.
select target_name from sysman.mgmt_targets where target_type=âoracle_emdâ;
If an agent shows up for that server, delete it with
exec mgmt_admin.cleanup_agent(â<host>:<port>â²);
On Wed, Sep 18, 2013 at 11:18 AM, Andrew Kerber <andrew.kerber@xxxxxxxxx>wrote:
> I have run into a problem with the 12c agent. Something happened with the
> file system, and most of the agent directories have been corrupted. I
> installed a new agent, but when it went in it showed as blocked.
> I went through and removed the entire target from grid control, then
> unblocked the agent. However, the newly installed agent doesnt show up
> under configure auto discovery.
>
> So, what I need to do (I think) is remove the record of the old agent from
> the oracle inventory, and force the new agent to show up under auto
> discovery.. Does anyone have any idea how to do that? the old agent
> installation directories are gone, but the information is still in the
> inventory. I need to figure out how to clean it out of the inventory, and
> also force the new agent to show under auto discovery.
>
> --
> Andrew W. Kerber
>
> 'If at first you dont succeed, dont take up skydiving.'
>
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
