Enterprise Manager 10G

Overview and Installation guide

Prepared for Internal Use

Author: Divakar Mehta

Creation Date: APR 29 2005
Last Updated: APR 29 2005
Document Ref:
Version: Draft Copy (1.0)

Hand Book Database Administration <<SID>> 1

 CONTENTS

Enterprise Manager 10G......................................................................................................1

CONTENTS.....................................................................................................................2
Enterprise Manager Overview.....................................................................................3
Oracle Enterprise Manager Architecture.....................................................................4
Understanding the Enterprise Manager Directories ....................................................6
Pre-Installation Checks..............................................................................................10
Installation Of EM.....................................................................................................12
Starting and Stopping the Management Service .......................................................14
Starting and Stopping the Management Agent .........................................................15
Accessing Enterprise Manager Grid Control ............................................................15
APPENDIX A............................................................................................................17

Hand Book Database Administration <<SID>> 2

Enterprise Manager Overview

Enterprise Manager is Oracle's single, integrated solution for administering and

monitoring targets that are based on the Oracle technology stack. It provides the tools and
framework needed for you to manage all the pieces that comprise your system and
hardware environment.
The Grid Control Console Home page provides a unified view of your ecosystem. It
gives one view of everything and the interdependencies of related targets.

The EM manages, but is not limited to managing, the following components:

• Database

Hand Book Database Administration <<SID>> 3

 • Oracle Application Server
• Oracle Collaboration Suite
• Hosts (for example, Solaris, Linux, Windows)
• Groups (applications and grids)

The following are examples of using Enterprise Manager to manage your ecosystem.

• Using Oracle Database Management, you can:

o Study top performance problems by analyzing the Top SQL pages. These
pages assess the problem SQL statements and provide recommendations
for correcting the problems.
o Check the health of a target of a database group by analyzing the Database
Group Maintenance page.
o By connecting to MetaLink, determine whether there are any patches that
need to be applied to your database.
o Monitor cluster databases on the Database Home page. In addition to the
typical database information, this page also lists the cluster to which this
database belongs.

• Using Oracle Application Server, you can:

o Identify the components of the Application Server and their current status,
and drill down to obtain more details on the performance of the
components.
o Monitor real-time performance of the Application Server from the
Performance property page.
o View the top applications performance problems and drill-downs by
accessing the Application Server’s J2EE applications page.
o By connecting to MetaLink, determine whether there are any patches that
need to be applied to your Application Server.

• Using Host and Host Configuration, you can:

o Analyze the top processes by CPU and memory on the Host Performance
page.
o Keep track of your hardware and software inventory using the Host
Configuration page.
o Study the top performance problems by analyzing the Performance page
related to a host.

Oracle Enterprise Manager Architecture

Hand Book Database Administration <<SID>> 4

The typical Enterprise Manager framework configuration consists of these functional
areas :

• Oracle Management Agent

A process deployed on each monitored host. The Oracle Management Agent 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.

• Managed Targets

Oracle Management Agents monitor and perform administrative functions on

managed targets in your enterprise. Targets include but are not limited to
Databases, Application Servers, Listeners, and Third-party Applications.

• Oracle Management Service

A J2EE Web application that renders the user interface for the Grid Control
Console, works with all Management Agents in processing monitoring and job
information, and uses the Management Repository as its data store.

• Oracle Management Repository

Two tablespaces in an Oracle database that contain information about

administrators, targets, and applications that are managed within Enterprise
Manager.

The Management Service uploads to the Management Repository the monitoring

data it received from the Management Agents. The Management Repository then
organizes the data so that the data can be retrieved by the Management Service
and displayed on the Grid Control Console.

• Oracle Enterprise Manager 10g Grid Control Console

Enterprise Manager Web-based user interface for centrally managing your entire
computing environment.

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, HTTP
Servers, and Web applications, are easily managed as one cohesive unit.

Hand Book Database Administration <<SID>> 5

 • Oracle Enterprise Manager 10g Application Server Control Console

The Enterprise Manager Web-based user interface for managing Oracle

Application Server 10g (9.0.4). The Application Server Control Console is
installed and available with every Application Server 10g installation.

