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

2 Things to Know

This chapter introduces you to some key concepts of Enterprise Manager Grid Control, and describes some important aspects of installation and upgrade that you must know before you proceed any further.

In particular, this chapter covers the following:

Note:

Besides the key concepts described in this chapter, you can also review the concepts and other relevant aspects of installation and upgrad described in My Oracle Support note 1073184.1.

Procuring Enterprise Manager Grid Control Software

You can procure the Enterprise Manager Grid Control software from either the product DVD or the Oracle Technology Network (OTN) Web site. This section describes these sources.

In particular, this section covers the following:

How Do You Access the Software from DVD?

You can obtain the Enterprise Manager Grid Control software from the product DVD that is available through Oracle Service Delivery Managers or Oracle Sales Representatives. The software may be available either on a single DVD or on multiple DVDs depending on the operating system.

This section covers the following:

Accessing Software from DVD

If the software is available on a single DVD, then insert the DVD into the DVD drive, and manually run the Enterprise Manager Grid Control Installation Wizard (For UNIX operating systems, invoke runInstaller. For Microsoft Windows operating systems, invoke setup.exe)

Note:

. For information about the Enterprise Manager Grid Control Installation Wizard, see What Is Enterprise Manager Grid Control Installation Wizard?.

If the software is available on multiple DVDs, then follow these steps:

  1. Insert the first DVD into the DVD drive.

  2. Copy the ZIP file from the DVD to a location on your local disk.

  3. Inser the second DVD into the DVD drive.

  4. Copy the ZIP file from the DVD to the same location on your local disk.

  5. Extract the contents of both the ZIP files in the same location.

  6. Run the Enterprise Manager Grid Control Installation Wizard (For UNIX operating systems, invoke runInstaller. For Microsoft Windows operating systems, invoke setup.exe).

Setting Mount Point for DVD

If you want to access the DVD from a shared DVD drive, then set a mount point for the DVD drive.

On most Linux operating systems, the disk mounts automatically when you insert the DVD into the DVD drive. However, for some Linux operating systems, you might have to manually mount the disk. To verify whether the disk mounts automatically and to manually mount the disk if it does not mount itself automatically, follow these steps:

  1. Insert the DVD into the disk drive.

  2. To verify if the disk is automatically mounted, run 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, then run 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>

On most AIX operating systems, the disk mounts automatically when you insert the DVD into the DVD drive. However, for some AIX operating systems, you might have to manually mount the disk. To verify whether the disk mounts automatically and to manually mount the disk if it does not mount itself automatically, follow these steps:

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

    $ su -root

  2. Insert the disk into the drive.

    Note:

    If required, enter the following command to eject the currently mounted disk and to remove it from the drive:

    # /usr/sbin/umount /<SD_DVD>

  3. Enter the following command:

    # /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.

  4. If you are prompted to specify the disk location, then specify the disk mount point directory path. For example, /SD_DVD

How Do You Procure the Software from Oracle Technology Network?

You can procure the Enterprise Manager Grid Control software from OTN. The software available on OTN is archived using Info-ZIP's highly portable ZIP utility. The software may be available either in a single ZIP file or in multiple ZIP files depending on the operating system. After downloading the software, you will need the UNZIP utility to extract the files.

This section covers the following:

Downloading Software

To download the Enterprise Manager Grid Control software from OTN, access the following URL:

http://www.oracle.com/technology/software/products/oem/index.html

The software may be available either in a single ZIP file or in multiple ZIP files depending on the operating system. Download the ZIP file to a common location on your local disk.

Verifying File Size

After downloading the ZIP file, run the cksum command against the file and check if the file checksum of the downloaded software is the same as the file checksum displayed on OTN.

The following is the format of the ZIP file:

GridControl_11.1.0.0_<platform>.zip (<value> bytes) (cksum - <value>)

The value (cksum - <value>) is the file checksum that you need to check.

To check the file checksum, run the following command:

$ cksum GridControl_11.1.0.1.0_<platform>.zip

Note:

If the software is available in multiple ZIP files, then the format is GridControl_11.1.0.1.0_<platform>_<n>of<n>.zip (<value> bytes) (cksum - <value>), where the first occurrence of <n> indicates the ZIP file number and the second occurrence of <n> indicates the total number of ZIP files available for download. In this case, you must verify the file checksum of every ZIP file.

Extracting Contents

You must unzip the archive on the platform for which it was intended. For example, if you download the software for the Linux x86 operating system, then you must unzip the file on a Linux x86 operating system only. If you unzip the file on a Microsoft Windows computer and then move the stage area to a Linux computer, then the staged area files will get corrupted. This is because Microsoft Windows does not preserve the case sensitivity or the permission bits of Linux file names.

If you downloaded a single ZIP file, then extract the contents of it and manually run the Enterprise Manager Grid Control Installation Wizard (For UNIX operating systems, invoke runInstaller. For Microsoft Windows operating systems, invoke setup.exe).

Note:

For information about the Enterprise Manager Grid Control Installation Wizard, see What Is Enterprise Manager Grid Control Installation Wizard?.

If you downloaded multiple ZIP files to a common location, then extract the contents of all the ZIP files in the same location, and then manually run the Enterprise Manager Grid Control Installation Wizard (For UNIX operating systems, invoke runInstaller. For Microsoft Windows operating systems, invoke setup.exe).

Tip:

If you plan to store the files on a DVD, then first extract the contents of the ZIP file, and then copy those extracted files to the DVD. Do NOT copy the ZIP file itself; you need the unzipped contents of the ZIP file to do the installation.

Verifying Platform Information

After extracting the contents of the ZIP file, access the following file to verify the platform information. Here, <Software_Location> can be either the DVD mount point or the location on your local disk where you have extracted the contents of the ZIP files.

<Software_Location>/stage/shiphomeproperties.xml

Note that a 32-bit Enterprise Manager Grid Control software (both Enterprise Manager Grid Control and Oracle Management Agent) can be installed only on a 32-bit operating system that is running on a 32-bit hardware. Similarly, a 64-bit Enterprise Manager software can be installed only on a 64-bit operating system that is running on a 64-bit hardware.

Do NOT try to try install a 32-bit software on a 64-bit platform or vice versa; the installation may proceed, but will fail eventually. Therefore, ensure that you use the right software download for the right platform.

The shiphomeproperties.xml file provides the platform information as shown here:

<?xml version="1.0" standalone="yes" ?>
<ORACLEHOME_INFO>
<ARU_PLATFORM_INFO>
<ARU_ID>46</ARU_ID>
<ARU_ID_DESCRIPTION>Linux x86</ARU_ID_DESCRIPTION>
</ARU_PLATFORM_INFO>
</ORACLEHOME_INFO>

You can see the platform information in the <ARU_ID_DESCRIPTION> syntax. Table 2-1 lists the platform names that may be enclosed in this syntax, and describes whether the names represent a 32-bit or 64-bit software.

Table 2-1 Verifying Platform Information

Platform Name Platform Specified in ARU_ID_DESCRIPTION 32-bit / 64-bit

Linux x86

Linux x86

32-bit

Microsoft Windows (32-bit)

Win 32

32-bit

Microsoft Windows (64-bit AMD64)

win 64

64-bit

Microsoft Windows (64-bit IA)

Windows Itanium

64-bit

Solaris Operating System (SPARC 64-bit)

Solaris

64-bit

HPUX PA-RISC(64-bit)

HPUNIX

64-Bit

AIX

AIX

64-bit

HP_IA64

HPI

64-bit

Linux x86-64

Linux AMD

64-bit

linux_ia64

Linux Itanium

64-bit

IBM Power Based Linux

Linux PPC

64-bit

linux_zseries64

zLinux

64-bit

HP Tru64 UNIX

Decunix

64-bit

Solaris Operating System (x86-64)

Solaris AMD64

64-bit

Solaris Operating System (x86)

Solaris AMD32

32-bit


Procuring Oracle Management Agent Software

