Skip Headers
Oracle® Enterprise Manager Grid Control Advanced Installation and Configuration Guide
11g Release 1 (11.1.0.1.0)

E16847-15
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

3 Installing Enterprise Manager System

This chapter describes how you can install Enterprise Manager Grid Control using an existing, certified Oracle Database and Oracle WebLogic Server, in silent mode. In particular, this section covers the following:

Note:

Do NOT install the Enterprise Manager system on an OCFS file system. This file system is not supported.

Overview

The installation type, Install a new Enterprise Manager system, enables you to install a complete Enterprise Manager system while utilizing an existing, certified Oracle Database to store Oracle Management Repository (Management Repository).

The existing, certified Oracle Database must be one of the databases listed in My Oracle Support note 412431.1.

Table 3-1 describes the installation process and the software components that are installed or configured for this installation type.

Table 3-1 Process for Installing Enterprise Manager System in Silent Mode

Step 1

Installation of Oracle Management Service 11g Release 1

Creates an Oracle home in the Oracle Middleware Home location, and installs the Oracle Management Service (OMS) software binaries in the new home.

Oracle Middleware Home consists of the Oracle WebLogic Server home, and, optionally, one or more Oracle homes.

If the Oracle Middleware Home is /u01/app/Oracle/Middleware, then the Oracle home for OMS is /u01/app/Oracle/Middleware/oms11g

Step 2

Installation of Oracle Management Agent 11g Release 1

Creates an Oracle home in the Oracle Middleware Home location, and installs the Oracle Management Agent (Management Agent) software binaries in the new home.

If the Oracle Middleware Home is /u01/app/Oracle/Middleware, then the Oracle home for Management Agent is /u01/app/Oracle/Middleware/agent11g

Step 3

Installation of Oracle Web Tier 11g Release 1

Creates an Oracle home in the Oracle Middleware Home location, and installs the Web tier software binaries in the new home.

If the Oracle Middleware Home is /u01/app/Oracle/Middleware, then the Oracle home for Web tier is /u01/app/Oracle/Middleware/Oracle_WT

Step 4

Installation of Oracle Common Directory

Creates a common directory in the Oracle Middleware Home location for storing configuration files.

If the Oracle Middleware Home is /u01/app/Oracle/Middleware, then the common directory is /u01/app/Oracle/Middleware/oracle_common.

Step 5

Configuration of Oracle Management Service Instance Base Location

Creates an instance home for Enterprise Manager Grid Control in the parent directory of the Oracle Middleware Home for storing all OMS-related configuration files. By default, the instance home is gc_inst. You can, however, edit this and specify a custom name.

If the Oracle Middleware Home is /u01/app/Oracle/Middleware and if you choose to retain the default instance home name, then the instance home location is /u01/app/Oracle/gc_inst

If the parent directory of the Oracle Middleware Home does not have write permission, then the Oracle Management Service Instance Base is created in the Oracle Middleware Home.

Step 6

Configuration of Core Components

Runs the Configuration Assistants to perform the following:

  1. Applying OMS-Related One-Off Patches: (Optional) Applies one-off patches to the Oracle home of the OMS (oms11g).

  2. Configuring SYSMAN Schema and MDS Schema: In the specified existing, certified Oracle Database, configures the SYSMAN schema and Metadata (MDS) schema, and creates these data files: mgmt.dbf, mgmt_ecm_depot1.dbf, mgmt_ad4j.dbf

  3. Configuring OMS: Configures the OMS and the independent instance where Enterprise Manager Grid Control is deployed.

  4. Add-on OMS Side Configuration: Configures the Virtualization Add-On detected in the Oracle home of the OMS (oms11g).

  5. Configures OCM (If required; Only if you have chosen to configure it): Configures Oracle Configuration Manager (OCM) in the Oracle home of the OMS (oms11g) and Oracle home of the Web tier (Oracle_WT).

  6. Applying Agent-Related One-Off Patches: (Optional) Applies one-off patches to the Oracle home of the Management Agent (agent11g).

  7. Configuring Management Agent: Configures the Management Agent to enable monitoring of targets, collection of information, and so on.

  8. Configures OCM (If required; Only if you have chosen to configure it): Configures Oracle Configuration Manager (OCM) in the Oracle home of the Management Agent (agent11g).

  9. Configures System Monitoring Plug-Ins: Configures the System Monitoring Plug-Ins detected in the Oracle home of the Management Agent (agent11g).


Before You Begin

