Professional Documents
Culture Documents
Oracle Enterprise Manager Administration - PPT
Oracle Enterprise Manager Administration - PPT
Administration
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 Administrators
Administrators 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 support
support 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 administrators. 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
Critical
Metric
Alerts
Compare Targets
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 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'.
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.
./ emctl start
agent
./ emctl stop
agent
./ emctl status
agent
./ emctl
status oms
./ emctl
start oms
./ emctl
stop oms
Start the
Repository
database
instance
Start the
Oracle
Management
Service
Start the
Management
Agent
Stop the
Oracle
Management
Service
Stop the
Management
Agent
Stop the
Repository
database
instance
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
Oracle Management
Agent log file
(emagent.log)
Oracle Management
Agent trace file
(emagent.trc)
Oracle Management
Agent startup log
file
(emagent.nohup)