What's New

This chapter describes new features in the Enterprise Manager 10g Grid Control Release 3 ( installer.

The new Enterprise Manager installer provides an installation that is almost completely automated. In this release, the Enterprise Manager installer also provides the following:


For information about Management Agent deployment best practices, see the Agent Best Practices paper available at http://www.oracle.com/technology/products/oem/pdf/10gr2_agent_deploy_bp.pdf.

Multiple Oracle Home Installations

The Enterprise Manager installer provides for a seamless installation experience by performing multiple Oracle home installations, depending on the type of installation that you select.

An Oracle Enterprise Manager Grid Control installation using a new database will create a separate Oracle home for:


The Oracle homes that are created as subdirectories by the installer will be placed under the Parent Directory that you specify. The Oracle homes will be created as db10g, oms10g, and agent10g.

Seamless Oracle Home Configurations

The Enterprise Manager installer performs multiple Oracle home configurations during the installation process. The configuration tools that are run during installation will depend on the installation type that you have selected.

The following table lists all the configuration tools that are run during an Enterprise Manager installation using a new database:

Product Configuration Tools
Oracle Enterprise Manager Repository Database
  • Oracle Net Configuration Assistant
  • Oracle Database Configuration Assistant

Oracle Enterprise Manager Grid Console
  • OC4J Configuration Assistant
  • HTTP Server Configuration Assistant

  • Java Configuration Assistant

  • Web Cache Configuration Assistant

  • Oracle AS Instance Configuration Assistant

  • Register DCM Plug-ins with Enterprise Manager

  • DCM Repository Backups Assistant

  • Enterprise Manager Technology Stack Upgrade

  • Oracle Management Service Configuration

Oracle Management Agent
  • Agent Configuration Assistant


Depending on the installation type you have chosen, any or all of the configuration tools listed in the preceding table will be run.

Running Root.sh (UNIX only)

You are now required to run only one script, allroot.sh, in this release of the installer, as compared to the three root.sh scripts (one for each Oracle home) that you had to run in the previous release.


If Enterprise Manager is the first Oracle product that you are installing, you will also be prompted to execute orainst Root.sh along with all root.sh.

Resuming an Enterprise Manager Grid Control Installation

In the event of an unexpected termination of the installation process, the Resumability feature of the installer allows you to resume the installation process (the next time the installer is invoked) from the point where the installation was aborted.

Out-of-Box Secure Grid Environment

The new Enterprise Manager 10g installer provides a secure Grid Control environment that is immediately ready to use.

Automated Startup Scripts (UNIX Only)

In this release of Enterprise Manager, the startup scripts to run the Oracle database, Management Service, listener, and agent are automatically executed in case a machine reboots. The services that are automatically started depend on the installation type that you chose.

Installing Automated Scripts Start the
Enterprise Manager Using New Database Repository database, listener, Management Service, and the agent.
Enterprise Manager Using Existing Database Management Service and agent.
Additional Management Service Management Service and agent.
Additional Management Agent Agent only.
NFS Agent NFS Agent


On Microsoft Windows, the services are started automatically by the operating system.

Automated Secure Shell (SSH) Setup During Push Install

In Enterprise Manager Grid control, users do not have to run the SSH user equivalence script (sshUserSetup.ssh/sshUserSetupNT.ssh, sshConnectivity.sh) before starting the push install, to establish the SSH user equivalence between the Oracle Management Service and agent targets. In Enterprise Manager Grid Control, the push application sets up and drops the SSH connection automatically between the Oracle Management Service and the agent targets accordingly, but if agent targets are on Windows operating systems, then user needs to setup Cygwin as explained in Appendix C, to start the push agent install.

Oracle Configuration Manager

Oracle Configuration Manager (OCM) is designed to gather and provide customer's configuration information and store it in Oracle repository for maintenance and other related tasks. This feature was introduced from Grid Control Release onwards.

Enhanced Installer Screens

The Enterprise Manager 10g R2 installer's enhanced Graphical User Interface (GUI) provides for a more user-friendly installation experience.

Installation Location

After you select the appropriate installation option in the first screen (Specify Installation Type), you will be prompted to specify the Parent Directory in the Specify Installation Location screen, wherein the Oracle homes are created automatically.

Specify Configuration

The Specify Configuration screen for installing Enterprise Manager using an existing database has changed. The single Connect String value (comprising a host name, port, and SID) that you had to specify in the previous release has been changed to three input fields.

Language Selection

This screen has been removed. You can now select the required languages by clicking Product Languages in the Installation Location screen.

Prefill Tablespace Location

The Specify Repository Database Configuration screen now includes the Prefill Tablespace Locations button. Upon clicking this button, the installer queries the database that you have specified, looks for the SYSAUX tablespace location, and automatically prefills that path in the appropriate tablespace location text boxes.


If the tablespaces are stored in a raw device/ASM disk, then you must ensure the raw device/ASM disk is accessible to store the SYSMAN tablespaces.