Oracle Enterprise Manager Administration

Presented By - Manasa AthallurChethan Srinivasaiah

AGENDAScope of OEM

Functions of OEM

OEM Functionality

Alerts

Steps for Configuring Notification Rules

Create/Edit Administrators on OEM

Starting and Stopping Enterprise Manager Components

Important Log files

Listing the Targets on a Managed Host

Controlling Blackouts

Scope of OEMApplications that are built on Oracle - Enterprise

Manager offers the most comprehensive monitoring of the Oracle Grid environment.

Non-Oracle components, such as third-party application servers, hosts, firewalls, server load

balancers, and storage.

Enterprise Manager can monitor a wide variety of components (such as databases, hosts, and

routers) within your IT infrastructure

Functions Of OEMIn-depth monitoring with Oracle-recommended metrics and thresholds.

Access to real-time performance charts.

E-mail notification for detected critical alerts.

Corrective actions allow you to specify automated responses to alerts.

Blackouts allow you to support planned outage periods to perform emergency or scheduled maintenance. When a target is put under blackout, monitoring is suspended, thus preventing unnecessary alerts from being sent.

OEM Functionality

The Collected information is also stored in the database for any further analysis.

Corrective actions can also be configured for each alert.

The alerts can also be sent as notification to the administrators. This can be customized as per the requirements.

This information is accessible from the OEM Grid Control which runs on OMS.

The management agent collects the information from each target about the metrics and sends the value to Oracle Managed server(OMS).

Set warning, critical threshold values for each metric.

Identify the metrics to be monitored on each target.

The Management agent is set up on each host.

First the hosts and targets that needs to be monitored is identified.

Alerts

•A metric is the measurement of a particular characteristic of a program's performance or efficiency.

Metric

•Attention is required in a particular area, but the area is still functional.Warning

•Immediate action is required in a particular area. The area is either not functional or indicative of imminent problemsCritical

Enterprise Manager Console

Warning Alerts Page

Warning Alert: Metric Details

Compare Targets

Steps for Configuring Notification Rules

Depending on the values calculated for that metric and the thresholds set, the severity states can change in any of the following sequences:

Warning -> Critical -> Warning -> Clear, Critical -> Clear,

Warning -> Clear,Warning  -> Critical -> Clear etc.

Severity states for the metrics chosen: Critical, Warning and Clear. 

Add 'Metrics' belonging to the chosen target type.

You can choose the target Availability States for which you want to receive notifications

Choose the Target Type, for which this rule will be applied.  

You can specify whether the rule is public or not.

Description of the notification rule.

Setting Up Repeat Notifications

The last criteria in the Actions tab of the Rule is to specify the Notification Method that will be used for sending the notifications. If Email is required, you

can choose 'Send Me E-mail'. 

Notifications sent for Enterprise Manager Jobs, executed from the EM console.

If a policy has associated corrective actions with its violation state, successful or failed attempts of these corrective actions can be enabled for notifications

as well. 

Notifications for Policy Violations defined in the console, in the Policies tab : Violation, Clear. 

Notifications for Corrective Actions defined on the metrics : Success or Failed

Create/Edit Administrators on OEM

To create, edit, or view an administrator account:1. From Enterprise Manager Grid Control,

click Setup.2. Click Administrators in the vertical

navigation bar.3. Click the appropriate task button on the

Administrators page.

Argument Description while creating new administrator Name Type: The default value is EM_USER.

The other possible values are:EXTERNAL_USER: Used for single-sign-on based authentication.DB_EXTERNAL_USER: Used for enterprise user based security

authentication.  Password Roles Email Privilege Desc: The description of the user being added. Expired: This parameter is used to set the password to "expired" status.

This is an optional parameter and is set to False by default. Prevent_change_ password : When this parameter is set to True, the user

cannot change the password. This is an optional parameter and is set to False by default.

Input_file: This parameter allows the administrator to provide the values for any of these arguments in an input file. The format of value is name_of_argument:file_path_with_file_name.

Starting and Stopping Enterprise Manager Components

•Starts the Management Agent./ emctl start agent

•Stops the Management Agent./ emctl stop agent

•If the Management Agent is running, this command displays status../ emctl status

agent

Change directory to the AGENT_HOME/bin directory Use the appropriate command:

Controlling Management Agent

Checking the Status of the Management Agent

For Ex: 50b/app/oracle/agent11g/bin[oracle@nooslux050b bin]$ ./emctl status agent  Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.---------------------------------------------------------------Agent Version : 11.1.0.1.0OMS Version : 11.1.0.1.0Protocol Version : 11.1.0.0.0Agent Home : /app/oracle/agent11gAgent binaries : /app/oracle/agent11gAgent Process ID : 14846Parent Process ID : 14824Agent URL : https://nooslux050b.gl.2wglobal.com:3872/emd/main/Repository URL : https://nooslux053b.gl.2wglobal.com:4900/em/uploadStarted at : 2012-02-26 13:50:54Started by user : oracleLast Reload : 2012-03-07 13:42:29Last successful upload : 2012-03-14 09:02:44Total Megabytes of XML files uploaded so far : 3995.59Number of XML files pending upload : 0Size of XML files pending upload(MB) : 0.00Available disk space on upload filesystem : 31.23%Last successful heartbeat to OMS : 2012-03-14 09:02:02---------------------------------------------------------------Agent is Running and Ready

Controlling the Management Service

•Starts the Fusion Middleware components required to run the Management Service J2EE application.

•Specifically, this command starts HTTP Server and the EMGC_OMS1 domain where the Management Service is deployed.

./ emctl start oms

•Stops the Management Service../ emctl stop oms

•Displays a message indicating whether or not the Management Service is running../ emctl status oms

Change directory to the ORACLE_HOME/bin Use the appropriate command:

Starting Grid Control and All Its Components

Start the Net Listener

Start the Repository database instance

Start the Oracle

Management Service

Start the Management

Agent

Stopping Grid Control and All Its Components

Stop the Oracle

Management Service

Stop the Management

Agent

Stop the Repository database instance

Stop the Net Listener

Important Log files

• The log file resides in the ORACLE_HOME/sysman/log directory of the Management

• Agent is updated every time you run an emctl command. If your emctl command fails for some reason, access this log file to diagnose the issue.

emctl.log

After running the command, navigate to the log directory to view the followinginformation in the emctl.log file:1114306 :: Wed Jun 10 02:29:36 2009::AgentLifeCycle.pm: Processing status agent1114306 :: Wed Jun 10 02:29:36 2009::AgentStatus.pm:Processing status agent1114306 :: Wed Jun 10 02:29:37 2009::AgentStatus.pm:emdctl status returned 3

Exit Code and Description

Management Agent Log and Trace Files

•The Agent saves information to the log file when the Agent performs an actionOracle Management

Agent log file (emagent.log)

•The Management Agent trace file provides an advanced method of troubleshooting that can provide support personnel with even more information about what actions the Agent was performing when a particular problem occurred.

Oracle Management Agent trace file (emagent.trc)

•The Watchdog Process saves information about the agent into the startup log file when the agent starts or stopsOracle Management Agent startup log

file (emagent.nohup)

• To list the name and type of each target currently being monitored by a particular Management Agent:

• [oracle@nooslux050b bin]$ ./emctl config agent listtargets

Listing the Targets on a Managed Host

• Blackouts allow Enterprise Manager users to suspend management data collection activity on one or more managed targets.

Controlling Blackouts (During maintenance activities)