DBA Tips Archive for Oracle
Installing Grid Control Management Agent (10.2.0.5)
by Jeff Hunter, Sr. Database Administrator
This article provides one approach (out of several available) used to install and configure the Oracle Management Agent (10.2.0.5) on an Oracle database server node running the Red Hat Enterprise Linux 5 operating system. Installing the Management Agent will be done using the GUI-based Oracle Universal Installer (OUI) interactive method - "Installing Management Agent Using Oracle Universal Installer (OUI)". The OUI is a GUI-based application and therefore requires the use of an X Server. This guide assumes you have a working Oracle Enterprise Manager 10g Grid Control Release 5 environment in place and running.
Oracle Management Agent is one of the integral components of the Enterprise Manager Grid Control architecture. Management Agent will discover, monitor and administer all targets on their hosts, including databases, application servers, other software, and aspects of the hosts themselves. Management Agent communicates with the monitored targets, collects information about their health and performances, transports that information to Oracle Management Service (OMS), which in turn stores the collected details in the central repository created in the Oracle database.
For the purpose of this article, the Oracle Management Agent (10.2.0.5) will be installed on a database server node named vmlinux1.idevelopment.info which hosts a single Oracle 10g database named TESTDB1. The Management Agent will be registered with a central Grid Control environment running on the node oemprod.idevelopment.info. The method used in this article to install the Oracle Management Agent will be:
Installing Management Agent Using OUI
The following is a conceptual view of what the configuration will look like by the end of this document:
Figure 1: Oracle Grid Control Configuration
Grid Control (and the Management Agent described in this article) is a large, bloated, and overly complex web application which, needless to say, is riddled with a considerable number of bugs. Consequently, this article should not be considered a substitute for completely reading and understanding the official installation guide and release notes from Oracle (although, in many cases, the documentation is as poorly written as the OEM application itself). Pay considerable attention to the prerequisites for your environment before attempting the install. The following links can be used to download the official installation guides and release notes for Oracle Enterprise Manager 10g:
Enterprise Manager 10g Grid Control Release 2 (10.2.0.1)
Enterprise Manager Grid Control Quick Installation Guide for Linux x86
Enterprise Manager Release Notes for Linux x86
Enterprise Manager 10g Grid Control Release 5 (10.2.0.5)
Enterprise Manager Grid Control Release Notes for Linux and Microsoft Windows
Oracle Management Agent
10g R2 Management Agent Deployment Best Practices
This section provides the pre-installation requirements for installing Oracle Management Agent (10.2.0.5) on Red Hat Enterprise Linux 5.
It should be noted that nearly all of the pre-installation requirements documented in this section should have already been met. The Management Agent installation will use the same oracle UNIX user account and group that was used to install the Oracle Database 10g software.
Verify the following package versions for Red Hat Enterprise Linux 5.
32-bit (x86) Installations
64-bit (x86_64) Installations
glibc-devel-2.5-18 (32 bit)
libXp-1.0.0-8.1 (32 bit)
This article assumes the Oracle Database 10g Release 2 software has already been installed on vmlinux1 and as such, includes the UNIX groups oinstall, dba, and oper and the UNIX user account oracle. The Management Agent software will be installed using this same account that was used to install the Oracle 10g database software.
Ensure that you have read, write, and execute permissions to oraInventory on the node you are installing the Management Agent to.
The host name must be a valid host name. For example, vmlinux1.idevelopment.info or vmlinux1. It cannot, however, be an IP address. At the same time, it cannot be localhost.localdomain as strings used in the /etc/hosts file. At the time of invoking the installer, you can pass "ORACLE_HOSTNAME=<host_name> -local" as an argument if necessary.
The existing Oracle database (TESTDB1 in this example) must be free of any prior repository contents, whether for Database Control or Grid Control. The existing Oracle 10g database in my example was configured with Database Control:
If your existing Oracle database is configured with Database Control, then ensure that you de-configure it before you begin the installation of Management Agent.
To de-configure Database Control for a single instance database, run the following command:
If your operating system is Linux, then ensure the NLS_LANG environment variable (or ORA_NLS10 in my case) is set with a value that is compatible with the operating system default locale setting and the database character set.
In this article, I set the ORA_NLS10 environment variable in the .bash_profile log in script for the oracle UNIX account as follows:
Prepare the Enterprise Manager 10g Grid Control environment by creating the following entry in the /etc/oratab file:
Verify /etc/oratab entries:
Download and install the Oracle Management Agent (10.2.0.5) for Linux to the database server vmlinux1.
Depending on the O/S platform (Linux x86 for this example), download the appropriate Oracle Management Agent (10.2.0.5) from the Oracle Technology Network (OTN).
Mass Deployment Agent Software from Oracle
After downloading the Management Agent for your platform, (as the "oracle" user account), extract the archived file to a temporary directory. In this example, I will use /home/oracle/software/management_agent/10.2.0.5/linux_x86.
After extracting the Management Agent software, verify you are logged in as the oracle user account, set your environment for the Management Agent (using agent10g from /etc/oratab), start your "X" emulation software (if required) and run the Oracle Universal Installer.
Specify Installation Type
In the "Specify Installation Type" window, select the forth option (the default and only option available) which is to perform a "Additional Management Agent" install.
Figure 2: Specify Installation Type
Specify Installation Location
Specify the "Parent Directory" that will be used to install the Management Agent". In this example, I will use "/u01/app/oracle/product" as the Parent Directory, however, the actual directory that will be created is "/u01/app/oracle/product/agent10g".
Figure 3: Specify Installation Location
My Oracle Support
(Optional) Specify an email address and My Oracle Support login credentials.
Figure 4: My Oracle Support
Product-Specific Prerequisite Checks
The Prerequisite check screen will appear and identify possible deficiencies in kernel settings, software packages needed, host configuration, or space available. During the installation of Oracle Management Agent, no deficiencies should occur.
There is one particular exception and that is if you receive the warning:
Checking for the Hostname...
Check complete. The overall result of this check is: Failed <<<<
Problem: The host name in /etc/hosts is not proper.
If you receive this warning, it is safe to ignore. Acknowledge the warning by clicking the checkbox and continuing the installation.
Figure 5: Product-Specific Prerequisite Checks
Specify Oracle Management Service Location
Enter the host name of the Oracle Management Service (OMS) location. When specifying the host name, use the fully qualified host name (including domain). Also, do not include the protocol when entering the host name (that is, http:// or https://). The default port (4889) is automatically entered in the "Management Service Port" field. For the purpose of this example, the default port will be used.
Figure 6: Specify Oracle Management Service Location
Specify Agent Registration Password
If the OMS is found to be running in a secure mode, the "Specify Agent Registration Password" screen appears. You must provide the correct password to enable communications between the new Management Agent and the Sockets Layer (SSL)-enabled OMS.
Figure 7: Specify Agent Registration Password
This screen displays a summary of the options that you have selected during the installation process. Verify that the Source and Oracle Home values are correct and click the "Install" button.
Figure 8: Summary Screen
Execute Configuration Scripts
After the install and link phase, the Oracle Universal Installer will present the "Execute Configuration Scripts" dialog specifying that the /u01/app/oracle/product/agent10g/root.sh script be run as the root UNIX user account.
If the target database is clustered using Oracle RAC, run the /u01/app/oracle/product/agent10g/root.sh script as the root UNIX user account on all nodes in the cluster.
Figure 9: Execute Configuration Scripts
After running the "root.sh" script and acknowledging the dialog window, the Oracle Universal Installer will start running the three core configuration assistant tasks. This is a crucial step in the installation process as it performs the patching required for Management Agent 10.2.0.5 and also automatically configures the discovered targets with the Oracle Management Service (OMS).
Figure 10: Configuration Assistants
End of Installation
After successfully installing and configuring Oracle Management Agent, the Oracle Universal Installer will present the "End of Installation" screen.
Figure 11: End of Installation
Verify the new Management Agent installation and configuration was successful by performing the following post installation tasks.
Verify the status of the agent and check to ensure the agent can upload data regarding its targets to the Oracle Management Service (OMS):
Verify the DBSNMP Oracle database account on the target database (TESTDB1) is not locked:
If the DBSNMP Oracle database account is locked for any reason, unlock it:
Login to the Oracle Grid Control Console. Note the one configuration error () under the "All Targets Alerts" section:
Figure 12: Oracle Grid Control Console
Click on the "Targets" tab and scroll down through the list of hosts to the entry for the hostname you recently installed (vmlinux1). If the link doesn't appear, click the refresh button periodically until the host appears.
Figure 13: Select Host Target
Once the link for the host appears, click on the link and proceed to the "Targets" link. Configure the target database instance by selecting the $ORACLE_SID.$DOMAIN_NAME entry:
Figure 14: Configure the Target Database Instance
From the target database page, click the "Configure" button.
Figure 15: Configure the Target Database Instance
Enter the password for the DBSNMP user on the target database and click on the "Test Connection" button to ensure the database user DBSNMP is correctly configured for the target database being added. If, as the figure below shows, the test is successful, click "Next".
Figure 16: Enter Database Monitor Password (DBSNMP)
On Screen 5 of 5, click the "Submit" button to configure the target database being added. After several seconds, you should see the results screen indicating the configuration for the database has been successfully updated.
Figure 17: Database Instance Configuration Result
If your Enterprise Manager grid environment is making use of firewalls, ensure you specify the appropriate ports.
The following figure provides a topology of an Enterprise Manager grid environment that is using a firewall, and also illustrates the appropriate ports that you must specify:
Figure 18: Grid Control Firewall Ports
The conventions used in the preceding illustration are as follows:
|C||Is the entity that is making the call.|
|*||Enterprise Manager will default to the first available port within an Enterprise Manager set range.|
|**||Enterprise Manager will default to the first available port.|
|***||Are the Database listener ports.|
These are the ports that need to open for bi-directional data communication between the OEM Grid Control management server and the target agent:
|3872||OMS / Agent Data Communications|
|1159||Enterprise Manager Central Console Secure Port|
|4898-4989||Console and OMS / Agent Data Communications|
|4889||OMS / Agent Data Communications|
|7200-7210||Oracle HTTP Server Diagnostic port|
The ports that should be open on a VPN tunnel to the OEM management console:
|4889||Enterprise Manager Central Console Port|
|4444||Oracle HTTP Server Listen (SSL) port|
|1156-1158||Application Server Control port, Oracle Management
Agent Port, Enterprise Manager Central Console Secure Port
|7200||Oracle HTTP Server Diagnostic port|
|7777||Oracle HTTP Server port|
|7778||Oracle HTTP Server Listen port|
|8250||Web Cache HTTP Listen (SSL) port|
|9400-9410||Oracle Web Cache Administration, Console, and Diagnostics|
Jeffrey Hunter is an Oracle Certified Professional, Java Development Certified Professional, Author, and an Oracle ACE. Jeff currently works as a Senior Database Administrator for The DBA Zone, Inc. located in Pittsburgh, Pennsylvania. His work includes advanced performance tuning, Java and PL/SQL programming, developing high availability solutions, capacity planning, database security, and physical / logical database design in a UNIX / Linux server environment. Jeff's other interests include mathematical encryption theory, tutoring advanced mathematics, programming language processors (compilers and interpreters) in Java and C, LDAP, writing web-based database administration tools, and of course Linux. He has been a Sr. Database Administrator and Software Engineer for over 20 years and maintains his own website site at: http://www.iDevelopment.info. Jeff graduated from Stanislaus State University in Turlock, California, with a Bachelor's degree in Computer Science and Mathematics.
Copyright (c) 1998-2017 Jeffrey M. Hunter. All rights reserved.
All articles, scripts and material located at the Internet address of http://www.idevelopment.info is the copyright of Jeffrey M. Hunter and is protected under copyright laws of the United States. This document may not be hosted on any other site without my express, prior, written permission. Application to host any of the material elsewhere can be made by contacting me at firstname.lastname@example.org.
I have made every effort and taken great care in making sure that the material included on my web site is technically accurate, but I disclaim any and all responsibility for any loss, damage or destruction of data or any other property which may arise from relying on it. I will in no case be liable for any monetary damages arising from such loss, damage or destruction.
Last modified on
Sunday, 18-Mar-2012 22:26:14 EDT
Page Count: 34028