| Oracle® Enterprise Manager Oracle Database and Database-Related Metric Reference Manual 12c Release 1 (12.1.0.2.0) Part Number E25160-03 |
|
|
PDF · Mobi · ePub |
| Oracle® Enterprise Manager Oracle Database and Database-Related Metric Reference Manual 12c Release 1 (12.1.0.2.0) Part Number E25160-03 |
|
|
PDF · Mobi · ePub |
The Oracle Cluster metrics provide the following information for each metric:
Description
Metric summary. The metric summary can include some or all of the following: target version, evaluation frequency, collection frequency, upload frequency, operator, default warning threshold, default critical threshold, consecutive number of occurrences preceding notification, and alert text.
Multiple Thresholds (where applicable)
Data source
User action
The metrics in this category provide an overview of the clusterware status for this cluster, how many nodes in this cluster have problems, and the CLUVFY utility output for all the nodes of this cluster. Generally, the clusterware is up if the clusterware on at least one host is up.
This metric shows the CLUVFY output of clusterware for all nodes of this cluster.
The load list is:
cluvfy comp crs -n node1, node2 ...
where node1, node2� is the node list for the cluster.
Search for the CLUVFY utility in the 10g Release 2 Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide.
This metric shows the overall clusterware status for this cluster. The clusterware is up if the clusterware on at least one host is up.
The following table shows how often the metric's value is collected.
Table 4-1 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
10.2.0.0 |
Every 5 Minutes |
After Every Sample |
= |
2 |
0 |
1 |
Clusterware has problems on all hosts of this cluster. %CRS_output% |
Note: Although the warning threshold by default is 0, you can change this value to represent how many nodes should have problems before an alert is triggered.
The load list is:
cluvfy comp crs -n node1, node2 ...
Search for the CLUVFY utility in the 10g Release 2 Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide.
This metric shows how many nodes have clusterware problems.
The load list is:
cluvfy comp crs -n node1, node2 ...
where node1, node2� is the node list for the cluster.
The following table shows how often the metric's value is collected.
Table 4-2 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 5 Minutes |
After Every Sample |
> |
0 |
Not Defined |
1 |
There are %CRS_failed_node_count% host(s) with Clusterware problems. %CRS_output% |
Note: Although the warning threshold by default is 0, you can change this value to represent how many nodes have problems before an alert is triggered.
Search for the CLUVFY utility in the 10g Release 2 Oracle Clusterware and Oracle Real Application Clusters Administration and Deployment Guide.
This metric monitors the status of the clusterware on the host.
Clusterware Status verifies the status of Oracle Clusterware on the local host. If verification fails, Clusterware on the local node is marked as Down.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-3 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 5 Minutes |
After Every Sample |
= |
Not Defined |
0 |
1 |
Clusterware on the local host has problems. %CRS_output% |
Clusterware status is derived using cluster verification utility cluvfy.
Check if all Clusterware processes are running on the local node. This can be verified using CLI cluvfy.
This section provides details of the Cluster Alert Log metrics
This column shows the name and full path of the CRS alert log.
This metric appears in Enterprise Manager Cloud Control 10.2.
The following table shows how often the metric's value is collected.
| Target Version | Collection Frequency |
|---|---|
| CRS Version 10.2 | Every 5 Minutes |
This metric collects certain error messages in the CRS alert log at the cluster level.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-4 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 5 Minutes |
After Every Sample |
CONTAINS |
Not Defined |
CRS- |
1* |
%crsErrStack% See %alertLogName for details. |
* After an alert is triggered for this metric, you must manually clear it.
For this metric, you can set different warning and critical threshold values for each "Time/Line Number" object. If warning or critical threshold values are currently set for any "Time/Line Number" object, you can view these thresholds on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Time/Line Number" object, use the Edit Thresholds page.
This column collects CRS-1607, 1802, 1803, 1804 and 1805 messages from the CRS alert log at the cluster level, and issues alerts based on the error code.
This metric appears in version 10.2 of Enterprise Manager Cloud Control.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-5 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 5 Minutes |
After Every Sample |
MATCH |
CRS-180(2|3|4|5) |
CRS-1607 |
1* |
%nodeErrStack% See %alertLogName for details. |
* After an alert is triggered for this metric, you must manually clear it.
For this metric, you can set different warning and critical threshold values for each "Time/Line Number" object. If warning or critical threshold values are currently set for any "Time/Line Number" object, these thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Time/Line Number" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This column collects CRS-1001, 1002, 1003, 1004, 1005, 1006, 1007, 1008, 1010 and 1011 messages from CRS alert log at the cluster level and issue alerts based on the error code.
This metric appears in version 10.2 of Enterprise Manager Cloud Control.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-6 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 5 Minutes |
After Every Sample |
MATCH |
CRS-100(1|2|3|4|5|7) |
CRS-(1006|1008|1010|1011) |
1* |
%ocrErrStack% See %alertLogName for details. |
* After an alert is triggered for this metric, you must manually clear it.
For this metric, you can set different warning and critical threshold values for each "Time/Line Number" object. If warning or critical threshold values are currently set for any "Time/Line Number" object, these thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Time/Line Number" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This column collects CRS-1607, 1802, 1803, 1804 and 1805 messages from the CRS alert log at the cluster level, and issues alerts based on the error code.
This metric appears in version 10.2 of Enterprise Manager Cloud Control.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-7 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 5 Minutes |
After Every Sample |
MATCH |
Not Defined |
CRS-160(4|5|6) |
1* |
%votingErrStack% See %alertLogName for details. |
* After an alert is triggered for this metric, you must manually clear it.
For this metric, you can set different warning and critical threshold values for each "Time/Line Number" object. If warning or critical threshold values are currently set for any "Time/Line Number" object, these thresholds can be viewed on the Metric Detail page for this metric.
To specify or change warning or critical threshold values for each "Time/Line Number" object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.
This section describes the Cluster Resource State (CRS) metrics.
This is the CRS resource status change metric.
This metric appears in version 10.2 of Enterprise Manager Cloud Control.
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
Table 4-8 Metric Summary Table
| Target Version | Evaluation and Collection Frequency | Upload Frequency | Operator | Default Warning Threshold | Default Critical Threshold | Consecutive Number of Occurrences Preceding Notification | Alert Text |
|---|---|---|---|---|---|---|---|
|
All Versions |
Every 24 Hours |
After Every Sample |
MATCH |
COMPLETE_INTERMEDIATE|PARTIALLY_UNKNOWN|PARTIALLY_OFFLINE|PARTIALLY_INTERMEDIATE |
COMPLETE_UNKNOWN|COMPLETE_OFFLINE|ADD|DOWN |
1* |
%crs_entity_name% has %resource_status_alert_count% instances in %resource_status_alert_state% State %resource_status_additional_mesg% |
* After an alert is triggered for this metric, you must manually clear it.
|
 Copyright © 2006, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
