System Monitoring Using Oracle Enterprise Manager 10g Release 2

This tutorial covers the new features of Oracle Enterprise Manager 10g Release 2 for system monitoring.

Approximately 1 hour

Topics

This tutorial covers the following topics:

Place the cursor over this icon to load and view all the screenshots for this tutorial. (Caution: Because this action loads all screenshots simultaneously, response time may be slow depending on your Internet connection.)

Note: Alternatively, you can place the cursor over each individual icon in the following steps to load and view only the screenshot associated with that step.

The screenshots will not reflect the specific environment you are using. They are provided to give you an idea of where to locate specific functionality in the Oracle Enterprise Manager 10g Grid Control console.

Overview

The System Monitoring functionality in Oracle Enterprise Manager 10g Release 2 refers to features that enable administrators to monitor infrastructure components of the Oracle Ecosystem. This includes Oracle components (such as the Oracle database and Oracle Application Server), as well as other components (such as hosts and third-party application servers that interact with Oracle and are also monitored in Oracle Enterprise Manager 10g Grid Control). This tutorial covers some of the new enhancements in System Monitoring such as Corrective Actions and Monitoring Templates. These features apply to any monitored component (called a "target") in Oracle Enterprise Manager 10g Release 2.

Back to Topic List

Oracle Enterprise Manager 10g Grid Control provides out-of-box monitoring for all managed targets. That is, metrics are collected for each managed target at predefined collection schedules. If enterprises need to customize these collection schedules, then administrators can change these collection schedules in the Oracle Enterprise Manager 10g Grid Control console. Perform the following steps to see how to do it.

1.

Open the browser and enter the following URL:

http://<management service hostname>.<domain>:<port>/em/

The default port value on a clear machine is 7777. However, if there are other instances running on the machine, then the port may be different.

The login page will be displayed. Enter the User Name and Password, and then click the Login button.

 

2.

The home page appears (similar to the one shown below) which gives you an overview of the health of all managed targets. To access specific targets, click the Targets tab.

 

3.

On the Targets tab, all managed targets are grouped by type, into different subtabs. On the Hosts tab click any host from the list.

 

4.

The host home page is displayed. Scroll down to the bottom of the page and click the Metric and Policy Settings link.

 

5.

For this host, all monitored metrics, their warning and critical thresholds and collection schedules are displayed. To change the collection schedule for a metric, click its collection schedule link (for example Every nth Minutes).

 

6.

On this page you can now change the schedule. Change the Collection Frequency to 30 minutes and click Continue. Similarly you can also use the Disable button to disable the data collection for this metric.

Note: Similar types of metrics are often collected together. Thus changing the collection schedule of a metric could potentially impact the collection of other metrics. Review the 'Affected Metrics' and 'Affected Policies' section of the page to see the impact of collection schedule changes before saving your changes. Be careful when changing the schedule or disabling a metric. It is recommended NOT to change the collection schedule to less than 5 minutes unless it is absolutely required, in order to avoid unnecessary load on the agent.

 

 

7.

You can now see that the collection schedule is changed from Every 15 Minutes to Every 30 Minutes. Click the OK button to save the settings.

 

8.

The new settings are now saved.

 

Back to Topic List

Defining Corrective Actions

Corrective actions are a way to specify an automated response to an alert. You can define different corrective actions for warning and critical alerts. To define a corrective action you need at least the Operator privilege on the target. By default, the corrective action task will run on the target on which the alert is triggered. However, you can also define multitask corrective actions that run against other targets. Perform the following steps to define a corrective action:

1.

You will define a corrective action for starting the listener if it goes down. First click the All Targets tab to get a list of all targets.

 

2.

To filter the list of all All Targets to show only Listener targets, select Listener from the Search drop-down list and click Go.

 

3.

Select any listener from the list.

 

4.

In the listener home page that comes up, scroll to the bottom of the page and click Metric and Policy Settings in the Related Links section.

 

5.

To define a corrective action for when the listener is detected to be down, click the pencil icon for the Status metric.


6.

On this page, you can define the corrective action. To define a corrective action click the Add button.

 

7.

Select OS Command from the drop-down list and click Continue.

 

8.

Provide a proper name and description and click the Parameters subtab.

 

9.

Select Script from the Command Type drop-down list. In the OS Script box, enter the commands as shown below in the screenshot. Click the Credentials subtab.

 