Oracle Management Agent (Management Agent) is one of the core components of Enterprise Manager Grid Control, and therefore, its software is part of the Enterprise Manager Grid Control software. When you install Enterprise Manager Grid Control or an additional Oracle Management Service (OMS), the installation wizard automatically installs a Management Agent.

In graphical mode, you can install additional Management Agents using the Agent Deployment Wizard, which is a GUI-rich interface within the Enterprise Manager Grid Control console. This wizard installs additional Management Agents using the Management Agent software that is already present in the Oracle home of the OMS.

Note:

In Enterprise Manager 11g, you cannot install a Management Agent using the Oracle Universal Installer (OUI), which is the Enterprise Manager installation wizard.

However, note that the Management Agent software present in the Oracle home of the OMS is always for the version and platform on which that OMS is running. For example, if the OMS is Oracle Management Service 11g Release 1 and it is running on Linux platform, then the Management Agent software available there is also for Linux platform.

If you want to install Oracle Management Agent 10g or Oracle Management Agent 11g Release 1 for a platform that is different from the one on which the Oracle Management Service 11g Release 1 is running, then ensure that you download that software either automatically using the Agent Download application available in Enterprise Manager Grid Control or manually from Oracle Technology Network (OTN).

This section describes how you can procure the Management Agent software. In particular, this section covers the following:

Automatically Downloading Management Agent Software Using Download Agent Software Application

This section describes how you can use the Download Agent Software application, which is available in Enterprise Manager Grid Control, to download the Management Agent software. In particular, this section covers the following:

What Is Agent Download Application?

The Agent Download application can be accessed using the Enterprise Manager Grid Control console and used to download Management Agent software from My Oracle Support Web site.

The Management Agent software on My Oracle Support is available in the form of a ZIP file. You can choose to download it either in the default location, that is, the Oracle home of the OMS, or in a custom location.

What Prerequisites You Must Meet?

Before downloading the Management Agent software, meet the following prerequisites:

  • Set the My Oracle Support credentials. To do so, in Enterprise Manager Grid Control, click Setup. On the Overview of Setup page, from the menu bar on the left, click Patching Setup. For more information, click Help on that page.

  • Set the proxy settings if you have a proxy server in your environment. To do so, in Enterprise Manager Grid Control, click Setup. On the Overview of Setup page, from the menu bar on the left, click Patching Setup and then click Proxy & Connection Settings. For more information, click Help on that page.

  • Ensure that the download location, that is, the directory where you want to download the software, is writable.

How Do You Download the Management Agent Software?

To download the Management Agent software using the Enterprise Manager Grid Control console, follow these steps:

  1. In Enterprise Manager Grid Control, click Deployments.

  2. On the Deployments page, from the Agent Installation section, click Download Agent Software.

  3. On the Download Agent Software page, in the Available Agent Software section, select the Management Agent software you want to download. The application downloads the software ZIP file, extracts its contents, and then deletes the ZIP file.

    • The Platform column indicates the platform for which the Management Agent is supported. For example, Linux x86, Microsoft Windows (32-Bit), and so on.

      While the first part of the platform name refers to the name of the supported operating system, the second part in parenthesis refers to the type of operating system, that is, 32-bit or 64-bit.

      A 32-bit software can be installed only on a 32-bit operating system that is running on a 32-bit hardware. Similarly, a 64-bit software can be installed only on a 64-bit operating system that is running on a 64-bit hardware. Do NOT try to install a 32-bit software on a 64-bit platform or vice versa; the installation may proceed, but will fail eventually. Therefore, ensure that you download the right software for the right platform.

      To determine the type of your operating system, refer to My Oracle Support note 421453.1.

    • The Version column indicates the release/version of the Management Agent that you can download. For example, 11.1.0.1.0.

    • The Available on this OMS column indicates whether the Management Agent software is already available in the default location of the OMS from where Enterprise Manager Grid Control is being accessed. In case of multi-OMS environment, the OMS referred here is the OMS shown in the OMS field on top of the page.

      Note:

      This column indicates whether the software is already available only in the default location of the OMS. It does not indicate the presence of software downloaded to a non-default location or a shared location.

      The values can be either TRUE or FALSE. TRUE indicates that the software is already available on the OMS. You do not have to download it again. FALSE indicates that the software is not available on the OMS. You may want to download it.

    • The Size (MB) column indicates the size (in megabytes) of the software ZIP file available for download.

      Note:

      Enterprise Manager Grid Control actually downloads the ZIP file to the staging location and extracts the contents in the same location. The total size of all the extracted files may be more than the size mentioned here. Therefore, the space required in the staging location is at least double the size of the what is mentioned here.
  4. In the Staging Location section, select the location where you want to stage the Management Agent software.

    • Select Default Location if you want to download the Management Agent software to the default location, that is, to the Oracle home of the OMS (the one shown on top of the screen against the field Oracle Management Service). The default download location on the OMS is <OMS_HOME>/sysman/agent_download/<version>

      In case of a single OMS environment, Enterprise Manager Grid Control downloads the software ZIP file to the default location, extracts the files to the same location, and then deletes the ZIP file, leaving only the extracted files. In case of a multi-OMS environment, Enterprise Manager Grid Control downloads the software ZIP file and extracts the files to the first OMS home (the OMS shown in the OMS field on top of the screen), then copies the ZIP file to the next OMS home and extracts the files there as well. Once all OMS homes have the software, Grid Control deletes the ZIP file from each of the OMS homes, leaving only the extracted files.

      For a multi-OMS environment, you must provide the credentials to access the Oracle home directories of the OMSes in the environment.

      • Select Use Oracle Home Preferred Credentials if you want to use preferred credentials stored in the Management Repository.

      • Select Override Oracle Home Preferred Credentials if you want to override them with new set of credentials. If you select this option, you can specify either the same credentials or different credentials to access the OMSes in your environment, depending on how they are configured.

    • Select Custom Location and specify a location of your choice if you want to download the Management Agent software to a custom location. The custom location must be accessible from all the remote hosts and OMSes, and must have 'write' permission.

      This is an ideal choice under the following conditions:

      • When you have a shared, mounted location that is visible on all OMSes. The shared location can be anywhere in the enterprise configuration.

      • When you do not want Enterprise Manager Grid Control to download the software and extract the files on all the OMSes automatically. This way, you can download the software to one particular location and manually copy the files to other OMSes, whenever required.

      If the custom location already exists (that is, if you have manually created it), then Enterprise Manager Grid Control downloads the software ZIP file to that location. However, if the location does not exist, then Enterprise Manager Grid Control automatically creates the directories and then downloads the software there. If you already have a copy of the software in the default location, then Enterprise Manager Grid Control overwrites that with the version selected for download.

      Enterprise Manager Grid Control downloads the software ZIP file to the custom location, extracts the files to the same location, and deletes the ZIP file. If you have multiple OMSes, you have to manually copy the extracted files to other OMSes.

  5. Click Download to download the Management Agent software.

Manually Downloading Management Agent Software from OTN

To manually download the Management Agent software from OTN, access the following URL:

http://www.oracle.com/technology/software/products/oem/htdocs/agentsoft.html

Understanding Installation Basics

This section describes the fundamental aspects of the installation process. In particular, this section covers the following:

What Different Installation Modes Can You Use?

You can install Enterprise Manager Grid Control or any of its core components either in an interactive, graphical mode or in a silent mode.

Graphical Mode Graphical mode is the Graphical User Interface (GUI) method that involves usage of a Java-based installation wizard or a browser-based application that is built into and accessed from the Enterprise Manager Grid Control console. This method is best suited for first-time installations because you are guided through the entire installation process and your installation details are captured using the interview screens.
Silent Mode Silent method involves usage of Oracle-supplied response files or scripts that capture all the information required for installation. This method is simpler and faster, but requires you to have some knowledge on the installation process so that you can provide your installation details in the response files without having to see the interview screens of the installation wizard.

