1. Download Oracle gridcontrol agent software.
2. Unzip oracle_home/sysman/agent_download/11.1.0.1.0. If patch not there create new folder.
3. Rename agent_download.rsp_bkp to agent_download.rsp.
4. Edit that file and add below informations.
s_OMSHost=acdf
s_OMSPort=7799
OMS_HOST=acdf.qataridiar.com
OMS_PORT=4889
AGENT_REGISTRATION_PASSWORD=
INSTALL_UPDATES_SELECTION="skip"
ORACLE_AGENT_HOME_LOCATION=/u01/agent11g/oemhome
FROM_LOCATION=/u01/appl/oracle/PROD/db/sysman/agent_download/11.1.0.1.0/linux_x64/agent/stage/products.xml
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
DECLINE_SECURITY_UPDATES=false
MYORACLESUPPORT_USERNAME=
MYORACLESUPPORT_PASSWORD=
5. Go to runinstaller path and run below .
./runInstaller -silent -responseFile /u01/app/oracle/product/11.2.0/sysman/agent_download/11.1.0.1.0/agent_download.rsp
2. Unzip oracle_home/sysman/agent_download/11.1.0.1.0. If patch not there create new folder.
3. Rename agent_download.rsp_bkp to agent_download.rsp.
4. Edit that file and add below informations.
s_OMSHost=acdf
s_OMSPort=7799
OMS_HOST=acdf.qataridiar.com
OMS_PORT=4889
AGENT_REGISTRATION_PASSWORD=
INSTALL_UPDATES_SELECTION="skip"
ORACLE_AGENT_HOME_LOCATION=/u01/agent11g/oemhome
FROM_LOCATION=/u01/appl/oracle/PROD/db/sysman/agent_download/11.1.0.1.0/linux_x64/agent/stage/products.xml
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
DECLINE_SECURITY_UPDATES=false
MYORACLESUPPORT_USERNAME=
MYORACLESUPPORT_PASSWORD=
5. Go to runinstaller path and run below .
./runInstaller -silent -responseFile /u01/app/oracle/product/11.2.0/sysman/agent_download/11.1.0.1.0/agent_download.rsp
1 comment:
This is a concise and practical walkthrough for anyone automating OEM Grid agent installs, especially in environments where interactive installs are not an option. Silent mode setups like this are often under documented, yet they are critical for consistency across servers and for reducing manual configuration drift.
What I like here is the clarity around preparing the response file. Calling out exactly which values need to be aligned with the OMS host and port removes a lot of guesswork, particularly for teams managing multiple environments. These are the small details that tend to trip people up during first time automation attempts.
From a quality and operations standpoint, documenting repeatable installation steps is just as important as testing application code. Treating infrastructure workflows as first class artifacts makes onboarding smoother and reduces risk during scaling or recovery scenarios. Keeping these procedures tracked and reviewed over time in a shared system like Tuskr test management software helps ensure they stay accurate as environments evolve.
Post a Comment