EM Configuration issue. $ORACLE_HOME/odprimary_PRIDB not found

by Eric Jenkinson on October 17, 2011

Categories: Grid Control

Tagged: , ,

We noticed that some of our databases monitored in Oracle Enterprise Manager Grid Control were showing a status of Agent Unreachable. When checking the status of the Agent on the server the following error was returned.

[oracle@odprimary bin]$ emctl status agent
EM Configuration issue. /u01/app/oracle/product/11.2.0/odprimary_PRIDB not found.
[oracle@odprimary bin]$

A common cause for this error is changing the hostname of the server in either /etc/hosts or DNS. In this case the there were no changes to the hostname as we were able to connect to the hostname listed in the last known state on the database home page.

Before spending a lot of time attempting to reconfigure the agent look closely at the error message, and the title of this post. The agent is looking for the configuration directory in the ORACLE_HOME and not the AGENT_HOME. Unlike Database Control, the Grid Control Agent stores the configuration directory in AGENT_HOME and not the ORACLE_HOME. Set the ORACLE_HOME appropriately prior to starting the agent to resolve the issue.


  • Hammad Farooq (December 7, 2015 7:45 am)

    Howto set the the ORACLE_HOME Proper we already set the oracle_home after clone the instance from Production

    I see or think that the EM agent would read the Production oracle_home path
    How will I set or any file changes than Run the ./emctl from ORACLE_HOME/bin

    so it will Resolved

    I forgot the Solution Plz help How to Resolve this Confusion

Post A Comment