3 Installing Enterprise Manager

Setting the Mount Point for the DVD-ROM

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>
     

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:

1. Make sure that 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. On the remote computer, map a drive letter to the shared hard drive. You would use the remote access software to do this on the remote computer.

4. Through the remote access software, run Oracle Universal Installer on the remote computer. You can access Oracle Universal Installer from the shared hard drive.

5. 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:

1. Make sure that the remote access software is installed and running on the remote and local computers.

2. On the local computer, share the DVD drive.

   On the remote computer, map a drive letter to the shared DVD drive. You would use the remote access software to do this on the remote computer.

3. Through the remote access software, run Oracle Universal Installer on the remote computer. You access Oracle Universal Installer from the shared DVD drive.

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

Permissions and Prerequisites

The installation should not be run by the root user.

• Create a token object

• Lock pages in memory

• Log in as Administrator

• Create a Service

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

   
   

2. Click Next. In the Specify Installation Location page that appears, enter a parent directory (base directory), for example, /scratch/OracleHomes, for the new installation. All the Oracle homes created during this installation are created as sub-directories 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

   
   

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

   The Language Selection page is displayed.

   Figure 3-3 Language Selection

   
   

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

   
   

   Note: The languages that you select here only change the language of Enterprise Manager, and not the language of the installation itself.

   
   

3. Click Next. The Specify Inventory Directory and Credentials page is displayed only if you are installing Grid Control for the first time.

   Figure 3-4 Specify Inventory Directory and Credentials

   
   

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

      Refer to the Enterprise Manager Online Help for more information on Oracle-recommended guidelines 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 page is displayed.

   Figure 3-5 Product-Specific Prerequisite Checks

   
   

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

   Early detection of problems with the system setup reduces the chances of you encountering problems during installation; for instance, problems with insufficient disk space, missing patches, inappropriate hardware, and so on.

   This page 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 re-run 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 page.

   
   

   Note: You can also run these prerequisite checks in standalone mode, prior to starting the runInstaller. See Chapter1, "Running the Prerequisite Checker 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

      
      

   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 page appears.

   Figure 3-7 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.

   
   

   Note: Your Management Repository Database 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 that you are a member of. These memberships are required to grant the SYSDBA and SYSOPER privileges that are, in turn, required to create the new database using the Operating System authentication.

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

   Figure 3-8 Specify Optional Configuration

   
   

   As the name suggests, all the fields on this page 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 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 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 Oracle MetaLink 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. The following table 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
      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	These are optional fields. You must specify the username and password only if the proxy server has been configured to use these credentials for authentication.
      Realm	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 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 Oracle MetaLink Web site.

      
      
      
      

      ATTENTION: If the proxy server requires user authentication before providing access, you must specify these credentials here or through the Patching Setup page under Setup in the Grid Control console.

      
      

7. Click Next. The Specify Security Options page is displayed.

   Figure 3-9 Specify Security Options

   
   

   You must specify the passwords that are used to secure your entire Grid Control environment. This page has two sections - Secure Management Server Password, and Repository Database Passwords.

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

     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, consider you have 10.1.x 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.x agents fails (since these agents have not been secured).

     
     

     Note: To secure an Agent, go to the Agent Oracle home command line of the particular target, and execute following command: AGWNT_HOME/bin/emctl secure agent

     
     

   • Repository Database Passwords: Specify the passwords for each of the following administrative database accounts.

     Table 3-3 Repository Database Passwords

     User Account	Applies To	Description
     SYS	Repository Database	Super Administrator for the repository database.
     SYSTEM	Repository Database	Administrator for the repository database.
     DBSNMP	Repository Database	Monitoring user for the repository database.
     SYSMAN	Repository Database, Application Server, and Grid Control	The default Grid Control Super Administrator and Owner of the 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 Oracle Application Server instances.

     
     

     You can use the same password for all four accounts, or specify a different password for each account. 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 the 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 cannot be the same as the user name.

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

       
       

       Note: The SYSMAN password can include underscores (_), and hypens (-) along with alphanumeric characters. Alpha characters can be uppercase or lowercase.

       
       

     • Passwords cannot be Oracle reserved words. See Appendix H, "Oracle Reserved Words" for more information.

     
     

     Note: Oracle recommends the passwords you specify: Have at least one letter, one integer, and one punctuation mark (underscore). Are not simple or obvious words such as welcome, account, database, or user.

     
     

