Silent Agent installation on Enterprise Manager 12c Cloud Control

In Enterprise Manager 10g and 11g, There was an available separate agent installation to be downloaded from E-Delivery or OTN, but this is not the case in Enterprise Manager Cloud Control 12c. To install Oracle Agent you need to use the EM console UI From Setup >> Targets >> add target manually, But in this case you have to setup SSH to be able to push the agent software to the new host.

But in my case I had to install Agent on Windows host while the OMS in on Linux host.I didn’t want to setup SSH on Windows which brings unnecessary hassle to me.


Step 1.Know what you already have:

[oracle@CloudControl bin]$ cd /u01/app/oracle/oms12cr2/oms/bin
[oracle@CloudControl bin]$ ./emcli login -username=sysman
Enter password :

Login successful

Now we need to know if the OMS Software library has the agent software for the desired platform

[oracle@CloudControl bin]$ ./emcli get_supported_platforms
Getting list of platforms …
Check the logs at /u01/app/oracle/oms12cr2/gc_inst/em/EMGC_OMS1/sysman/emcli/setup/.emcli/agent.log
About to access self-update code path to retrieve the platforms list..
Getting Platforms list  …
Version =
Platform = Linux x86-64
Version =
Platform = Microsoft Windows x64 (64-bit)
Platforms list displayed successfully.

As seen above the agent has versions for Linux x86 64 bit and Windows x64 64 bit, if you need another agent platform advance to step 2 if you don’t the above output works for your environment skip the next step.

Step 2.Add a specific agent to the library:

– From Setup >> Extensibility >> Self Update
You will here all the software library contents, We are now interested in Agent Software.
– Clicking on Agent software will bring agent software list- Select your desired Agent version and Platform and click Download.3

If you’re on Online Mode, EM will connect to My Oracle Support, Download the agent and Add it to the library.Then we will need to extract the Agent install zip file from the library.

./emcli get_agentimage -destination=/u01/agents12clibrary -platform=”Microsoft Windows x64 (64-bit)” -version=”″

Please remember to change the parameters with:
destination: Where to save the agent file
platform: the name of the platform as taken from step 1 output
version: version of the agent software as taken from step 1 output

[oracle@Gridctl bin]$ ./emcli get_agentimage -destination=/u01/agents12clibrary -platform=”Microsoft Windows x64 (64-bit)” -version=”″
Platform:Microsoft Windows x64 (64-bit)
=== Partition Detail ===
Space free : 262 GB
Space required : 1 GB
Check the logs at /u01/app/oracle/oms12cr2/gc_inst/em/EMGC_OMS1/sysman/emcli/setup/.emcli/get_agentimage_2013-08-13_12-11-47-PM.log
Setting property ORACLE_HOME to:/u01/app/oracle/oms12cr2/oms
calling pulloneoffs with arguments:/u01/app/oracle/oms12cr2/oms/u01/app/oracle/oms12cr2/oms/software_library/59/D2C62646FECF0F56E04332CA1EAC1F3612.
Check this logs for more information: /u01/app/oracle/oms12cr2/oms/sysman/prov/agentpush/logs

[oracle@Gridctl bin]$ ls -l /u01/agents12clibrary
total 248980
-rw-r—– 1 oracle oinstall 254955500 Aug 13 12:12

If you’re on offline mode, EM will give you the direct link to download your Agent Software, then you will need to add to the library(if desired) but we can use it directly to install.

In both cases, you will end with the file of the agent in hand for example in our case.

Step 3: Install the agent on the desired host(s):

-Transfer the output file to the host and unzip the file.

-We need to pass the installation parameters to the agent installation script either using response file or parameters.

Using response file, Edit agent.rsp and change the values of the following parameters:

OMS_HOST:<String> OMS host info required to connect to OMS
EM_UPLOAD_PORT:<String> OMS port info required to connect to OMS
AGENT_REGISTRATION_PASSWORD:<String> Agent Registration Password needed to establish a secure connection to the OMS.
ORACLE_HOSTNAME:<String> Fully qualified domain name of host where is the agent is deployed.

Now run the installation/Deploy script:

Using Response file:

./ AGENT_BASE_DIR=/u01/app/oracle/agent12c2 RESPONSE_FILE=/stage/agent12c2/agent.rsp


agentDeploy.bat AGENT_BASE_DIR=c:\agent12c RESPONSE_FILE=c:\stage\agent12c2\agent.rsp

Or pass the parameters directly:





Now we will have to wait until the agent installation finishes.

Note: In *nix Platforms as usual, script will need to run as root OS user before the end of the installation.

Now we will(hopefully) end with the happy following happy ending:

Agent deployment completed successfully.

Step 4.Check the Agent status after deployment:

As a final step we need to check the agent status, so we will change directory agent_inst/bin under the installed agent directory:

$ ./emctl status agent
Oracle Enterprise Manager Cloud Control 12c Release 2
Copyright (c) 1996, 2012 Oracle Corporation.  All rights reserved.
Agent Version     :
OMS Version       :
Protocol Version  :
Agent Home        : /u01/agent12c2/agent_inst
Agent Binaries    : /u01/agent12c2/core/
Agent Process ID  : 4472
Parent Process ID : 2357
Agent URL         :
Repository URL    :
Started at        : 2013-06-16 16:45:31
Started by user   : oracle
Last Reload       : (none)
Last successful upload                       : 2013-08-13 18:34:49
Last attempted upload                        : 2013-08-13 18:34:49
Total Megabytes of XML files uploaded so far : 205.36
Number of XML files pending upload           : 0
Size of XML files pending upload(MB)         : 0
Available disk space on upload filesystem    : 58.85%
Collection Status                            : Collections enabled
Heartbeat Status                             : Ok
Last attempted heartbeat to OMS              : 2013-08-13 18:34:07
Last successful heartbeat to OMS             : 2013-08-13 18:34:07
Next scheduled heartbeat to OMS              : 2013-08-13 18:35:07

Agent is Running and Ready

Agent is Running and Ready >> This should tell us the agent is running fine.

Last successful upload >> Should be recent to indicate the agent is uploading fine to the OMS.

Posted in Uncategorized | 1 Comment