In both these modes, you can perform a software-only installation. A Software-Only installation is an approach that enables you to install only the software binaries of Enterprise Manager Grid Control or an OMS, that is, without any configuration to the installation. This is best suited when you want to install the software at one point and configure it later.

What Is Enterprise Manager Grid Control Installation Wizard?

Enterprise Manager Grid Control Installation Wizard is a Java-based wizard that helps you install or upgrade Enterprise Manager Grid Control or any of its core components in a graphical mode. If you are installing Enterprise Manager Grid Control or any of its core components for the first time, then Oracle strongly recommends you to use this installation wizard.

Figure 2-1 describes the key elements of the installation wizard.

Figure 2-1 Enterprise Manager Grid Control Installation Wizard

Surrounding text describes Figure 2-1 .

Note:

In Enterprise Manager 11g, you cannot install a Management Agent using the Oracle Universal Installer (OUI), which is the Enterprise Manager installation wizard.

What Installation Types Are Offered by the Installation Wizard?

Table 2-2 describes the installation types offered by the Enterprise Manager Grid Control installation wizard.

Note:

The procedures for the installation types offered by the Enterprise Manager Grid Control Install Wizard are documented in the Oracle Enterprise Manager Grid Control Basic Installation Guide available at:

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

Table 2-2 Installation Types Offered by the Enterprise Manager Grid Control Installation Wizard

Installation Type Description Core Components Installed and Configured, or Upgraded Reference Links

Install a new Enterprise Manager system

Installs Enterprise Manager Grid Control using an existing, certified Oracle Database where a Management Repository does not exist.

  • Installs Oracle Management Service 11g Release 1 (Deployed to the existing Oracle WebLogic Server)

  • Installs Oracle Management Agent 11g Release 1

  • Installs Oracle Web Tier 11g Release 1

  • Configures the Management Repository (in the existing Oracle Database), Oracle Management Service, and Oracle Management Agent

Graphical Mode

Oracle Enterprise Manager Grid Control Basic Installation Guide

Silent Mode

Add an additional Management Service

Installs an additional OMS to your existing Enterprise Manager Grid Control environment.

  • Installs Oracle Management Service 11g Release 1 (Deployed to the existing Oracle WebLogic Server)

  • Installs Oracle Management Agent 11g Release 1

  • Installs Oracle Web Tier 11g Release 1

Graphical Mode

Oracle Enterprise Manager Grid Control Basic Installation Guide

Silent Mode

Upgrade to Enterprise Manager 11g

Upgrades the following:

  • Enterprise Manager 10g Grid Control Release 2 (10.2.0.4.0) or higher to Enterprise Manager 11g Grid Control Release 1 (11.1.0.1.0)

  • (Additional) Oracle Management Service 10g Grid Control Release 2 (10.2.0.4.0) or higher to Oracle Management Service 11g Release 1 (11.1.0.1.0)

Automatically detects the Oracle homes and upgrades them to 11g Release 1 (11.1.0.1.0).

Graphical Mode

Oracle Enterprise Manager Grid Control Basic Installation Guide

Silent Mode


Note:

In Enterprise Manager 11g, you cannot install a Management Agent using the Oracle Universal Installer (OUI), which is the Enterprise Manager installation wizard.

What Ports Are Used for Installation?

This section describes the default ports that are honored while installing Enterprise Manager Grid Control. In particular, this section covers the following:

What Default Ports Are Used?

The following are the default ports used for installation:

  • Enterprise Manager Grid Control

      Upload Port Console Port
    HTTP Port 4889

    If 4889 is not available, then the first available free port from the range 4889 to 4898 is selected.

    The first available free port from the range 7788 - 7798 is selected.
    HTTPS Port 1159

    If 1159 is not available, then the first available free port from the range 4899 to 4908 is selected.

    The first available free port from the range 7799 - 7809 is selected.

  • Oracle Management Agent

    The default upload port for Management Agent is 3872. The same port is used for both HTTP and HTTPS. If 3872 is not available, then the first available free port from the range 1830 to 1849 is selected.

  • Admin Server

    The default HTTPS port for Admin Server is 7101. If 7101 is not available, then the first available free port from the range 7101 to 7200 is selected.

  • Node Manager

    The default HTTPS port for Node Manager is 7401. If 7401 is not available, then the first available free port from the range 7401 to 7500 is selected.

  • Managed Server

    The default HTTP port for Managed Server is 7201. If 7201 is not available, then the first available free port from the range 7201 to 7300 is selected.

    The default HTTPS port for Managed Server is 7301. If 7310 is not available, then the first available free port from the range 7301 to 7400 is selected.

How Can You Customize Ports?

Enterprise Manager Grid Control offers you the flexibility to use custom ports instead of default ports.

  • If you are installing Enterprise Manager Grid Control in graphical mode, that is, using the Enterprise Manager Grid Control Installation Wizard, then you can use the Customize Ports screen to specify custom ports.

  • If you are installing Enterprise Manager Grid Control in silent mode, that is, using the installation procedures described in Part III, "Installing Oracle Management Agent", then update the staticports.ini file with suitable custom ports.

    The staticports.ini file is available at the following location on the installation DVD:

    <DVD>/response/staticports.ini
    

    While updating the staticports.ini file, you must be extremely careful because an error in the file can cause the installation wizard to use default ports without displaying any warning. Therefore, before updating the staticports.ini file, check for these points:

    • If a port is already being used by a component or any other application, do not specify that port (used port) in the staticports.ini file. If you specify a port that is already in use, then the related Configuration Assistant also fails.

    • If you have specified the same port for more that one component, then the installation displays an error after the prerequisite checks phase. You must rectify this error before proceeding with the installation.

    • If you have syntax errors in the staticports.ini file (for example, if you omitted the equal (=) character for a line), then the installation wizard ignores the line. For the components specified on such lines, the installer assigns the default ports. The installation wizard does not display a warning for lines with syntax errors.

    • If you misspell a component name, then the installation wizard assigns the default port for the component. Names of components in the file are case-sensitive. The installation wizard does not display a warning for lines with unrecognized names.

    • If you specify a nonnumeric value for the port number, then the installation wizard ignores the line and assigns the default port number for the component. It does this without displaying any warning.

    • If you misspell the parameter on the command line, then the installation wizard does not display a warning. It continues and assigns default ports to all components.

    • If you specify a relative path to the staticports.ini file (for example, ./staticports.ini) on the command line, then the installation wizard does not find the file. It continues without displaying a warning and it assigns default ports to all components. You must specify a full path to the staticports.ini file.

    • If the parameter you specify on the command line does not match the installation type that you are performing (for example, if you specify the parameter for the middle tier but you are installing the infrastructure), the installation wizard does not give a warning. It continues and assigns default ports to all components.

What Precautions Must You Take While Customizing Port Numbers?

While customizing port numbers, consider the following:

  • Port numbers cannot be greater than 65536.

  • If you use a port number less than 1024 for a component, then you must run the component as the root user.

  • If you use a port number less than 1024 for a component, then the component cannot be started at the end of the installation. You may need to configure the component first before you can start it up.

How Can You Change the Language Used in Enterprise Manager Grid Control Console?

By default, the Enterprise Manager Grid Control Installation Wizard installs Enterprise Manager Grid Control console with English language. If you want to view them in another language, then select the required languages in the Select Languages screen of the installation wizard.

Note:

The language you select here changes the language used in the Enterprise Manager Grid Control console screens only; it does NOT change the language used in the installation wizard screens. The language of the installation wizard screens is based on the operating system language.

When you select additional languages to install, the installation wizard also installs fonts required to display the languages.

For some components, languages are installed only if you select them during installation. In this case, if you access the application in a language that is not available, it reverts to the locale language.

For other components, available languages are installed regardless of what you select during installation. In this case, however, fonts are installed only for the languages that are explicitly selected. When you access the application, it uses text in your language because the language was installed. However, if you do not have the appropriate fonts to render the text, the text appears as square boxes. This usually applies to the Chinese, Japanese, and Korean languages.