8. Click Next. The Summary page is displayed.

   Figure 3-10 Summary

   
   

   This page displays a summary of the options that you have selected during the installation process. Depending on the installation type, this page displays 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 page that appears displays the installation progress bar.

      Figure 3-11 Installation in Progress

      
      

      Enterprise Manager 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 that is displayed (only for Linux).

      Figure 3-12 Execute Configuration Scripts

      
      

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

   3. Return to the above dialog box after executing the scripts, and click OK to continue the installation.

9. The Configuration Assistants page is displayed. At this point, the Installer starts running the recommended Configuration Assistants.

   Figure 3-13 Configuration Assistants

   
   

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

   The following table 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
   Oracle Enterprise Manager Grid Console	OC4j Configuration Assistant HTTP Server Configuration Assistant Java Configuration Assistant Web Cache Configuration Assistant Oracle iAS 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

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

   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.

      
      
      
      

      Caution: In the event a particular configuration assistant fails, you can choose to rerun only that configuration assistant (in standalone mode). See Appendix D, "Executing the runConfig Command Line Tool" for more information.

      
      

10. After successfully running all the recommended configuration tools, the End of Installation page is displayed.

    This page 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. If necessary, write this information down so that you can remember it.

Prerequisites

• Ensure the installation is not run by the root user.

• Ensure the Password Verification option is disabled in the database. 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 for more information on the recommended hard disk and memory requirements. See Chapter1, "Recommended CPU and Memory Allocation for Enterprise Manager Deployments" for more information.

• The RDBMS version should be 9.2.0.6 and higher, or 10.1.0.4 and higher. Execute select banner from v$version to find out the current RDBMS version.

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

  
  

  ATTENTION: 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 AppendixB, "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 versions of the Oracle Database and Real Application Clusters Database that qualify for Management Repository creation.

See Chapter 1, "Pre-Installation Requirements" for more information on hardware and software requirements.

To Install Enterprise Manager Using Existing Database

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

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 page, select the second option (Enterprise Manager 10g Grid Control Using an Existing Database). Click Next.

   Figure 3-14 Specify Installation Type

   
   

3. The Specify Installation Location page 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 sub-directories under this parent directory. For example: oms10g, and agent10g.

      
      

      ATTENTION: 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.

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

      The Language Selection page is displayed. 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 page 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 page appears.

   This page 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 re-run these checks, select the checks that you want to re-run 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 page. 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 Checker in Standalone Mode" for more information.

   
   

6. Click Next. The Specify Repository Database Configuration page appears.

   Figure 3-15 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 versions:

   • Oracle 10g Database Release 1 (10.1.0.4 and higher), Enterprise Edition

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

   • Oracle 9i Database Release 2 (9.2.0.6 and higher), Enterprise Edition

   • Oracle 9i Real Application Clusters Database Release 2 (9.2.0.6 and higher)

   1. In the Database Connection Details section, specify a fully-qualified host name, repository Port number, SID (Oracle System Identifier) for the database instance, and the SYS Password.

      The Oracle System Identifier (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 must replace the SID value with 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.

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

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

   Specify the full path file locations for the above-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. Make sure 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. The installer then queries the database you have specified. Look for the SYSAUX tablespace location, and prefill that path in the appropriate box.

   
   

   Notes: 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.

   
   
   
   

   ATTENTION: 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 the DBMS_SHARED_POOL package has been installed, login to the database and execute the following query: select object_name, object_type from all_objects where object_name = 'DBMS_SHARED_POOL' To install the DBMS_SHARED_POOL package, execute the following scripts: <DB_HOME>/rdbms/admin/dbmspool.sql <DB_HOME>/rdbms/admin/prvtpool.plb

   
   

7. Click Next. The Specify Optional Configuration page appears.

   As the name suggests, all the fields on this page 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 MetaLink credentials if you are going to use a proxy server to access MetaLink.

      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 MetaLink 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 for a description on each of the input fields in this section.

      
      

      ATTENTION: If the proxy server requires user authentication before providing access, you must specify these credentials here, or through the Patching Setup page under Setup in the Grid Control console.

      
      

8. Click Next. The Specify Passwords page appears.

   Figure 3-16 Specify Passwords

   
   

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

   2. Select Lock 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.x) agents in the Grid environment, and you have secured the OMS and selected the Require Secure Communications option, then all communication between the 10g R2 (10.2) OMS and 10.1 agents fails (since 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 page appears.

   This page displays a summary of the options that you have selected during the installation process. Depending on the installation type, this page displays 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 page that appears displays the installation progress bar.

   Enterprise Manager 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 that is displayed (only for Linux). Refer to Figure 3-12.

    1. To execute these scripts, go to the terminal 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 page 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 Eg.emca_repos_create05_13_33.log) is available at the following directory: OMS_HOME/sysman/log/

    
    

    This page 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.

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

    This page 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. If necessary, write this information down so that you can remember it.