10.

Select Override Preferred Credentials option button, enter your Host credentials and then click Continue.

 

11.

You can see the newly defined corrective action. You can use the Remove button to remove the corrective action in the future when it is not needed. Click Continue.

 

12.

A new corrective action is defined. Click OK to save your changes.

 

13.

The corrective action is successfully defined. Click the OK button.

 

14.

You return to the listener home page.

 

Back to Topic List

Creating SQL User-Defined Metrics

SQL User-Defined Metrics (SQL UDMs) enables you to extend monitoring of databases by plugging in your own SQL queries to monitor conditions that are specific to your environment. The values returned by your queries can be compared against the thresholds that you specify, and alerts are triggered when thresholds are crossed. In Oracle Enterprise Manager 10g Release 2, SQL UDMs have been enhanced in the following ways:

Perform the following steps to create SQL User-Defined Metrics:

1.

Click the Databases subtab to access the list of databases..

 

2.

Select any database from the list.

 

3.

The Database homepage is displayed. Scroll down to the bottom of the page and click User-Defined Metrics.

 

4.

User-Defined SQL Metrics enable you to extend the monitoring of your environment by defining new metrics to be monitored. New metrics are defined by specifying your own SQL statements. The table shows you a list of User-Defined Metrics defined for this database target. Click the Create button to create a new SQL user-defined metric.

 

5.

Enter the specifics for the User-Defined Metric. You can refer to the instruction text on the page but generally you will need to enter the Metric Name, select the Metric Type, SQL Query Output (the number of values returned by your query - single value or two-column values) and then enter the SQL Query. You can use your own query (see Note below if you do so) or use the sample query as shown in the screenshot below (select ename, sal from emp;).

For Database Credentials, you can use database user scott (with password tiger). Specify the threshold information, customize the alert message and specify the collection schedule. Feel free to use the sample settings shown in the screenshot below. After all the required values are entered click the Test button to verify the correct execution of the SQL statement.

Note: When you use your own SQL query, the query must return either a single scalar value or 2-column multi-row values. In the latter case, the first column is the KEY and the second column is the VALUE. The Metric Type for your User-Defined Metric should match the data type of the VALUE column.

 

6.

You can see that the test is successful. The test only shows the first 10 rows returned by the SQL statement. Click OK to continue.

 

7.

You have successfully created a new SQL user-defined metric. Based on the query and thresholds you specified, you may wait a few minutes for an alert to be triggered for your metric.

 

Back to Topic List

Using Monitoring Template

A Monitoring Template is a collection of monitoring settings that you can define once and apply to multiple targets. It enables administrators to easily propagate standardized monitoring settings across managed targets. In this section you see how to create a monitoring template and also how to apply this template to a target. In real-world scenarios, templates would most likely be applied to many targets or groups, but the process for applying the template to a single target or to groups of targets is the same. Perform the following steps to see how to use templates:

1.

To access the monitoring templates functionality, click Setup from the top-right corner.

 

2.

Click Monitoring Templates from the left-navigation bar.

 

3.

To create a new monitoring template click the Create button.

 

4.

A Monitoring Template is initially prefilled by copying monitoring settings from a target. Choose the target that has the monitoring settings that you would like to use in the template. Click the flashlight icon to select the target.

 

5.

In this exercise you use a database target. Select Database Instance from the Target Type drop-down list. You can choose any of the available databases. Select the database target and click Select.

 

6.

The database you selected should now be in the Target field. Click Continue.

 

7.

Specify a name for the new template and click the Metric Thresholds subtab.

 

8.

On this page you can edit the thresholds of the metrics that are part of this template. For this exercise we will do a few simple changes. Change the Warning Threshold for the Archive Area Used (%) to 90 and also click the link under the Collection Schedule column to change the collection schedule.

 

9.

Change the frequency to 15 minutes and click Continue.

 

10.

You can now see the updated Collection Schedule. Click the Policies subtab.

 

11.

This template does not involve any policy settings, therefore you can remove the policy rules from the template. Click the Select All link to select all the policies and then click the Remove button.

Note: Removing of policy rules from the template does not remove or impact any policy rules defined on the destination target when you actually apply the template to a target.

 

12.

Click Yes to confirm.

 

13.

You might have to do steps 11 and 12 repeatedly until all policies rules have been removed from the template. Once you're done, click OK to save the changes.

 

