My Oracle Support Banner

Case Study - Installation of Enterprise Manager Grid Control Using an Existing Database with the Software Only Method on Linux x86 (Doc ID 763347.1)

Last updated on AUGUST 19, 2022

Applies to:

Enterprise Manager Base Platform - Version to [Release 10.2]
Linux x86
x86 32 bit


This procedure is for Oracle Enterprise Linux 5.3 x86, but the principle is applicable to all platforms with a base product version available. Nevertheless, other platforms may show slight differences in the configuration required to complete a successful installation. Likewise, different stage sources may result in a different filepath to required locations in the staged software, so adjust accordingly.

The software-only method of installation, first offered in version, allows;

- Installation with an existing database of a variety not supported with the base product
- Achieving a DST-compliant installation of the agent (from any Grid Control installation type) prior to initial startup

The procedure for version is presented here.

This method is specifically for full installation of version Grid Control.
Do NOT use this method to install any other version of Grid Control.
Do NOT use this method to patch or upgrade any existing Grid Control installation

Note that filepath designations such as .../oms10g and .../agent10g are relative, represent generic locations, are for descriptive use only and indicate that the Parent Directory should be prepended to arrive at a usable filepath value. A descriptive character string such as .../agent10g" should never be used in an installation exercise. The same is true for .../oraInventory, but in this case, the filepath to be prepended may not be the Parent Directory, rather the actual value should be that described in the /etc/oraInst.loc file.

For this exercise, the following configuration is used in the example: base product install stage: /u02/gc10201/ patchset install stage: /u02/gc10205/
Parent directory for installation: /u01/app/gc/
Database Oracle Home is /u01/app/db102
/oradata/ location for repository database: /u01/app/db102/oradata/
/oraInventory location: /u01/app/ 
sys password for DB: dbauser32
sysman password for DB: sysman32
Respository database SID: emrep
OMS will be unlocked
/etc/oraInst.loc pointing to /u01/app

Values used in response files and command executions must be altered if a different configuration is used. These values are for demonstration use only and should be changed to be applicable to the system receiving the installation.


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.