Prerequisites

Ensure the following prerequisites are met before starting the installation:

• Ensure the installation is not run by the root user.

• Ensure the hard disk and physical memory requirements are met. See Table 3-1 for more information.

• Besides the RDBMS version, ensure the Repository version is 10.2.0.1.0.

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

  
  

  ATTENTION: 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 an Additional Management Service

Complete the following steps to install an additional Management Service.

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 page, select the third option (Additional Management Service).

   Figure 3-17 Specify Installation Type

   
   

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

   
   

   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 page is displayed. Make the required language selections here. See Figure 3-3, "Language Selection" for details.

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

   This page 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 page. 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 Checker in Standalone Mode" for more information.

   
   

5. Click Next. The Specify Repository Database Configuration page appears.

   Figure 3-18 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 versions: Oracle 10g Database Release 1 (10.1.0.4), Enterprise Edition Oracle 10g Real Application Clusters Database Release 1 (10.1.0.4) Oracle 9i Database Release 2 (9.2.0.6 and higher), Enterprise Edition Oracle9i Real Application Clusters Database Release 2 (9.2.0.6 and higher) 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 (Oracle System Identifier) for the database instance.

      The Oracle System Identifier (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 Service name.

      
      

   3. Enter the password for the SYSMAN user (the default Super Administrator account for Enterprise Manager).

   4. In the Management Server Security section, specify the password used to secure 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.x) agents in the Grid environment, and you have secured the OMS and selected the Require Secure Communications option, then all communication between the 10g R2 (10.2) OMS and 10.1 agents fails (since 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 <password>
      
      

      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 (OMS).

      
      

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

   Figure 3-19 Specify Optional Configuration

   
   

   As the name suggests, all the fields on this page 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 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 page appears.

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

   • Global Settings

   • Product Languages

   • Space Requirements

   • New Installations

   For more information on each of the above-listed details, see the Enterprise Manager Online Help.

   Verify the choices that you have made and click Install to start the installation. Enterprise Manager 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 that is displayed (only for Linux). Refer to Figure 3-12.

   1. To execute these scripts, go to the terminal 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 page appears. At this point, the installer starts running the recommended configuration tools.

   This page 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.

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

    This page 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. If necessary, write this information down so that you can remember it.

Prerequisites

Ensure the Agent Oracle home must not contain any other Oracle software installation.

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 page, select the fourth option (Additional Management Agent), and specify the parent directory path and installation name.

   Figure 3-20 Specify Installation Type

   
   

3. In the Specify Installation Location page, 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 page appears. Make the required language selections here, and click Next. See Figure 3-3, "Language Selection" for details.

4. The Product Specific Prerequisites Check page appears.

   This page 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 page. 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 Checker in Standalone Mode"for more information.

   
   

5. Click Next. The Specify Oracle Management Service Location page appears.

   Figure 3-21 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).

      
      

      ATTENTION: 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 Management Service, you must still enter the non-secure 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 configured to use HTTPS, 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 page appears. You must provide the correct password to enable communications between the new Management Agent and the SSL-enabled Management Service.

   Figure 3-22 Specify Agent Registration Password

   
   
   
   

   IMPORTANT: 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 agent and secure OMS: Find out the correct password for the secure 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 the following command: emctl secure agent <password> where <password> is the Agent Registration Password.

   
   

7. Click Next. The Summary page appears.

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

   • Global Settings

   • Product Languages

   • Space Requirements

   • New Installations

   For more information on each of the above-listed details, see the Enterprise Manager Online Help.

   Verify the choices that you have made and click Install to start the installation. Enterprise Manager 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 that is displayed (only for Linux). Figure 3-12, "Execute Configuration Scripts" provides details on this page .

   1. To execute these scripts, go to the terminal 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 page appears. At this point, the installer starts running the recommended configuration tools.

   This page 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.

   See Appendix D, "Executing the runConfig Command Line Tool" for information on executing the runConfig tool.

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

    This page 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. If necessary, write this information down so that you can remember it.