Before you begin, keep these points in mind:

  • This installation type only supports installation of Enterprise Manager Grid Control locally on the server where the installer is invoked, and does not support installing on multiple or remote hosts.

  • Do NOT install the additional OMS on an OCFS file system. This file system is not supported

  • Install Enterprise Manager Grid Control on a dedicated Oracle WebLogic Server instance (in a separate middleware home). Do NOT install Enterprise Manager Grid Control on an Oracle WebLogic Server instance that already has an Oracle Fusion Middleware product installed. For example, if the middleware home already has Oracle SOA Suite 11.1.1.2.0 installed, then do not install Enterprise Manager Grid Control in the same middleware home. Enterprise Manager Grid Control cannot co-exist with any Oracle Fusion Middleware product in the same middleware home because the ORACLE_COMMON property is used by both the products.

  • By default, the upload ports and console ports as described in What Ports Are Used for Installation? are used.

    However, if you want to use custom ports instead, then update the staticports.ini file as described in What Ports Are Used for Installation?, and pass the -staticPortsIniFile parameter while invoking the installer.

    For example:

    ./runInstaller -silent -staticPortsIniFile <absolute_path_to_ini_file_location>/staticports.ini -responseFile <absolute_path_to_response_file> [-invPtrLoc <absolute_path_to_inventory_directory>]

  • By default, the software updates cannot be applied during installation because the INSTALL_UPDATES_SELECTION parameter in the response file is set to "skip". However, if you want to apply them during installation, then modify this parameter as described in Table 3-5.

  • Do NOT set the DISPLAY environment variable.

  • No environment variable specific to Enterprise Manager Grid Control needs to be set prior to installation. The ORACLE_HOME and ORACLE_SID variables should not be set; Oracle directories should not appear in the PATH.

  • Oracle offers code fixes for a product based on the Oracle Lifetime Support Policy. When the license period expires for a particular product, the support for code fixes offered by Oracle also ends. For more information, see the Oracle Lifetime Support Policy available at:

    http://www.oracle.com/support/library/brochure/lifetime-support-technology.pdf

    When determining supportability and certification combinations for an Enterprise Manager Grid Control installation, you must consider Enterprise Manager Grid Control's framework components as well as the targets monitored by Enterprise Manager Grid Control. Oracle recommends keeping your Grid Control components and targets updated to the latest certified versions in order to receive code fixes without having to purchase an Extended Support license. For information about the certified combinations of Enterprise Manager Grid Control components and monitored targets, see My Oracle Support note.412431.1.

  • For accessing the Enterprise Manager Grid Control console, ensure that you use only certified browsers as mentioned in My Oracle Support note 412431.1.

Prerequisites

Before installing a complete Enterprise Manager system in silent mode, ensure that you meet the following prerequisites.

If you want, you can print out this section and write 'Yes' or 'No' against each prerequisite. This will help you to track the prerequisites you have met and the prerequisites you have not met.

Table 3-2 Prerequisites for Installing Enterprise Manager System in Silent Mode

Requirement Description Yes/No

Hardware Requirements

Ensure that you meet the hard disk space and physical memory requirements as described in Appendix A, "Meeting Hardware Requirements".

 

Operating System Requirements

Ensure that you install the OMS only on certified operating systems as mentioned in the Enterprise Manager Certification Matrix available on My Oracle Support.

To access this matrix, follow these steps:

  1. Log in to My Oracle Support, and click the Certifications tab.

  2. On the Certifications page, in the Certification Search region, from the Product list, select Enterprise Manager Base Platform - OMS.

  3. From the Release list, select 11.1.0.1.0, and click Search.

 

Package Requirements

Ensure that you install all the platform-specific packages as described in Appendix B, "Meeting Package, Kernel Parameter, and Library Requirements ".

 

Operating System Groups and Users Requirements

Ensure that you create the required operating system groups and users as described in Appendix C, "Creating Operating System Groups and Users Requirements".

 

Unique Host Name and Static IP Address Requirements

Ensure that you check the network configuration to verify that the host on which you are installing resolves to a unique host name and a static IP address that are visible to other hosts in the network.

Note: You must use only a static IP address. If you use a dynamic IP address, the installation will fail.

 

File Descriptor Requirements

Ensure that you set the file descriptors to a minimum of 4096.

To verify the current value set to the file descriptors, run the following command:

/bin/sh -c "ulimit -n"

If the current value is not 4096, then as a root user, update the /etc/security/limits.conf file with the following entries:

<UID> soft nofile 4096

<UID> hard nofile 4096

 

System Parameter Value Requirements for AIX

Ensure that the value set for the system parameter ncarg is 1024. To verify the value of ncarg, run the following command:

-lsattr -EH -l sys0 | grep ncargs

If the value is less than 1024, then increase it to 1024 by running the following command:

chdev -l sys0 -a ncargs=1024

 

Temporary Directory Space Requiremens

Ensure that you allocate 400 MB of space for a temporary directory where the executables can be copied. For example, /tmp on UNIX hosts and c:\Temp on Microsoft Windows hosts.

 

Central Inventory Requirements

Ensure that you allocate 100 MB of space for the central inventory directory.

Also ensure that the central inventory directory is not on a shared file system.If it is already on a shared file system, then switch over to a non-shared file system by following the instructions outlined in My Oracle Support note 1092645.1

 

UMASK Value Requirements

Ensure that you set the default file mode creation mask (umask) to 022 in the shell startup file.

For example:

  • Bash Shell

    $ . ./.bash_profile

  • Bourne or Korn Shell

    $ . ./.profile

  • C Shell

    % source ./.login

 

JDK Requirements

