Regarding OEM GC getting stuck

[fasi rehman]

Hi folks,

 

Hope u are doing good.

I need a favor from you.

There was an issue in one of our databases recently

The OEM 10g Grid control was stuck & restarting the listener dint resolve it.

Atlast the server was rebooted & it resolved the issue.

Can you let me know if any one came across this issue anytime.

I tried to search in metalink but dint get any clues on it.

iam guessing high CPU on the node as the reason.

This happend few weeks back & so not sure about the details.

Looking forward for your reply.

 

Regards,

Fasi

[ddf]

Comments embedded.

On May 24, 5:59 pm, fasi rehman <fasi_...@yahoo.co.in> wrote:
> Hi folks,
>
> Hope u are doing good.
> I need a favor from you.
> There was an issue in one of our databases recently
> The OEM 10g Grid control was stuck & restarting the listener dint resolve it.

I wouldn't expect it to, honestly.

> Atlast the server was rebooted & it resolved the issue.

The reboot restarted the GC agent which corrected the issue you had.
Many times the agent is the reason GC is 'stuck' and restarting the
agent clears any communication problems.

> Can you let me know if any one came across this issue anytime.
> I tried to search in metalink but dint get any clues on it.
> iam guessing high CPU on the node as the reason.
> This happend few weeks back & so not sure about the details.
> Looking forward for your reply.
>
> Regards,
> Fasi

David Fitzjarrell

[fasi rehman]

Can u decribe more about agent?

Iam new to RAC.

which agent are u speaking over here ?

 

---

From: ddf <ora...@msn.com>
To: Oracle in World <oracle-...@googlegroups.com>
Sent: Wed, 25 May, 2011 10:49:29 AM
Subject: Re: Regarding OEM GC getting stuck

[ddf]

On May 27, 10:37 am, fasi rehman <fasi_...@yahoo.co.in> wrote:
> Can u decribe more about agent?
> Iam new to RAC.
> which agent are u speaking over here ?
>
>  
>

Please do not top-post.

Grid control uses a repository and grid control agents installed on
the monitored nodes; these agents 'talk' to the grid control service
on the repository server, sending requested data to the repository.
This configuration can be used on RAC and non-RAC installations.
Apparently the agent on the database server failed to communicate with
the repository; rebooting the server ( a rather drastic measure, if
you ask me) restarted all of your services, including the grid control
agent, and when the agent was started it established a connection with
the repository and you regained functionality.

All of this information, and more, is available at http://tahiti.oracle.com
(the online documentation).


David Fitzjarrell

[fasi rehman]

DO you have any script to check the OEM health status ?

---

From: ddf <ora...@msn.com>
To: Oracle in World <oracle-...@googlegroups.com>

Sent: Fri, 27 May, 2011 12:52:11 PM

Subject: Re: Regarding OEM GC getting stuck

[ddf]

On May 27, 10:57 am, fasi rehman <fasi_...@yahoo.co.in> wrote:
> DO you have any script to check the OEM health status ?
>
> ________________________________

> From: ddf <orat...@msn.com>

> To: Oracle in World <oracle-...@googlegroups.com>
> Sent: Fri, 27 May, 2011 12:52:11 PM
> Subject: Re: Regarding OEM GC getting stuck
>
> On May 27, 10:37 am, fasi rehman <fasi_...@yahoo.co.in> wrote:
>
> > Can u decribe more about agent?
> > Iam new to RAC.
> > which agent are u speaking over here ?
>
> >  
>
> Please do not top-post.
>
> Grid control uses a repository and grid control agents installed on
> the monitored nodes; these agents 'talk' to the grid control service
> on the repository server, sending requested data to the repository.
> This configuration can be used on RAC and non-RAC  installations.
> Apparently the agent on the database server failed to communicate with
> the repository; rebooting the server ( a rather drastic measure, if
> you ask me) restarted all of your services, including the grid control
> agent, and when the agent was started it established a connection with
> the repository and you regained functionality.
>

> All of this information, and more, is available athttp://tahiti.oracle.com

> (the online documentation).
>
> David Fitzjarrell

And again you top post; I'll answer this and should you top-post again
I will not respond.

Your health check for OEM, as far as I know, is the proper functioning
of OEM, which you determined was failing. I know of no script to
check the agents within Oracle or OEM; you might try talking with
your sys admin about the server resources and cpu time a normally
running agent consumes, monitor that with a ps -ef command piped to
some filter to return only the information for the grid control agent
process. This requires work on your part to write such a script.


David Fitzjarrell

[fasi rehman]

Iam sorry,what did you mean by top post ?

i dint get u

---

From: ddf <ora...@msn.com>

To: Oracle in World <oracle-...@googlegroups.com>

Sent: Fri, 27 May, 2011 1:05:37 PM

[ddf]

On May 27, 2:18 pm, fasi rehman <fasi_...@yahoo.co.in> wrote:
> Iam sorry,what did you mean by top post ?

> i dint get u <---- THIS is 'top posting'
posting at the TOP of the message rather than at the BOTTOM, as I have
done.

> David Fitzjarrell- Hide quoted text -
>
> - Show quoted text -