Enterprise manager – How To Install An Additional Management Service
Posted by John Hallas on June 7, 2011
How To Install An Additional Management Service
This document will describe how to install an additional management service for Oracle Enterprise Manager Grid Control 10.2.0.5 on HP-UX. It was written by my colleague Carl Holmes.
You must first install the base release of Enterprise Manager (10.2.0.3) and patch it to 10.2.0.5
The recommended installation method is to install the software, patch it to 10.2.0.5 and then configure Enterprise Manager.
To do this, use these installer commands
./runInstaller -noconfig -ignoreSysPreReqs b_skipDBvalidation=TRUE
Explanation of this command
-noconfig – Do not run the configuration assistants after the software is installed
-ignoreSysPreReqs – Skip the system pre req checks as this version of Enterprise Manager is not aware of HP-UX version 11.31
b_skipDBvalidation=TRUE – Use this command to stop the installer checking the repository database version, as it is not aware of version 220.127.116.11
When the system pre req screen appears, manually verify the OS version to continue.
When the installation is complete you will be prompted to run $OMS_HOME/allroot.sh.
This runs the root.sh scripts for the OMS and the management agent that have just been installed
Use this command to patch the software to 10.2.0.5
./runInstaller -noconfig b_softwareonly=true
-noconfig – Do not run the configuration assistants
b_softwareonly=true – Just patch the software, configuration to be done later
Use this installer command to patch the OMS, then repeat for the management agent.
Take a TAR backup of the OMS_HOME at this point, so it can be restored easily in the event of configuration failing
Configure Enterprise Manager
Now that the software is installed, Enterprise Manager needs to be configured. The installers add all the actions of the configuration assistants that were skipped to a perl script that needs to be run.
It is advised to do this before apply any other patch.
First set PERL5LIB to $OMS_HOME/perl/lib/5.6.1
Now run the perl script (all one line)
<$OMS_HOME>/perl/bin/perl <$OMS_HOME>/sysman/install/ConfigureGC.pl <$OMS_BASE>
If OMS home is /app/oracle/product/gc10.2/oms10g then OMS_BASE is /app/oracle/product/gc10.2
Apply patches to the OMS
Once the perl script configuration is complete, any patches applied to the existing OMS server need to be applied to the new OMS
Refer to the read me’s of each patch. – Any SQL scripts do not need to be run.
Import the config from the existing OMS in to the new OMS.
First export the config from the existing OMS
emctl exportconfig oms -dir
Copy the file to the new OMS server and import it
First shutdown the new OMS
Then import the file
emctl importconfig oms -file
Start up the new OMS
This sets up the emoms.properties file, ensuring that the configuration across the OMS’s is the same
Re-secure the Management Agent
Perform this step if you are using a load balancer
emctl secure agent -emdWalletSrcUrl <a href=”https://slb.example.com:https://slb.example.com:<upload port>/em
Configure the OMS’s to use the shared filesystem loader
The two OMS’s need to be able to access a shared filesystem, from which the files uploaded by the agents are processed by each OMS. This can be an NFS share between the two OMS servers. First stop the new OMS’s and then use this command to configure them to use the shared filesystem loader
emctl config oms loader -shared yes -dir /omscache
Check that reports are working
All reports run from the reports tab use the MGMT_VIEW user to connect to the repository.
To ensure the new OMS servers are using the correct password run this command from each OMS.
emctl config oms -change_view_user_pwd -sysman_pwd-user_pwd
If this fails to work check the database parameter SEC_CASE_SENSITIVE_LOGON
Set this to FALSE, restart the OMS and retry the report.
This only applies to 11g databases.