Ensure that you have the following version of JDK installed on the host where you are planning to install Enterprise Manager Grid control.

  • Linux Platform (64 Bit): SUN JDK 1.6_18+

    (On Linux 32-bit platforms, you need not install JDK because it is packaged by default with Oracle WebLogic Server)

  • Solaris Platform: SUN JDK 1.6_18+

  • HP-UX Platform: JDK 6.0.05+

  • AIX Platform: JDK 1.6.0 SR6

  • Microsoft Windows Platform (64 Bit): SUN JDK 1.6_18

Download the JDK version for your platform from the platform vendor's Web site. For example, download SUN JDK 1.6_18+ for Linux platforms from Oracle Web site. Similarly, download the JDK for other platforms from other vendors' trusted Web sites.

You can also refer to My Oracle Support note 1063587.1 for an example on installing JDK 1.6_18+ on Linux x86_64 platform.

If you already have a JDK installed, then verify its version by navigating to the <jdk>/bin directory and running the following command. The output of this query should give you the complete version number.

java -fullversion

Note: JROCKIT is not supported.

 

Oracle WebLogic Server Requirements

  • Ensure that Oracle WebLogic Server 10.3.2 (Oracle Fusion Middleware 11g Release 1 Patch Set 1) is already installed on the host where you plan to install Enterprise Manager Grid Control.

  • Ensure that the installation was a typical installation, and even if it was a custom installation, ensure that components chosen for custom installation were the same as the ones associated with a typical installation.

  • Ensure that the installation was under the Middleware Home directory. For example, /scratch/aime/Oracle/Middleware1/wlserver_10.3.

  • Ensure that no other Oracle Fusion Middleware products or components are installed in the Middleware Home directory where Oracle WebLogic Server 10.3.2 is installed.

Enterprise Manager Grid Control will create a new domain in this Oracle WebLogic Server, and not use any of the existing domains.

For information on installing Oracle WebLogic Server, see My Oracle Support note 1063762.1. For more information, downloads, demos, access the following URL:

http://www.oracle.com/technology/products/weblogic/index.html

 

Oracle WebLogic Server Patch Requirements

Ensure that you apply either the consolidated patch WDJ7 or the individual patches 4D53, XLXA, and NIXN on Oracle WebLogic Server using the Oracle Smart Update utility. For information on applying the consolidated patch WDJ7, see My Oracle Support note 1072763.1.

IMPORTANT: The consolidated patch WDJ7 fixes bugs 8990616, 9100465, and 9221722. However, if you have already applied the individual patches 4D53, XLXA, and NIXN, then no need to apply the consolidated patch WDJ7.

For information on Oracle Smart Update utility, see Oracle Smart Update Installing Patches and Maintenance Packs documentation available at:

http://www.oracle.com/technology/products/weblogic/index.html

 

Existing Database Version Requirements

Ensure that the existing, certified Oracle Database is one of the databases listed in My Oracle Support note 412431.1. The database can reside either on the host where you are installing the product or on a remote host.

Ensure that the existing, certified Oracle Database is not configured with Oracle Grid Infrastructure. This type of configuration is not supported.

If you are installing using Oracle Database 11g Release 1 (11.1.0.7.0), then ensure that you apply the patch for bug# 9066130.

If you are installing using Oracle Database 11g Release 2 (11.2.0.1.0), then ensure that you apply the patch for bug# 9002336 and 9067282.

Note: For information about these patches and their availability for different platforms, see My Oracle Support note 1073166.1

 

Database Partitioning Requirements

Ensure that the existing, certified Oracle Database has the Partitioning Option enabled.

 

Existing Database Not to Be in QUIESCE Mode

Ensure that existing, certified Oracle Database is not in QUIESCE mode. To verify this, run the following SQL in the database:

select active_state from v$instance;

 

Existing Database Not to Have Database Control

(If you are upgrading from Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or higher, which uses an Oracle Database where the Management Repository is already created, that is, where the Grid Control SYSMAN schema is already created, then ignore this prerequisite. This prerequisite applies only when you install Enterprise Manager 11g Grid Control Release 1 (11.1.0.1.0) using an existing, certified Oracle Database that has Database Control SYSMAN schema created, which you want to replace now with Grid Control SYSMAN schema.)

Ensure that your existing, certified Oracle Database does NOT have Database Control SYSMAN schema. If it has, that is, if your existing database is configured with Database Control, then deconfigure it.

  1. Verify whether your database has Database Control SYSMAN schema.

    To do so, log in to the database as SYS user and run the following query:

    SELECT COUNT(*) FROM ALL_USERS WHERE USERNAME='SYSMAN'

    If the result of this query is 1, then the database has this schema, so deconfigure it.

  2. Before deconfiguring the Database Control, set the environment variable ORACLE_HOME to the Oracle home of the database, and ORACLE_SID to the SID of the database.

    For example, in bash shell, you can set them in the following way:

    export ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1

    export ORACLE_SID=orcl

  3. Deconfigure the Database Control.

    To deconfigure Database Control for a standalone database, run the following command from the Oracle home of the database as the user who installed the database. If the command hangs, then restart the database and rerun the command.

    $<ORACLE_HOME>/bin/emca -deconfig dbcontrol db -repos drop -SYS_PWD <sys pasword> -SYSMAN_PWD <sysman password>

    To deconfigure Database Control for a Real Application Cluster (RAC) database, run the following command from the Oracle home of the database as the user who installed the database. If the command hangs, then restart the database and rerun the command.

    $<ORACLE_HOME>/bin/emca -deconfig dbcontrol db -repos drop -cluster -SYS_PWD <sys pasword> -SYSMAN_PWD <sysman password>

    Note: If the deconfigure operation hangs, then refer to My Oracle Support note 375946.1.

 

