Moneycontrol Brokerage Recos

Tuesday, September 25, 2012

Oracle 11g R2 EM Agent Unreachable

Usually Agent Unreachable status shown when agent is not running so first try to start the agent and wait for sometime that to be reflected in OEM or if  you have changed your hostname/IP or timezone of your oracle server then follow up the following steps.

1. emctl resetTZ agent
Oracle Enterprise Manager 11g Database Control Release 11.2.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
Updating E:\app\Administrator\product\11.2.0\dbhome_1/rajkumar-pc_orcl/sysman/config/
emd.properties...
Successfully updated E:\app\Administrator\product\11.2.0\dbhome_1/rajkumar-pc_orcl/sy
sman/config/emd.properties.

2. Login as the em repository user and run the  script:
exec mgmt_target.set_agent_tzrgn('rajkumar-pc:3938','America/New_York')
and commit the changes
SQL> exec mgmt_target.set_agent_tzrgn('rajkumar-pc:3938','America/New_York')
SQL> commit

3. emctl status dbconsole
Oracle Enterprise Manager 11g Database Control Release 11.2.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
EM Daemon is not running.
------------------------------------------------------------------
Logs are generated in directory E:\app\Administrator\product\11.2.0\dbhome_1/COL-OR
A01_orcl/sysman/log

4. emctl start dbconsole
Oracle Enterprise Manager 11g Database Control Release 11.2.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation.  All rights reserved.
Starting Oracle Enterprise Manager 11g Database Control ...The OracleDBConsoleor
cl service is starting...................
The OracleDBConsoleorcl service was started successfully.

Enjoy.............................

5 comments:

  1. Thanks ! this post is a great help to me.. i was all over the internet to figure out this problem.
    I really appreciate your work. Stay blessed :-)

    ReplyDelete
    Replies
    1. You're welcome and thanks for your valuable feedback.

      Delete
  2. or try simple connect to other node via ssh ($ssh rac2)
    and tipe
    $emctl status dbconsole
    if the demon is not already started
    execute
    $emctl start dbconsole
    and make it for all nodes in your cluster

    then check agein status of agents

    ReplyDelete