Skip Headers
Oracle® Enterprise Manager Grid Control Installation and Basic Configuration
10g Release 3 (10.2.0.3.0)

Part Number B40103-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

3 Installing Enterprise Manager

This chapter describes the installation options available for Enterprise Manager, and provides basic instructions for installing using Oracle Universal Installer. This chapter contains the following sections:

Accessing the Installation Software

The Oracle Enterprise Manager Grid Control software is available on a DVD-ROM, or you can download it from the Oracle Technology Network (OTN) Web site. You can access and install Enterprise Manager Grid Control by using the following scenarios:

Installing from a Remote DVD Drive (UNIX Only)

If the computer where you want to install Enterprise Manager does not have a DVD drive, you can perform the installation from a remote DVD drive by mounting (sharing) that DVD drive.

Setting the Mount Point for the DVD-ROM on Linux

On most Linux systems, the disk mounts automatically when you insert it into the disk drive. To mount the disk, complete the following steps:

  1. Insert the Oracle Enterprise Manager DVD into the disk drive.

  2. To verify if the disk is automatically mounted, enter the following command:

    • On Red Hat Enterprise Linux:

      # ls /mnt/cdrom
      
      
    • On SUSE Linux Enterprise Server:

      # ls /media/cdrom
      
      
  3. If the command in step 2 fails to display the contents of the disk, enter the following command:

    • On Red Hat Enterprise Linux:

      # mount -t nfs <host name>:/mnt/<full path to the dvdrom>
      
      
    • On SUSE Linux Enterprise Server:

      # mount -t nfs <host name>:/media/<full path to the dvdrom>
      

Setting the Mount Point for the DVD-ROM on AIX

On most AIX systems, the disk mounts automatically when you insert it into the disk drive. To manually mount the disk, complete the following steps:

  1. Switch the user to root user by executing the following command:

    $ su -root
    
    
  2. If required, enter a command similar to the following to eject the currently mounted disk and to remove it from the drive:

    # /usr/sbin/umount /<SD_DVD>
    
    
  3. Insert the disk into the drive.

  4. Enter a command similar to the following:

    # /usr/sbin/mount -rv cdrfs /dev/cd0 /SD_DVD
    
    

    In this example command, /SD_DVD is the disk mount point directory and /dev/cd0 is the device name for the disk device.

  5. If Oracle Universal Installer displays the Disk Location dialog box, enter the disk mount point directory path. For example: /SD_DVD

Installing on Remote Computers Using Remote Access Software

Consider a scenario where the remote computer has the hard drive and will run Enterprise Manager, but you do not have physical access to the computer. You can perform the installation on the remote computer, provided it is running remote access software such as VNC or Symantec pcAnywhere. You also need the remote access software running on your local computer.

You can install Enterprise Manager on the remote computer in one of two ways:

  • If you have copied the contents of the Oracle Enterprise Manager Grid Control DVD to a hard drive, you can install from the hard drive.

  • You can insert the DVD into a drive on your local computer, and install from the DVD.

Installing from a Hard Drive

If you have copied the contents of the Oracle Enterprise Manger DVD to a hard drive, you can install from the hard drive. The steps that you need to complete are the following:

  1. Ensure the remote access software is installed and running on the remote and local computers.

  2. Share the hard drive that contains the Oracle Enterprise Manager DVD.

  3. Map a drive letter on the remote computer to the shared hard drive. You would use the remote access software to do this on the remote computer.

  4. Run Oracle Universal Installer on the remote computer using the remote access software. You can access Oracle Universal Installer from the shared hard drive.

For more information on running the installer, see Chapter3, "Starting the Installer" for more information.

Installing from a Remote DVD Drive

You can insert the DVD into a drive on your local computer, and install from the DVD.The steps that you need to complete are the following:

  1. Ensure the remote access software is installed and running on the remote and local computers.

  2. Share the DVD content on the local computer.

    Map a drive letter on the remote computer to the shared hard drive. You would use the remote access software to do this on the remote computer.

  3. Run Oracle Universal Installer on the remote computer using the remote access software. You access Oracle Universal Installer from the shared DVD drive.

For more information on running the installer, see Chapter3, "Starting the Installer" for more information.

Using Oracle Universal Installer

The Enterprise Manager installation uses Oracle Universal Installer, a Java-based graphical user interface application that enables you to install Oracle components from a DVD, multiple DVDs, or the Web.

See Also:

For information on using Oracle Universal Installer to install Oracle software, refer to the Oracle Universal Installer and OPatch User's Guide.

Specifying a Temporary Directory

When you start Oracle Universal Installer (OUI), it automatically copies some executable files and link files into the default /tmp directory (C:\Documents and Settings\<user ID>\Local Settings\Temp on Microsoft Windows) on the machine. If the machine is set to run cron jobs (along with many other processes that may be running) periodically, these jobs attempt to clean up the default temporary directory, thereby deleting some files and causing OUI to fail.

If there are any cron jobs or processes that are automatically run on the machines to clean up the temporary directories, ensure you set the TMP or TEMP environment variable to a different location (than the default location) that is secure on the hard drive (meaning a location on which the cleanup jobs are not run). Also ensure that you have write permissions on this alternative TEMP directory. This must be done before you execute runInstaller (setup.exe on Microsoft Windows).

Note:

Specifying an alternative temporary directory location is not mandatory, and is required only if any cron jobs are set on the computers to clean up the /tmp directory.

Starting the Installer

Start Oracle Universal Installer by executing the runInstaller (or setup.exe on Microsoft Windows) from the top-level directory of the DVD.

Alternatively, you can change the directory to the Parent Directory (or the root directory) where you will install the Oracle home, then specify the full path to /runInstaller (setup.exe on Microsoft Windows).

To specify a response file for a silent installation, use the following command:

$ ./<runInstaller or setup.exe> -responseFile <responsefile_location> <optional_parameters> -silent

See Also:

Refer to the Creating and Customizing Response Files chapter of the Oracle Universal Installer and OPatch User's Guide for more information on silent installations.

When you invoke the installer, the installation runs prerequisite checks on the following:

  • Operating System Version

  • Operating System Packages

  • Operating System Patches

  • User Credentials

  • TEMP and SWAP space

  • DISPLAY Colors

  • Additional Patches

  • Kernel version

  • Oracle home is empty

  • Oracle home space

  • Physical memory

The list of prerequisite checks that must be executed can be viewed in the initialization parameters file located in the following directory of the product-specific installation:

<DVD>/install/oraparam.ini

If a prerequisite check fails, you are prompted to continue, or stop the installation process. You may install the missing software at this point, or discontinue the installation. Note, however, that you may have newer patches that supersede the required patches.

Once you continue, follow the installation instructions on the screen. At any time while installing Enterprise Manager, you can click Help for information about the pages.

Enterprise Manager Installation Types

This section contains the following topics:

The following predefined installation options, described in Table 3-1, determine which components will be installed on your system. During installation, you are prompted to choose one of the following options. Note that the hard disk space represents the footprint that the components of the installation consume, and the physical memory prerequisites refer to the initial RAM required for installation, and not the operating memory.

Table 3-1 Enterprise Manager Installation Options

Installation Option Description Hard Disk Space (Oracle Homes) Physical Memory

Enterprise Manager 10g Grid Control Using a New Database

Installs Enterprise Manager Grid Control onto the host machine, creating the Management Repository on a new Enterprise Edition Oracle Database 10g Release 1 (10.1.0.4).

Note: Enterprise Manager Grid Control consists of the Management Repository, Management Service, Management Agent, and OracleAS J2EE and Web Cache, against which the middle-tier Management Service Web application is deployed.

  • 4.5 GB (Linux/Solaris)

  • 9GB (HP-UX)

  • 4.5 GB (Win)

  • 9 GB (AIX)

  • 2 GB (Linux/Sola-ris)

  • 2 Gb (HP-UX)

  • 2 GB (Win)

  • 2 GB (AIX)