What Data Files Are Created While Configuring Oracle Management Repository?

The following are the data files created while configuring Oracle Management Repository:

  • mgmt_ecm_depot1.dbf

  • mgmt.dbf

  • mgmt_ad4j.dbf

How Do You Delete Data Files?

To delete the data files, you must drop the SYSMAN/MDS schema. To do so, run 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>

Note:

  • For Microsoft Windows, invoke RepManager.bat.

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

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

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%';

Understanding Oracle WebLogic Server Requirement

To install Enterprise Manager Grid Control, as a prerequisite, you must have Oracle WebLogic Server 10.3.2 (Oracle Fusion Middleware 11g Release 1 Patch Set 1). This section describes some important aspects related to Oracle WebLogic Server that you must know before you install Enterprise Manager Grid Control. In particular, this section covers the following:

How Do I Install Oracle WebLogic Server?

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

How Do I Verify Whether Oracle WebLogic Server Is Installed?

As a prerequisite, you must have Oracle WebLogic Server 10.3.2 (Oracle Fusion Middleware 11g Release 1 Patch Set 1) for installing Enterprise Manager Grid Control.

To verify whether Oracle WebLogic Server is installed, check the following file in the Oracle home of the Oracle WebLogic Server:

$<ORACL_HOME>/logs/log.txt

The following is the sample output of the log.txt file:

    release  10.3.2.0 [Added]
    |_____Common Infrastructure Engineering 6.8.0.0 [Added]
    |    |_____Uninstall [Added]
    |    |_____Patch Client [Added]
    |    |_____Patch Attachment Facility [Added]
    |    |_____Clone Facility [Added]
    |_____WebLogic Server 10.3.2.0 [Added]
    |    |_____Core Application Server [Added]
    |    |_____Administration Console [Added]
    |    |_____Configuration Wizard and Upgrade Framework [Added]
    .
    .
    .
    .

Is Oracle WebLogic Server Cluster Supported?

Oracle WebLogic Server cluster consists of multiple Oracle WebLogic Servers running simultaneously and working together to provide increased scalability and reliability. A cluster appears to be a single Oracle WebLogic Server instance. The server instances that constitute a cluster can run on the same host, or be located on different hosts.

You can install Enterprise Manager Grid Control on an Oracle WebLogic Server Cluster, however, you cannot take advantage of the cluster configurations.

Is the Existing Admin Server in Oracle WebLogic Server Used?

To install Enterprise Manager Grid Control, the Enterprise Manager Grid Control Installation Wizard uses the software binaries of the existing Oracle WebLogic Server, however, it does not use the existing Admin Server that is available. The Enterprise Manager Grid Control Installation Wizard create a new Admin Server and deploys the Enterprise Manager Grid Control software to it.

When and Why Do You Need Oracle WebLogic Server Credentials?

While installing or upgrading Enterprise Manager Grid Control and while upgrading an additional OMS, you are prompted to specify the Oracle WebLogic Server credentials (user name and password). The credentials are used for creating Oracle WebLogic Domain and other associated components such as the Admin Server, the managed server, and the node manager.

The WebLogic user name is the default user name that will be used as the administrative user for the WebLogic Domain. By default, the user name is weblogic. And the WebLogic password is the password for this default administrative user account.

When and Why Do You Need Node Manager Credentials?

While installing or upgrading Enterprise Manager Grid Control and while upgrading an additional OMS, you are prompted to specify the Node Manager password for the default Node Manager user account, which is nodemanager. The password is used for configuring the Node Manager. A Node Manager enables you to start, shut down, or restart an Oracle WebLogic Server instance remotely, and is recommended for applications with high availability requirements.

How Do You Find Admin Server Port While Installing an Additional OMS

To install an additional OMS, you might need to know the port of the Admin Server that is used by the first OMS. To find the port, view the value set for the AS_HTTPS_PORT parameter in the emgc.properties file. This file is available in the Oracle Management Service Instance Base location.

For example,

/u01/app/Oracle/gc_inst/user_projects/domains/EMGC_DOMAIN/em/EMGC_OMS1/emgc.properties

How Do You Verify Whether Admin Server Is Running?

To install an additional OMS, the Admin Server that is used by the first OMS must be up and running. To verify whether the Admin Server is running, access the Admin Server console using the following URL:

http://host:port/console

Here, host and port are values specified in the EM_INSTANCE_HOST and AS_HTTPS_PORT parameters, respectively, in the emgc.properties file. This properties file is available in the following location, that is, in the Oracle home of the OMS (first OMS) that was initially installed:

<ORACLE_HOME>/gc_inst/user_projects/domains/EMGC_DOMAIN/em/EMGC_OMS1/emgc.properties

How Do You Start Admin Server?

To install an additional OMS, the Admin Server that is used by the first OMS must be up and running. If it is not running, then start the Admin Server using the instructions outlined in the Oracle Fusion Middleware Administrator's Guide 11g Release 1 (11.1.1).

Alternatively, you can start the Admin Server by running the following command. Although the command is used essentially to start the OMS, the command in turn starts the Admin Server on which that OMS is running. So run this command even if you know that the OMS is already running.

emctl start oms

Understanding Installation Directories

This section describes the installation directories that need to be specified while installing Enterprise Manager Grid Control or any of its core components. In particular, this section covers the following:

What Is Oracle Inventory Directory?

If Enterprise Manager Grid Control is the first Oracle product that you are installing, then the Enterprise Manager Grid Control Installation Wizard prompts you to specify an inventory directory (also called the oraInventory directory).

This inventory directory is used by the installation wizard to place all the installer files and directories on the host. The installation wizard automatically sets up subdirectories for each Oracle product to contain the inventory data.

You can specify the OraInventory directory in two ways:

  • While installing Enterprise Manager Grid Control using the installation wizard, you can specify the OraInventory directory in the Oracle Inventory screen. When you specify it in this screen, you must also select the appropriate operating system group name that will own the OraInventory directories. The group you select must have write permission on the OraInventory directories.

  • While installing Enterprise Manager Grid Control in silent mode, that is, without using the installation wizard, you can specify the OraInventory directory using the -invPtrLoc parameter. This parameter considers the path to a location where the inventory pointer file (oraInst.loc) is available. For example, ./runInstaller -invPtrLoc /scratch/OracleHomes/oraInst.loc

Note:

Ensure that the Oracle Inventory (oraInventory) is not in a shared location.

If you already have an Oracle product installed on the host, then the installer uses the existing OraInventory directory that was created while installing that Oracle product. Ensure that you have write permission on that directory. To do so, run the installer as the same operating system user as the one who installed the other Oracle product.

Note:

OraInventory directory is different from Installation Directory. For information about Installation Directory, see What Is Oracle Middleware Home?.

What Is Oracle Middleware Home?

While installing Enterprise Manager Grid Control or an additional OMS using the Enterprise Manager Grid Control Installation Wizard, you are required to specify the Oracle Middleware Home location.

Oracle Middleware Home is the parent directory that has the Oracle WebLogic Server home, the Web tier instance files, and, optionally, one or more Oracle homes. This is where the OMS and the Management Agent are deployed.

The installation wizard uses its built-in algorithm to identify this location, and displays it for you to validate. By default, the following is the Oracle Middleware Home location:

/u01/app/Oracle/Middleware

You can either accept the default location or select another location that has write permission.

Note:

Oracle Middleware Directory is different from Oracle home of OMS or Oracle Management Agent. For information about Oracle home, see What Is Oracle Home?.

What Is Oracle Management Service Instance Base Location?

While installing Enterprise Manager Grid Control or an additional OMS using the Enterprise Manager Grid Control Installation Wizard, you are required to specify the Oracle Management Service Instance Base Location.

Oracle Management Service Instance Base Location is the directory under the parent directory of the Oracle Middleware Home, where the configuration files of OMS are stored. 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 itself.

The installation wizard uses its built-in algorithm to identify this location, and displays it for you to validate. If the Oracle Middleware Home was /u01/app/Oracle/Middleware/, then by default, the following is the Oracle Management Service Instance Base Location:

/u01/app/Oracle/gc_inst

You can either accept the default location or specify another location that has write permission.

Note:

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

What Is Oracle Home?

Oracle home is the directory where OMS and Management Agent are installed. By default, the Oracle home of OMS is oms11g and the Oracle home of Management Agent is agent11g. Both these Oracle homes are created in the Oracle Middleware Home.

For example, if you specify /u01/app/Oracle/Middleware as the Oracle Middleware Home, then the Oracle home of the OMS is created as /u01/app/Oracle/Middleware/oms11g, and the Oracle home of the Management Agent is created as /u01/app/Oracle/Middleware/agent11g.

Note:

Oracle home is different from OraInventory and Oracle Management Agent Home. For information about OraInventory directory, see What Is Oracle Inventory Directory?.

What Is Installation Base Directory?

While installing a Management Agent using the Agent Deployment Wizard, you are required to specify an Installation Base Directory.

Installation Base Directory is the parent directory on the remote host where the Oracle home of the Management Agent is created.

For example, if you specify the installation base directory as /john/oracle/, then the Oracle home of the Management Agent is created as /john/oracle/agent11g.

What Is EMSTATE Directory?

While installing a Management Agent using the Shared Agent Deployment Wizard, you are required to specify an EMSTATE directory.

EMSTATE directory is the directory that is created on each of the remote hosts and is used for storing configuration files such as emd.properties, targets.xml, log files, and so on.

Every host that shares the Management Agent binaries has its own EMSTATE directory, and you can specify any name for it. For example, you can have an EMSTATE directory titled emstatedir_11_1.

The EMSTATE directory location must meet the following conditions:

  • The EMSTATE directories of agents on different hosts should be local to the host instead of on the mounted drive, for security reasons.

  • Since the EMSTATE directory contains the targets pertaining to each host, it is highly recommended to have it on a local host.

The EMSTATE directory must meet the following space requirements:

  • The initial space required for EMSTATE directories is 1 MB.

  • Since all the upload files, collection files, and log files are stored in this directory, the size of the directory will increase. Consequently, Oracle recommends that you allocate sufficient space for the EMSTATE directories after taking these factors into account.

What Is /TMP C:\Temp Directory Used For?

When you invoke the Enterprise Manager Grid Control Installation Wizard, it automatically copies some executable files and link files to a temporary directory on the host. For example, the default /tmp directory on UNIX hosts, and C:\Temp on Microsoft Windows hosts.

If the host is set to run cron jobs along with many other processes that may be running periodically, then these jobs attempt to clean up the default temporary directory, thereby deleting some files and causing the installation wizard to fail.

If there are any cron jobs or processes that are automatically run on the hosts to clean up the temporary directories, then ensure that you set the TMP or TEMP environment variable to a location that is different from the default location. Ensure that the non-default location you set is secure on the hard drive, that is, the non-default location is a location where cleanup jobs are not run. Also ensure that you have write permissions on this alternative directory.

This must be done before you run the installer to invoke the Enterprise Manager Grid Control Installation Wizard. (For UNIX operating systems, you invoke runInstaller, and for Microsoft Windows, you invoke setup.exe).

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.

Understanding Additional Components Installed

This section describes the additional components that are installed along with the core components of Enterprise Manager Grid Control. In particular, this section covers the following:

What Is Oracle Configuration Manager?

While installing Enterprise Manager Grid Control or any of its core components, you can choose to enable Oracle Configuration Manager. Alternatively, you can enable it after installing Enterprise Manager Grid Control.

Oracle Configuration Manager automatically collects configuration information from your environment at regular intervals and uploads it to Oracle repository. This helps Oracle maintain up-to-date information about your environment, identify security vulnerabilities, quickly diagnose support issues, and offer better solutions consistently.

However, no business or personal information is collected and uploaded, except for local contact name in the event of transmission problems. Oracle guarantees that all the information collected will be kept strictly confidential and under no circumstances will this information be shared with any other party.

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

If the host from where you are running the installation wizard has a connection to the Internet, then on the Oracle Configuration Manager screen of the installation wizard, specify the My Oracle Support user name (or e-mail address) and password.

Otherwise, specify only the e-mail address and leave the other fields blank. After you complete the installation, manually collect the configuration information and upload it to My Oracle Support. To understand how the configuration information can be manually collected and uploaded, see the steps outlined in Manually Collecting and Uploading Configuration Information.

If you want to enable it after installation Enterprise Manager Grid Control, then see Enabling Oracle Configuration Manager After Installing Enterprise Manager Grid Control.

Manually Collecting and Uploading Configuration Information

To manually collect the configuration information, follow these steps:

  1. Navigate to the Oracle home of the OMS and run the following command:

    $<ORACLE_HOME>/ccr/bin/emCCR collect

    For Oracle Configuration Manager 10.2.7 and higher, the collected configuration information is stored in the /ccr/hosts/state/upload/ocmconfig.jar file. For lower versions of Oracle Configuration Manager, the collected configuration information is stored in the /ccr/state/upload/ocmconfig.jar file. When you run the same command next time, the ocmconfig.jar file gets overwritten with fresh data. Therefore, at any point, you will see only one ocmconfig.jar file.

  2. Upload the ocmconfig.jar file to a Service Request on My Oracle Support.

  3. Repeat Step (1) and Step (2) from the Oracle home of Oracle Management Agent.

Enabling Oracle Configuration Manager After Installing Enterprise Manager Grid Control

To enable Oracle Configuration Manager at a later point, do the folllowing:

  1. Set the environment variable ORACLE_CONFIG_HOME to the Oracle Management Service Instance Base. Oracle Management Service Instance Base is the directory where the configuration files of the OMS are created.

  2. From the Oracle home of the OMS, run the following command:

    $<ORACLE_HOME>/ccr/bin/setupCCR

  3. From the Oracle home of Oracle Management Agent, run the following command:

    $<ORACLE_HOME>/ccr/bin/setupCCR

What Are Software Updates?

While installing or upgrading Enterprise Manager Grid Control or an additional OMS, you can choose to install software updates.

Software updates include interim patches, critical patch updates, prerequisite updates, install updates, and so on released by Oracle periodically.

How Can You Download the Software Updates?

You can either manually download the software updates or have the Enterprise Manager Grid Control Installation Wizard automatically download them for you.

  • Manual Download by User: If you choose to manually download the software updates yourself, then run the following utility and provide the required information:

    <DVD>/install/utility/downloadSWUpdates -u <My_Oracle_Support_Username> -p <My_Oracle_Support_Password>

    Note:

    If you want to know about the different arguments that can be passed with the utility, then run the following command:

    <DVD>/install/utility/downloadSWUpdates -h

    Manual download option is best suited when you are installing Enterprise Manager Grid Control or an additional OMS in silent mode. Oracle recommends you to use this option even while installing in graphical mode.

    For information on where the software updates get downloaded by default, and for information on how to download to a custom location, see Where Are the Software Updates Downloaded?.

  • Automatic Download by Installation Wizard: If you choose to have the Enterprise Manager Grid Control Installation Wizard automatically download the software updates, then on Install Software Updates screen of the installation wizard, specify the My Oracle Support account user name and password. The installation wizard will connect to My Oracle Support and automatically download the updates from there.

When Can You Apply the Software Updates?

You can apply the software updates in one of the following ways depending on the download mechanism:

  • Manual Download by User: If you have manually downloaded the software updates, then:

    • In Silent Mode: Before you invoke the installer using the response file, edit the response file to set the INSTALL_UPDATES_SELECTION parameter to "staged". Then, for the STAGE_LOCATION parameter, specify the full path, which leads to the Updates directory, where the software updates are available.

    • In Graphical Mode: On the Install Software Updates screen of the Enterprise Manager Grid Control Installation Wizard, specify the full path, which leads to the Updates directory, where the software updates are available.

  • Automatic Download by Installation Wizard: If you choose to have the Enterprise Manager Grid Control Installation Wizard automatically download and apply the software updates, then on Install Software Updates screen of the installation wizard, specify the My Oracle Support account user name and password. The installation wizard will connect to My Oracle Support and automatically download the updates from there, and then apply them during installation.