Existing Database Not to Have SYSMAN and SYSMAN_MDS Schema

(If you are upgrading from Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or higher, which uses an Oracle Database where the Management Repository is already created, that is, where the Grid Control SYSMAN schema is already created, then ignore this prerequisite. This prerequisite applies only when you install Enterprise Manager 11g Grid Control Release 1 (11.1.0.1.0) using an existing, certified Oracle Database that has Database Control SYSMAN schema created, which you want to replace now with Grid Control SYSMAN schema.)

Ensure that your existing, certified Oracle Database does NOT have Enterprise Manager Grid Control SYSMAN schema and Metadata (MDS) schema.

  1. Verify whether your database has Enterprise Manager Grid Control SYSMAN schema and MDS schema.

    To do so, log in to the database as SYS user and run the following query:

    SELECT COUNT(*) FROM ALL_USERS WHERE USERNAME IN ('SYSMAN','SYSMAN_MDS');

    If the result of this query is 1, then the database has these schemas, so drop them.

  2. Before dropping the schema, set the environment variable LD_LIBRARY_PATH to the ORACLE_HOME/lib directory of the OMS. Also set the ORACLE_HOME to the Oracle home of the OMS.

  3. Drop the schema by running the following command from the Oracle home of the OMS.

    $<ORACLE_HOME>/sysman/admin/emdrep/bin/RepManager <repository_database_host> <repository_database_port> <repository_database_sid> -action dropall -dbUser <repository_database_user> -dbPassword <repository_database_password> -dbRole <repository_database_user_role> -mwHome <middleware_home> -mwOraHome <oms_oracle_home> -oracleHome <oms_oracle_home>

    If you are dropping the schemas that belong to a 10g Release 2 (10.2.x.x) Management Repository, then run previous command without these arguments: -mwHome <middleware_home> -mwOraHome <middleware_ora_home> -oracleHome <oracle_home>

    Note:

    For Microsoft Windows, invoke RepManager.bat.

    RepManager 11.1 supports -action dropall (drops SYSMAN as well as SYSMAN_MDS) and -action drop (drops only SYSMAN).

    RepManager 10.2.0.5 supports -action drop (drops only SYSMAN).

  4. After dropping the schema, manually delete the database files mgmt.dbf and mgmt_ecm_depot1.dbf.

    You can find these files by running the following command as SYS:

    SELECT FILE_NAME FROM DBA_DATA_FILES WHERE UPPER (TABLESPACE_NAME) LIKE 'MGMT%';

 

Existing Oracle Database Initialization Parameters Requirements

Ensure that you have correctly set the database initialization parameters for the existing, certified Oracle Database so that the Management Repository can be created. For information about setting the parameters, see Setting Database Initialization Parameters.

 

Fine-Grained Access Control Requirements

Ensure that the fine-grained access control option is set to TRUE in the existing, certified Oracle Database so that the Management Repository can be created. To verify this, run the following command:

select value from v$option where parameter = 'Fine-grained access control';

 

UNDO Tablespace Size Requirements

Ensure that the UNDO tablespace has a minimum space of 200 MB. To verify this, run the following query:

SELECT SUM(DECODE(autoextensible,'YES',200*1024*1024+1,bytes)) total

FROM dba_data_files f, dba_tablespaces s

WHERE s.contents = 'UNDO'

AND s.tablespace_name = f.tablespace_name;

Note: The result of this query is in bytes.

If the minimum space is less than 200 MB, then set it to 200 MB by running the following command:

alter database datafile '<absolute_path>/<file_name>' resize 200M;

 

UNDO Tablespace and Temporary Tablespace Settings Requirements

Ensure that the UNDO tablespace and the TEMP tablespace are autoextensible in the existing, certified Oracle Database. To verify this, run the following command:

select count(*) from  dba_temp_files where tablespace_name='TEMP' and AUTOEXTENSIBLE  <> 'YES';

select count(*) from dba_data_files where tablespace_name='UNDOTBS' and AUTOEXTENSIBLE <> 'YES';

If the result of the query is 0, then the tablespace is autoextensible. If the result it not 0, then refer to Oracle Database Administrator's Guide available in the following location to make the tablespace autoextensible.

http://www.oracle.com/technology/documentation/database.html

 

Archive Logging Settings Requirements

