This chapter describes new features in the Enterprise Manager 10g Grid Control Release 3 (10.2.0.3.0) 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:
Facilitates individual maintenance cycles for each of the top-level product components.
This is brought about by installing the database and Oracle Management Service (OMS) in separate Oracle homes. In this release, the Enterprise Manager installer will perform a chain install, wherein it will install the OMS, database, and the agent in separate Oracle homes (
Facilitates an Oracle Management Service upgrade from 10.1.0.4 release (and later) to 10.2.0.3.0
Facilitates an Oracle Management Agent upgrade from 10.1.0.3 release (and later) to 10.2.0.3.0
Facilitates mass deployment of the Management Agent using the Agent Deploy application.
Provides a ready-to-use secure Enterprise Manager Grid Control environment.
Provides automated startup scripts that help start the Oracle Database, Management Service, listener, and the Management Agent during a machine reboot (UNIX platforms only).
Allows the user to resume the installation process from the point where it was terminated, through the built-in resumability feature of the installer.
Note: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.
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:
Oracle Management Service
Oracle Management Agent
Note: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
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:
|Oracle Enterprise Manager Repository Database||
|Oracle Enterprise Manager Grid Console||
|Oracle Management Agent||
Note:Depending on the installation type you have chosen, any or all of the configuration tools listed in the preceding table will be run.
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.
Note:If Enterprise Manager is the first Oracle product that you are installing, you will also be prompted to execute
orainst Root.shalong with
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.
The new Enterprise Manager 10g installer provides a secure Grid Control environment that is immediately ready to use.
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|
Note:On Microsoft Windows, the services are started automatically by the operating system.
In Enterprise Manager Grid control 10.2.0.3.0, 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 10.2.0.3.0, 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 (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 10.2.0.2.0 onwards.
The Enterprise Manager 10g R2 installer's enhanced Graphical User Interface (GUI) provides for a more user-friendly installation experience.
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.
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.
This screen has been removed. You can now select the required languages by clicking Product Languages in the Installation Location screen.
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.
Note: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.