Section I: Installation Types

Installing Enterprise Manager 10g Grid Control Using a New Database

This option is selected by default when you run the Enterprise Manager Grid Control installer. Keep this selection if you want to install Enterprise Manager and all its dependent components on a single host. Oracle Management Server, a enterprise edition database which be used as a Management repository and Management Agent are the components which are installed on a single host if this installation type is choosen.

Though it is the simplest form of installation it is not recommended for production environments with a large number of targets to be managed by the Enterprise Manager grid control.

Prerequisites

The installation should not be run by the root user (UNIX only). Ensure the following prerequisites are met:

• User should be a DBA user.
• User should be able to create process-level tokens (Microsoft Windows only).
• User should be able to log in as a batch job (Microsoft Windows only).
• User should be able to adjust memory quota for process (Microsoft Windows only).
• User should be part of the ORA-DBA group (Microsoft Windows only) and have Administrator permissions.
• The name of the host on which the installation is being performed should neither be localhost.localdomain nor an IP address. It must be a valid host name. At the time of invoking the installer, you can pass ORACLE_HOSTNAME as an argument.

Installing Enterprise Manager 10g Grid Control Using an Existing Database

This is the recommended install type for most of the environments. Select this option if you want to perform a complete Enterprise Manager Grid Control installation and have a qualified existing database in which to create the Management Repository. Oracle Management Server, Management Agent are the components which are installed on a machine if this installation type is choosen, while the neccessary schemas are created in the existing database to use it as a Management repository .

The existing database can be local or remote to the machine on which you are installing. Oracle Real Application Clusters (RAC) databases must be on a shared disk.

The hardware requirements for the Management Repository and the operating system patch requirements for the host machine must be satisfied regardless of whether you choose to create a new database or use an existing database for the Management Repository during the installation session.

If you plan to use an existing database for your Management Repository creation, check all software requirements for the database and host, as well as for the repository.

Prerequisites

• Ensure the installation is not run by the root user.
• Verify Database Setting (Initialization Parameters).
• Ensure the existing database and listener are up.
• Ensure that the profile of the Password Verification resource name has the "Default" value. If the Password Verification is enabled, repository creation may fail.
• Ensure there is sufficient physical memory available for this installation type.
• Ensure the database release should be 9.2.0.6 and later, or 10.1.0.4 and later. Execute select banner from v$version to find out the current database version.
• Ensure the name of the host on which the installation is being performed is neither be localhost.localdomain nor an IP address. It must be a valid host name. At the time of invoking the installer, you can pass ORACLE_HOSTNAME as an argument.

The Management Repository database can be created on the following database releases:

• Oracle Database 10g Release 1 (10.1.0.4 and later), Enterprise Edition
• Oracle Real Application Clusters 10g Release 1 (10.1.0.4 and later)
• Oracle9i Release 2 (9.2.0.6 and later), Enterprise Edition
• Oracle9i Real Application Clusters Release 2 (9.2.0.6 and later)

Installing an Additional Management Service

Select this option if you need to add an additional Management Service to your environment for High Availability or Scalability. Multiple Management Services that provide high availability should be behind a load balancer.

Prerequisites

Ensure the following prerequisites are met before starting the installation:

• Ensure the installation is not run by the root user.
• Ensure the user has Administrator permissions and is part of the DBA group.
• Ensure the hard disk and physical memory requirements are met.
• Besides the database release, ensure the repository release is 10.2.0.1.0 (or 10.2.0.2 for Microsoft Windows).
• The name of the host on which the installation is being performed should neither be localhost.localdomain nor an IP address. It must be a valid host name. At the time of invoking the installer, you can pass ORACLE_HOSTNAME as an argument.

Recommended Highly Available Configuration for the Enterprise Manager Grid Control

• Use the "Installing Enterprise Manager 10g Grid Control Using an Existing Database" option to install Enterprise Manager using an existing Real Application Cluster (RAC) database.
• Use the "Installing an Additional Management Service" option to install additional OMS behind a load balancer configured.
  
  A pictorial representation of a highly available Enterprise Manager Configuration is depicted in the figure below
  

Installing a Management Agent

Select this option to install the Management Agent in an Oracle home directory on a specified host target. Each host you wish to monitor must have a Management Agent installed.

You can install the Management Agent in the following ways:

• On each host computer, run Oracle Universal Installer from the Enterprise Manager DVD-ROM and select the Additional Management Agent installation type. This method installs one Management Agent at a time in interactive GUI mode. You may also perform silent installations using a response file.
• Use the Agent Deploy application to perform a new agent installation (standalone or cluster agent) or a shared agent installation.
• Use the nfsagentinstall script to install and deploy the shared Management Agent.
• Use the agentDownload script to install and deploy Management Agents to many managed hosts through HTTP or over the network.

Prerequisites

• Ensure the Management Agent Oracle home must not contain any other Oracle software installation.
• The name of the host on which the installation is being performed should neither be localhost.localdomain nor an IP address. It must be a valid host name. At the time of invoking the installer, you can pass ORACLE_HOSTNAME as an argument.

Section II: Prerequisite Checks

The following table lists all the prerequisite checks that the installer performs for each installation type: