Oracle Enterprise Manager istration_ppt 5f5w

Oracle Enterprise Manager istration Presented By -

Manasa Athallur Chethan Srinivasaiah

AGENDA Scope Scope of of OEM OEM Functions Functions of of OEM OEM OEM OEM Functionality Functionality Alerts Alerts Steps Steps for for Configuring Configuring Notification Notification Rules Rules Create/Edit Create/Edit s s on on OEM OEM Starting Starting and and Stopping Stopping Enterprise Enterprise Manager Manager Components Components Important Important Log Log files files Listing Listing the the Targets Targets on on a a Managed Managed Host Host Controlling Controlling Blackouts Blackouts

Scope of OEM Applications 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 OEM In-depth In-depth monitoring monitoring with with Oracle-recommended Oracle-recommended metrics metrics and and thresholds. thresholds.

Access Access to to real-time real-time performance performance charts. charts.

E-mail E-mail notification notification for for detected detected critical critical alerts. alerts.

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

OEM Functionality First the hosts and targets that needs to be monitored is identified . The Management agent is set up on each host. Identify the metrics to be monitored on each target. Set warning, critical threshold values for each metric. The management agent collects the information from each target about the metrics and sends the value to Oracle Managed server(OMS). This information is accessible from the OEM Grid Control which runs on OMS. The alerts can also be sent as notification to the s. This can be customized as per the requirements. Corrective actions can also be configured for each alert. The Collected information is also stored in the database for any further analysis.

Warning

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

Critical

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

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

Metric

Alerts

Enterprise Manager Console

Warning Alerts Page

Warning Alert: Metric Details

Compare Targets

Steps for Configuring Notification Rules Description of the notification rule. You can specify whether the rule is public or not.

Choose the Target Type, for which this rule will be applied. You can choose the target Availability States for which you want to receive notifications Add 'Metrics' belonging to the chosen target type.

Severity states for the metrics chosen: Critical, Warning and Clear. 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.

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

Notifications for Policy Violations defined in the console, in the Policies tab : Violation, Clear. 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 sent for Enterprise Manager Jobs, executed from the EM console.

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'.

Setting Up Repeat Notifications

Create/Edit s on OEM To create, edit, or view an : 1. From Enterprise Manager Grid Control, click Setup. 2. Click s in the vertical navigation bar. 3. Click the appropriate task button on the s page.

Argument Description while creating new  

      



Name Type: The default value is EM_. The other possible values are: EXTERNAL_: Used for single-sign-on based authentication. DB_EXTERNAL_: Used for enterprise based security authentication. Roles Email Privilege Desc: The description of the being added. Expired: This parameter is used to set the to "expired" status. This is an optional parameter and is set to False by default. Prevent_change_ : When this parameter is set to True, the cannot change the . This is an optional parameter and is set to False by default. Input_file: This parameter allows the 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 Controlling Management Agent Change directory to the AGENT_HOME/bin directory

Use the appropriate command:

./ emctl start agent

• Starts the Management Agent

./ emctl stop agent

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

./ emctl status 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.0 Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved. --------------------------------------------------------------Agent Version : 11.1.0.1.0 OMS Version : 11.1.0.1.0 Protocol Version : 11.1.0.0.0 Agent Home : /app/oracle/agent11g Agent binaries : /app/oracle/agent11g Agent Process ID : 14846 Parent Process ID : 14824 Agent URL : https://nooslux050b.gl.2wglobal.com:3872/emd/main/ Repository URL : https://nooslux053b.gl.2wglobal.com:4900/em/ Started at : 2012-02-26 13:50:54 Started by : oracle Last Reload : 2012-03-07 13:42:29 Last successful : 2012-03-14 09:02:44 Total Megabytes of XML files ed so far : 3995.59 Number of XML files pending : 0 Size of XML files pending (MB) : 0.00 Available disk space on filesystem : 31.23% Last successful heartbeat to OMS : 2012-03-14 09:02:02 --------------------------------------------------------------Agent is Running and Ready

• Displays a message indicating whether or not the Management Service is running.

./ emctl status oms ./ emctl start oms

• 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 stop oms

• Stops the Management Service.

Change directory to the ORACLE_HOME/bin

Use the appropriate command:

Controlling the Management Service

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 following information in the emctl.log file: 1114306 :: Wed Jun 10 02:29:36 2009::AgentLifeCycle.pm: Processing status agent 1114306 :: Wed Jun 10 02:29:36 2009::AgentStatus.pm:Processing status agent 1114306 :: Wed Jun 10 02:29:37 2009::AgentStatus.pm:emdctl status returned 3

Exit Code and Description

Oracle Management Agent log file (emagent.log)

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

Oracle Management Agent trace file (emagent.trc)

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

Oracle Management Agent startup log file (emagent.nohup)

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

Management Agent Log and Trace Files

Listing the Targets on a Managed Host

• To list the name and type of each target currently being monitored by a particular Management Agent: • [oracle@nooslux050b bin]$ ./emctl config agent listtargets Controlling Blackouts (During maintenance activities) • Blackouts allow Enterprise Manager s to suspend management data collection activity on one or more managed targets.