Oracle strongly recommends you to apply them while the installation is in progress for the following reasons:

  • Keeping track of the availability of software updates at the time of installation is difficult

  • Keeping track of the patch numbers, and manually downloading them and applying them after installation is a cumbersome process

Automatically downloading and applying the software updates during installation saves time and effort, and ensures that you do not miss out on important software updates. However, note that when you deinstall the product, the updates are downloaded and stored in a directory titled Updates in the scratch path location. For example, if the scratch path location is /scratch/OracleHomes/, then the software updates are downloaded and stored in /scratch/OracleHomes/Updates.

Where Are the Software Updates Downloaded?

By default, the software updates are downloaded and stored in a subdirectory titled Updates in the temporary directory location (for example, /tmp in UNIX and C:\Temp in Microsoft Windows). For example, /tmp/Updates.

If you do not want the software updates to be downloaded in the temporary directory location, then run the following command and specify a download location of your choice:

<DVD>/install/utility/downloadSWUpdates -u <My_Oracle_Support_Username> -p <My_Oracle_Support_Password> -s <Custom_Download_Location>

Understanding Configuration Assistants

This section describes the postinstallation activities that are performed by the installation wizard. In particular, this section covers the following:

What Are Configuration Assistants?

While installing or upgrading Enterprise Manager Grid Control or any of its core components using the Enterprise Manager Grid Control Installation Wizard, a set of Configuration Assistants are run at the end of the installation process to configure the installed components. Your installation process is complete only after all the installed components are configured using these Configuration Assistants.

What Configuration Assistants Are Run by the Installation Wizard?

The following are the Configuration Assistants run by the installation wizard:

Table 2-3 Configuration Assistant

Installation Type Configuration Assistant

Install a new Enterprise Manager system

(Install type offered by the Enterprise Manager Grid Control installer)

  1. (Optional) OMS One-Off Patch Application

  2. Repository Configuration Assistant

  3. (Optional) MDS Schema Configuration Assistant

  4. (Optional) OCM EM Repository Instrumentation

  5. OMS Configuration Assistant

  6. Add-On OMS Side Configuration

  7. (Optional) OCM Configuration for OMS (Runs only if My Oracle Support credentials were provided in the installation wizard)

  8. (Optional) Agent One-Off Patch Application

  9. Agent Configuration Assistant

  10. (Optional) OCM Configuration (Runs only if My Oracle Support credentials were provided in the installation wizard)

  11. (Optional) Agent Add-On Plug-In (Runs only if Oracle System Monitoring Plug-ins are detected on the host)

Add an additional Management Service

(Install type offered by the Enterprise Manager Grid Control installer)

  1. (Optional) OMS One-Off Patch Application

  2. OMS Configuration Assistant

  3. Add-On OMS Side Configuration

  4. (Optional) OCM Configuration for OMS (Runs only if My Oracle Support credentials were provided in the installation wizard)

  5. (Optional) Agent One-Off Patch Application

  6. Agent Configuration Assistant

  7. (Optional) OCM Configuration (Runs only if My Oracle Support credentials were provided in the installation wizard)

  8. (Optional) Agent Add-On Plug-In (Runs only if Oracle System Monitoring Plug-ins are detected on the host)

Upgrade to Enterprise Manager 11g

(Install type offered by the Enterprise Manager Grid Control installer)

  • While upgrading Enterprise Manager 10g Grid Control Release 4 (10.2.0.4.0) or higher, the Configuration Assistants run are the same as the ones run for the install type Install a new Enterprise Manager system (as described in the first row of this table), but the Repository Configuration Assistant is called Repository Upgrade Configuration Assistant, and the Agent Configuration Assistant is called Agent Upgrade Configuration Assistant.

  • While upgrading Oracle Management Service 10g Release 4 (10.2.0.4.0) or higher, then Configuration Assistants run are the same as the ones run for the install type Add an additional Management Service (as described in the second row of this table), but the Agent Configuration Assistant is called Agent Upgrade Configuration Assistant.

Oracle Management Agent (Using any of the Management Agent installation methods described in this guide. This is not an install type offered by the Enterprise Manager Grid Control installer)

  1. (Optional) Agent One-Off Patch Application

  2. Agent Configuration Assistant

  3. (Optional) OCM Configuration (Runs only if My Oracle Support credentials were provided in the installation wizard)

  4. (Optional) Agent Add-On Plug-In (Runs only if Oracle System Monitoring Plug-ins are detected on the host)


Note:

  • If an optional Configuration Assistant fails, then the installation wizard ignores the failure and runs to the next Configuration Assistant automatically. However, if a mandatory Configuration Assistant fails, then the installation wizard stops the installation process.

  • If you use the Installing Enterprise Manager Software Only and Configuring Later approach, then an additional Configuration Assistant called Verify Addons Installed is run.

What Is Agent Configuration Assistant Used For?

The Agent Configuration Assistant (agentca) is a Configuration Assistant that is run during the configuration phase to configure the Management Agent.

Besides configuring the Management Agent when it is first installed, you use the agentca script to discover the newly installed targets, convert a standalone Management Agent to a cluster-based Management Agent, discover the targets installed on the new nodes of a cluster, and reconfigure a cluster-based Management Agent. To understand how you can perform these operations, see Appendix I, "Reconfiguring Oracle Management Agent and Discovering New Targets".

Table 2-4 shows the arguments you can pass with the agentca script.

Table 2-4 Arguments Supported by Agent Configuration Assistant (agentca)

Option Description

-n

Specify the cluster name (CLUSTER_NAME).

-c

Specify a comma-separated cluster node list.

-t

Do not start the agent after reconfiguration or target rediscovery.

-d

Rediscover targets.

-f

Reconfigure agents.

-i

Specify the oraInst.loc (oracle inventory location). This is required when the Oracle home does not exist in the central inventory.

-h

Get information on all the available options.


What Do You Do When Configuration Assistants Fail?

Table 2-5 describes what you must do when Configuration Assistants fail.

Table 2-5 Actions to be Performed When Configuration Assistants Fail

Configuration Assistant Log Files to Review Actions to be Taken

OMS One-Off Patch Application

$<ORACLE_HOME>/cfgtoollogs/opatch/opatch<timestamp>.log

(ORACLE_HOME refers to the Oracle home of the OMS)

  1. Resolve the cause of the issue.

  2. Rerun the Configuration Assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Grid Control Installation Wizard and click Retry.

    If you are installing in silent mode, then rerun the configureGC.pl script from the Oracle home of the OMS:

    $<ORACLE_HOME>/perl/bin/perl <ORACLE_HOME>/sysman/install/ConfigureGC.pl

Repository Configuration Assistant

Review the log files in the following locations:

$<ORACLE_HOME>/cfgtoollogs/cfgfw/emmdscreate_<timestamp>.log

$<ORACLE_HOME>/sysman/log/schemamanager/m_<timestamp>/m_<timestamp>.<ACTION>/

(ORACLE_HOME refers to the Oracle home of the OMS. <ACTION> refers to any of the schema actions, for example, CREATE, TRANSX, MY_ORACLE_SUPPORT, and so on. For more information about these repository log files, see Repository Configuration Logs.)

  1. Resolve the cause of the issue.

  2. Clean up the Management Repository by running the following command:

    $<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>

    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)

  3. Rerun the Configuration Assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Grid Control Installation Wizard and click Retry.

    If you are installing in silent mode, then rerun the configureGC.pl script from the Oracle home of the OMS:

    $<ORACLE_HOME>/perl/bin/perl <ORACLE_HOME>/sysman/install/ConfigureGC.pl

MDS Schema Configuration Assistant