Enterprise Manager 10g Grid Control Using an Existing Database

Installs Enterprise Manager Grid Control onto the host machine, creating the Management Repository on a qualified existing database, which may be local to the host or remote. See Chapter1, "Management Repository Software Requirements" for more information on supported repository releases.

Note: If the repository is on the same machine as the Management Service, allow 1 GB more memory than recommended.

Oracle recommends installing Enterprise Manager on a separate machine from the Oracle Database that contains the Management Repository.

  • 2.5 GB (Linux/Solaris)

  • 5 GB (HP-UX)

  • 2.5 GB (Win)

  • 5 GB (AIX)

  • 2 GB (Linux/Sola-ris)

  • 2 GB (HP-UX)

  • 2 GB (Win)

  • 2 GB (AIX)

Additional Management Service

Installs the Management Repository onto the host machine. Allows you to specify an existing Management Repository, either local or remote.

  • 2 GB (all UNIX platforms)

  • 2.5 Gb (Win)

  • 2 GB (all UNIX platforms)

  • 2 GB (Win)

Additional Management Agent

Installs the Management Agent on the target machine you want to monitor with the Grid Control console. The Management Service and Management Repository are not required on the same machine as the Management Agent, but must exist within the enterprise.

The Management Agent may be installed on a cluster node. Oracle recommends that the target host on which you are installing the agent have a static IP address and not DHCP.

  • 400 MB (all UNIX platforms)

  • 500 MB (Win)

No minimum requirement


Note:

When you perform an Enterprise Manager installation, this installation does not include Enterprise Manager Configuration Plug-in (EMCP) in the database Oracle home. EMCP is part of the repository database Oracle home only when you perform a standalone database installation.

See Also:

Refer to Oracle Enterprise Manager Concepts for more detailed information about the Grid Control Console, the Management Repository, Management Service, and Management Agent, and how they work together.

See Chapter 4, "Enterprise Manager Silent Installations" for more information.

Installation Instructions

Start Oracle Universal Installer by executing the runInstaller script in Linux (<DVD>/runInstaller).

On Microsoft Windows, execute <DVD>/setup.exe to start the Oracle Universal Installer.

Installation types are predefined component sets that determine which components to install. The Enterprise Manager 10g Grid Control installation involves four top-level components, each representing an installation type. Select one of the installation types described in the following sections.

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. If you choose this installation option, you do not need an existing Enterprise Edition database, because one is created during the installation.

Note:

The default port for the listener is 1521 for the Oracle Database 10g R2 (10.2.0.2) provided with the full installation.

Permissions and 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.

    Caution:

    Do not pass the argument as ORACLE_HOSTNAME=<localhost.localdomain> or ORACLE_HOSTNAME=<IP address>. You must pass the argument as ORACLE_HOSTNAME=<valid host name>.

To Install Enterprise Manager Using a New Database

