Deployment of an Agent – Preparation

To be able to do deployment of an agent with EM the following preparations must be taken care of:

Download the Mass Agent deployment zip file from
Oracle Enterprise Manager 10g Grid Control Management Agents ( for Windows, Linux x86, and Solaris SPARC

On each OMS
Unzip the zip file ( to $OMS_HOME//sysman/agent_download/

$ unzip -d /u01/app/oracle/product/10.2.0/oms10g/sysman/agent_download/

$ pwd
$ ls -al
total 64
total 64
drwxrwxr-x 8 oracle dba 4096 Apr 11 06:24 .
drwxrwx— 4 oracle dba 4096 Apr 17 09:05 ..
drwxrwxr-x 2 oracle dba 4096 Apr 11 06:24 addons
drwxrwxr-x 4 oracle dba 4096 Apr 11 07:16 agent
drwxrwxr-x 2 oracle dba 4096 Apr 11 06:24 agentdeploy
-rw-r–r– 1 oracle dba 28608 Sep 3 2007 agentDownload.linux_x64
-rw-r–r– 1 oracle dba 165 Jul 21 2006 agent_scripts.jar
drwxrwxr-x 2 oracle dba 4096 Apr 11 06:24 oui
drwxrwxr-x 2 oracle dba 4096 Apr 11 07:00 prereqs
drwxrwxr-x 2 oracle dba 4096 Apr 11 06:24 response

Modification of configuration files
On each OMS server the following checks should be made:

Check that the file $OMS_OH/sysman/agent_download/ contains the correct settings.
#Name : s_OMSHost
#Datatype : String
#Description: Fully-qualified hostname where the OMS resides
# Example: “”
#Component :

#Name : s_OMSPort
#Datatype : String
#Description: Port number used to communicate with the Management Service
# If port 4889 is in use by another application, please reset.
#Component :

Normally these values were set to the correct values, during installation of the OMS.

Check that the file $OMS_OH/sysman/prov/resources/ contains the correct settings:


Next you need to setup the ssh configuration, allowing to ssh from you OMS server to the servers you want to deploy to:

$ cd $OMS_HOME/sysman/prov/resources/scripts
$ ./ -hosts “

One thought on “Deployment of an Agent – Preparation

  1. amy says:

    i have my grid control up and running with repository DB at and
    OMS and OMA both at 11.1. All inside one machine.

    Now we want to deploy agent. Which i know how to, as i have already deployed some agents. But at this paticular server, the setup of oracle is little weird.

    So here is what the setup is…
    Actual hostname(physical) = hostname_act
    Inside this host, we create some logical partitions i beleive or something of that case…

    the reason why i say the above is…
    we login a user1 on hostname1 but when i type hostname cmd it says hostname_act ( not hostname1)
    and so one for other users

    we have 4 DB, using 4 diff oracle home, with 4 diff listiner
    under 4 Different oracle account.

    Db = oracle home = user = hostname(or alias or logical name)

    db1 = /oracle/home1 = user1 = hostname1
    db2 = /oracle/home2 = user2 = hostname2
    db3 = /oracle/home3 = user3 = hostname3
    db4 = /oracle/home4 = user4 = hostname4

    as user1 is not able to access file for user2.
    and so on….

    so now my question is, when i deploy the agent, with what user shall i deploy the agent as ?? (user1, user2, user3 or 4) or shall i create a new user and deploy agent with that ??

    Also, as we are using a alias/logical server name in our listiner.ora file(hostname1, hostname2…instead of hostname_act)…will this effect the agent deployment ?? Please suggest…

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s