$<ORACLE_HOME>/cfgtoollogs/cfgfw/emmdscreate_<timestamp>.log

For more information, review the following log files:

<ORACLE_HOME>/sysman/log/schemamanager/m_<timestamp>/m_<timestamp>.CREATE/mds.log

$<ORACLE_HOME>/sysman/log/schemamanager/m_<timestamp>/m_<timestamp>.CREATE/rcu.log

(ORACLE_HOME refers to the Oracle home of the OMS)

  1. Drop the MDS schema by running the following command from the Oracle home of OMS:

    $<ORACLE_HOME>/sysman/admin/emdrep/bin/mdsschemamanager.pl -action=-dropRepository -connectString=<database_connect_string> -dbUser= <database_user> -dbPassword=<database_password> -oracleHome=<OMS_oracle_home> -mwHome=<middleware_home>

    Where where <database_connect_string> must be in the following format:<database_host>:<database_port>:<database_sid>

  2. Rerun the Configuration Assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Grid Control Installation Wizard and click Retry.

    If you are installing in silent mode, then rerun the configureGC.pl script from the Oracle home of the OMS:

    $<ORACLE_HOME>/perl/bin/perl <ORACLE_HOME>/sysman/install/ConfigureGC.pl

OCM EM Repository Instrumentation

$<ORACLE_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

(ORACLE_HOME refers to the Oracle home of the OMS)

  1. Resolve the cause of the issue.

  2. Rerun the Configuration Assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Grid Control Installation Wizard and click Retry.

    If you are installing in silent mode, then rerun the configureGC.pl script from the Oracle home of the OMS:

    $<ORACLE_HOME>/perl/bin/perl <ORACLE_HOME>/sysman/install/ConfigureGC.pl

OMS Configuration Assistant

  • If the installer fails BEFORE the OMS Configuration Assistant starts running, review the following log file:

    $<ORACLE_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

  • If the installer fails AFTER the OMS Configuration Assistant starts running, then review the following log file:

    $<ORACLE_HOME>/cfgtoollogs/omsca/omsca_<timestamp>.log

(ORACLE_HOME refers to the Oracle home of the OMS)

  1. Check whether any Java processes are running from the Oracle Middleware Home. To do so, run the following command from the host where the OMS is running:

    ps -ef | grep java | grep <Oracle_Middleware_Home>

  2. Kill all the running processes, except for installer-related Java processes, by the running the following command. The installer-related Java processes run from the temp directory, so you can ignore the processes from that directory.

    kill -9 <process_id>

  3. Remove the Oracle Management Service Instance Base by running the following command:

    rm -rf <OMS_Instance_Home>

  4. Rerun the Configuration Assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Grid Control Installation Wizard and click Retry.

    If you are installing in silent mode, then rerun the configureGC.pl script from the Oracle home of the OMS:

    $<ORACLE_HOME>/perl/bin/perl <ORACLE_HOME>/sysman/install/ConfigureGC.pl

Add-on OMS Side Configuration

$<ORACLE_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

(ORACLE_HOME refers to the Oracle home of the OMS)

  1. Resolve the cause of the issue.

  2. Rerun the Configuration Assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Grid Control Installation Wizard and click Retry.

    If you are installing in silent mode, then rerun the configureGC.pl script from the Oracle home of the OMS:

    $<ORACLE_HOME>/perl/bin/perl <ORACLE_HOME>/sysman/install/ConfigureGC.pl

Oracle Configuration Manager Repeater Configuration

Review the following log file and identify the patch that failed:

$<ORACLE_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

(ORACLE_HOME refers to the Oracle home of the OMS)

  1. Resolve the cause of the issue.

  2. Rerun the Configuration Assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Grid Control Installation Wizard and click Retry.

    If you are installing in silent mode, then rerun the configureGC.pl script from the Oracle home of the OMS:

    $<ORACLE_HOME>/perl/bin/perl <ORACLE_HOME>/sysman/install/Confi ureGC.pl

OCM Configuration for OMS

$<ORACLE_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

(ORACLE_HOME refers to the Oracle home of the OMS)

  1. Resolve the cause of the issue.

  2. Rerun the Configuration Assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Grid Control Installation Wizard and click Retry.

    If you are installing in silent mode, then rerun the configureGC.pl script from the Oracle home of the OMS:

    $<ORACLE_HOME>/perl/bin/perl <ORACLE_HOME>/sysman/install/ConfigureGC.pl

Agent One-Off Patch Application

$<ORACLE_HOME>/cfgtoollogs/opatch/opatch<timestamp>.log

(ORACLE_HOME refers to the Oracle home of the Management Agent)

  1. Resolve the cause of the issue.

  2. Rerun the Configuration Assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Grid Control Installation Wizard and click Retry.

    If you are installing in silent mode, then run the following command from the Oracle home of the Management Agent:

    $<ORACLE_HOME>/OPatch/opatch apply -invPtrLoc <ORACLE_HOME>/oraInst.loc -silent -local -oh <ORACL_HOME> <one-off_patch_location>

Agent Configuration Assistant

$<ORACLE_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

(ORACLE_HOME refers to the Oracle home of the Management Agent)

If secure fails, then review the following log file:

$<ORACLE_HOME>/sysman/log/secure.log

  1. Resolve the cause of the issue.

  2. Rerun the Configuration Assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Grid Control Installation Wizard and click Retry.

    If you are installing in silent mode, then run the following command from the Oracle home of the Management Agent:

    $<ORACLE_HOME>/bin/agentca -f

OCM Configuration

$<ORACLE_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

(ORACLE_HOME refers to the Oracle home of the Management Agent)

  1. Resolve the cause of the issue.

  2. Rerun the Configuration Assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Grid Control Installation Wizard and click Retry.

    If you are installing in silent mode, then run the following command from the Oracle home of the Management Agent:

    $<ORACLE_HOME>/bin/agentca -f

Agent Add-On Plug-In

$<ORACLE_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

(ORACLE_HOME refers to the Oracle home of the Management Agent)

  1. Resolve the cause of the issue.

  2. Rerun the Configuration Assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Grid Control Installation Wizard and click Retry.

    If you are installing in silent mode, then run the following command from the Oracle home of the Management Agent:

    $<ORACLE_HOME>/perl/bin/perl <ORACLE_HOME>/sysman/install/AddonConfig.pl <ORACLE_HOME>

Repository Upgrade Configuration Assistant

Review the log files in the following locations:

$<ORACLE_HOME>/cfgtoollogs/cfgfw/emmdscreate_<timestamp>.log

$<ORACLE_HOME>/sysman/log/schemamanager/m_<timestamp>/m_<timestamp>.<ACTION>/

(ORACLE_HOME refers to the Oracle home of the OMS. <ACTION> refers to any of the schema actions, for example, PREUPGRADE, UPGRADE, TRANSX, and so on. For more information about these repository log files, see Repository Configuration Logs.)

  1. Resolve the cause of the issue.

  2. Rerun the Configuration Assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Grid Control Installation Wizard and click Retry.

    If you are installing in silent mode, then rerun the configureGC.pl script from the Oracle home of the OMS:

    $<ORACLE_HOME>/perl/bin/perl <ORACLE_HOME>/sysman/install/ConfigureGC.pl

Agent Upgrade Configuration Assistant

$<ORACLE_HOME>/cfgtoollogs/cfgfw/CfmLogger_<timestamp>.log

If secure fails, then review the following log file:

$<ORACLE_HOME>/sysman/log/secure.log

(ORACLE_HOME refers to the Oracle home of the Management Agent)

  1. Resolve the cause of the issue.

  2. Rerun the Configuration Assistant.

    If you are installing in graphical mode, then return to the Enterprise Manager Grid Control Installation Wizard and click Retry.

    If you are installing in silent mode, then run the following command from the Oracle home of the Management Agent:

    $<ORACLE_HOME>/bin/agentca -f -u


Understanding Prerequisite Checks

