8i | 9i | 10g | 11g | 12c | 13c | 18c | 19c | 21c | 23c | Misc | PL/SQL | SQL | RAC | WebLogic | Linux

Home » Articles » 13c » Here

Enterprise Manager Cloud Control Agent Notes

This article includes a variety of notes related to the Enterprise Manager Cloud Control Agent, relevant to both 13c and 12c.

Related articles.


If you installed the agent in into the "/u01/app/oracle/product/agent13c" directory, the main log location will be as follows.


Restart Agent

I would normally create a script called "restart_agent.sh" as follows.

mkdir -p ~/scripts/

cat > ~/scripts/restart_agent.sh <<EOF
export AGENT_INST=/u01/app/oracle/product/agent13c/agent_inst

\$AGENT_INST/bin/emctl stop agent
\$AGENT_INST/bin/emctl start agent
\$AGENT_INST/bin/emctl upload agent

chmod u+x ~/scripts/restart_agent.sh

The agent is restarted by running the following command.


Hard Kill

Assuming the agent is installed in the "/u01/app/oracle/product/agent13c" directory we might use the following commands to do a hard kill of the agent and then restart it.

kill -9 `ps -ef | grep [a]gent13c | awk '{print $2}'`

Agent Memory (Cloud Control)

Set the AGENT_HOME to the location of the agent home from your cloud control installation and stop the agent.

export AGENT_HOME=/u01/app/oracle/middleware/agent/core/
$AGENT_HOME/bin/emctl stop agent

Edit the "emd.properties" file setting the appropriate values of the "agentJavaDefines" parameter.

vi /u01/app/oracle/middleware/agent13c/agent_inst/sysman/config/emd.properties

agentJavaDefines=-Xmx2048M -XX:MaxPermSize=128M

Start the agent again.

$AGENT_HOME/bin/emctl start agent

Agent Memory (Client)

You might want to do something similar to the previous section on the client agent if you are having repeated problems. In these situations, consider the following edit to alter the memory in the "emd.properties" file. Adjust as required.

vi /u01/app/oracle/product/agent13c/agent_inst/sysman/config/emd.properties

agentJavaDefines=-Xmx512M -XX:MaxPermSize=96M

Restart the agent.


Force Agent Resync

In some situations you need to resynchronise the agent, but it's not in a state that allows you to run the resynchronise job. Here's how you fix that. I came across a situation like this when I was dealing with "Metric Collection Error, Status Event (Doc ID 2335484.1)".

The reported target status should be accurate after resynchronization.

Update Plugins

This is explained here.

For more information see:

Hope this helps. Regards Tim...

Back to the Top.