From the Application Server Control Console, you can monitor and administer a
single Oracle Application Server instance, a farm of Oracle Application Server
instances, or Oracle Application Server Clusters.

Fig: Architecture of EM 10g.

Understanding the Enterprise Manager Directories

When you install Oracle Enterprise Manager 10g Grid Control, you can select from four
installation types. All of these installation types, except the Oracle Management Agent
installation type, install the Oracle Management Service.

Hand Book Database Administration <<SID>> 6

 When you install the Oracle Management Service, you actually install two Oracle home
directories:
- The Management Service home directory

- The Management Agent home directory

About the Oracle Management Service Home Directory

The Oracle Management Service is a J2EE application that is installed and deployed
using 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, which is used to deploy the Oracle
Management Service.
The installation procedure installs the Enterprise Manager components within the
Oracle Application Server Home, including:

- The Oracle Management Service

- Optionally, the Oracle Management Repository

• About the Oracle Management Agent Home (AGENT_HOME) Directory

In addition to the Management Service home directory, the installation procedure

installs the Oracle Management Agent that is used to gather management data and
perform administration tasks for the targets on the Management Service host.
The Management Agent is installed in a separate Oracle home directory at the same
level as the Oracle Application Server home directory.
If the Oracle Universal Installer does not have the proper privileges, the Management
Agent is installed in a subdirectory of the Oracle Application Server home directory.

• Summary of the Important Directories in the Management Service Home

Figure below shows some of the important directories you should be familiar with in
a typical Grid Control Console installation.

Hand Book Database Administration <<SID>> 7

Description:

Table below describes in more detail the Management Service directories shown in
Figure above. In the table, ORACLE_HOME refers to the Management Service home
directory in which the Oracle Management Service is installed and deployed.

Directory Description
ORACLE_HOME/bin The bin directory in the Oracle Application Server Home
contains commands used to control the components of the
Oracle Application Server J2EE and Web Cache installation,
including the Application Server Control Console, which is
used to monitor and configure Oracle Application Server
instances.

ORACLE_HOME/sysman The sysman directory in the Oracle Application Server Home

contains the system management files associated with this
Oracle Application Server Release 2 (9.0.4) installation.
Note that the ORACLE_HOME/sysman/log directory contains the
Oracle Management Service log files (emoms.log) and trace
files (emoms.trc).
ORACLE_HOME/opmn This directory contains files used to control the Oracle
Process Manager and Notification Server (OPMN) utility.
OPMN can be used to start and stop the instances of Oracle
Application Server Containers for J2EE (OC4J) associated
with this instance of Oracle Application Server. The Oracle

Hand Book Database Administration <<SID>> 8

Directory Description
Management Service runs as an application in one of those
OC4J instances.
ORACLE_HOME/j2ee This directory contains the files associated with the OC4J
instances running in this instance of Oracle Application
Server. For example, you will notice a directory for the
OC4J_EM instance, which is the OC4J instance used to
deploy the Management Service J2EE Web application.

Table below describes in more detail the Management Agent Home directories shown in
Figure above. In the table, AGENT_HOME refers to the Agent home directory in which
the Management Agent is installed.

Directory Description
AGENT_HOME The agent directory contains all the files required to
configure and run the Oracle Management Agent on
this host.
AGENT_HOME/bin The agent/bin directory in the Oracle Application
Server Home contains the emctl command that
controls the Management Agent for this host.
AGENT_HOME/sysman/admin This directory contains the files used by the
Management Agent to define target types (such as
databases, hosts, and so on), to run configuration
scripts, and other administrative tasks.
AGENT_HOME/sysman/config This directory contains the configuration files for the
Management Agent. For example, this is where
Enterprise Manager stores the emd.properties file. The
emd.properties file defines settings such as the
Management Service upload URL for this particular
agent.
AGENT_HOME/sysman/log This directory contains the log files for the
Management Agent.

Hand Book Database Administration <<SID>> 9

Pre-Installation Checks

-Download the software for installing Enterprise Manager 10g grid control from
otn.oracle.com.
Eg:
Linux_Grid_Control_full_10_1_0_3_Disk1.cpio.gz,
Linux_Grid_Control_full_10_1_0_3_Disk2.cpio.gz,
Linux_Grid_Control_full_10_1_0_3_Disk3.cpio.gz