Every time you install Enterprise Manager Grid Control using the installation wizard, a set of prerequisite checks are run to verify if the environment meets the minimum requirements for a successful installation. The installation wizard checks for a variety of things including required operating system patches, operating system packages, kernel parameters, and so on.

The following sections describe these prerequisite checks. In particular, this section covers the following:

What Prerequisite Checks Are Run by Default?

Table 2-6 lists the default prerequisite checks that are run by the Enterprise Manager Grid Control Installation Wizard for different installation types.

Table 2-6 Prerequisite Checks Run by Enterprise Manager Grid Control Installation Wizard for Different Installation Types

Installation Type Prerequisite Checks
  • Install a new Enterprise Manager system

  • Additional Oracle Management Service

  • Upgrading an existing, previous release of Enterprise Manager Grid Control or any additional Oracle Management Service

  • Oracle Management Agent

  • Upgrading an existing, previous release of Oracle Management Agent


How Can You Run Prerequisite Checks in Standalone Mode?

You can run the prerequisite checks in standalone mode before invoking the installation wizard. This helps you identify and resolve issues that might otherwise cause the installation to fail.

Table 2-7 shows the commands you need to run to run the prerequisite checks in standalone mode:

Table 2-7 Running Prerequisite Checks in Standalone Mode

Installation Type Command
  • Install a new Enterprise Manager system

  • Additional Oracle Management Service

  • Upgrading an existing, previous release of Enterprise Manager Grid Control or any additional Oracle Management Service

<Software_Location>/install/runInstaller -prereqchecker PREREQ_CONFIG_LOCATION=<Software_Location>/emgc/Disk1/stage/prereq -entryPoint "oracle.sysman.top.oms_Core" -prereqLogLoc <absolute_path_to_log_location> -silent -waitForCompletion

  • Oracle Management Agent

  • Upgrading an existing, previous release of Oracle Management Agent

<Software_Location>/install/runInstaller -prereqchecker PREREQ_CONFIG_LOCATION=<Software_Location>/emgc/Disk1/stage/prereq -entryPoint "oracle.sysman.top.agent_Complete" -prereqLogLoc <absolute_path_to_log_location> -silent -waitForCompletion


Note:

On Microsoft Windows, replace /runInstaller with setup.exe. Also, <Software_Location> mentioned in the commands in Table 2-7 refer to the location where the Enterprise Manager software is available. For example, DVD. If you have downloaded the software from Oracle Technology Network (OTN), then specify the full path to that downloaded location.

Understanding Limitations of Enterprise Manager Grid Control

This section describes the limitations you might face while using Enterprise Manager Grid Control. In particular, this section covers the following:

Can You Access Unlicensed Components?

Although the installation media in your media pack contain many Oracle components, you are permitted to use only those components for which you have purchased licenses. Oracle Support Service does not provide support for components for which licenses have not been purchased.

For more information, access the Enterprise Manager documentation library at the following URL and view the Oracle Enterprise Manager Licensing Information Guide:

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

What Are the Limitations with DHCP-Enabled Machines?

Do NOT run the OMS on a computer that is DHCP enabled. Oracle strongly suggests that you use a static host name or IP address assigned on the network for Enterprise Manager Grid Control components to function properly.

For more information, refer to My Oracle Support Note 428665.1 at:

https://metalink.oracle.com/

Understanding Other Miscellaneous Concepts

This section covers miscellaneous concepts related to the installation of Enterprise Manager Grid Control. In particular, this section covers the following:

What Is a Host List File?

While using the Agent Deployment Wizard, you can specify the hosts on which you want to install Oracle Management Agent, in two ways:

  • Specify either the host name or the IP address. Separate multiple host names using a comma, a white space, or a new line.

  • Select an external file that contains a list of hosts mentioned.

    If you choose to select an external file that contains a list of all required host names, then ensure that the file format is similar to /etc/hosts file. The following is the recommended format of the /etc/hosts file.

    154.87.3.229 host1.foo.com host1
    154.87.3.109 host2.foo.com host2
    154.80.5.218 host3.foo.com host3 
    

    IPv6 entries are supported in the file for fresh installations of 11g Release 1 (11.1). However, they are not supported for upgrade from 10g Release 4 (10.2.0.4) or higher to 11g Release 1 (11.1).

    Note:

    According to RFC 952, the following are the assumptions: A "name" (Net, Host, Gateway, or Domain name) is a text string up to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus sign (-), and period (.). Note that periods are only allowed when they serve to delimit components of "domain style names". No blank or space characters are permitted as part of a name. No distinction is made between upper and lower case. The first character must be an alpha character.

    The Agent Deployment Wizard picks up only the values in the first column of the Host List file that you select. Ensure that the host list format is appropriate because the Agent Deployment Wizard does not validate this format on the selected file.

    WARNING:

    Ensure that you do not specify duplicate entries of the hosts. If there are duplicate host entries in the list, then the application hangs. Also ensure that you use the same host names for which the SSH has been set.

What SYSDBA Privileges Are Required for Creating Repository Schema?

Table 2-8 lists the SYSDBA privileges required by the existing DBA to create the Management Repository schema:

Table 2-8 SYSDBA Privileges Required for Creating Repository Schema

Object Name Privilege Required Whether or Not the Privilege Can Be Granted Command to Grant the Privilege

dbms_aq

execute

true

grant EXECUTE on DBMS_AQ to <username> with grant option

dbms_aqadm

execute

true

grant EXECUTE on DBMS_AQADM to <username> with grant option

dbms_rls

execute

true

grant EXECUTE on DBMS_RLS to <username> with grant option

aux_stats$

select

true

grant SELECT on AUX_STATS$ to <username> with grant option

aux_stats$

insert

true

grant INSERT on AUX_STATS$ to <username> with grant option

aux_stats$

update

true

grant UPDATE on AUX_STATS$ to <username> with grant option

aux_stats$

delete

true

grant DELETE on AUX_STATS$ to <username> with grant option

dbms_random

execute

true

grant EXECUTE on DBMS_RANDOM to <username> with grant option

dbms_redefinition

execute

true

grant EXECUTE on DBMS_REDEFINITION to <username> with grant option

dbms_lob

execute

true

grant EXECUTE on DBMS_LOB to <username> with grant option

dbms_lock

execute

true

grant EXECUTE on DBMS_LOCK to <username> with grant option

dbms_crypto

execute

true

grant EXECUTE on DBMS_CRYPTO to <username> with grant option

dbms_session

execute

true

grant EXECUTE on DBMS_SESSION to <username> with grant option

dbms_utility

execute

true

grant EXECUTE on DBMS_UTILITY to <username> with grant option

utl_file

execute

true

grant EXECUTE on UTL_FILE to <username> with grant option

Access Policy

exempt

true

grant EXEMPT ACCESS POLICY to <username>


What Scripts Are Run During the Installation Process?

At least once during or after the installation of Enterprise Manager Grid Control or Management Agent, you are prompted to log in as a root user and run oraInstRoot.sh, allroot.sh, or root.sh. You must log in as a root user because the scripts edit files in the /etc directory and create files in the local bin directory (/usr/local/bin, by default).

After every installation, a check is performed to identify the Central Inventory (oraInventory) directory. The Central Inventory directory is a directory that is automatically created by the installation wizard when an Oracle product is installed on a host for the very first time.

Note:

Ensure that 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
  • If you have NOT installed an Oracle product before on the host, then run the oraInstRoot.sh script from the Central Inventory:

    $Home/oraInventory/oraInstRoot.sh

    The oraInstRoot.sh script is run to create the oraInst.loc file. The oraInst.loc file contains the Central Inventory location.

  • However, if you already have an Oracle product on the host, then run the following:

    • If you are installing Enterprise Manager Grid Control or an additional OMS, then run allroot.sh script from the Oracle home of the OMS (oms11g):

      <Oracle_Home>/allroot.sh

    • If you are installing a Management Agent, then run root.sh script from the Oracle home of the Management Agent (agent11g):

      <Oracle_Home>/root.sh