Skip Headers
Oracle® Enterprise Manager Oracle Database Plug-in Metric Reference Manual
Plug-in Release 12.1.0.5

E25160-09
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

4 Cluster

The Oracle Cluster metrics provide the following information for each metric:

4.1 Clusterware Metrics

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 Cluster Verification (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.

4.1.1 Cluster Verification Output

This metric shows the CLUVFY output of clusterware for all nodes of this cluster.

Data Source

The load list is:

cluvfy comp crs -n node1, node2 ...

where node1, node2� is the node list for the cluster.

User Action

Search for the Cluster Verification (CLUVFY) utility in the Oracle Clusterware Administration and Deployment Guide.

4.1.2 Clusterware Status

This metric shows the overall clusterware status for this cluster. The clusterware is up if the clusterware on at least one host is up.

Metric Summary

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

10gR2, 11g, 12c

Every 5 Minutes

After Every Sample

=

2

0

-

Clusterware has problems on the master agent host %CRS_output%


Data Source

The load list is:

cluvfy comp crs -n node1, node2 ...

User Action

Search for the Cluster Verification (CLUVFY) utility in the Oracle Clusterware Administration and Deployment Guide.

4.1.3 Node(s) with Clusterware Problem

This metric shows how many nodes have clusterware problems.

Data Source

The load list is:

cluvfy comp crs -n node1, node2 ...

where node1, node2 is the node list for the cluster.

Metric Summary

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.

User Action

Search for the Cluster Verification (CLUVFY) utility in the Oracle Clusterware Administration and Deployment Guide.

4.2 Clusterware Alert Log Metrics

This section provides details of the Cluster Alert Log metrics

4.2.1 Clusterware Service Alert Log Error

This metric collects certain error messages in the CRS alert log at the cluster level.

Metric Summary

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

10gR2, 11gR1

Every 5 Minutes

After Every Sample

MATCH

CRS-1601

Not Defined

-

%clusterwareErrStack%

See %alertLogName% for details.

11gR2, 12c

Every 5 Minutes

After Every Sample

MATCH

CRS-(8011|8013|8014|8015)

Not Defined

-

%clusterwareErrStack%

See %alertLogName% for details.


Note:

Do not modify the default warning and critical thresholds for this metric.

4.2.2 Node Configuration Alert Log Error

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.

Metric Summary

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

10gR2, 11gR1

Every 5 Minutes

After Every Sample

MATCH

CRS-180(2|3|4|5)

CRS-1607

-

%nodeErrStack%

See %alertLogName for details.

11gR2, 12c

Every 5 Minutes

After Every Sample

MATCH

Not Defined

CRS-1607

-

%nodeErrStack%

See %alertLogName% for details.


Note:

Do not modify the default warning and critical thresholds for this metric.

4.2.3 OCR Alert Log Error

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.

Metric Summary

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

10gR2, 11gR1

Every 5 Minutes

After Every Sample

MATCH

CRS-100(1|2|3|4|5|7)

CRS-(1006|1008|1010|1011)

-

%ocrErrStack%

See %alertLogName for details.


Note:

Do not modify the default warning and critical thresholds for this metric.

4.2.4 Voting Disk Alert Log Error

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.

Metric Summary

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

10gR2, 11gR1

Every 5 Minutes

After Every Sample

MATCH

Not Defined

CRS-160(4|5|6)

-

%votingErrStack%

See %alertLogName for details.

11gR2, 12c

Every 5 Minutes

After Every Sample

MATCH

Not Defined

CRS-160(4|5|6)

-

%votingErrStack%

See %alertLogName% for details.


Note:

Do not modify the default warning and critical thresholds for this metric.

4.3 QoS Events Metrics

This section describes the Quality of Service (QoS) event metrics.

4.3.1 Compliance State

For a database to be managed by Oracle Database QoS Management, the database must be compliant.

Metric Summary

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

11gR2, 12c

-

After Every Sample

MATCH

Not Defined

NOT_COMPLIANT

-

Server pool %wlm_entity_name% has a violation. Please refer to the Grid Operations Manager log for details


4.3.2 Memory Pressure Analysis Risk State

Oracle Database QoS Management detects memory pressure on a server in real time and redirects new sessions to other servers to prevent using all available memory on the stressed server.

This metric indicates that the database server is experiencing memory pressure.

Metric Summary

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

11gR2, 12c

-

After Every Sample

MATCH

RED

Not Defined

-

Server %wlm_server% is under elevated memory pressure and services on all instances on this server will be stopped


4.3.3 QoSM State Change

This metric displays the reason for a change in the Oracle Database QoS Management state.

Metric Summary

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-9 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

11gR2, 12c

-

After Every Sample

MATCH

USER_DISABLED

EXCEPTION_DISABLED

-

QoSM service is disabled due to %wlm_qosm_state%.


4.4 Resource State Metrics

This section describes the Cluster Resource State (CRS) metric.

4.4.1 State Change

This is the CRS resource status change metric.

Metric Summary

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-10 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

11gR2, 12c

Every 24 Hours

After Every Sample

MATCH

COMPLETE_INTERMEDIATE|PARTIALLY_UNKNOWN|PARTIALLY_OFFLINE|PARTIALLY_INTERMEDIATE

COMPLETE_UNKNOWN|COMPLETE_OFFLINE|ADD|DOWN

-

%crs_entity_name% has %resource_status_alert_count% instances in %resource_status_alert_state% State %resource_status_additional_mesg%