-Ftp the files to the server which where OMS and respository will be installed.

-Create staging dir by first unzipping the file using gunzip command and then use cpio
command.
Eg: gunzip Linux_Grid_Control_full_10_1_0_3_Disk1.cpio.gz,
cpio –idmv < Linux_Grid_Control_full_10_1_0_3_Disk1.cpio

-Perform the following checks before you start the installation:

1. Kernel parameters:
Check /etc/sysctl.conf file for following kernel parameters

kernel.sem=256 32000 100 142

kernel.shmmax=2147483648
kernel.shmmni=4096
kernel.shmseg=4096
kernel.shmall=3279547
kernel.shmmin=1
kernel.semvmx=32767
fs.file-max=131072
kernel.msgmni=2878
kernel.msgmax=8192
kernel.msgmnb=65535
net.ipv4.ip_local_port_range=20000 65000

Run /sbin/sysctl –p command to load the parameter values

Run /sbin/sysctl –a command to check the kernel values currently set

2. OS packages:
gcc-3.2.3-20
compat-glibc-7.x-2.2.4.32.5
gcc-3.2.3-20
setarch-1.3-1
pdksh-5.2.14
openmotif21-2.1.30-8
gnome-libs-1.4.1.2.90-34.1

Hand Book Database Administration <<SID>> 10

 compat-glibc-7.x-2.2.4.32.5
compat-gcc-7.3-2.96.122
compat-libstdc++-7.3-2.96.122
compat-libstdc++-devel-7.3-2.96.122
compat-gcc-c++-7.3-2.96.122
sysstat-4.0.7
openmotif-2.2.2-16.i386.rpm

use following command to query the installed packages:

rpm –qa | grep gcc

rpm –qa |grep glibc

use following command to install the packages:

rpm –ivh (for Installing)
rpm –Uvh (for Updating)

3. Hardware Components:

Components Hard disk Memory

Management Repository 1 GB 1GB(min)
Management Service 1.4GB 1GB
Management Agent 350MB 20MB
Application Server Core 500MB 512MB

4. /usr/bin/gcc should point to /usr/bin/gcc296

$mv /usr/bin/gcc /usr/bin/gcc323

$mv /usr/bin/g++ /usr/bin/g++323
$ln -s /usr/bin/gcc296 /usr/bin/gcc
$ln -s /usr/bin/g++296 /usr/bin/g++

5. Specifying ports other than default ports (optional):

If you want to specify ports other than default ports then, create a file named
staticports.ini file and specify your custom port before starting the installation.
Format of the file is given below:

Oracle HTTP Server port = 7779

Oracle HTTP Server Listen port = 7780
Oracle HTTP Server SSL port = 4445
Oracle HTTP Server Listen (SSL) port = 4446
Oracle HTTP Server Jserv port = 8007

Hand Book Database Administration <<SID>> 11

 Oracle HTTP Server Diagnostic port = 7200
Oracle Management Agent port = 1830
Application Server Control RMI port = 1850
Oracle HTTP Server Listen port = 7780
Oracle HTTP Server Listen (SSL) port = 4446
Oracle Notification Server Request port = 6003
Oracle Notification Server Local port = 6100
Oracle Notification Server Remote port = 6200
Log Loader port = 44000

Java Object Cache port = 7010

DCM Java Object Cache port = 7101
Application Server Control port = 1810
Web Cache HTTP Listen port = 7779
Web Cache HTTP Listen (SSL) port = 4445
Web Cache Administration port = 4000
Web Cache Invalidation port = 4001
Web Cache Statistics port = 4002
Oracle Net Listener = 1524
Oracle Management Service Upload (non-SSL) Port = 4889
Oracle Management Service Upload (SSL) Port = 4888

6. Log in as the application user and set the env before invoking runInstaller.

export DISPLAY=igtehydap08:0.0
export LD_ASSUME_KERNEL=2.4.19
unset LANG
export TMP=/tmp
export TMPDIR=/tmp
xhost + igtehydap08

7. Create the directory which will contain the EMS home.

8. Ensure that following entry is present in the /etc/hosts file of the server:
127.0.0.1 localhost.localdomain localhost

Installation Of EM