14.

A new template is successfully created. The next step is to apply this template to a target. Select the template that you just created and click the Apply button.

Note: When applying a template to a target the user that is doing the Apply operation needs at least Operator privileges on the destination targets. Different templates can be applied to the same target. If these templates contain the same metric, then the settings from previously applied templates could be overwritten. Thus collaboration among administrators is recommended when using templates. Administrators also have an option to prevent templates from overriding a target's metric settings.

 

15.

You have to select the destination target to which this template will be applied. Click the Add button.

 

16.

You can choose any set of targets or groups on which the template will be applied and click the Select button.

 

17.

You can select multiple targets or groups before you apply the template. In this case you are only selecting one target. Click OK to apply the template.

 

18.

The new template is successfully applied to the selected target.

 

Back to Topic List

Working with Blackouts

Blackouts enables you to suspend monitoring on one or more targets in order to perform maintenance operations. You need to have at least the Operator privileges on the target to black out a target .With the new release of grid control you can now create a blackout for any target from its homepage. Perform the following steps to see how to do it.

1.

Click the Targets tab.

 

2.

In this exercise you will black out a database. Click the Databases tab.


3.

Select any database from the list. .

 

4.

The database's home page appears. Click the Black Out button.

 

5.

The Create Blackout wizard launches in context of the target. Note that the database target has been preselected in the Selected Targets list. Click Next on the Properties page..

 

6.

Keep the default immediate schedule for 1 hour. This means the black out is scheduled to run immediately and will last for 1 hour. Click Next.

 

7.

Click Finish.

Note: With the new release of Grid Control you can also create a blackout for any target from its homepage.

 

8.

Blackout is successfully created. Click the target in the Target list.

 

9.

You can see that the Status is Under Blackout. To stop the blackout click the End Blackout button.

 

10.

Click Yes to confirm.

 

11.

The request to end the Blackout has gone through successfully. Click the target in the Target list.

 

12.

At the end of the blackout, the status of the target is reevaluated. The target home page will then show you the current status of the target.

 

Back to Topic List

Targets that are collectively managed together can be put into Groups in order to facilitate management of these targets. The Group management features have been enhanced with default performance charts, more detailed home pages and a System Dashboard to enable administrators to easily manage the targets as one. This exercise takes you through some of these features.

1.

You will be creating a group that you can manage collectively through the group management features in Oracle Enterprise Manager 10g Release 2. Click the Groups tab.

 

2.

Click the Add button to create a new group.


3.

Give an appropriate name for the group and click the Add button to select the targets.

 

4.

Select Host from the Target Type drop-down list. Select two targets and click Select.

 

5.

Click the Add button to add more targets.

 

6.

Select Database Instance from the Target Type drop-down list. Select two targets and click Select.

 

7.

Click OK to create the group.

 

8.

The group is successfully created. Click the group that you just created.

 

9.

This is the home page for the group and shows you the overall health of the group. You can get an overview of the combined availability status, open alerts and policy violations, and configuration changes over the past 7 days across all group members. Click the Charts subtab.

 

10.

Default performance charts are predefined for you based on the members of the group. These charts enable to you monitor the overall performance of the group.

We will next look at the System Dashboard for the group. To launch the dashboard, click the Launch Dashboard button. The System Dashboard enables administrators to easily keep a proactive eye on the overall health of the group.

 

11.

The system dashboard is predefined with a set of metrics based on the members of the group. You can customize the system dashboard for your particular environment. Click the Customize link at the top-right corner to customize the dashboard.

 

12.

Select the Group by Target Type option button and Show Alert Details check box. Then click OK.

 

13.

You can now see that the member targets of the group are not listed individually but a summary of all target types in the group is shown. A rollup of the status and alerts for members within each target type is also shown, with drilldowns to get more details. Once you are done reviewing the dashboard information, click the link Group:Generic Group to return to the group home page.

 

Back to Topic List

In this lesson, you learned how to:

Change collection schedule and disable data collection of metrics
Define corrective actions
Create SQL User-Defined Metrics
Create and apply monitoring template
Work with blackouts
Use the System Dashboard

Back to Topic List

To ask a question about this OBE tutorial, post a query on the OBE Discussion Forum.

Back to Topic List

Place the cursor over this icon to hide all screenshots.