| Oracle® Enterprise Manager Grid Control Installation and Configuration Guide 10g Release 5 (10.2.0.5.0) Part Number E10953-15 |
|
|
View PDF |
| Oracle® Enterprise Manager Grid Control Installation and Configuration Guide 10g Release 5 (10.2.0.5.0) Part Number E10953-15 |
|
|
View PDF |
This chapter provides information about the preinstallation requirements you must meet before installing Enterprise Manager Grid Control (Grid Control).
In particular, this chapter covers the following:
This section lists the recommended hardware requirements for running the various Grid Control deployment sizes on all the supported platforms. In particular, this section covers the following:
Table 3–1 and Table 3–2 approximate the host, CPU, and physical memory requirements for running a Grid Control deployment (typical scenario with 2 to 3 GHz machines), based on experiences with real-world Grid Control deployments.
Table 3-1 CPU and Memory Allocation for Oracle Management Service
| Deployment Size | Host | CPU/Host | Physical Memory (RAM)/Host | Total Recommended Space |
|---|---|---|---|---|
|
Small (100 monitored targets) |
1 |
1 (3 GHz) |
2 GB |
2 GB |
|
Medium (1,000 monitored targets) |
1 |
2 (3 GHz) |
2 GB |
Number of OMS x 5 GB |
|
Large (10,000 monitored targets) |
2 |
2 (3 GHz) |
2 GB |
Number of OMS x 10 GB |
Table 3-2 CPU and Memory Allocation for Oracle Management Repository
| Deployment Size | Host | CPU/Host | Physical Memory (RAM)/Host | Total Repository Storage |
|---|---|---|---|---|
|
Small (100 monitored targets) |
1 (3 GHz) |
2 GB |
10 GB |
|
|
Medium (1,000 monitored targets) |
1 |
2 (3 GHz) |
4 GB |
30 GB |
|
Large (10,000 monitored targets) |
2 |
4 (3 GHz) |
6 GB |
150 GB |
Footnote 1 Share Host with the Oracle Management Service for small deployments.
For Oracle Management Agent (Management Agent), the hard disk space required is 400 MB for Linux (32-bit) and500 MB for Microsoft Windows (32-bit). For information about hard disk space required for other platforms, see the Agent Best Practices document available at the following URL:
http://www.oracle.com/technology/products/oem/pdf/10gr2_agent_deploy_bp.pdf
ATTENTION:
Oracle recommends that you allocate a minimum default size of 1 GB hard disk space for the
MGMT_ECM_DEPOT_TS tablespace and allocate the rest of the recommended repository database space for the MGMT_TABLESPACE.
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.
To determine the amount of free disk space available in the /tmp directory, enter the following command:
# bdf /tmp
If there is less than 1.2 GB of disk space available in the /tmp directory, then complete one of the following steps:
Delete unnecessary files from the /tmp directory.
Set the TEMP and TMPDIR environment variables to a writable directory with at least 1.2 GB of available disk space.
Extend the file system that contains the /tmp directory. If required, contact your system administrator for information about extending file systems.
To determine the amount of free disk space available in the /tmp directory, enter the following command:
# df /tmp
If there is less than 1300 MB of disk space available in the /tmp directory, then complete one of the following steps:
Delete unnecessary files from the /tmp directory.
Set the TEMP and TMPDIR environment variables to a writable directory with at least 1300 MB of available disk space.
Extend the file system that contains the /tmp directory. If required, contact your system administrator for information about extending file systems.
For Management Agent deployments, make sure that /tmp directory has 1300 MB of disk space available on the target machine.
Carefully consider resource allocation when choosing the disk on which you want to install Oracle Management Service (OMS) and the database that will house the Oracle Management Repository (Management Repository).
Grid Control's ready-to-use monitoring starts generating information upon installation, meaning that resource consumption begins immediately. As such, consider the base system resource consumption prior to installing. Select your installation locations strategically, taking into account system load, memory usage, and disk input/output.
For example, you can split the input/output load across disks. Avoid installing the database, which will house the Management Repository, or the OMS on the swap volume, a volume with a busy state (as per iostat) of 10 percent or more, or on a memory-constrained system. As with any data-intensive application, if your Management Repository is going to service a large number of targets, it is important to tune the database appropriately to maximize input/output capacity. Refer to the Database Performance Tuning Guide for more information.
While adding more resources can help alleviate potential problems (for instance, adding a second disk dedicated to the OMS on a system), understanding and accounting for resource allocation is the best way to achieve strategic setup and good performance.
For information about the operating systems, browsers, and targets certified for Grid Control, see the My Oracle Support note 412431.1.
To access this note, access My Oracle Support (formerly Metalink) at the following URL. Once you log in, select the Certify tab. On the Certify page, click View Certifications by Product, and from the list, select Enterprise Manager 10g Grid Control. On the following page, click note 412431.1.
For detailed information on the required packages and kernel parameters for each platform, see Appendix D, "Platform-Specific Package and Kernel Requirements".
Note:
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.
This section describes the software requirements for each Enterprise Manager component. In particular, this section covers the following:
Grid Control requires an Oracle Database where the Management Repository can be created.
For Enterprise Manager Grid Control with a New Database: Enterprise Manager 10g Grid Control Release 2 (10.2.0.1 for Linux or 10.2.0.2 for Microsoft Windows) comes with an embedded Oracle Database 10g Release 1 (10.1.0.4). Therefore, if you install Enterprise Manager Grid Control with a new database, then this Oracle Database is installed automatically and you do not need to install any other software manually.
For Enterprise Manager Grid Control with an Existing Database: If you install Enterprise Manager Grid Control with an existing database, then ensure that you have a certified Oracle Database as described in My Oracle Support note 412431.1.
If you want to use a RAC database, which is configured on a virtual host as the existing database, then refer to My Oracle Support note 561441.1.
If you want to use Oracle Database 11g as the existing database, then you must follow one of these methods. The instructions for these methods are described in My Oracle Support note 467677.1.
Method 1: Install Enterprise Manager 10g Grid Control Release 2 (for example, 10.2.0.1 Linux or 10.2.0.2 Microsoft Windows) with a database certifeid for that base release. Then, patch Grid Control to Enterprise Manager 10g Grid Control Release 4 (10.2.0.4 or higher) and upgrade the database to Oracle Database 11g.
Method 2: Install Enterprise Manager 10g Grid Control Release 4 (10.2.0.4 or higher) directly using the software-only and configure later method as described in Installing 'Software-Only' and Configuring Later with a database certifeid for that base release. Then, upgrade the database to Oracle Database 11g.
Note:
When using an existing database for the Management Repository, ensure that all software, patches, and tuning requirements are met for the existing database and host, as well as for the Management Repository. For more information on the recommended database initialization parameters refer to Check Database Initialization Parameters.OMS has NO additional software requirements.
OMS is installed with and deployed on Oracle Application Server. As a result, when you install the OMS, the installation procedure first installs Oracle Application Server.
Specifically, the installation procedure installs the Oracle Application Server J2EE and Web Cache installation type. The OMS is deployed on its own OC4J container in this application server instance.
The software requirements for Management Agents depend on the installation method chosen for installing them.
agentDownload Script: If you choose to install Management Agents using the agentDownload script on Linux as well as Microsoft Windows platforms, then you need WGET software. For information about agentDownload script, see Overview.
To download the WGET software, access the following URL:
Agent Deploy Application: If you choose to install Management Agents using the Agent Deploy application, then you need an SSH software to set up SSH connectivity between the host running OMS and the host where the Management Agent needs to be installed. For information about Agent Deploy application, see Installing Management Agent Using Agent Deploy Application.
For Linux platforms, the SSH software is available on the hosts by default. However, for Microsoft Windows platforms, you need to download and install Cygwin Suite. To download Cygwin Suite, access the following URL:
For detailed information on the required packages and kernel parameters for each platform, see Appendix D, "Platform-Specific Package and Kernel Requirements".
Note:
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.
This section describes the following network requirements:
The OMS host and the Repository host must be located in close proximity to each other. Ideally, the round trip network latency between the two should be less than 1 millisecond.
See Network Issues for more information about network requirements.
Before installing any of the components, ensure that the host names and IP addresses are configured properly in the /etc/hosts file. For example, for installing a Management Agent on a host, ensure that the host name specified in the /etc/hosts file maps to the correct IP address of that host. Otherwise, the installation can fail on the product-specific prerequisite check page.
To resolve this issue, first run the following command on the host to list all the IP addresses configured and then note the IP address for that host:
For UNIX Platforms:
ifconfig
For Microsoft Windows Platforms:
ipconfig
After noting the IP address of that host, open the /etc/hosts file and check the entries for this host name. Ensure that the host name maps to the correct IP address of that host.
Also, if DNS server is configured in your environment, then you should be able to use DNS to resolve the name of the host on which you want install OMS. For more information, contact your network administrator.
While installing Management Agents, note that the server name is resolved based on the entry made in the /etc/hosts file.
If the entry in the /etc/hosts file is as shown below, then the Management Agent shows up as the fully qualified domain name.
<ip> <fully qualified domain name> <server name>
If the entry in the /etc/hosts file is as shown below, then the Management Agent shows up as the server name.
<ip> <server name> <fully qualified domain name>
The recommended "umask" is 022. Set the default file mode creation mask (umask) to 022 in the shell startup file.
For example:
$ . ./.bash_profile
$ . ./.profile
% source ./.login
The section explains what operating system groups and users you need to create and how to create them. In particular, this section covers the following:
The following operating system group and user are required for all installation types:
The Oracle Inventory Group (oinstall)
You must create this group the first time you install Oracle software on the system. The default name chosen for this group is oinstall. This group owns the Oracle inventory that is a catalog of all Oracle software installed on the system.
Note:
If Oracle software is already installed on the system, then the existing Oracle Inventory group must be the primary group of the operating system user that you use to install other Oracle software.The Oracle Software Owner User (typically, oracle)
You must create this user the first time you install Oracle software on the system. This user owns all of the software installed during the installation. This user must have the Oracle Inventory group as its primary group. If you are installing Enterprise Manager Grid Control with a New Database, then the user must also have the OSDBA and OSOPER groups as secondary groups. For details about OSDBA and OSOPER groups, refer to For The Installation Type "Enterprise Manager Grid Control with a New Database".
Note:
In Oracle documentation, this user is referred to as theoracle user.A single Oracle Inventory group is required for all installations of Oracle software on the system. After the first installation of Oracle software, you must use the same Oracle Inventory group for all subsequent Oracle software installations on that system. However, you can choose to create different Oracle software owner users, OSDBA groups, and OSOPER groups (other than oracle, dba, and oper) for separate installations. By using different groups for different installations, members of these different groups have DBA privileges only on the associated databases rather than on all databases on the system.
If you are installing Enterprise Manager Grid Control with a New Database, then in addition to the operation system group and user mentioned in For All Installation Types, the following are also required:
You must create this group if you do not have Oracle Database already installed. It identifies the operating system user accounts that have database administrative privileges (the SYSDBA privilege). The default name for this group is dba.
This is an optional group. Create this group if you want a separate group of operating system users to have a limited set of database administrative privileges (the SYSOPER privilege). By default, members of the OSDBA group also have the SYSOPER privilege.
Verify that the unprivileged user nobody exists on the system. The nobody user must own the external jobs (extjob) executable after the installation.
See Also:
For more information about the OSDBA and OSOPER groups and the SYSDBA and SYSOPER privileges, see Oracle Database Administrator's Reference for UNIX-Based Operating Systems and Oracle Database Administrator's Guide.The following sections describe how to create the required operating system users and groups:
Note:
As an alternative to creating local users and grouops, you can create the appropriate users and groups in a directory service, for example, Network Information Services (NIS). For information about using directory services, contact your system administrator or refer to your operating system documentation.You must create the Oracle Inventory group if it does not already exist. The following subsections describe how to determine the Oracle Inventory group name, if it exists, and how to create it if necessary.
When you install Oracle software on the system for the first time, Oracle Universal Installer creates the oraInst.loc file. This file identifies the name of the Oracle Inventory group and the path to the Oracle Inventory directory.
To determine whether the Oracle Inventory group exists, enter the following command:
# more /etc/oraInst.loc
If the output of this command shows the oinstall group name, then the group already exists.
If the oraInst.loc file exists, then the output from this command looks like:
inventory_loc=/u01/app/oracle/oraInventory inst_group=oinstall
The inst_group parameter shows the name of the Oracle Inventory group, oinstall.
You must create an OSDBA group in the following cases:
An OSDBA group does not exist, for example, if you do not have Oracle Database already installed on the system.
An OSDBA group exists, but you want to give a different group of operating system users database administrative privileges in a new Oracle installation.
If the OSDBA group does not exist or if you require a new OSDBA group, then create it as follows. In the following command, use the group name dba unless a group with that name already exists.
# /usr/sbin/groupadd dba
Create an OSOPER group only if you want to identify a group of operating system users with a limited set of database administrative privileges (SYSOPER operator privileges). For most installations, it is sufficient to create only the OSDBA group. If you want to use an OSOPER group, then you must create it in the following circumstances:
If an OSOPER group does not exist, for example, if this is the first installation of Oracle Database software on the system
If an OSOPER group exists, but you want to give a different group of operating system users database operator privileges in a new Oracle installation
If you require a new OSOPER group, then create it as follows. In the following command, use the group name oper unless a group with that name already exists.
# /usr/sbin/groupadd oper
You must create an Oracle software owner user in the following circumstances:
If an Oracle software owner user does not exist, for example, if this is the first installation of Oracle software on the system
If an Oracle software owner user exists, but you want to use a different operating system user, with different group membership, to give database administrative privileges to those groups in a new Oracle Database installation
To determine whether an Oracle software owner user named oracle exists, run the following command:
# id oracle
If the oracle user exists, then the output from this command looks like this:
uid=440(oracle) gid=200(oinstall) groups=201(dba),202(oper)
If the user exists, then determine whether you want to use the existing user or create another oracle user.
To use the existing user, ensure that the user's primary group is the Oracle Inventory group and that it is a member of the appropriate OSDBA and OSOPER groups.
To modify an existing user, refer to the Modifying an Oracle Software Owner User.
To create a user, refer to Creating an Oracle Software Owner User.
Note:
If necessary, contact your system administrator before using or modifying an existing user.If the Oracle software owner user does not exist or if you require a new Oracle software owner user, then follow these steps to create one. In the following procedure, use the user name oracle unless a user with that name already exists.
To create the oracle user, enter a command similar to the following:
# /usr/sbin/useradd -g oinstall -G dba[,oper] oracle
In this command:
The -g option specifies the primary group, which must be the Oracle Inventory group, for example oinstall
The -G option specifies the secondary groups, which must include the OSDBA group and if required, the OSOPER group. For example, dba or dba,oper
Set the password of the oracle user:
# passwd oracle
If the oracle user exists, but its primary group is not oinstall or it is not a member of the appropriate OSDBA or OSOPER groups, then enter a command similar to the following to modify it. Specify the primary group using the -g option and any required secondary group using the -G option:
# /usr/sbin/usermod -g oinstall -G dba[,oper] oracle
|
 Copyright © 1996, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|