(Recommended) Ensure that you turn on archive logging in the existing, certified Oracle Database for any environment where continuity of data is important. To verify this, run the following command:

select log_mode from v$database;

 

Tablespace-Related Hard Disk Space Requirements

Ensure that you allocate a minimum of 1 GB hard disk space for the following tablespaces:

  • Management Tablespace (mgmt.dbf)

  • Cofiguration Data Tablespace (mgmt_ecm_depot1.dbf)

  • JVM Diagnostics Data Tablespace (mgmt_ad4j.dbf)

Oracle also recommends that you keep the auto-extend feature enabled for the tablespace data files.

Note that the space requirement increases as the number of monitored targets increase, along with the input/output performance demands on the storage devices.

 

Installing User Requirements

Ensure that you meet the following requirements:

  • (For UNIX only) The installation must NOT be run by a root user.

  • (For Microsoft Windows only) User must be part of the ORA-DBA group and have administrator permissions.

  • (For Microsoft Windows only) User must belong to the DBA group, and have permissions to perform the following: Act as part of the operating system, Create a token object, Log on as a batch job, and Adjust memory quotas for a process.

    To verify whether the agent user has these rights, from the Start menu, click Settings and then select Control Panel. From the Control Panel window, select Administrative Tools, and from the Administrative Tools window, select Local Security Settings. In the Local Security Settings window, from the tree structure, expand Local Policies, and then expand User Rights Assignment.

 

Permission Requirements

Ensure that you are able to access and write in the following locations:

  • Oracle Middleware Home location

  • Oracle Management Service Instance Base location

  • Oracle Inventory Directory

For more information about these locations, see Understanding Installation Directories.

Ensure that you have write permission on the temporary directory where the executables will be copied. For example, /tmp or c:\Temp.

 

Oracle Inventory Location Requirements

Ensure that the Oracle Inventory (oraInventory) is not in a shared location. When you use the oraInst.loc file, ensure that the inventory location specified there is not pointing to a shared location. If it is, change it to a non-shared location.

 

Proximity Requirements

Ensure that the host on which the OMS is being installed and the host on which the Management Repository is being configured are located in close proximity to each other. Ideally, the round trip network latency between the two should be less than 1 millisecond.

 

Firewall Requirements

If you have a firewall in your environment, then see Chapter 19, "Configuring Enterprise Manager for Firewalls".

 

Internet Connection Requirements

Oracle recommends that the host from where you are running the installer have a connection to the Internet so that the configuration information can be automatically collected and uploaded to My Oracle Support.

 

Setting Database Initialization Parameters

As one of the prerequisites, ensure that you set the initialization parameters as described in Table 3-3 and Table 3-4 for your existing, certified Oracle Database so that the Management Repository can be created. For information on how you can set these initialization parameters, see My Oracle Support note 1073647.1.

Important:

After you set the parameters, restart the database.

Table 3-3 Setting Fixed Initialization Parameters

Fixed Initialization Parameter Value

cluster_database

(Only for Oracle RAC Database)

TRUE

compatible

10.2.0.1.0 or higher

max_commit_propogation_delay

(Only for Oracle RAC Database)

0

remote_login_passwordfile

SHARED or EXCLUSIVE

statistics_level

TYPICAL

timed_statistics

TRUE

undo_management

AUTO

workarea_size_policy

AUTO


Table 3-4 Setting Variable Initialization Parameters

Variable Initialization Parameter Value

db_block_size

8192 or greater

instance_groups

As described in Oracle Database Reference Guide available at:

http://www.oracle.com/technology/documentation/database.html

job_queue_processes

(For Installation) 10 or greater

(For Upgrade) If you are upgrading Enterprise Manager 10g Grid Control Release 4 (10.2.0.4) or higher, then ensure that you set the value to 0 before upgrading. And after upgrading, reset it to the original value that existed before upgrading the product.

log_buffer

10485760 or greater

memory_target

(Only for Oracle Database 11g Release 2 (11.2) and higher)

As described in Oracle Database Reference Guide available at:

http://www.oracle.com/technology/documentation/database.html

open_cursors

300 or greater

parallel_instance_groups

As described in Oracle Database Reference Guide available at:

http://www.oracle.com/technology/documentation/database.html

processes

500 or greater

session_cached_cursors

200 or greater

sga_target

As described in Oracle Database Reference Guide available at:

http://www.oracle.com/technology/documentation/database.html


Installation Procedure

