| Oracle® Enterprise Manager Grid Control Installation and Basic Configuration 10g Release 3 (10.2.0.3.0) Part Number B40103-01 |
|
|
View PDF |
| Oracle® Enterprise Manager Grid Control Installation and Basic Configuration 10g Release 3 (10.2.0.3.0) Part Number B40103-01 |
|
|
View PDF |
This chapter introduces Enterprise Manager and its components, and provides preinstallation requirements and certifications. This chapter also lists all targets that Enterprise Manager is certified to manage.
Oracle recommends reading this chapter before proceeding with your installation for a better understanding of the requirements and certifications for the Enterprise Manager installation environment.
The following topics are covered in this chapter:
Note:
Ensure you also read the Enterprise Manager Grid Control Release Notes that accompany the product.The following sections will give you a better understanding of the Oracle Enterprise Manager Grid Control installation process and facilitate a successful installation:
Enterprise Manager Components Overview: This section briefly describes each Enterprise Manager component.
Preinstallation Considerations for Enterprise Manager: This section provides information on the preinstallation requirements. You must ensure these requirements are met before starting the Enterprise Manager installation.
Installing Enterprise Manager: This chapter provides detailed information on how to use Oracle Universal Installer to install Enterprise Manager.
Deploying the Management Agent: This chapter provides information on various methods of deploying the Management Agent.
Postinstallation Configuration Tasks: This chapter describes the tasks that must be completed after the installation.
Enterprise Manager is a single, integrated solution for administering and monitoring certified targets. See Chapter1, "Certified Enterprise Manager Targets" for a list of Oracle targets and components that Enterprise Manager can manage.
Oracle Enterprise Manager includes the Management Agent, Management Service (OMS), and Management Repository, as well as the Grid Control console, which is a browser-based central console through which administrators can perform all monitoring, administration, and configuration tasks for the enterprise.
Table 1-1 explains the different Enterprise Manager components and how they work together to manage your enterprise.
Table 1-1 Enterprise Manager Grid Control Components
| Component | Definition |
|---|---|
|
From the Grid Control console, you can monitor and administer your entire computing environment from one location on the network. All the services within your enterprise, including hosts, databases, listeners, application servers, Oracle Collaboration Suite applications, and Web applications are easily managed from one central location (console). |
|
|
The Management Agent is a process that is deployed on each monitored host. It is responsible for monitoring all targets on the host, for communicating that information to the middle-tier Management Service, and for managing and maintaining the host and its targets. |
|
|
The Management Service is a J2EE Web application that renders the user interface for the Grid Control console. It works with all Management Agents to process monitoring and jobs information, and uses the Management Repository to store data. |
|
|
The Management Repository consists of objects such as database jobs, packages, procedures, views, and two tablespaces in Oracle Database that contain all available information about administrators, targets, and applications managed within Enterprise Manager. The Management Service uploads the monitoring data it receives from the Management Agents to the Management Repository. The Management Repository then organizes the data so that it can be retrieved by the Management Service and displayed in the Grid Control console. Because data is stored in the Management Repository, it can be shared between any number of administrators accessing the Grid Control console. |
This section provides information about Oracle Universal Installer and other concepts you should know when you plan the installation.
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 Services does not provide support for components for which licenses have not been purchased.
For more information refer to Oracle Enterprise Manager Licensing Information.
If you choose to install Enterprise Manager Grid Control using a new database on a computer with no other Oracle software installed, Oracle Universal Installer creates an Oracle base directory for you. If Oracle software is already installed, then one or more Oracle base directories already exist. In the latter case, you must specify the Oracle base directory into which you want to install Oracle Database.
You are not required to create an Oracle base directory before installation, but you can do so if desired. You can set the ORACLE_BASE environment directory to point to this directory, which the Oracle Universal Installer will recognize.
Note:
You can choose to create a new Oracle base directory, even if other Oracle base directories exist on that system.Enterprise Manager is installed on multiple Oracle homes within the Oracle base directory. This means that a typical Enterprise Manager Grid Control installation creates three Oracle homes in different Oracle home directories. For example, oms10g, db10g, and agent10g.
Note:
You must ensure that you install this product into a new Oracle home directory. You cannot install products from one release of Enterprise Manager into an Oracle home directory of a different release. For example, you cannot install 10g R2 (10.2) software into an existing Oracle9i home directory. If you attempt to install this release into an Oracle home directory that contains software from an earlier Oracle release, the installation will fail.You can install this release more than once on the same system, as long as each installation is done in a separate Oracle home directory.
This section provides information about the minimum hardware and software requirements for Enterprise Manager components:
This section lists the recommended hardware requirements for running the various Enterprise Manager deployment sizes on all the supported platforms.
Table 1–2 and Table 1–3 approximate the host, CPU, and physical memory requirements for running an Enterprise Manager Grid Control deployment (typical scenario with 2 to 3 GHz machines), based on experiences with real-world Enterprise Manager deployments.
Table 1-2 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 1-3 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.
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 to install the Management Service and Management Repository database. Enterprise Manager'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 Management Repository database or the Management Service 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 Management Service on a system), understanding and accounting for resource allocation is the best way to achieve strategic setup and good performance.
This section contains certification information for each Enterprise Manager component, including the Management Repository, Management Service, and the Management Agent. Browser certifications for the Grid Control console have also been detailed.
Also included in this section are the certifications for all targets managed by Enterprise Manager:
The operating system platforms certified for Enterprise Manager Grid Control components are listed in Table 1-4.
Table 1-4 Certified Operating System Platforms for Enterprise Manager Grid Control
| Operating System | Platform | Version |
|---|---|---|
|
Linux |
|
|
|
Solaris |
SPARC 64-bit |
|
|
Microsoft Windows (32-bit) |
|
|
|
HP-UX PA-RISC (64-bit) |
PA-RISC (64-bit) |
|
|
AIX |
AIX 5L |
|
Important:
The platforms listed in Table 1-4 are certified for the Management Agent that is packaged along with the Oracle Management Service.If you are installing a standalone Management Agent or using the agentDownload script for agent installation, refer to the AgentDownload Install Readme for more information on the certified platforms.
Refer to the Oracle Technology Network Web site's "Certify and Availability" page for the latest information on all supported platforms.
For detailed information on the required packages and kernel parameters for each platform, see Appendix B, "Platform-Specific Package and Kernel Requirements".
The browser versions that are certified for viewing the Grid Control console are the following:
Internet Explorer 6.0 (SP2)
Netscape 7.2
Mozilla 1.7
Firefox 1.0.4
Safari 1.2
Note:
For services monitoring, you can record and play back Web application transactions using the Transaction Recorder. The Transaction Recorder is supported only on Microsoft Internet Explorer 5.5 (Service Pack 1) and later, and not on other browsers. Alternatively, if you do not have this requirement, you can configure Web transaction steps manually. Refer to the Enterprise Manager online Help for details on creating Web transactions for monitoring.Table 1-5 identifies the Oracle targets and components that Enterprise Manager Grid Control can manage.
Table 1-5 Certified Oracle Targets
| Supported Targets | Release |
|---|---|
|
Oracle Application Server |
9.0.4.2 and later patchsets 10.1.2.0.0 (Phase 1) 10.1.0.2.0.1 (SEONE) 10.1.2.0.2 (Phase 2) 10.2.0.2.1 Patchset 10.1.3 (Standalone OC4J) |
|
Oracle DatabaseFoot 1 , Listener |
8.1.7.4 9.0.1.5 9.2.0.7 and later patchsets 10.1.0.4 and later patchsets 10.2 |
|
Oracle Real Application Clusters Database |
9.2.0.6 10.1.0.4 10.1.0.5 10.2 |
|
Oracle Collaboration Suite |
9.0.4.2 and later 10.1.1 |
|
Management Service and RepositoryFoot 2 |
10.2 |
|
Management AgentFoot 3 |
10.1.0.2 10.2 |
|
Enterprise Manager Web site |
10.2 |
|
Host |
Linux x86 32-bit Red Hat Enterprise Linux AS/ES 3.0 Oracle recommends that the target host on which you are installing the Management Agent have a static IP address and not DHCP. |
Footnote 1 Enterprise Edition, Standard Edition, Personal Edition
Footnote 2 The Management Service and Management Repository releases correspond to the release of the Grid Control installation and not the release in which the repository is created.
Footnote 3 The Management Agent includes Beacon function.
This section describes the software requirements for each Enterprise Manager component.
The embedded Oracle Database 10g Release 1 (10.1.0.4), Enterprise Edition, is supported for Management Repository creation. Otherwise, you may only install the Management Repository in one of the following existing databases:
Oracle Database 10g Release 1 (10.1.0.4 and later), Enterprise Edition
Note:
If you are performing an Enterprise Manager Grid control installation using an existing database, ensure the database is a 10.1.0.3 release or later.Oracle Real Application Clusters 10g Release 1 (10.1.0.4 and later)
Note:
If you are performing an Enterprise Manager Grid control installation using an existing database, ensure the existing Oracle RAC database is a 10.1.0.3 release or later.Oracle9i Database Release 2 (9.2.0.6 and later), Enterprise Edition
Oracle9i Real Application Clusters Release 2 (9.2.0.6 and later)
Note that the Enterprise Edition database you use for the Management Repository must have fine-grained access control turned on. This is required for successful Management Repository creation. Check v$options for this setting.
When using an existing database for the repository, be sure that all software, patch, and tuning requirements are met for the existing database and host, as well as for the repository.
Note:
Refer to the Oracle Technology Network Web site for the latest information on the certified Management Repository platforms.For more information on the recommended database initialization parameters refer to Chapter3, "Check Database Initialization Parameters".
The Management Service has no additional software requirements.
The Oracle Management Service is installed with and deployed on Oracle Application Server. As a result, when you install the Oracle Management Service, the installation procedure first installs Oracle Application Server.
Specifically, the installation procedure installs the Oracle Application Server J2EE and Web Cache installation type. The Management Service is deployed on its own OC4J container in this application server instance.
The Oracle Management Service host and 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 AppendixA, "Network Issues" for more information about network requirements.
Table 1-6 lists all the prerequisite checks that the installer performs for each installation type.
Table 1-6 Prerequisites Checks for Each Installation Type
| Installation Type | Component Name | Checks |
|---|---|---|
|
Installing Enterprise Manager Using New Database |
|
|
|
Installing Enterprise Manager Using Existing Database |
|
|
|
Installing Additional Management Service |
|
|
|
Installing Additional Management Agent |
|
|
Footnote 1 Disallowed component = oracle.rsf.oracore_rsf.
Footnote 2 The name of the host on which the installation is being performed should neither be localhost.localdomain nor an IP address. It must be a valid host name. At the time of invoking the installer, you can pass ORACLE_HOSTNAME as an argument.
You can run the prerequisite check in standalone mode prior to starting the runInstaller. This helps you identify and resolve issues that might otherwise cause the installation to fail.
Table 1-7 lists the prerequisite check that is run for each installation type followed by the command that you must execute to run these checks:
Table 1-7 Installation Type and the Corresponding Prerequisite Check
| Installation Type | Component Name |
|---|---|
|
Installing Enterprise Manager Using a New Database |
|
|
Installing Enterprise Manager Using an Existing Database |
|
|
Installing an Additional Management Service |
|
|
Installing an Additional Management Agent |
|
To run the prerequisite checker in standalone mode, execute the following command:
<DVD>/install/runInstaller -prereqchecker PREREQ_CONFIG_LOCATION=<DVD>/rdbms/Disk1/stage/prereq -entryPoint <component name>_Core -prereqLogLoc <log location> -silent -waitForCompletion
For the prerequisite checker to run successfully, ensure that the filepath specified in --prereqLogLoc exists on the machine. Substitute the data in contained within the angled brackets (< >) with the appropriate prerequisite check component name. For example, if you want to run the prerequisite check for the first installation type, execute the following command:
<DVD>/install/runInstaller -prereqchecker PREREQ_CONFIG_LOCATION=<DVD>/rdbms/Disk1/stage/prereq -entryPoint oracle.sysman.top.em_seed_Core -prereqLogLoc <log location> -silent -waitForCompletion
Note:
On Microsoft Windows, replace/runInstaller with setup.exe and execute the command.