Scribd
Upload
50 views2 pages

Database Monitoring: Scope

This document discusses improving database monitoring by using Oracle Enterprise Manager (OEM) templates rather than scripts. It proposes monitoring hosts, databases, clusters, listeners, and Automatic Storage Management using OEM templates. Metrics would be selected for each target type and warning/critical thresholds set to trigger notifications or ticket creation. An excel file lists the metrics and thresholds for each target type to implement this improved monitoring approach.

Uploaded by

Oracleconslt Oracleconslt
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
50 views2 pages

Database Monitoring: Scope

This document discusses improving database monitoring by using Oracle Enterprise Manager (OEM) templates rather than scripts. It proposes monitoring hosts, databases, clusters, listeners, and Automatic Storage Management using OEM templates. Metrics would be selected for each target type and warning/critical thresholds set to trigger notifications or ticket creation. An excel file lists the metrics and thresholds for each target type to implement this improved monitoring approach.

Uploaded by

Oracleconslt Oracleconslt
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Database Monitoring Date : 05th Dec, 2013

Scope:

This document is intended for the use of monitoring templates provided by Oracle Enterprise
Manager (OEM 12c). In this document, we will look into the current environment, the proposed
approach and all the related things.

Existing Environment:-

The current environment has many database monitoring scripts those have been scheduled in
the crontab. The scripts are engaged in many database monitoring checks like Database status
check, listener status check, tablespace usage, blocking session and resumable sessions (just to
name few of them).

Drawbacks in the current environment:

1.) These scripts require good amount of time to reschedule or editing by logging on each
monitored server.

2.) Manual intervention is required everywhere.

3.) Requires good amount of time to troubleshoot if any issue is encountered

Proposed Approach:-

The EM comes with monitoring templates/metrics, which can be customized as per the
requirement.

Targets:

There are various target types defined in the EM for which the templates can be customized.
Host, Database Instance, Cluster Database, Automatic Storage Management, Cluster ASM,
Listeners etc. We can customize all the target type templates as per our requirement. We can
define the “Warning Threshold” and “Critical Threshold” on the metrics defined for a particular
target type. And then, we can decide what action needs to be taken if warning or critical
threshold is reached.

Symphony Teleca Corporation (I) Pvt. Ltd.

For Internal Use Only Page | 1


Database Monitoring Date : 05th Dec, 2013

It is important to decide which metrics you want to use for a particular target type template,
they should be be of good use and relevant. After you decide on the metrics, then you need to
decide on the threshold values for them in the warning and critical condition.

The next step will be to decide the action on any of the warning or critical threshold. The
following actions could be taken:

1. Send a notification to a particular mail address


2. Send notification to a group
3. Thresholds can be integrated with the ticketing tool as well, and you can decide if any
threshold value is reached, it will send a mail to the service desk and a ticket/incident
will be created.

Now, we will be going ahead on this. The following target types have been chosen to create the
customized templates:

1. Host
2. Database Instance
3. Cluster Database
4. Cluster
5. Listeners
6. Automatic Storage Management
7. Cluster ASM

Now, the first step is to identify the “monitoring metrics” for these target types. And then, we
will set the “Warning Threshold” and “Critical Threshold” for these metrics on a particular
target type. And then the action required.

Please find the excel sheet below for the “Metrics” of each of the target type along with their
warning and critical threshold values.

Targets_Metrics.xlsx

Symphony Teleca Corporation (I) Pvt. Ltd.

For Internal Use Only Page | 2

You might also like