The Oracle Configuration Manager (OCM) has been around since Oracle 10.2.0.5. Oracle has obviously expanded their product portfolio since then, and their offering includes OEM Grid Control and Cloud Control that were in their infancy.
Meanwhile, in the background, little workhorse OCM has been quietly gathering and uploading configuration data to make our relationahip with Oracle Support smoother. Really. Resolving an SR requires lots of background detail for the Support Analyst to match solutions to configurations at a fairly fine level. Patch and release levels can affect the solution.
OCM is fairly homogenous across platforms. As a result, it’s also quite particular.
Here are some things you can do reduce the heart-ache when implementing OCM for as the Harvester on your OEM management servers.
- Always download the latest version of OCM before installing it
OCM is shipped as part of the OEM management server installation but the pre-installed version is only up-to-date through release date for your Oracle Home. 12cR1 installations are over a year old already and so is OCM.
- Follow the procedure in MOS document Doc ID 761313.1 to ensure a clean removal of the old version, including database objects in your repository, before installing a current copy
- Verify that you have the correct 32-bit libraries.
OCM is a 32-bit application, even in its old age. Install these rpms on RedHat to make it work
yum install libgcc.i686
yum install libaio.i686
yum install libstdc++.i686
yum install libstdc++-devel.i686
yum install compat-db.i686
yum install compat-libstdc++-296.i686
- Set and verify a JAVA_HOME environment variable prior to executing setupCCR
- Set and verify environment variable for ORACLE_CONFIG_HOME
- Provide both a MOS user name and password when promoted for them by setupCCR script.
- Each management server in your OMS cluster must have OCM installed and configured
Every morning the cluster assigns one its members to upload OCM data to Oracle Support. The assignment, from what I’ve heard from Oracle Support, is purely random. If they followed a round-robin scheme and you only have OCM configured on OMS1, the uploads/syncs would happen every three days. Because the assignment between OMS’ is randomized your reposting gap could be longer or shorter.