To install a complete Enterprise Manager system in silent mode, follow these steps:

  1. Copy the following response file to an accessible location on your local host:

    <Software_Location>/response/em_using_existing_db.rsp

    In this command, <Software_Location> is either <DVD> or <Software_Downloaded_Location>.

  2. Edit the response file and specify appropriate values for the parameters described in Table 3-5.

  3. Invoke the installer:

    • If this is the first Oracle product you are installing on the host, then run the following command:

      ./runInstaller -silent -responseFile <location>/em_using_existing_db.rsp [-invPtrLoc <absolute_path_to_inventory_directory>]

      Note:

      • For Microsoft Windows, invoke setup.exe instead of runInstaller.

      • In Microsoft Windows, if the path to the software download location contains a subdirectory name with two or more words and a space between each of the words, then ensure that the parent directory of such a subdirectory does not contain a file whose name matches with the first word of that subdirectory.

        For example, if the software is downloaded to C:\Documents and Settings, then before you invoke setup.exe, ensure that there are no files titled Documents (for example, shortcut files such as C:\Documents) in the C:\ drive.

      • The central inventory location you specify must NOT be on a shared file system. If it is already on a shared file system, then switch over to a non-shared file system by following the instructions outlined in My Oracle Support note 1092645.1.

    • Otherwise, run the following command:

      ./runInstaller -silent -responseFile <location>/em_using_existing_db.rsp

    Note:

    • For Microsoft Windows platforms, run setup.exe instead of runInstaller

    • If you are planning to have multiple OMSes, then Oracle strongly recommends you to configure a shared file system loader so that a common location is maintained to store all the metric data files uploaded by the Management Agents. If you configure the central directory now, then all subsequent additional OMS installations, which connect to the same Oracle Database, will automatically be mapped to this central directory.

      To configure a shared file system loader, invoke the installer using the following command. Ensure that the location you specify is accessible and writable by all the OMSes.

      ./runInstaller -silent -responseFile <absolute_path_to_response_file>/em_using_existing_db.rsp SHARED_RECEIVE_DIRECTORY_LOCATION=<absolute_path_to_central_directory>

    • After the installation ends successfully, the OMS and the Management Agent start automatically. If you do not want them to start automatically, then invoke the installer using the START_OMS=false and b_startAgent=false arguments.

      However, if you pass the START_OMS=false argument, the installation does not configure the EMCLI tool, and as a result, none of the EMCLI commands will work. Therefore, after the installation ends, you must manually configure the EMCLI tool in the $<ORACLE_HOME>/bin directory. To do so, refer to the Oracle Enterprise Manager Command Line Interface available at:

      http://www.oracle.com/technology/documentation/oem.html

    • By default, GCDomain is the default name used for creating the WebLogic Domain.

      To override this, invoke the installer using the following command and specify a unique custom WebLogic Domain name:

      ./runInstaller WLS_DOMAIN_NAME=<Custom_Domain_Name>

    • If any of the Configuration Assistants fail, then review the relevant log files, resolve the issues, and rerun the Configuration Assistants as described in What Do You Do When Configuration Assistants Fail?. You can also review the log files described in Appendix L, "Installation and Configuration Log Files".

Table 3-5 Response File Parameters for Installing Enterprise Manager System in Silent Mode

Parameter Description

SECURITY_UPDATES_VIA_MYORACLESUPPORT

  • Specify TRUE if you want to download and install security updates. Then, specify the credentials for the following parameters:

    MYORACLESUPPORT_USERNAME

    MYORACLESUPPORT_PASSWORD

  • Specify FALSE if you do not want to download and install security updates:

DECLINE_SECURITY_UPDATES

  • Specify TRUE if you want to decline the security updates. In this case, you should have specified False for SECURITY_UPDATES_VIA_MYORACLESUPPORT.

  • Specify FALSE if you do not want to decline the security updates. In this case, you should have specified TRUE for SECURITY_UPDATES_VIA_MYORACLESUPPORT.

INSTALL_UPDATES_SELECTION

By default, this parameter is set to "skip" indicating that the software updates cannot be installed during installation.

However, if you want to install the software updates during installation, then set this parameter to "staged". Then, for the following parameter, specify the full path, which leads to the Updates directory, where the software updates are available:

STAGE_LOCATION

ORACLE_MIDDLEWARE_HOME_LOCATION

Specify the location that was specified while installing Oracle WebLogic Server. For example, u01/app/Oracle/Middleware. Ensure that the middleware location has write permission to create the Oracle home for OMS and the Oracle home for Management Agent

For example, if you accept the default location /u01/app/Oracle/Middleware, then the Oracle home for OMS is created as /u01/app/Oracle/Middleware/oms11g, and the Oracle home for Management Agent is created as /u01/app/Oracle/Middleware/agent11g.

For more information about this location, see What Is Oracle Middleware Home?.

Note: Ensure that the Middleware Home you specify here is used only for Enterprise Manager Grid Control. Ensure that no other Oracle Fusion Middleware products or components are installed in the same Middleware Home that is designated for Enterprise Manager Grid Control

ORACLE_INSTANCE_HOME_LOCATION

By default, gc_inst is considered as the OMS Instance Base directory for storing all OMS-related configuration files. If you want to accept the default directory, then leave this field blank. However, if you want to have a custom directory, then specify the name of the custom directory.

Whether you accept the default directory or specify a custom one, by default, the directory is created under the parent directory of the Oracle Middleware Home. For example, if the Oracle Middleware Home is /u01/app/Oracle/Middleware, then the directory is is /u01/app/Oracle/gc_inst.

For more information about this location, see What Is Oracle Management Service Instance Base Location?.

WLS_ADMIN_SERVER_USERNAME