Complete the following steps to perform an Enterprise Manager installation using a new database:

  1. Select the first option (Enterprise Manager 10g Grid Control Using a New Database). By default, this option is selected when you invoke the installer.

    Figure 3-1 Specify Installation Type

    Select the Installation Type in this page.
  2. Click Next. In the Specify Installation Location screen that appears, specify a parent directory (base directory), for example, /scratch/OracleHomes (on Linux), for the new installation. All the Oracle homes created during this installation are created as subdirectories under this parent directory. For example: db10g, oms10g, and agent10g.

    Note:

    Ensure you do not use symbolic links to specify the Oracle home path.

    Figure 3-2 Specify Installation Location

    Specify the Installation location in this page.

    The selected products are installed in the English language by default. If you want to install the product in a different language, click Product Languages.

    The Language Selection screen appears.

    Figure 3-3 Language Selection

    Select the required product languages.

    Choose the languages that you want to use to run Enterprise Manager.

    Note:

    The languages that you select here change the language of Enterprise Manager only, and not the language of the installation itself.
  3. Click Next. The Specify Inventory Directory and Credentials screen appears only if Enterprise Manager Grid Control is the first Oracle product that you are installing on the machine.

    Figure 3-4 Specify Inventory Directory and Credentials

    Specify the Inventory Directory and Credentials.
    1. Specify the full path to the directory where Oracle Universal Installer (OUI) should place inventory files and directories. For example, oracle_base/oraInventory (on Linux).

      Note:

      If you are performing the installation on a Microsoft Windows platform, the Specify Inventory Directory and Credentials screen will not appear.

      On Microsoft Windows, the default inventory files location is <system drive>\Program Files\Oracle\Inventory.

      Refer to the Enterprise Manager online Help for more information on guidelines recommended by Oracle for naming the directories.

    2. Select the appropriate operating system group name that will own the Oracle inventory directories. The group that you select must have write permissions on the Oracle Inventory directories.

  4. Click Next. The Product-Specific Prerequisite Checks screen appears.

    Figure 3-5 Product-Specific Prerequisite Checks

    Specify Product-specific Prerequisite Checks

    At this point, the installer runs some prerequisite checks to verify if the environment meets the minimum requirements for a successful Enterprise Manager installation.

    Early detection of system environment problems such as insufficient disk space, missing patches, inappropriate hardware, and so on results in a smoother installation later.

    This screen displays the name, type, and status for all prerequisite checks designed for the installation. Automatic checks are run first, followed by optional and manual checks.

    Depending on the status of the automatic checks, you must verify all warning and manual checks. At some point, if you have stopped the prerequisite check and want to rerun these checks, select the checks that you want to rerun and click Retry. As each check runs, a progress bar is shown, and test details (expected results, actual results, error messages, instructions) are displayed in the details section at the bottom of the screen.

    Note:

    You can also run these prerequisite checks in standalone mode, prior to starting the runInstaller. See Chapter1, "Running the Prerequisite Check in Standalone Mode" for more information.
    1. To stop all prerequisite checks, click Stop. At any point in time, click a prerequisite check to view its corresponding details, including the recommended user actions.

      Note:

      You must manually verify and confirm all checks that were flagged with a warning, skipped (stopped by user), or failed.
    2. To continue with the installation without retrying, click Next.

      An error message is displayed if some recommended prerequisite checks have failed.

      Figure 3-6 Warning

      Error Message if recommended prereq checks have failed.
    3. Click No to go back and rerun the prerequisite check. Click Yes to ignore the message and continue with the installation.

      Note:

      It is recommended that you retry checks that were flagged with warnings, failed, or were skipped (stopped by the user) before continuing with the installation.
  5. The Specify Configuration screen appears.

    Figure 3-7 Specify Configuration

    Specify Configuration

    You must specify the configuration details for the new database that you are creating, and select the appropriate recipients of the OSDBA and OSOPER privileges (on UNIX only).

    Note:

    Your Management Repository may also require patches to be applied after successful installation. See Chapter1, "Enterprise Manager Platform and Target Certification Requirements" for more information.
    1. Specify the new Database Name and the Database File Location (location where the new database is going to reside).

      Note:

      It is recommended that you specify a fully qualified database name (for example, emrep.<domain_name>), though appending the database name with the domain name is not mandatory.
    2. In the Group Specification section, select the OSDBA and OSOPER groups of which you are a member. These memberships are required to grant the SYSDBA and SYSOPER permissions that are, in turn, required to create the new database using the operating system authentication.

  6. Click Next. The Specify Optional Configuration screen appears.

    Figure 3-8 Specify Optional Configuration

    Specify Optional Configuration

    As the name suggests, all the fields on this screen are optional, and are disabled by default. Select the required check box to enable the corresponding fields.

    1. In the Configure Email Notification section, specify an appropriate e-mail address, and the corresponding SMTP server name. You will receive important information on the condition of the monitored targets, including critical alerts at this e-mail address.

      The e-mail address that you specify should be associated with the SYSMAN user to receive notifications.

      The SMTP Server is the name of the mail server (for example mail.acme.com). For Linux, the default SMTP server is the local host name. Use the fully qualified host name (including domain).

      Note:

      If you do not provide the e-mail notification information, this feature is not enabled upon installation. You may also choose to configure these settings through the Enterprise Manager console by clicking Notification Methods under Setup. Refer to the Enterprise Manager online Help for more information.
    2. Specify the OracleMetaLink credentials.

      If you prefer, you can also enter this information through the Enterprise Manager console after installation by clicking Patching Setup, under Setup.

      Note:

      Enterprise Manager uses these credentials to search for and download patches from http://oracle.com/support/metalink/index.html
    3. Specify the Proxy Information if Enterprise Manager is using a proxy server for external access. Table 3-2 describes each of the fields under this section.

      Table 3-2 Specify Proxy information - Input Fields

      Input Description

      Proxy Server

      Specify the proxy server host name. For example, www-fooproxy.here.com

      Port

      Specify the port at which the server is listening. For example, 80. See Appendix E, "Enterprise Manager Firewall Port Requirements" for more information on specifying ports when you are using a firewall in your grid environment.

      Do Not Proxy For

      Specify the URLs that do not need the proxy server to be accessed. You can specify multiple comma-separated values. For example, .here.com, .us.mycompany.com, .uk.mycompany.com, and so on.

      Note that you must always specify fully qualified host names.

      Proxy User and Password

      Specify the user name and password only if the proxy server has been configured to use these credentials for authentication. These are optional fields.

      Realm

      Specify an appropriate realm value. This becomes a mandatory field only if the proxy server credentials have been configured using a realm.

      A realm is a string value assigned by the proxy server to indicate the secure space that requires authentication.

      Test Proxy

      Click this button to verify your proxy server settings.


      Note:

      When you search for a patch, if the proxy properties (saved in the sysman/config/emoms.properties file) are not set, or are set incorrectly, you receive an error message indicating that Enterprise Manager cannot access the OracleMetaLink Web site.

      Caution:

      If the proxy server requires user authentication before providing access, you must specify these credentials here or through the Patching Setup screen under Setup in the Grid Control console.
  7. Click Next. The Specify Security Options screen appears.

    Figure 3-9 Specify Security Options

    Specify Security Options

    You must specify the passwords that are used to secure your entire Grid Control environment. This screen has two sections - Management Service Security, and Repository Database Passwords.

    • Management Server Security: The password that you specify here is used to secure and lock the Oracle Management Service (OMS).

      Select Require Secure Communications for all agents if you want the secure OMS to communicate only with secure Management Agents. This is optional, though recommended.

      For example, consider you have unsecured 10.1.n agents in the Grid and you have secured the OMS. Now, if you select the Require Secure Communications option, then all communication between the 10.2 OMS and 10.1.n agents fails (because these agents have not been secured).

      Note:

      To secure a Management Agent, execute following command:
      <AGENT_HOME>/bin/emctl secure agent
      
    • Repository Database Passwords: Specify the passwords for each of the administrative database accounts listed in Table 3-3.

      Table 3-3 Repository Database Passwords

      User Account Applies to Description

      SYS

      Management Repository

      Super Administrator for the Management Repository database.

      SYSTEM

      Management Repository

      Administrator for the Management Repository database.

      DBSNMP

      Management Repository

      Monitoring user for the Management Repository database.

      SYSMAN

      Management Repository, Application Server, and Grid Control

      The default Grid Control Super Administrator and Owner of the Management Repository database schema and the Grid Control application user.

      The default ias_admin password is the same as the password assigned to the SYSMAN account. This is required to access the Oracle application server (ias_admin). The ias_admin user is the administrative user for the Oracle Application Server console.


      You can use the same password for all four accounts, or specify a different password for each one. These passwords are used to secure the Management Repository database.

      To specify a different password for each account, select Use different passwords for these accounts and specify the passwords for each account.

      To specify the same password for all accounts, select Use the same password for all accounts and specify one password to be used for all database accounts.

      Note:

      The SYS, SYSMAN, DBSNMP, and SYSTEM users are privileged database users. You must remember the passwords that you specify for them. For more information on password restrictions and recommendations, see Oracle Database Administrator's Guide.

      Password Restrictions and Recommendations

      The following restrictions apply to passwords:

      • Passwords must be between 5 and 30 characters long.

      • Passwords should not start with a number.

      • Passwords cannot be the same as the user name.

      • Passwords must include letters (lowercase/uppercase) and numbers only.

        Note:

        The SYSMAN password can include underscores (_), and hyphens (-), dollar ($), and hash (#) along with alphanumeric characters. Alphabetic characters can be uppercase or lowercase.
      • Passwords cannot be Oracle reserved words. See Appendix G, "Oracle Reserved Words" for more information.

      Note:

      Oracle recommends that the passwords you specify have the following characteristics:
      1. Have at least one letter, one integer, and one special character (underscore).

      2. Are not simple or obvious words such as welcome, account, database, or user.

  8. Click Next. The Summary screen appears.

    Figure 3-10 Installation Summary

    Installation Summary

    This screen provides a summary of the options that you have selected during the installation process. Depending on the installation type, it also provides any or all of the following details:

    • Global Settings

    • Product Languages

    • Space Requirements

    • Installed Products

    Verify the choices that you have made.

    1. Click Install to start the installation. The Install screen that appears displays the installation progress bar.

      Figure 3-11 Installation in Progress

      Installation in Progress

      The installer seamlessly installs all Grid Control components based on the installation type you selected.

    2. During the installation, you are prompted to execute certain configuration scripts. These scripts and their locations are listed in the Execute Configuration Scripts dialog box that appears (on UNIX only).

      Note:

      The Execute Configuration Scripts dialog box will not appear on Microsoft Windows. You will be directed to the Configuration Assistants screen (step 9) in the next step.

      Figure 3-12 Execute Configuration Scripts

      Execute Configuration Scripts

      Go to the computer window, log in as root, and run these configuration scripts.

    3. Return to the dialog box (shown in Figure 3-12) after executing the scripts, and click OK to continue the installation.

  9. The Configuration Assistants screen appears. At this point, the installer starts running the configuration assistants.

    Figure 3-13 Configuration Assistants

    Configuration Assistants

    This screen displays the name, status, and the type of each configuration tool that Oracle recommends to be run before completing the installation.

    Table 3-4 lists all the configuration tools that are run during a typical Enterprise Manager installation (Install Enterprise Manager Using a new database).

    Table 3-4 Enterprise Manager Configuration Tools

    Product Configuration ToolFoot 1 

    Oracle Repository Database

    • Oracle Net Configuration Assistant

    • Oracle Database Configuration Assistant

    • OC4J Configuration Assistant

    Oracle Enterprise Manager Grid Console

    • OC4J Configuration Assistant

    • HTTP Server Configuration Assistant

    • Java Configuration Assistant

    • Web Cache Configuration Assistant

    • OracleAS Instance Configuration Assistant

    • Register DCM Plugins with Enterprise Manager

    • DCM Repository Backups Assistant

    • Enterprise Manager Technology Stack Upgrade

    • Oracle Management Service Configuration

    Oracle Management Agent

    • Agent Configuration Assistant


    Footnote 1 Depending on the installation type that you have selected, any or all of the configuration tools listed in this table will be run.

    For more information on the installation logs that are created and their locations, see Appendix F, "Installation and Configuration Log File Locations". In case of failure of any configuration assistant, refer to the logs and re-rerun the configuration assistants as described in AppendixA, "Configuration Assistants Fail During Enterprise Manager Installation".

    Note:

    The individual log files for each configuration tool are available at the following directory:
    ORACLE_HOME/cfgtoollogs/cfgfw
    
    

    Besides the individual configuration logs, this directory also contains cfmLogger_timestamp.log (The timestamp depends on the local time and has a format such as cfmLogger_2005_08_19_01-27-05-AM.log.). This log file contains all the configuration tool logs.

    1. To stop running a configuration tool, select it and click Stop.

    2. To rerun a configuration tool, select it and click Retry.

      Note:

      The installation is considered successful even if all the configuration tools fail, irrespective of their type (recommended/optional). However, failing to successfully run all the configuration tools results in an improperly configured product, which may not function. Refer to the Enterprise Manager installation online Help for more information.

      Note:

      In the event a particular configuration assistant fails, you can choose to rerun only that configuration assistant (in standalone mode). See Chapter3, "Executing the runConfig Tool from the Command Line" for more information.
  10. After successfully running all the recommended configuration tools, the End of Installation screen appears.

    This screen displays some important information about the products you have installed. This information is also available in the <AGENT_HOME>/sysman/setupinfo.txt file.

    For example, it might contain information about the URLs for particular Web applications.

Installing Enterprise Manager 10g Grid Control Using an Existing Database

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. The 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. See Table 3-1, "Enterprise Manager Installation Options" for more information on the recommended hard disk and memory requirements. See Chapter1, "Recommended CPU and Memory Allocation" for more information.

  • 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.

    Caution:

    Do not pass the argument as ORACLE_HOSTNAME=<localhost.localdomain> or ORACLE_HOSTNAME=<IP address>. You must pass the argument as ORACLE_HOSTNAME=<valid host name>.

See Chapter3, "Check Database Initialization Parameters" for a detailed list of database initialization parameter settings based on the Enterprise Manager deployment size.

Chapter1, "Enterprise Manager Software Requirements" includes information on the releases of Oracle Database and Oracle Real Application Clusters Database that qualify for Management Repository creation.

See Chapter 1, "Preinstallation Requirements" for more information on hardware and software requirements.

Check Database Initialization Parameters

The initialization parameters must be set correctly for your qualified existing Enterprise Edition database to be able to run a Management Repository. You should also set all fixed parameters for your Management Repository database.

See Also:

For more information about managing initialization parameters, refer to the Managing Initialization Parameters Using a Server Parameter File chapter of the Oracle Database Administrator's Guide.

After making the changes, you must shut down and restart the database.

See Also:

For instructions on shutting down the database, refer to the Starting Up and Shutting Down chapter in the Oracle Database Administrator's Guide.

Fixed Initialization Parameter Values

The following table lists the parameters and their fixed values that must be met for successful Management Repository database creation. These parameters are verified by Oracle Universal Installer prerequisite checks during installation.

Note:

Make sure that the Enterprise Edition database you select for your Management Repository has the fine-grained access control option set to true. This is required for successful Management Repository creation. Check v$options for this setting.

Table 3-5 Fixed Initialization Parameter Values

Parameter Value

job_queue_processes

10

db_block_size

8192

timed_statistics

TRUE

open_cursors

300

session_cached_cursors

200

aq_tm_processesFoot 1 

1

compatible

<currently installed Oracle Database release> (default)

undo_management

AUTO

undo_retention

10800

undo_tablespace

<any acceptable name>

processes

150

log_buffer

1048576

statistics_level

TYPICAL (Note that this value is specific only to Enterprise Manager 10g Repository Database release and later.)

TEMP space (Tablespace)Foot 2 

50 MB (extending to 100 MB)

_b_tree_bitmap_plans

false (hidden parameter)


Footnote 1 Setting the aq_tm_processes parameter is not a prerequisite if you are using a 10.n Oracle Database.

Footnote 2 The TEMP space is an initialization parameter only when you are performing an Enterprise Manager installation using a new database.

Variable Initialization Parameter Values

The variable parameter setting values are based on the size of the Enterprise Manager Grid Control environment. For the sake of clarity, the environment has been categorized as Small, Medium, and Large based on the number of targets in the environment, where:

  • Small = Approximately 100 monitored targets

  • Medium = Approximately 1000 monitored targets

  • Large = 10000 or more monitored targets

Table 3-6 lists the variable parameter setting values.

Table 3-6 Variable Initialization parameter Values

Size pga_aggregate_target Redo logsFoot 1  db_cache_size (for 91 rep. DB) shared_pool_size (for 91 rep. DB) sga_target (for 10g rep. DB)Foot 2 

Small

256 MB

100 MB

384 MB (or more)

128 MB

512 MB (or more)

Medium

384 MB

512 MB

1024 MB (or more)

384 MB

1408 MB (or more)

Large

512 MB

1024 MB

2048 MB (or more)

512 MB

2560 MB (or more)


Footnote 1 One redo log group with four members each of the listed size

Footnote 2 This new setting replaces settings for db_cache_size and shared_pool_size from Oracle9i.

NLS_LANG Environment Variable

If your operating system is Linux, ensure the NLS_LANG environment variable is set with a value that is compatible with the operating system default locale setting and the Management Repository database character set. For information on the specific values for language, territory, or character set, refer to the Globalization Support Guide of the Oracle product that you are using.

A Typical Installation Scenario

If you choose to install Enterprise Manager using an existing database, you must provide the location of an existing database where the installer will create the repository. Here again, the database should be of release 9.2.0.6 and later, or 10.1.0.4 and later. If you have an earlier database release installed, you must first upgrade this database instance to the specified minimum release (9.2.0.6 and later, or 10.1.0.4 and later) and then proceed with the Enterprise Manager installation.

To Install Enterprise Manager Using Existing Database

Complete the following steps to install Enterprise Manager using an existing database:

  1. Start Oracle Universal Installer by running the runInstaller script in Linux (<DVD>/runInstaller) from the top directory of the DVD.

  2. In the Specify Installation Type screen, select the second option (Enterprise Manager 10g Grid Control Using an Existing Database). Click Next.

    Figure 3-14 Specify Installation Type

    Select the appropriate installation option.
  3. The Specify Installation Location screen appears.

    1. Specify the full path to the parent directory (base directory), for example, /scratch/OracleHomes. All the Oracle homes created during the installation are placed as subdirectories under this parent directory. For example: oms10g, and agent10g.

      Caution:

      Do not use symbolic links to specify the Oracle home path.

      The installer by default installs the selected products in the English language.

    2. If you want to install the product in a different language, click Product Languages.

      The Language Selection screen appears. Make the required language selections here, and click Next. See Figure 3-3, "Language Selection" for details.

  4. Click Next. The Specify Inventory Directory and Credentials screen appears if Enterprise Manager is the first Oracle product that you are installing on the machine. See Figure 3-4, "Specify Inventory Directory and Credentials" for details.

  5. Click Next. The Product Specific Prerequisites Check screen appears.

    This screen displays the name, type, and status for all prerequisite checks designed for the installation. Automatic checks are run first, followed by optional and manual checks.

    Depending on the status of the automatic checks, you must verify all warning and manual checks. At some point, if you have stopped the prerequisite check and want to rerun these checks, select the checks that you want to rerun and click Retry. As each check runs, a progress bar is shown, and test details (expected results, actual results, error messages, instructions) are displayed in the details section at the bottom of the screen. See Figure 3-5, "Product-Specific Prerequisite Checks" for details.

    Note:

    You can also run these prerequisite checks in standalone mode, prior to starting the runInstaller. See Chapter1, "Running the Prerequisite Check in Standalone Mode" for more information.
  6. Click Next. The Specify Repository Database Configuration screen appears.

    Figure 3-15 Specify Repository Database Configuration

    Specify Repository Database Configuration

    Specify the connection details for the existing database in which the Management Repository should be created. 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

      Note:

      If you are performing an Enterprise Manager Grid control installation using an existing database, ensure the database is of a 10.1.0.3 release or later.
    • Oracle Real Application Clusters 10g Release 1 (10.1.0.4 and later)

      Note:

      If you are performing an Enterprise Manager Grid control installation using an existing database, ensure the existing Oracle RAC database is of a 10.1.0.3 release or later.
    • Oracle9i Release 2 (9.2.0.6 and later), Enterprise Edition

    • Oracle9i Real Application Clusters Release 2 (9.2.0.6 and later)

    1. In the Database Connection Details section, specify a fully qualified host name, listener Port number, SID (system identifier) for the database instance, and the SYS password.

      The SID identifies a specific Oracle Database and distinguishes it from other databases on the computer.

      Note:

      When selecting an existing cluster database for creating the Management Repository, you can either specify the SID value, or use the Management Service name.
    2. Enter the password for the SYS user. This account is used to create the SYSMAN user, which is the primary owner of the Management Repository schema.

    3. In the Additional Tablespace section, specify the location for the following:

    • Management Tablespace Location: The MGMT_TABLESPACE tablespace holds data for the Management Repository.

    • Configuration Data Tablespace Location: The MGMT_ECM_DEPOT_TS tablespace holds Configuration Management data for the Management Repository.

    Caution:

    If the existing database that you have selected to create the repository already contains a SYSMAN schema, the installer will display an error similar to the following:

    "The Grid Control schema already exists in the database that you have provided."

    You can choose to manually drop this schema before proceeding with the repository creation.

    You can also click Continue. The installer will then automatically drop the existing schema and create a new SYSMAN schema.

    For ASM (Automatic Storage Management) devices, the tablespace locations should be specified relative to the ASM disk group. For example: +<ASM Disk>/emrep/tablespace.dbf

    For tuning/performance reasons, Oracle recommends placing Binary large objects (BLOBs) in their own tablespace. Because Enterprise Configuration Management data support BLOBs, the Management Repository requires two tablespaces: MGMT_TABLESPACE and MGMT_ECM_DEPOT_TS.

    Specify the full path of the file locations for the previously mentioned tablespaces. The directories you specify for these tablespaces must already exist for repository creation to succeed. For raw devices, you must partition your disk before specifying its location. Note that raw device path names vary across volume managers. Ensure to use the right path format for your raw device locations.

    If you do not have the complete path for the tablespaces, click Prefill Tablespace Location. Note that the Prefill Tablespace button will be enabled only after you have specified all the Database Connection details. The installer then queries the database you have specified. Look for the SYSAUX tablespace location, and prefill that path in the appropriate box.

    Note:

    • The two tablespaces initially require 120 MB of disk space, with MGMT_TABLESPACE requiring 20 MB and MGMT_ECM_DEPOT_TS requiring about 100 MB. Ensure there is enough disk space available.

    • If you are selecting an existing cluster database for the new Management Repository, the management tablespace file locations must be on a shared device that is accessible to all instances that provide the database service.

    Caution:

    If the DBMS_SHARED_POOL package has not been installed at the time of the database creation, Oracle Universal Installer displays an error message and prompts you to execute this package before proceeding with the installation.

    To check whether or not the DBMS_SHARED_POOL package has been installed, login to the database and execute the following query:

    Select count(*) from dba_objects where OWNER = 'SYS' 
    AND object_name = 'DBMS_SHARED_POOL' 
    AND object_type IN ( 'PACKAGE','PACKAGE BODY') ;
    
    

    This query should return a count of 2.

    To install the DBMS_SHARED_POOL package, execute the following script:

    <DB_HOME>/rdbms/admin/dbmspool.sql
    
  7. Click Next. The Specify Optional Configuration screen appears.

    As the name suggests, all the fields on this screen are optional, and are disabled, by default. Select the required check box to enable the corresponding fields.

    1. In the Configure Email Notification section, specify an appropriate e-mail address, and the corresponding SMTP server name in this section. You will receive information on important developments and events in Grid Control, including critical alerts, at this e-mail address.

      The e-mail address that you specify should be associated with the SYSMAN user to receive notifications.

      The SMTP server is the name of the mail server (for example mail.acme.com). For Linux, the SMTP server must be the local host name. Use the fully qualified host name (including domain).

      Note:

      If you do not provide the e-mail notification information, this feature is not enabled upon installation. You may also choose to configure these settings through the Enterprise Manager console by clicking Notification Methods under Setup. Refer to the Enterprise Manager online Help for more information.
    2. Specify the OracleMetaLink credentials if you are going to use a proxy server to access OracleMetaLink.

      If you prefer, you may also enter this information through the Enterprise Manager console after installation by clicking Patching Setup, under Setup.

      Note:

      Enterprise Manager uses the OracleMetaLink credentials to search for and download patches from http://oracle.com/support/metalink/index.html
    3. Specify the Proxy Information if Enterprise Manager is using a proxy server for external access. See Table 3-2, "Specify Proxy information - Input Fields" for a description on each of the input fields in this section.

      Note:

      If the proxy server requires user authentication before providing access, you must specify these credentials here, or through the Patching Setup screen under Setup in the Grid Control console.
  8. Click Next. The Specify Passwords screen appears.

    Figure 3-16 Specify Passwords

    Specify Mgmt Service security passwords
    1. Specify the Management Service Security, and Repository Database passwords that are used to secure your entire Grid Control environment.

    2. Select Require Secure Communications if you want the secure OMS to communicate only with Secure Agents. This is optional, though recommended.

      For example, if you have 10g R1 (10.1.n) agents in the Grid environment and you have secured and locked the Oracle Management Service (OMS), and selected the Require Secure Communications option, then all communication between the 10g R2 (10.2) OMS and 10.1 agents fails (because these agents have not been secured).

      To secure an agent, execute the following command from the agent Oracle home of that particular target:

      emctl secure agent
      
      

      See the section on Password Restrictions and Recommendations in this chapter for more information.

  9. Click Next. The Summary screen appears.

    This screen provides a summary of the options that you have selected during the installation process. Depending on the installation type, this screen also provides any or all of the following details:

    • Global Settings

    • Product Languages

    • Space Requirements

    • New Installations

    • Installed Products

    Verify the choices that you have made and click Install to start the installation. The Install screen that appears displays the installation progress bar.

    The installer seamlessly installs all Grid Control components based on the installation type you selected.

  10. During the installation, you are prompted to execute certain configuration scripts. These scripts and their locations are listed in the Execute Configuration Scripts dialog box that is displayed (only on UNIX). Refer to Figure 3-12, "Execute Configuration Scripts".

    1. To execute these scripts, go to the computer window, log in as root, and run these configuration scripts.

    2. Return to the Execute Configuration Scripts dialog box after executing the scripts, and click OK to continue the installation.

  11. The Configuration Assistants screen appears. At this point, the installer starts running the recommended Configuration Assistants.

    Note:

    The OMS Configuration Assistant will create the repository. The repository creation log (emca_repos_create<TimeStamp>.log For example, emca_repos_create05_13_33.log) is available at the following directory:
    OMS_HOME/sysman/log/
    

    This screen displays the name, status, and the type of each configuration tool that Oracle recommends to be run before completing the installation. Refer to Table 3-4, "Enterprise Manager Configuration Tools" to see the list of configuration tools that are run. In case of failure of any configuration assistant, refer to the logs and re-rerun the configuration assistants as described in AppendixA, "Configuration Assistants Fail During Enterprise Manager Installation".

  12. After successfully running all the recommended configuration tools, the End of Installation screen appears.

    This screen tells you whether or not the installation was successful, and displays some important information that you must remember about the products you have installed. For example, it might contain information about the URLs for particular Web applications.

Configuration Assistant

During the installation process, if the SYSMAN schema already exists in the database that you specify for the Management Repository, the installer will prompt you to manually drop the schema. If this is not done, the installer will automatically drop the schema before proceeding to the next configuration assistant.

If the Oracle Management Service Configuration Assistant fails before completion, you can click Retry, which automatically cleans up the repository when the configuration tool is rerun. To manually clean up the repository, use the following command:

OMS_HOME/sysman/admin/emdrep/bin/RepManager <Host name> <Port> <SID> -ACTION Drop

You may need to set the LD_LIBRARY_PATH to the Management Service's ORACLE_HOME/lib directory before running the script.

Refer to Oracle Enterprise Manager Advanced Configuration for further instructions on how to drop the existing repository from the database.

Note:

The listener that is associated with the specified database must be running. Otherwise, Management Repository creation may fail.

Installing an Additional Management Service

Select this option if you need to add an additional Management Service to your environment. Note that setting credentials for OracleMetaLink is not necessary for this installation type, as the Management Repository is not affected.

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. See Table 3-1, "Enterprise Manager Installation Options" for more information.

  • 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.

Caution:

Do not pass the argument as ORACLE_HOSTNAME=<localhost.localdomain> or ORACLE_HOSTNAME=<IP address>. You must pass the argument as ORACLE_HOSTNAME=<valid host name>.

See Also:

Refer to the Reconfiguring the Management Agent and Management Service chapter of the Oracle Enterprise Advanced Configuration Guide for more information on controlling the Management Service.

See Appendix G, "Assigning Custom Ports" for more information on assigning port numbers for Enterprise Manager components.

To Install an Additional Management Service

Complete the following steps to install an additional Management Service:

  1. Start Oracle Universal Installer by running the runInstaller script (<DVD>/runInstaller on Linux and /DVD/setup.exe on Microsoft Windows) from the top directory of the DVD.

  2. In the Specify Installation Type screen, select the third option (Additional Management Service).

    Figure 3-17 Specify Installation Type

    Specify Installation Type
  3. In the Specify Installation Location screen, specify the full path to the parent directory (base directory), for example, /scratch/OracleHomes. The Oracle Management Service (OMS) home created during the installation is placed as a sub-directory under this parent directory. For example: oms10g.

    Figure 3-18 Specify Installation Location

    Specify Installation Location

    Note:

    Ensure you do not use symbolic links to specify the Oracle home path.

    The installer by default installs the selected products in the English language.

    1. If you want to install the product in a different language, click Product Languages.

    2. The Language Selection screen is displayed. Make the required language selections here. See Figure 3-3, "Language Selection" for details.

  4. Click Next. The Product Specific Prerequisites Check screen appears.

    This screen displays the name, type, and status for all prerequisite checks designed for the installation. Automatic checks are run first, followed by optional and manual checks.

    Depending on the status of the automatic checks, you must verify all warning and manual checks. At some point, if you have stopped the prerequisite check and want to rerun these checks, select the checks that you want to rerun and click Retry. As each check runs, a progress bar is shown, and test details (expected results, actual results, error messages, instructions) are displayed in the details section at the bottom of the screen. See Figure 3-5, "Product-Specific Prerequisite Checks" for more information.

    Note:

    You can also run these prerequisite checks in standalone mode, prior to starting the runInstaller. For more information on running these prerequisite checks in standalone mode, see Chapter1, "Running the Prerequisite Check in Standalone Mode" for more information.
  5. Click Next. The Specify Repository Database Configuration screen appears.

    Figure 3-19 Specify Repository Database Configuration

    Specify Repository Database Configuration
    1. You must configure the additional Management Service to establish the connections with the existing Management Repository.

      Note:

      The existing Management Repository database must be one of the following releases:
      • Oracle Database 10g Release 1 (10.1.0.4), Enterprise Edition

      • Oracle Real Application Clusters 10g Release 1 (10.1.0.4)

      • Oracle9i Database Release 2 (9.2.0.6 and later), Enterprise Edition

      • Oracle9i Real Application Clusters Release 2 (9.2.0.6 and later)

      The Management Repository database may also require patches to be applied, prior to successful installation. See Chapter1, "Enterprise Manager Platform and Target Certification Requirements" for more information.

    2. In the Repository Database Connection Details section, specify a fully qualified host name on which the Management Repository database is installed, the repository port, and the SID (system identifier) for the database instance.

      The SID identifies a specific Oracle database and distinguishes it from other databases on the computer.

      Note:

      When selecting an existing cluster database for creating a Management Repository, you must replace the SID value with the Management Service name.
    3. Enter the password for the SYSMAN user (the default Super Administrator account for Enterprise Manager).

    4. In the Management Service Security section, specify the password used to secure and lock the Oracle Management Service (OMS).

    5. Select Require Secure Communications for all agents if you want the secure OMS to communicate only with Secure Agents. This is optional, though recommended.

      For example, if you have 10g R1 (10.1.n) agents in the Grid environment, and you have secured the OMS and selected the Require Secure Communications option, then all communication between the Oracle Management Service 10g R2 (10.2) and Oracle Management Agent 10g R1 (10.1) fails (because these agents have not been secured).

      To secure an agent, execute the following command from the agent Oracle home of that particular target:

      emctl secure agent
      
      

      See the section Password Restrictions and Recommendations in this chapter for more information.

      Note:

      The password that you specify here must be the same as the password that you specified to secure the Management Service.

      Ensure that all Management Service instances using the same repository must use the same secure password.

  6. Click Next. The Specify Optional Configuration screen appears.

    Figure 3-20 Specify Optional Configuration

    Specify Optional Configuration

    As the name suggests, all the fields on this screen are optional, and are disabled, by default. Select the required check box to enable the corresponding fields.

    1. Select the Configure Proxy check box (optional) if Enterprise Manager is using a proxy server for external access. Specify the properties for the proxy server host name (enter a fully qualified host name), port number, Do Not Proxy for list, and the Proxy user credentials. See Table 3-2, "Specify Proxy information - Input Fields" for a description of the input fields.

    2. Specify an appropriate Realm value. This becomes a mandatory field only if the proxy server credentials have been configured using a Realm, in which case, you must specify an appropriate Realm value.

      A Realm is a string value that is assigned by the proxy server to indicate the secure space that requires authentication.

  7. Click Next. The Summary screen appears.

    This screen displays a summary of the options that you have selected during the installation process. Depending on the installation type, this screen displays any or all of the following details:

    • Global Settings

    • Product Languages

    • Space Requirements

    • New Installations

    For more information on each of the previously listed details, see the Enterprise Manager online Help.

    Verify the choices that you have made and click Install to start the installation. The installer begins installing the selected Oracle product.

  8. During the installation, you are prompted to execute certain configuration scripts. These scripts and their locations are listed in the Execute Configuration Scripts dialog box that is displayed (only for Linux). Refer to Figure 3-12, "Execute Configuration Scripts".

    1. To execute these scripts, go to the computer window, log in as root and run these configuration scripts.

    2. Return to the Execute Configuration Scripts dialog box after executing the scripts, and click OK to continue the installation.

  9. The Configuration Assistants screen appears. At this point, the installer starts running the recommended configuration tools.

    This screen displays the name, status, and the type of each configuration tool that Oracle recommends to be run before completing the installation. Refer to Table 3-4, "Enterprise Manager Configuration Tools" to see the list of configuration tools that are run. In case of failure of any configuration assistant, refer to the logs and re-rerun the configuration assistants as described in AppendixA, "Configuration Assistants Fail During Enterprise Manager Installation".

  10. After successfully running all the recommended configuration tools, click Next. The End of Installation screen appears.

    This screen tells you whether or not the installation was successful and displays some important information that you must remember about the product you have installed. For example, it might contain information about the URLs for particular Web applications.

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.

    See Also:

    Chapter 6, " Deploying the Management Agent" for a full and detailed explanation on installing Management Agents using the agentDownload script and the nfsagentinstall script.

    See Appendix G, "Assigning Custom Ports" for information on assigning custom port numbers for Enterprise Manager components.

    Caution:

    If you install the Management Agent on a system where you have already installed an Oracle Application Server instance, you must install the Management Agent from a user account that belongs to the same OS Group group that was used to install the Application Server. Otherwise, you cannot monitor the application server metrics.
    • To see which group was used to install the Application Server, type ls -l on the command line in the directory containing opmn.xml: <AS_ORACLE_HOME>/opmn/conf.

    • To see the groups to which you belong, type groups on the command line. You may be a member of several groups. Note that it is not sufficient to be a member of the group used to install the Application Server; that group must be your current group.

    • To see which user/group you are currently using, type id on the command line. Use the newgrp command to change to the group used to install the Application Server. Oracle recommends installing all software using a single group.

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.

    Caution:

    Do not pass the argument as ORACLE_HOSTNAME=<localhost.localdomain> or ORACLE_HOSTNAME=<IP address>. You must pass the argument as ORACLE_HOSTNAME=<valid host name>.

Note:

Enterprise Manager does not support uploading of data to the same Management Repository from two Management Agents running on the same host.

To Install an Additional Management Agent Using OUI

  1. Start the Oracle Universal Installer by running the runInstaller script in Linux (<DVD>/runInstaller) from the top directory of the DVD.

  2. In the Specify Installation Type screen, select the fourth option (Additional Management Agent), and specify the parent directory path and installation name.

    Figure 3-21 Specify Installation Type

    Specify Installation Type
  3. In the Specify Installation Location screen, specify the full path to the parent directory (base directory), for example, /scratch/OracleHomes. The agent home created during the installation is placed as a sub-directory under this parent directory. For example: agent10g.

    Note:

    Ensure you do not use symbolic links to the Oracle home path.

    The installer by default installs the selected products in the English language.

    1. If you want to install the product in a different language, click Product Languages.

    2. The Language Selection screen appears. Make the required language selections here, and click Next. See Figure 3-3, "Language Selection" for details.

  4. The Product Specific Prerequisites Checks screen appears.

    This screen displays the name, type, and status for all prerequisite checks designed for the installation. Automatic checks are run first, followed by optional and manual checks.

    Depending on the status of the automatic checks, you must verify all warning and manual checks. To do this, select the appropriate prerequisite status check box and click Retry. As each check runs, a progress bar is shown, and test details (expected results, actual results, error messages, instructions) are displayed in the details section at the bottom of the screen. See Figure 3-5, "Product-Specific Prerequisite Checks" for more information.

    Note:

    You can also run these prerequisite checks in standalone mode, prior to starting the runInstaller. For more information on running these prerequisite checks in standalone mode, see Chapter1, "Running the Prerequisite Check in Standalone Mode"for more information.
  5. Click Next. The Specify Oracle Management Service Location screen appears.

    Figure 3-22 Specify Oracle Management Service Location

    Specify Oracle Management Service Location
    1. Specify the Management Service host name. For example: dlsun1444.acme.com. Use the fully qualified host name (including domain).

      Caution:

      When specifying the host name, ensure you do not include the protocol (that is, http:// or https://).
    2. Enter the port number for the Management Service. The default port is 4889 and the default secure port number is 1159.

      However, even if you are specifying a secure and locked Management Service, you must still enter the nonsecure port number (4889) here. You must connect over HTTP to receive the certificate before you can connect over HTTPS.

      Note:

      If your Management Service has been secured and locked, you are prompted to enter the Agent Registration password (used to secure the Management Service environment). If you do not know the password, obtain it from the user who configured the Management Service for SSL.
  6. Click Next. If the Management Service is found to be running in a secure mode, the Specify Agent Registration Password screen appears. You must provide the correct password to enable communications between the new Management Agent and the Secure Sockets Layer (SSL)-enabled Management Service.

    Figure 3-23 Specify Agent Registration Password

    Specify Agent Registration Password

    Note:

    If you do not know the password and choose to leave the Password field blank, you must do the following after installation to enable communication between the Management Agent and secure OMS:
    • Find out the correct password for the secure and locked OMS environment. If you do not know the password, obtain it from the user who configured the Management Service for SSL.

    • In the <AGENT_HOME>/bin directory, execute any of the following commands:

      emctl secure agent -reg_passwd <password>
      
      

      The variable <passwd> should be replaced with the Agent Registration password.

      emctl secure agent
      
      

      When you execute this command, you will be prompted to specify the Agent Registration password.

  7. Click Next. The Summary screen appears.

    This screen displays a summary of the options that you have selected during the installation process. Depending on the installation type, this screen displays any or all of the following details:

    • Global Settings

    • Product Languages

    • Space Requirements

    • New Installations

    For more information on each of the previously listed details, see the Enterprise Manager online Help.

    Verify the choices that you have made and click Install to start the installation. The installer starts installing the selected Oracle product.

  8. During the installation, you are prompted to execute certain configuration scripts. These scripts and their locations are listed in the Execute Configuration Scripts dialog box that is displayed (only for Linux). Figure 3-12, "Execute Configuration Scripts" provides details on this screen.

    1. To execute these scripts, go to the computer window, log in as root, and run these configuration scripts.

    2. Return to the Execute Configuration Scripts dialog box after executing the scripts, and click OK to continue the installation.

  9. The Configuration Assistants screen appears. At this point, the installer starts running the recommended configuration tools.

    This screen displays the name, status, and the type of each configuration tool that Oracle recommends to be run before completing the installation. Refer to Table 3-4 to see the list of configuration tools that are run. In case of failure of any configuration assistant, refer to the logs and re-rerun the configuration assistants as described in AppendixA, "Configuration Assistants Fail During Enterprise Manager Installation".

    See Chapter3, "Executing the runConfig Tool from the Command Line" for information on executing the runConfig tool.

  10. After successfully running all the recommended configuration tools, click Next. The End of Installation screen appears.

    This screen displays some important information about the products you have installed. This information is also available in the <AGENT_HOME>/sysman/setupinfo.txt file.

    For example, it might contain information about the URLs for particular Web applications.

Executing the runConfig Tool from the Command Line

This command-line tool is typically used to run any of the failed configuration tools of your product(s) under an Oracle home.

The usage to execute the runConfig tool is:

./runConfig.sh OPTION1=value1 OPTION2=value2 ...

The options, OPTION1, OPTION2, and so on, can be the options discussed in the following section.

Note:

On Microsoft Windows, replace runConfig.sh with runConfig.bat or just runConfig (without the file extension).

Options You Can Specify to Execute runConfig

You can specify the following options to execute the runConfig tool.

ORACLE_HOME

This is the absolute location of the Oracle home. All products/top-level components under this Oracle home that have been installed using the Oracle Universal Installer (OUI) 10g R 2 (10.2) are eligible for the ACTION. Products installed using an OUI that is earlier to 10.2 are not eligible for this ACTION.

ACTION

This is a mandatory option. This option can have values such as configure/clone / addnode/addlanguage/deconfigure/patchsetConfigure.

MODE

This is optional, and can have values such as perform/showStatus/listTools. For example, if the value is perform, then that ACTION is performed.

If MODE is absent, the MODE option will assume a default value of listTools.

If the value is showStatus, the status of the last-performed ACTION is displayed to the user.

Examples

Tool1 - Optional    - Failed      Tool2 - Recommended - Succeeded       Tool3 - Optional    - Succeeded

If the value of MODE option is listTools, a list of recommended/optional/other tools for the specified ACTION are displayed.

Example

Recommended Tools(1): Tool2       Optional Tools (2): Tool1, Tool3       Other Tools(0):

COMPONENT_XML

This is optional. You can specify a comma-separated list of Aggregate XML names from the OH/inventory/ContentsXML/ConfigXML/ and only these XMLs and the items dependent on them will be configured. If there are two components with the same name in the ORACLE_HOME, the one that is of a later version is considered for the ACTION option.

RESPONSE_FILE

This is optional. This is the absolute location of the response file that is used to overwrite some existing parameters. Pairs such as ComponentID|variable = value are to be specified in this file, per line, per variable as:

oracle.assistants.server|var1=true oracle.network.client|var2=orcl 

Example

RESPONSE_FILE=/scratch/rspfile.properties

Note:

Secure variables are not stored in the instance aggregate XML files and hence while running runConfig, if any of the configuration tools that you want to run use secure variables, such as passwords, you must supply the value of these secure variables using the RESPONSE_FILE option of runConfig. Otherwise, the tools with secure variables as arguments fail.

INV_PTR_LOC

This is optional. This is the full path of oraInst.loc file.

The orainst.loc file contains inventory_loc=<location of central inventory>

inst_group=<>

Example

INV_PTR_LOC=<absolute path of oraInst.loc>

RERUN

This is optional. Possible values are true and false. RERUN has a default value of false. This means that only failed tools or those tools that were skipped are executed. All those tools that were successfully executed are skipped during the rerun.

A RERUN=true value will execute all the tools anew, including the tools that completed successful runs.

Typical Usage of the runConfig.sh

A typical usage of the runConfig.sh script is as follows:

./runConfig.sh ORACLE_HOME=<path of database home> ACTION=configureMODE=perform COMPONENT_XML={encap_emseed.1_0_0_0_0.xml}

Note:

On Microsoft Windows, replace runConfig.sh with runConfig.bat or just runConfig (without the file extension).

runConfig Log Files

The log files for runConfig configActions<timestamp>.log/.err are generated under ORACLE_HOME/cfgtoollogs/oui/.

Executing the configToolFailedCommands Script (UNIX Only)

During the installation, if any of the configuration assistants fails to run successfully, a configToolFailedCommands script is created in the respective Oracle home directories. If you want to rerun the failed configuration tools, you can either execute the runConfig tool, or navigate to the configToolFailedCommands script under the corresponding Oracle home location, and execute this script.

A typical usage of the configToolFailed Commands scripts is as follows:

./configToolFailedCommands

Deinstallation of Enterprise Manager Grid Control

If you deinstall the Enterprise Manager 10g Oracle homes using Oracle Universal Installer, the Oracle homes are de-registered from the central inventory and the oratab file. However, some files may remain in these Oracle homes.

If an Oracle home has been successfully removed (verify this in OUI by clicking Installed Products), you can manually delete the files through the operating system.

The proper deinstallation sequence is the following:

  1. Shut down all opmn processes that are running by executing the following command:

    <OMS_HOME>/opmn/bin/opmn stopall
    
    
  2. Shut down the Management Agent in the Agent Oracle home using the emctl stop agent command.

  3. Stop Enterprise Manager by executing the following command:

    <OMS_HOME>/bin/emctl stop em
    
    
  4. Shut down the repository database (if the database software is installed as a part of the Management Service Oracle home being uninstalled).

  5. Shut down the Oracle Database listener.

  6. Run the Database Configuration Assistant (DBCA) to delete the database before proceeding to deinstall the Oracle home.

  7. Run the Oracle Universal Installer and select the Oracle home to deinstall. It is removed from the Central Inventory.

Caution:

After deinstallation of certain Grid Control targets, when you try and remove the same targets from the Grid Control console, you may encounter an error.

To resolve this issue, deinstall the Grid Control targets and wait for at least 15 minutes before you attempt to remove the targets from the Grid Control console using the Hosts screen.

Additional Deinstallation Steps for Windows Operating Systems

For Windows operating system, you will need to perform the following manual steps to remove entries from the registry. Ensure that you are logged in as a user with Administrator privileges on that computer.

Remove Entries in Windows Registry

  1. Start the registry editor. Choose Start > Run > regedit.

  2. Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\

  3. Go to HKEY_LOCAL_MACHINE\SOFTWARE\ODBC and expand all subkeys and remove the key "Oracle in <HOME_NAME>". Check if the "Oracle ODBC Driver" key contents refer to the ORACLE_HOME to be deleted. If yes, delete the key.

  4. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services. Delete the keys that begin with Oracle.

  5. Go to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet2\Services. Delete the keys that begin with Oracle.

  6. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\...\Application. Delete the keys whose names begin with Oracle and contain references to the EventMessageFile string entry for the ORACLE_HOME to be deleted or a location under it.

  7. Go to HKEY_CLASSES_ROOT and search in the keys starting with Ora or ORCL (for example, Oracle..., ORADC... ..., OraPerf..and ORCL...). Delete keys which include string values with the specific ORACLE_HOME that is to be deleted.

  8. Close the registry editor.

Clean Up Environment Settings

  1. On Windows NT: Choose Start > Settings > Control Panel > System > Environment.

    On Windows 2000 and Windows XP: Choose Start > Settings > Control Panel > System > Advanced > Environment Variables.

  2. In the System Variables section, click the variable PATH in order to modify the value. For example, you may see a path similar to this one:

    C:\ORACLE\EM10g\BIN
    C:\PROGRAM FILES\ORACLE\JRE\1.1.7\BIN
    
    

    If you are deleting the Oracle home C:\ORACLE\EM10g, remove the C:\ORACLE\EM10g\BIN expression from the PATH variable.

    Delete any path expression in the PATH variable that contains the Oracle home to be removed or some location underneath.

  3. If there is a CLASSPATH variable under "System Variables", delete the path expressions in the variable that contains the ORACLE_HOME to be removed or some location underneath.

  4. Check if there are any other Oracle variables set in "System Variables". Delete those variables that contain the ORACLE_HOME that you are trying to remove. For example, ORACLE_HOME, ORACLE_SID, TNS_ADMIN, inventory_loc, and so on.

  5. Click Apply and then click OK.

  6. Close the Control Panel window.

Delete Software and Start Menu Icons

  1. On Windows NT: Choose Start > Programs > Windows NT Explorer.

    On Windows 2000 and Windows XP: Choose Start > Programs > Accessories > Windows Explorer.

  2. On Windows NT: Go to %SystemDrive%\WINNT\PROFILES\ALL USERS\START MENU\PROGRAMS

    On Windows 2000 and Windows XP: Go to %SystemDrive%\DOCUMENTS AND SETTINGS\ALL USERS\START MENU\ ...\PROGRAMS

    Note:

    These locations depend on whether the operating system was upgraded from NT or was a new install of Windows 2000 or Windows XP.
  3. Delete the folders -Oracle - <HOME_NAME> where <HOME_NAME> is the Oracle home that you are trying to remove.

    Note:

    To locate your System Drive, type echo %SystemDrive% in the Command Prompt.
  4. Go to the temp directory and delete all files and directories at the following locations:

    On Windows NT: %SystemDrive%\Temp

    On Windows 2000 and Windows XP: %SystemDrive%\Documents and Settings\<username>\Local Settings\Temp\

  5. Reboot the machine.