OEM Incident: Agent is Unreachable

Posted: April 29, 2016 in Agent Unreachable, OEM12c
Tags: ,

Happy Friday, Students of the Oracle!

This is a quick post because I know it’s Friday and who wants to read lengthy technical writing right before cutting loose from work for two days?

In the past I have bounced the OEM Agent. This stops and starts the whole Agent. I have been getting an alert for the agent on one node of one Exadata Database Server. Along with that, all of the targets on that node are unreachable as well.

  1. I just patched that server last Friday. I had performed an OEM Blackout on the entire server, bounced the cluster for the Grid Patch set, and bounced RAC for the Database Patch set. I then lifted the blackout and went to bed. So my first inclination was to perform another blackout and then cancel it after ten minutes. That has worked for me in the past. No such luck this time.
  2. I logged into the offending node as Oracle. I then changed my environment and navigated to the agent home.
    • $ . oraenv
    • ORACLE_SID = [] ? agnt12c
    • $ cd $ORACLE_HOME
    • oracle@xdt**:/u01/app/oracle/agent/core/12.1.0.4.0 agnt12
  3. Next, I check the status of the agent just like I would on the OEM Server.
    • Oracle Enterprise Manager Cloud Control 12c Release 4
    • $ emctl status agent
      Copyright (c) 1996, 2014 Oracle Corporation. All rights reserved.
      —————————————————————
      Agent is Not Running
    • Hmm. Let’s start the agent.
  4. Start the agent.
    • $ emctl start agent
      Oracle Enterprise Manager Cloud Control 12c Release 4
      Copyright (c) 1996, 2014 Oracle Corporation. All rights reserved.
      Starting agent …………………… started.
  5. Check status again…
    • $ emctl status agent
      Oracle Enterprise Manager Cloud Control 12c Release 4
      Copyright (c) 1996, 2014 Oracle Corporation. All rights reserved.
      —————————————————————Agent is Running and Ready
  6. I then refreshed my OEM–>Summary page. After 30 seconds, all targets on that node are up and running.

Easy Peasy. There is a way to do this inside of OEM but it is restricted in our environment.

Thanks for reading!

Jason Brown

 

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s