Specify the default user name that will be used as the administrative user for the WebLogic Domain. By default, the user name is weblogic.

WLS_ADMIN_SERVER_PASSWORD

Specify the password for the WebLogic user account.

WLS_ADMIN_SERVER_CONFIRM_PASSWORD

Confirm the password for the WebLogic user account.

NODE_MANAGER_PASSWORD

Specify the node manager password.

NODE_MANAGER_CONFIRM_PASSWORD

Confirm the node manager password.

DATABASE_HOSTNAME

Specify the fully-qualified name of the host where the existing database resides. For example, db.host.com.

If you are connecting to an Oracle RAC Database, and if the nodes have virtual IP address, then specify the virtual IP of one of its nodes for this parameter. The connection to the database will be established with a connection string that is formed using only this virtual IP, and the installation will end successfully.

However, if you want to update the connection string with other nodes of the cluster, then perform a software-only installation as described in one of these chapters:

If you follow the instructions in Chapter 5, "Installing Enterprise Manager Software Only in Silent Mode and Configuring Later" and create a response file as described in Table 3-5 (this table), then do the following:

  1. In this response file, for this parameter, that is, DATABASE_HOSTNAME parameter, specify the virtual IP of one of its nodes.

  2. Pass this response file while invoking the installation wizard (runInstaller or setup.exe) as described in Installation Procedure.

  3. Then, while invoking the ConfigureGC.pl script as described in Configuration Procedure, pass an OMS-specific response file that has the CONNECT_STRING parameter updated with details of all the other nodes of the cluster.

    For information about creating this OMS-specific response file, updating the CONNECT_STRING parameter, and passing the response file with the ConfigureGC.pl script, see Appendix J, "Understanding Optional Arguments Run with ConfigureGC.pl Script".

LISTENER_PORT

Specify the listener port to connect to the existing database.

SERVICENAME_OR_SID

Specify the Service name or the System ID (SID) of the existing database.

SYS_PASSWORD

Specify the SYS user account's password.

MANAGEMENT_TABLESPACE_LOCATION

Specify the full path to the location where the data file for management tablespace (mgmt.dbf) can be stored. Ensure that the specified path leads up to the file name.

For example:

  • If the database is on a file system, then the path must look like /u01/oracle/prod/oradata/mgmt.dbf

  • If the database is on Automatic Storage Management (ASM), then the path must look like +<disk_group1>/prod/oradata/mgmt.dbf, where disk_group1 is a diskgroup created on ASM and prod is the Service ID (SID).

  • If the database is on a raw device, then the path must look like </dev/raw1>/prod/oradata/mgmt.dbf, where /dev/raw1 is the raw device and prod is the SID.

Enterprise Manager Grid Control requires this data file to store information about the monitored targets, their metrics, and so on. Essentially, everything else other than configuration data, software library data, and audit data.

CONFIGURATION_DATA_TABLESPACE_LOCATION

Specify the full path to the location where the data file for configuration data tablespace (mgmt_ecm_depot1.dbf) can be stored. Ensure that the specified path leads up to the file name.

For example, /home/john/oradata/mgmt_ecm_depot1.dbf

Enterprise Manager Grid Control requires this data file to store configuration information collected from the monitored targets.

JVM_DIAGNOSTICS_TABLESPACE_LOCATION

Specify the full path to a location where the data file for JVM diagnostics data tablespace (mgmt_ad4j.dbf) can be stored. Ensure that the specified path leads up to the file name. Enterprise Manager Grid Control requires this data file to store JVM-related monitoring data.

For example, /home/john/oradata/mgmt_ad4j.dbf

LOCK_ORACLE_MANAGMENT_SERVICE

OMS always runs in a secure mode, and can further have a locked or an unlocked state. In an unlocked state, the Management Agents that are secure and the Management Agents that are not unsecure communicate with the OMS using HTTPS and HTTP protocols, respectively. However, in a locked state, only secure Management Agents communicate with the OMS using HTTPS protocol.

  • Specify TRUE if you want to lock the OMS running in a secure mode and further enhance the security of communication between the OMS and the Management Agents.

  • Specify FALSE if you do NOT want to further enhance the security of communication between the OMS and the Management Agent.

SYSMAN_PASSWORD

Specify a password for creating a SYSMAN user account. This password is used to create the SYSMAN user, which is the primary owner of the Management Repository schema.

SYSMAN_CONFIRM_PASSWORD

Confirm the password for creating a SYSMAN user account.

ALLOW_ONLY_SECURE_ACCESS_TO_CONSOLE

By default, you can use either HTTP or HTTPS protocol to access the Enterprise Manager Grid Control console.

  • Specify TRUE if you want to secure the access and allow users to access the console only using HTTPS protocol.

  • Specify FALSE if you do NOT want to secure the access and do NOT want to allow users to access the console only using HTTPS protocol.

AGENT_REGISTRATION_PASSWORD

To secure the communication between the OMS and the Management Agents, specify a password. Note that you have to provide the same registration password for securing your Management Agents.