Hand Book Database Administration <<SID>> 12

 • Once the pre-installation steps are done, EM can be installed by invoking
runInstaller from the location where EM software is stored.

Cd /stage/oem10g/Disk1/
./runInstaller

If default ports are not being changed then simply invoke runInstaller from the
staging location or else give the following command specifying full location of
staticports.ini file.

./runInstaller oracle.sysman.top.em_seed:s_staticPorts=<full path of

staticports.ini>

• Choose to Install EM with new database.

• Follow the instructions and complete the installation. Enterprise agents are
automatically installed after the installation of Management Service.

• Separate installation of Agents will be reqd. on all the hosts which needs to be
monitored thru OEM. Do the following steps:
 FTP the software to the hosts, create staging dirs
 Make entry in /etc/hosts for the OMS host
 Ensure that OMS host is accessible from the host where agent is going to
be installed.
 Ensure DISPLAY,TMP and TMPDIR env variable are set.
 Invoke runInstaller from the stage dir and choose option ‘Additional
Agent Installation’
 Enter the correct hostname of OMS when prompted for.
 Complete the installation.

Hand Book Database Administration <<SID>> 13

Starting and Stopping the Management Service

You must be in the AS_HOME/bin directory to issue the emctl commands, where
AS_HOME is the Oracle Application Server home directory in which the Oracle
Management Service is installed and deployed.

Enter the following

If you want to ... command
Start the Management Service emctl start oms
Stop the Management Service emctl stop oms
Verify status of the Management Service emctl status oms
Start all components of the Application Server, including the opmnctl startall
Management Service and WebCache
Stop all components of the Application Server, including the opmnctl stopall
Management Service and WebCache

Hand Book Database Administration <<SID>> 14

 Starting and Stopping the Management Agent

You must be in the AGENT_HOME/bin directory to issue the emctl commands, where
AGENT_HOME is the Oracle home directory for your Management Agent. Note that
this directory is different than the AS_HOME/bin directory, which is for the Oracle
Application Server Control Agent.

If you want to ... Enter the following command

Start the Management Agent emctl start agent
Stop the Management Agent emctl stop agent
Verify status of the Management Agent emctl status agent

Accessing Enterprise Manager Grid Control

• The Enterprise Manager Grid Control Console is the primary tool for managing your
Oracle environment.

Hand Book Database Administration <<SID>> 15

 • Use the following URL to log in to the Grid Control Console:

http://<oms_hostname>.<domain>:<port>/em

eg: http://igtehydap08.igatecorp.com:7779/em

If you are uncertain about the port number, you can refer to one of the following files:

• ORACLE_HOME/install/setupinfo.txt as displayed by the Oracle Universal

Installer at the end of the install
• ORACLE_HOME/install/portlist.ini on the Management Service machine

• When the login dialog appears, enter the user name and password.

By default, SYSMAN is the superuser.

You can create EM users having restricted privileges.

To create, edit, or view an administrator:

1. From the Enterprise Manager Console, click Setup.

2. Click Administrators in the vertical navigation bar.
3. Click the appropriate task button on the Administrators page.

• Configurig Additional targets

Once the Agents are installed, hosts, DB and Listeners are automatically configured
in OEM. For adding additional components:

-Go to ‘Management System’ tab

-click ‘Agent’ sub tab

-select the appropriate agent.

- select the additional component to be added from the drop down list labelled as
‘Add’

- enter proper configuration details.

Hand Book Database Administration <<SID>> 16

APPENDIX A

Resource Information of OEM setup

OMS Host :igtehydap08

OMS Home : /apps2/Ora10grid

OMS DB :oragrid

OMS url : http://igtehydap08.igatecorp.com:7779/em

Agent Home: /apps2/agent

Super user : sysman/emsysman342

Viewer user : viewer/viewer

OMS stop : /apps2/Ora10grid/opmn/bin/opmnctl stopall

OMS start : /apps2/Ora10grid/opmn/bin/opmnctl startall

Agent start :/apps2/agent/bin/emctl start agent

Agent stop :/apps2/agent/bin/emctl stop agent

OMS DB Home: /apps2/Ora10grid

Hand Book Database Administration <<SID>> 17

Hand Book Database Administration <<SID>> 18