Database Reference
In-Depth Information
Armed with that information it is possible to get the agent image and deploy it to the staging directory on the
OMS as shown here:
[oracle@oem12oms1 ~]$ mkdir /u01/temp
[oracle@oem12oms1 ~]$ emcli get_agentimage -destination=/u01/temp \
> -platform="Linux x86-64"
Platform:Linux x86-64
Destination:/u01/temp
=== Partition Detail ===
Space free : 14 GB
Space required : 1 GB
Check the logs at /u01/app/oracle/oem12/gc_inst/em/EMGC_OMS1/sysman/emcli/setup/
.emcli/get_agentimage_2013-01-01_21-03-28-PM.log
Setting property ORACLE_HOME to:/u01/app/oracle/oem12/oms
calling pulloneoffs with arguments:/u01/app/oracle/oem12/oms/u01/app/oracle/oem12/oms/sysman/
agent/12.1.0.2.0_AgentCore_226.zip12.1.0.2.0linux_x64
Check this logs for more information: /u01/app/oracle/oem12/oms/sysman/prov/
agentpush/logs
The result of this process's execution is a deployable agent image for Linux x86-64. This process only needs to be
completed once, the resulting zip file can be reused on as many hosts as you like. You could move the resulting zip file
to a shared area to make it easier to deploy the zip file later. Whichever way you chose to make the image available,
the newly created zip file needs to be accessible on the destination host. Most users decide to install the agent using
the same user ID as they chose for the RDBMS binaries, as does this example. Once logged in as “oracle” on the
destination host, prepare for the installation. If your host already has an Oracle database installed you should be fine
with regards to the agent installation prerequisites. If not, you should review Table 6-1 in the Advanced Installation
and Configuration Guide. Next you unzip the zip file to a convenient location, it is
/tmp/agent12c
in this example.
Before the agent can be installed you need to provide a response file. An example response file is shown below,
stripped of comments and empty lines:
[oracle@oem12db agent12c]$ sed -e '/^#/d' -e '/^$/d' agent.rsp
RESPONSEFILE_VERSION=2.2.1.0.0
EM_UPLOAD_PORT=4900
AGENT_REGISTRATION_PASSWORD=<secretPassword>
b_startAgent=true
EM_INSTALL_TYPE="AGENT"
The full description of the response file parameters is listed in Table 6-3 in the Oracle® Enterprise Manager
Cloud Control Advanced Installation and Configuration Guide. The above example is complete and can be used after
changing it to match your environment. If you are unsure about the ports to be used, you can interrogate the OMS
directly, using the command shown here:
[oracle@oem12oms1 ~]$ emctl status oms -details
Oracle Enterprise Manager Cloud Control 12c Release 2
Copyright (c) 1996, 2012 Oracle Corporation. All rights reserved.
Enter Enterprise Manager Root (SYSMAN) Password :
Console Server Host :
oem12oms1.example.com
HTTP Console Port : 7788
HTTPS Console Port : 7799
HTTP Upload Port : 4889
HTTPS Upload Port : 4900
Search WWH ::
Custom Search