1. Cloud Control Release Notes
  2. Oracle Enterprise Manager Cloud Control Release Notes 13c Release 4
  3. Installing Oracle Enterprise Manager Cloud Control 13c Release 4
  4. Generic Known Installation Issues
  5. Installation of Additional OMS Fails If Primary OMS Was Installed in Silent Mode

Installation of Additional OMS Fails If Primary OMS Was Installed in Silent Mode

If you installed the primary OMS in silent mode, adding another OMS using the graphical interface (using a deployment procedure) will fail.

The workaround is to install an additional OMS, on a secondary host, in silent mode and configure it manually as follows:

Prerequisites: Ensure that the software library and BIP are configured. The software library and BIP shared storage must be mounted and accessible from the secondary host.

  1. Install software-only only on the secondary host by running the EM installer from the shared stage. Follow the steps outlined in Installing the Enterprise Manager Cloud Control 13c Release Software Binaries in Silent Mode.

  2. Run root.sh on the secondary host as outlined in Running the Root Script.

  3. Connect to the Management Repository and run the following SQL query to retrieve a list of plug-ins installed on the primary OMS.

    SELECT epv.plugin_id, epv.version, epv.rev_version FROM em_plugin_version epv, em_current_deployed_plugin ecp WHERE epv.plugin_type NOT IN ('BUILT_IN_TARGET_TYPE', 'INSTALL_HOME') AND ecp.dest_type='2' AND epv.plugin_version_id = ecp.plugin_version_id;

  4. Perform the plug-ins deployment using silent mode method as follows:

    <OMS_HOME>/sysman/install/PluginInstall.sh -silent PLUGIN_SELECTION="{<plug-in internal name 1>, <plug-in internal name 2>,...}

    For example, if the query from your repository returns the following plug-ins: oracle.sysman.emas,oracle.sysman.si,oracle.em.satc,oracle.sysman.csm,oracle.em.smad,oracle.em.smis,oracle.em.savf,oracle.sysman.bda,oracle.sysman.ssa,oracle.sysman.cfw,oracle.sysman.db,oracle.sysman.xa,oracle.sysman.emct,oracle.sysman.emfa,oracle.sysman.orhc,oracle.sysman.empa,oracle.sysman.smf,oracle.sysman.vi,oracle.sysman.vt,oracle.sysman.am you would run the following:

    <OMS_HOME>/sysman/install/PluginInstall.sh -silent PLUGIN_SELECTION=" {oracle.sysman.emas,oracle.sysman.si,oracle.em.satc,oracle.sysman.csm,oracle.em.smad,oracle.em.smis,oracle.em.savf,oracle.sysman.bda,oracle.sysman.ssa,oracle.sysman.cfw,oracle.sysman.db,oracle.sysman.xa,oracle.sysman.emct,oracle.sysman.emfa,oracle.sysman.orhc,oracle.sysman.empa,oracle.sysman.smf,oracle.sysman.vi,oracle.sysman.vt,oracle.sysman.am}"

  5. Use EM UI to install an Oracle Management Agent on the secondary host and run root.sh. See more details at Installing a Standalone Oracle Management Agent Using Add Host Targets Wizard or EM CLI.

For any additional OMS installs, use the EM Add OMS Deployment Procedure. For more details, see Adding Additional Oracle Management Services.

(Bug 30682423)