AGENT_REGISTRATION_CONFIRM_PASSWORD

Confirm the agent registration password.

START_OMS

Specify TRUE if you want the OMS to start automatically after installation. Specify FALSE if you do NOT want it to start automatically.


After You Install

After you install Enterprise Manager Grid Control, do these:

  1. Verify the installation:

    1. Navigate to the Oracle home of the OMS (oms11g) and run the following command to see a message that confirms that OMS is up and running.

      $<ORACLE_HOME>/bin/emctl status oms

    2. Navigate to the Oracle home of the Management Agent (agent11g) and run the following command to see a message that confirms that the Management Agent is up and running.

      $<ORACLE_HOME>/bin/emctl status agent

    3. Navigate to the Oracle home of the Management Agent (agent11g) and run the following command to see a message that confirms that EMD upload completed successfully.

      $<ORACLE_HOME>/bin/emctl upload

    Note:

    By default, you can access Enterprise Manager Grid Control only using the HTTPS protocol. If you want to use the HTTP protocol, then unlock it by running the following command from the Oracle home of the OMS:

    emctl secure unlock -console

  2. (Only for UNIX Operating Systems) Run the following scripts as a root user:

    • If you have not specified the inventory location while invoking the installer and if this is the first Oracle product you just installed on the host, then run the oraInstRoot.sh script from the Central Inventory:

      $HOME/oraInventory/oraInstRoot.sh

      For example, if you are using SUDO to change to a root user, then you will run the following command:

      /usr/local/bin/sudo $Home/oraInventory/oraInstRoot.sh
      
    • Run the allroot.sh script from the Oracle home of the OMS (oms11g):

      <ORACLE_HOME>/allroot.sh

      For example, if you are using SUDO to change to a root user, then you will run the following command:

      /usr/local/bin/sudo /scratch/OracleHomes/oms11g/allroot.sh
      
  3. Configure your proxy server as described in Appendix H, "Setting Up Proxy Configuration for Oracle Management Service".

  4. Configure the Oracle Database and Oracle Automatic Storage Management (Oracle ASM) target for monitoring as described in Appendix G, "Configuring Database and ASM Targets for Monitoring".

  5. (Optional) If you had not configured a shared file system loader while installing a complete Enterprise Manager system, and if you want to configure a shared location for it now, then run the following command from the Oracle home of the OMS:

    $<ORACLE_HOME>/bin/emctl config oms loader -shared yes -dir <Loader_Directory>

    For example,

    $<ORACLE_HOME>/bin/emctl config oms loader -shared yes -dir /share/recv

  6. For accessing the Enterprise Manager Grid Control console, ensure that you use only certified browsers as mentioned in My Oracle Support note 412431.1.

  7. (Optional) If you want to connect to another Management Repository, then shut down the OMS, run the following command, and then restart the OMS.

    emctl config oms -store_repos_details (-repos_host <host> -repos_port <port> -repos_sid <sid> | -repos_conndesc <connect descriptor>) -repos_user <username> [-repos_pwd <pwd>] [-no_check_db]

    Note:

    On Linux, you need to double escape the connect descriptor using single and double quotes. However, on Microsoft Windows, you need not.

    For example, on Linux:

    emctl config oms -store_repos_details -repos_host myreposhost.mydomain.com -repos_port 12345 -repos_sid mydb -repos_conndesc '"(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=myreposhost.mydomain.com)(PORT=12345))(CONNECT_DATA=(SID=mydb)))"' -repos_user sysman

    For example, on Microsoft Windows:

    emctl config oms -store_repos_details -repos_host myreposhost.mydomain.com -repos_port 12345 -repos_sid mydb -repos_conndesc (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=myreposhost.mydomain.com)(PORT=12345))(CONNECT_DATA=(SID=mydb))) -repos_user sysman

  8. (Optional) If you want to change the SYSMAN password, then shut down the OMS, run the following command, and then restart the OMS.

    emctl config oms -change_repos_pwd

  9. (Optional) If you want to discover the newly installed targets, if you want to convert the standalone Management Agent to a cluster-based Management Agent, if you want to discover the targets on the new nodes of the cluster, or if you want to reconfigure the cluster-based Management Agent, you must run the agentca script to reconfigure and discover all new targets.

    For information about the agentca script, see What Is Agent Configuration Assistant Used For?.

    For information about reconfiguring the Management Agent and discovering all new targets, see Appendix I, "Reconfiguring Oracle Management Agent and Discovering New Targets".

  10. (Optional) If you want to enable the Request Monitoring feature for tracing transaction requests in WLS, you need JVM Diagnostics as well as Application Dependency and Performance (ADP) managers and agents configured against the target to be monitored.

    For information about installing JVM Diagnostics and enabling the Request Monitoring feature, refer to the Oracle Enterprise Manager Administration Guide.

    For information about enabling the ADP feature in Enterprise Manager Grid Control, refer to the Oracle Enterprise Manager Getting Started with Management Pack Plus for SOA.

    Both these guides are available at:

    http://www.oracle.com/technology/documentation/oem.html