Automatic Storage Management

1.1 Alert Log

This metric signifies that the ASM target being monitored has generated errors to the ALERT log file since the last sample time. The ALERT log file is a special trace file containing a chronological log of messages and errors.

Critical Alerts are generated for different type of failure, for example, when archiver hung, data block corrupted and Media failure are found in the alert log with the following error code (ORA-00257, 16038, 01157,01578,27048). The metric shows the user the line number and time when the error occurred.

Warning alerts are also generated when Session Terminated Error Stack (ORA- 00603) are present in the alert log. Many other critical alerts also occur when the Ora-15130 (Disk Group is being dismounted), Ora-15050 (Disk contains errors) and Ora-15051 (File contains errors) are present in alert log.

You can edit the metric threshold and change the value of error you want to collect under a different head. Also, you can modify the warning and critical alert values.

This metric is collected at a time interval of 15 minutes. You can change the threshold limit as per your requirements.

1.1.1 Alert Log Error Stack

This metric contains the information about different ORA- errors present in the alert log file. It ignores error patterns like ORA-0*(54|1142|1146) present in the alert log file and generate a warning alert when ORA-0*600x, ORA-07445, ORA-04 [0-9][0-9][0-9])[^0-9] errors are present.

Edit the metric threshold and change the value of the ORA- error to generate the warning and critical alert for a different set of ORA- errors.

Metric Summary for Database 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
10.1.0.x; 10.2.0.x	Every 5 Minutes	After Every Sample	MATCH	ORA-0*(600?\|7445\|4[0-9][0-9][0-9])[^0-9]	Not Defined	1^Foot 1	ORA-error stack (%errCodes%) logged in %alertLogName%.

^Footnote 1Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

For this metric column you can set different warning and critical threshold values for each for each "Timestamp/LineNumber" object.

If warning or critical threshold values are currently set for any "Timestamp/LineNumber" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Timestamp/LineNumber" object, use the Edit Thresholds page. .

Data Source

The data comes from Alert Log Files. It is collected using the perl script $ORACLE_HOME/sysman/admin/scripts/alertlog.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent. The alert log file is scanned for the ORA- errors ignoring the patterns like ORA-0*(54|1142|1146).

User Action

Examine ALERT log for additional information.

1.1.2 Alert Log Error Stack Trace File Name

This metric provides information about the trace file name in which ORA- errors are present. It provides the detail of the trace file name and the line at which the error has occurred.

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version	Evaluation and Collection Frequency
10.1.0.x; 10.2.0.x	Every 5 Minutes

Data Source

The data comes from the Alert Log files. It is collected using the perl script $ORACLE_HOME/sysman/admin/scripts/alertlog.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

No user action is required.

1.1.3 Alert Log Name

This metric provides the information about the alert log file in which ORA- errors are present. It displays the file name and the line at which the error has occurred.

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version	Evaluation and Collection Frequency
10.1.0.x; 10.2.0.x	Every 5 Minutes

Data Source

The data comes from Alert Log Files. It is collected using the perl script $ORACLE_HOME/sysman/admin/scripts/alertlog.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

Examine ALERT log for additional information.

1.1.4 Archive Hung Error Stack

This metric contains the information about different ORA- errors, which indicate the presence of Archive Hung in the alert log files. The errors ORA-00257 and ORA-16038 in the alert log indicates an archive-hung problem. This also generates a critical alert when these problems are found in alert logs.

You can edit the metric threshold and change the value of the error you want to collect under a different head. Also, the warning and critical alert values can be modified or set.

Metric Summary for Database 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
10.1.0.x; 10.2.0.x	Every 5 Minutes	After Every Sample	CONTAINS	Not Defined	ORA-	1^Foot 1	The archiver hung at time/line number: %timeLine%.

^Footnote 1Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

For this metric column you can set different warning and critical threshold values for each for each "Timestamp/LineNumber" object.

If warning or critical threshold values are currently set for any "Timestamp/LineNumber" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Timestamp/LineNumber" object, use the Edit Thresholds page.

Data Source

The data comes from Alert Log Files. It is collected using the perl script $ORACLE_HOME/sysman/admin/scripts/alertlog.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent. Alert log file is scanned for the ORA-00257 and ORA-16038 error.

User Action

Examine ALERT log for additional information.

1.1.5 Data Block Corruption Error Stack

This metric contains the information about different ORA- errors, which indicate the presence of Data Block Corruption errors in the alert log files. The errors ORA- 01157, ORA-01578, and ORA-27048 in the alert log indicates Data Block Corruption problems. This also generates a critical alert when these problems are found in alert logs.

You can edit the metric threshold and change the value of the error you want to collect under a different head. Also, the warning and critical alert values can be modified or set.

Metric Summary for Database 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
10.1.0.x; 10.2.0.x	Every 5 Minutes	After Every Sample	CONTAINS	Not Defined	ORA-	1^Foot 1	The data block was corrupted at time/line number: %timeLine%.

^Footnote 1Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

For this metric column you can set different warning and critical threshold values for each for each "Timestamp/LineNumber" object.

If warning or critical threshold values are currently set for any "Timestamp/LineNumber" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Timestamp/LineNumber" object, use the Edit Thresholds page.

Data Source

The data comes from Alert Log Files. It is collected using the perl script $ORACLE_HOME/sysman/admin/scripts/alertlog.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent. Alert log file is scanned for the ORA- 01157, ORA-01578, and ORA-27048 error.

User Action

Examine ALERT log for additional information.

1.1.6 Media Failure Error Stack

This metric contains the information about different ORA- errors, which indicate the presence of Media Failure Errors in the alert log files. The errors ORA- 15130,ORA-15049, ORA-15050 and ORA-15051 in the alert log indicates Media Failure Error problems. This generates a critical alert when these problems are found in alert logs.

You can edit the metric threshold and change the value of the error you want to collect under a different head. Also the warning and critical alert values can be modified or set.

Metric Summary for Database 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
10.1.0.x; 10.2.0.x	Every 5 Minutes	After Every Sample	CONTAINS	Not Defined	ORA-	1^Foot 1	Media failure was detected at time/line number: %timeLine%.

^Footnote 1Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

For this metric column you can set different warning and critical threshold values for each for each "Timestamp/LineNumber" object.

If warning or critical threshold values are currently set for any "Timestamp/LineNumber" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Timestamp/LineNumber" object, use the Edit Thresholds page.

Data Source

The data comes from Alert Log Files. It is collected using the perl script $ORACLE_HOME/sysman/admin/scripts/alertlog.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent. Alert log file is scanned for the ORA- 15130,ORA-15049, ORA-15050and ORA-15051 error.

User Action

Examine ALERT log for additional information.

1.1.7 Session Terminated Error Stack

This metric contains the information about different ORA- errors, which indicate the presence of Session Terminated problems in the alert log files. The ORA- 00603 error in the alert log indicates Session Terminated problems. This also generates a warning alert when these problems are found in alert logs.

You can edit the metric threshold and change the value of the error you want to collect under a different head. Also, the warning and critical alert values can be modified or set.

Metric Summary for Database 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
10.1.0.x; 10.2.0.x	Every 5 Minutes	After Every Sample	CONTAINS	ORA-	Not Defined	1^Foot 1	A session was terminated at time/line number: %timeLine%.

^Footnote 1Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

For this metric column you can set different warning and critical threshold values for each for each "Timestamp/LineNumber" object.

If warning or critical threshold values are currently set for any "Timestamp/LineNumber" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Timestamp/LineNumber" object, use the Edit Thresholds page.

Data Source

The data comes from Alert Log Files. It is collected using the perl script $ORACLE_HOME/sysman/admin/scripts/alertlog.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent. The alert log file is scanned for the ORA- 00603 error.

User Action

Examine the ALERT log for additional information.

1.2 Alert Log Error Status

This metric displays the number of times an Alert has been generated for the Alert log metric. It provides information about the current status of different errors present in the alert log file.

This Metric is part of 10g Release 2 and generates a warning alert with any occurrence of ORA- Error [excluding ORA-0*(54|1142|1146)]. It also generates a Warning alert when it detects an Archiver Hung Error, Data Block Corruption Error, Media Failure Error and Session Terminated Error.

This metric is collected with the help Alert Log Metric, and the time interval for collection 5 Minutes. You can change the threshold limit count for the Warning alert and critical alert as required.

1.2.1 Archiver Hung Alert Log Error Status

This metric signifies the number of times the Archiver Hung error (ORA-00257 and ORA-16038) has been generated in the Alert log metric. It gives user an idea about the current status of Archiver Hung error present in the alert log file. This also generates a warning alert when this count is greater than zero.

User can edit the metric threshold and change the value of error he/she wants to collect under different head. Also the warning alert and critical alert values can be modified or set.

Metric Summary for Database 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
10.1.0.x; 10.2.0.x	Every 5 Minutes	After Every Sample	>	0	Not Defined	1	Archiver hung errors have been found in the alert log.

Data Source

Calculated based on the Archive Hung Error Stack Metric rollup.

User Action

Examine ALERT log for additional information. Note: This event does not automatically clear since there is no automatic way of determining when the problem has been resolved. Hence, you need to manually clear the event once the problem is fixed.

1.2.2 Data Block Corruption Alert Log Error Status

This metric signifies the number of times the Data Block Corruption error (ORA- 01157, ORA-01578, and ORA-27048) has been generated in the Alert log metric. It gives user an idea about the current status of Data Block Corruption error present in the alert log file. This also generates a warning alert when this count is greater than zero.

User can edit the metric threshold and change the value of error he/she wants to collect under different head. Also the warning alert and critical alert values can be modified or set.

Metric Summary for Database 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
10.1.0.x; 10.2.0.x	Every 5 Minutes	After Every Sample	>	0	Not Defined	1	Data block corruption errors have been found in the alert log.

Data Source

Calculated based on the Data Block Corruption Error Stack Metric rollup.

User Action

Examine ALERT log for additional information. Note: This event does not automatically clear since there is no automatic way of determining when the problem has been resolved. Hence, you need to manually clear the event once the problem is fixed.

1.2.3 Generic Alert Log Error Status

This metric signifies the number of times the Generic Alert error (ORA-0*600x, ORA-07445, ORA-04 [0-9][0-9][0-9])[^0-9]) has been generated in the Alert log metric. It gives user an idea about the current status of Generic Alert (ORA-) error present in the alert log file. This also generates a warning alert when this count is greater than zero.

User can edit the metric threshold and change the value of error he/she wants to collect under different head. Also the warning alert and critical alert values can be modified or set.

Metric Summary for Database 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
10.1.0.x; 10.2.0.x	Every 5 Minutes	After Every Sample	>	0	Not Defined	1	%value% distinct types of ORA- errors have been found in the alert log.

Data Source

Calculated based on the Generic Alert Error Stack Metric rollup.

User Action

Examine ALERT log for additional information.

1.2.4 Media Failure Alert Log Error Status

This metric signifies the number of times the Media Failure Alert error (ORA- 15130,ORA-15049, ORA-15050and ORA-15051) has been generated in the Alert log metric. It gives user an idea about the current status of Media Failure Alert (ORA-) error present in the alert log file. This also generates a warning alert when this count is greater than zero.

User can edit the metric threshold and change the value of error he/she wants to collect under different head. Also the warning alert and critical alert values can be modified or set.

Metric Summary for Database 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
10.1.0.x; 10.2.0.x	Every 5 Minutes	After Every Sample	>	0	Not Defined	1	Media failure errors have been found in the alert log.

Data Source

Calculated based on the Media Failure Alert Error Stack Metric rollup.

User Action

Examine ALERT log for additional information. Note: This event does not automatically clear since there is no automatic way of determining when the problem has been resolved. Hence, you need to manually clear the event once the problem is fixed.

1.2.5 Session Terminated Alert Log Error Status

This metric signifies the number of times the Session Terminated Alert error (ORA- 00603) has been generated in the Alert log metric. It gives user an idea about the current status of Session Terminated Alert (ORA-) error present in the alert log file. This also generates a warning alert when this count is greater than zero.

User can edit the metric threshold and change the value of error he/she wants to collect under different head. Also the warning alert and critical alert values can be modified or set.

Metric Summary for Database 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
10.1.0.x; 10.2.0.x	Every 5 Minutes	After Every Sample	>	0	Not Defined	1	Session terminations have been found in the alert log.

Data Source

Calculated based on the Session Terminated Alert Error Stack Metric rollup.

User Action

Examine ALERT log for additional information. Note: This event does not automatically clear since there is no automatic way of determining when the problem has been resolved. Hence, you need to manually clear the event once the problem is fixed.

1.3 ASM Cluster File System Metrics

The ASM Cluster File System metrics show the space used by all the ASM Cluster File Systems. These metrics are used to collect information about the ASM Cluster File System space usage and are used to show the trend of ASM Cluster File System space usage in the application. These metrics collect information for both mounted and dismounted ASM Cluster File Systems. This information is used to determine the following metrics for Space Usage: Allocated Space (GB), Size (GB), Free (GB), Used (GB), and Used (%). These metrics also collect information whether the ASM Cluster File System is corrupt. For dismounted ASM Cluster File Systems, 0 is returned for the Free (GB), Used (GB), and Used (%) metrics.

These metrics only collect information about the ASM Cluster File System that is not specific to a node in a cluster. They collect Space Usage information which is the same across all nodes in the cluster. Information like State and Availability of the ASM Cluster File System can be different across the nodes in a cluster and is collected by the ASM Cluster File System State metrics.

These metrics generate a warning alert if the ASM Cluster File System is 85% used and a critical alert if 97% used. These metrics also generate a critical alert if the ASM Cluster File System has sections that are corrupt.

These metrics are collected at a time interval of 15 minutes. You can change the threshold limit as required.

1.3.1 Corrupt

This metric shows if the mounted ASM Cluster File System has sections that are corrupt. A value of "TRUE" for this metric indicates that there are sections that are corrupt and hence the "Check and Repair" operation should be run on the ASM Cluster File System to fix it. For dismounted ASM Cluster File Systems, it returns a value of Null for this metric.

This metric generates a warning alert if the ASM Cluster File System is dismounted on a given host. The metric also generates a critical alert if the mounted ASM Cluster File System is not available on a host.

This metric is collected at a time interval of 15 minutes. You can change the threshold limit as required.

This metric is collected with the help of a SQL query which queries the V$ASM_FILESYSTEM, V$ASM_VOLUME, V$ASM_OFSVOLUMES views.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.2.0.x	Every 15 Minutes	After Every Sample	=	Not Defined	TRUE	1	The ASM Cluster File System using volume device %ofs_volume_device% has sections that are corrupt. Run check and repair operation on the file system to fix the issue.

Multiple Thresholds

For this metric column you can set different warning and critical threshold values for each unique combination of "Volume Device" and "Disk Group" objects.

If warning or critical threshold values are currently set for any unique combination of "Volume Device" and "Disk Group" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Volume Device" and "Disk Group" objects, use the Edit Thresholds page.

Data Source

This metric is collected from the column CORRUPT in the V$ASM_FILESYSTEM view for mounted ASM Cluster File Systems. For Dismounted File Systems, a value of Null is returned for this metric.

User Action

Run Check and Repair on the ASM Cluster File System to fix the corrupted sections.

1.3.2 Disk Group Allocated Space (GB)

This metric shows the space allocated from the disk group for this ASM Cluster File System in GB.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every 15 Minutes

Data Source

This metric is collected from the column SPACE in the V$ASM_FILE view

User Action

No user action is required.

1.3.3 Free (GB)

This metric shows the unused capacity of the ASM Cluster File System in gigabytes. It gives an indication of the free space available in the ASM Cluster File System. For dismounted ASM Cluster File Systems, a value of 0 is returned for this metric.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every 15 Minutes

Data Source

This metric is collected from the column TOTAL_FREE in the V$ASM_FILESYSTEM view. For dismounted ASM Cluster File Systems, a value of 0 is returned.

User Action

Consider resizing the ASM Cluster File System if there is not enough Free Space available.

1.3.4 Size (GB)

This metric shows the Size in GB of the ASM Cluster File System.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every 15 Minutes

Data Source

This metric is collected from the column TOTAL_SIZE in the V$ASM_FILESYSTEM view for mounted File Systems and from the column SIZE_MB in the view V$ASM_VOLUME for dismounted File Systems.

User Action

Consider resizing the ASM Cluster File System to add space.

1.3.5 Used (GB)

This metric shows the Space in GB that is used on the mounted ASM Cluster File System. For dismounted ASM Cluster File Systems, a value of 0 is returned for this metric.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every 15 Minutes

Data Source

This metric is calculated from the columns TOTAL_SIZE and TOTAL_FREE in the V$ASM_FILESYSTEM view. It is calculated as:

TOTAL_SIZE - TOTAL_FREE

For dismounted ASM Cluster File Systems, a value of 0 is returned for this metric

User Action

Consider Resizing the ASM Cluster File System to add more space.

1.3.6 Used (%)

This metric shows the percentage of Space that is used on the ASM Cluster File System. For dismounted ASM Cluster File Systems, a value of 0 is returned for this metric.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.2.0.x	Every 15 Minutes	After Every Sample	>	85	97	1	The ASM Cluster File System using volume device %ofs_volume_device% is %ofs_used_pct%%% full. Resize the file system to add more space.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Volume Device" and "Disk Group" objects.

If warning or critical threshold values are currently set for any unique combination of "Volume Device" and "Disk Group" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Volume Device" and "Disk Group" objects, use the Edit Thresholds page.

Data Source

This metric is calculated from the columns TOTAL_SIZE and TOTAL_FREE in the V$ASM_FILESYSTEM view. It is calculated as:

TOTAL_SIZE - TOTAL_FREE/TOTAL_SIZE * 100

For dismounted ASM Cluster File Systems, a value of 0 is returned for this metric

User Action

Consider resizing the ASM Cluster File System to add more space to fix the alert generated by this metric.

1.3.7 Volume Name

This metric shows the Volume Name of the Volume Device used to create the ASM Cluster File System.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every 15 Minutes

Data Source

This metric is collected from the column VOLUME_NAME in the V$ASM_VOLUME view.

User Action

No user action is required.

1.4 ASM Cluster File System State Metrics

The ASM Cluster File System State metrics show the state of the ASM Cluster File System, whether it is MOUNTED or DISMOUNTED on a given host. In a cluster environment, the ASM Cluster File System could be mounted only on specific hosts. If the ASM Cluster File System is MOUNTED on a given host, the metrics also display if the system is AVAILABLE and the time since it is available. This is used to determine the following metrics: Mount Point, Mount State, Availability, and Available Time.

These metrics generate a warning alert if the ASM Cluster File System is dismounted on a given host. These metrics also generate a critical alert if the mounted ASM Cluster File System is not available on a host.

These metrics are collected with the help of a SQL query which queries the V$ASM_FILESYSTEM, V$ASM_VOLUME, V$ASM_OFSVOLUMES views.

1.4.1 ASM Cluster File System Availability

This metric shows if the MOUNTED ASM Cluster File System is AVAILABLE on a given host in a cluster. For DISMOUNTED ASM Cluster File System's this metric returns a value of NULL.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.2.0.x	Every 5 Minutes	After Every Sample	=	Not Defined	Not Available	1	The ASM Cluster File System %ofs_mount_point% is not available on host %ofs_host%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Volume Device" and "Host" objects.

If warning or critical threshold values are currently set for any unique combination of "Volume Device" and "Host" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Volume Device" and "Host" objects, use the Edit Thresholds page.

Data Source

This metric is collected from the column STATE in the V$ASM_FILESYSTEM view.

User Action

No user action is required.

1.4.2 ASM Cluster File System Available Time

This metric shows the timestamp since which the MOUNTED ASM Cluster File System is AVAILABLE on a given host in a cluster. For DISMOUNTED ASM Cluster File System's this metric returns a value of NULL.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every 5 Minutes

Data Source

This metric is collected from the column AVAILABLE_TIME in the V$ASM_FILESYSTEM view.

User Action

No user action is required.

1.4.3 ACM Cluster File System Mount Point

This metric shows the mount point of the ASM Cluster File System on a given host in a cluster. The same ASM Cluster File System could be mounted on different mount points, on different hosts in a cluster. For DISMOUNTED ASM Cluster File Systems it will return NULL if the OFS has never been mounted on the host or it will return the last mount point if it was mounted and then dismounted on the host.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every 5 Minutes

Data Source

For MOUNTED file systems this metric is collected from the column FS_NAME in the V$ASM_FILESYSTEM view. For DISMOUNTED file systems this metric is collected from the column MOUNTPATH in the V$ASM_VOLUME view.

User Action

No user action is required.

1.4.4 ASM Cluster File System Mount State

This metric shows the state of the ASM Cluster File Systems, whether it is MOUNTED or DISMOUNTED on a given host. In a cluster environment the ASM Cluster File System could be mounted only on specific hosts.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.2.0.x	Every 5 Minutes	After Every Sample	=	Dismounted	Not Defined	1	The volume device %volume_device% is dismounted on host %ofs_host%

Multiple Threshold

For this metric you can set different warning and critical threshold values for each unique combination of "Volume Device" and "Host" objects.

If warning or critical threshold values are currently set for any unique combination of "Volume Device" and "Host" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Volume Device" and "Host" objects, use the Edit Thresholds page.

Data Source

An ASM Cluster File System is "MOUNTED" if the usage of the volume_device is "ACFS" and the volume_device exists in the V$ASM_ACFSVOLUMES view and the mount path exists in the V$ASM_FILESYSTEM view.

An ASM Cluster File System is "DISMOUNTED" if the usage of the volume_device is "ACFS" and the volume_device does not exist in the V$ASM_ACFSVOLUMES view and the mount path does not exist in the V$ASM_FILESYSTEM view.

User Action

Mount the ASM Cluster File System on the given host in the cluster

1.5 ASM Volumes Metrics

The ASM Volumes metrics show information about the Volumes created on a disk group. An ASM Volume file is a file created on the disk group to provide storage for an ASM Cluster File System or a third-party file system. This is used to determine the following metrics for ASM volumes: Volume Name, Status, Usage, Mount Point, Size (GB), Allocated Space (GB), and Redundancy.

These metrics are collected with the help of the V$ASM_VOLUME and GV$ASM_DISKGROUP views.

1.5.1 Disk Group Allocated Space (GB)

This metric gives the space in GB allocated on the disk group for the volume.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every 15 Minutes

Data Source

This metric is retrieved from the column SPACE from the V$ASM_FILE view.

User Action

No user action is required.

1.5.2 Mount Point

An ASM Cluster File System is built on an ASM Volume which in turn uses ASM disk groups for storage. The ASM Cluster File System can then be mounted on any host in a cluster. This metric returns the current MOUNT POINT of the ASM Cluster File System if it is mounted or the most recent MOUNT POINT if it is currently DISMOUNTED. For ASM Volumes that are not used for ASM Cluster File Systems, this metric returns null.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every 15 Minutes

Data Source

This metric is retrieved from the column MOUNTPATH from the V$ASM_VOLUME view.

User Action

No user action is required.

1.5.3 Redundancy

This metric returns the redundancy for the ASM Volume file. The ASM Volume file can use whatever redundancy (external, normal=2-way mirror, high=3-way mirror) is available to the ASM disk group where the ASM Volume file is created.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every 15 Minutes

Data Source

This metric is retrieved from the REDUNDANCY column from the V$ASM_VOLUME view.

User Action

No user action is required.

1.5.4 Size (GB)

This metric returns the size of the ASM Volume in GB. The Volume Size is always created in multiples of the Volume Allocation Unit,

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every 15 Minutes

Data Source

This metric is retrieved from the column SIZE_MB from the V$ASM_VOLUME view.

User Action

No user action is required.

1.5.5 Status

This metric shows the Status of the ASM Volume, if it is ENABLED or DISABLED.

Metric Summary

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every 15 Minutes

Data Source

This metric is retrieved from the column STATE from the V$ASM_VOLUME view.

User Action

No user action is required.

1.5.6 Usage

This metric returns a string indicating what the ASM Volume is used for: ACFS, EXT3, null. A value of null means the usage of the Volume is Unknown.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every 15 Minutes

Data Source

This metric returns a string indicating what the ASM Volume is used for: ACFS, EXT3, null. A value of null means the usage of the Volume is Unknown.

User Action

No user action is required.

1.5.7 Volume Name

This metric returns the name of the ASM volume. This is the name entered when the user creates the ASM Volume on the disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every 15 Minutes

Data Source

This metric is retrieved from the column VOLUME_NAME from the view V$ASM_VOLUME view.

User Action

No user action is required.

1.6 Checker Failure

NOTE TO JACKIE: Sent e-mail to Mary Pawelko on 19-Feb-2010 requesting information. Mary pointed me to Sukumar.Vanka (IDC), the author of the metric. I sent Sukumar e-mail on 19-Feb-2010.

This metric...

1.6.1 Alert Log Name

This metric returns the name of the Alert Log.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.1.0.x; 11.2.0.x	Every 5 Minutes

Data Source

This metric is retrieved from the....

User Action

No user action is required.

1.6.2 Checker Failure Detected

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x; 11.2.0.x	Every 5 Minutes	After Every Sample	MATCH	Not Defined	.^Foot 1	1^Footref 1	Health checker runs found %numberOfFailures% new failures in %alertLogName% at time/line number: %timeLine%.

^Footnote 1Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

For this metric column you can set different warning and critical threshold values for each for each "Time/LineNumber" object.

If warning or critical threshold values are currently set for any "Time/LineNumber" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Time/LineNumber" object, use the Edit Thresholds page.

Data Source

The data comes from

User Action

1.7 Cluster Disk Group Performance Metrics

The Cluster Disk Group Performance metrics show the Cluster Disk Group performance parameters for all the disk groups present in a cluster. These metrics are used to collect information, for example, total I/O and read/write requests, total I/O and read/write time, and total number of bytes read/written for the cluster disk group. These metrics also show the disk group response, throughput, operations per second, and size for read, write, and I/O.

1.7.1 I/O Per Second

This metric shows the sum of disks I/O performance per second in terms of total I/O requests for all the disks within the disk group. The data is aggregated for all instances that are part of the cluster.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average I/Os per second for each disk, the total number of I/O responses is divided by the total I/O time during the collection interval. This data is aggregated by the disk group name to get the average I/O operations per second of a disk group. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.7.2 I/O Size (MB)

This metric shows the sum of disk I/O size for all disks within the disk group. The data is aggregated for all instances that are part of the cluster.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average I/O size of each disk, the total number of bytes read and written is divided by the total number of I/Os during the collection interval. This data is aggregated by the disk group name to get the average I/O size of a disk group. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.7.3 I/O Throughput

This metric shows the sum of I/O throughput for all disks within the disk group The data is aggregated for all instances that are part of the cluster. This gives an indication of the disk group I/O performance in terms of read and write.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average I/O throughput of each disk, the total number of bytes read and written is divided by the total I/O time during the collection interval. This data is aggregated by the disk group name to get the average I/O throughput of a disk group. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.7.4 Read Response Time (MS)

This metric shows the read response time detail for a disk group in an Automatic Storage Management (ASM) instance. This gives an indication for the disk group response time in terms of read requests for the disks included in the disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average read response time for each disk, the total read time is divided by the total number of read responses during the collection interval. This data is aggregated by the disk group name to get the average read response time of a disk group. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.7.5 Read Size (MB)

This metric shows the sum of all disk read size for all disks within the disk group which are part of the cluster. The data is aggregated for all instances.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average read size of each disk, the total number of bytes read is divided by the total number of reads during the collection interval. This data is aggregated by the disk group name to get the average read size of a disk group. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.7.6 Read Throughput

This metric shows the read throughput detail of a disk group mounted in an Automatic Storage Management (ASM) instance. This gives an indication for the total number of bytes read from the disk group with proportion to the total read time for this disk group in an instance.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average read throughput of each disk, the total number of bytes read is divided by the total read time during the collection interval. This data is aggregated by the disk group name to get the average read throughput of a disk group. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.7.7 Reads Per Second

This metric shows the detail of total read requests per second for the disk group. This metric shows the read performance of the disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average reads per second for each disk, the total number of read responses is divided by the total read time during the collection interval. This data is aggregated by the disk group name to get the average read operations per second of a disk group. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.7.8 Response Time (MS)

This metric shows the I/O response time detail of mounted disk groups. For this disk group, this metric indicates the response time in terms of total I/O requests for all the disks included in the disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average I/O response time for each disk, the total I/O time is divided by the total number of I/O responses during the collection interval. This data is aggregated by the disk group name to get the average I/O response time of a disk group. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.7.9 Write Response Time (MS)

This metric shows the write response time detail for a disk group in an Automatic Storage Management (ASM) instance. This gives an indication for the disk group response time in terms of total write requests for the disks included in a disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average write response time for each disk, the total write time is divided by the total number of write responses during the collection interval. This data is aggregated by the disk group name to get the average write response time of a disk group. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.7.10 Write Size (MB)

This metric shows the sum of all disk write size for all disks within the disk group which are part of the cluster. The data is aggregated for all instances.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average write size of each disk, the total number of bytes written is divided by the total number of writes during the collection interval. This data is aggregated by the disk group name to get the average write size of a disk group. The data is then aggregated for all instances that are part of the cluster

User Action

No user action is required.

1.7.11 Write Throughput

This metric shows the write throughput detail of a disk group mounted in an Automatic Storage Management (ASM) instance. This gives an indication for the total number of bytes written from the disk group with proportion to the total write time for this disk group in an instance.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average write throughput of each disk, the total number of bytes written is divided by the total write time during the collection interval. This data is aggregated by the disk group name to get the average write throughput of a disk group. The data is then aggregated for all instances that are part of the cluster

User Action

No user action is required.

1.7.12 Writes Per Second

This metric shows the detail of total write requests per second for a disk group in an Automatic Storage Management (ASM) instance. This metric shows the write performance of the disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average writes per second for each disk, the total number of write responses is divided by the total write time during the collection interval. This data is aggregated by the disk group name to get the average write operations per second of a disk group. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.8 Cluster Disk Performance Metrics

The Cluster Disk Performance metrics show the cluster disk performance parameters for all the disks. These metrics are used to collect information, for example, total I/O and read/write requests, failed read/write and I/O for the disks, total I/O and read/write time, and total number of bytes read/written to the disks. These metrics also show the response of the disks for read, write, and I/O throughput.

1.8.1 I/O Per Second

This metric shows the sum of disks I/O performance per second in terms of total I/O requests for all the disks within the disk group. The data is aggregated for all instances that are part of the cluster.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average I/Os per second for each disk, the total number of I/O responses is divided by the total I/O time during the collection interval. This data is aggregated by the disk group name to get the average I/O operations per second of a disk group. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.8.2 I/O Size (MB)

This metric shows the sum of disk I/O size for all disks within the disk group. The data is aggregated for all instances that are part of the cluster.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average I/O size of each disk, the total number of bytes read and written is divided by the total number of I/Os during the collection interval. This data is aggregated by the disk group name to get the average I/O size of a disk group. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.8.3 I/O Throughput

This metric shows the sum of I/O throughput for all disks within the disk group The data is aggregated for all instances that are part of the cluster. This gives an indication of the disk group I/O performance in terms of read and write.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average I/O throughput of each disk, the total number of bytes read and written is divided by the total I/O time during the collection interval. This data is aggregated by the disk group name to get the average I/O throughput of a disk group. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.8.4 Read Response Time (MS)

This metric shows the read response time detail for a disk group in an Automatic Storage Management (ASM) instance. This gives an indication for the disk group response time in terms of read requests for the disks included in the disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average read response time for each disk, the total read time is divided by the total number of read responses during the collection interval. This data is aggregated by the disk group name to get the average read response time of a disk group. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.8.5 Read Size (MB)

This metric shows the sum of all disk read size for all disks within the disk group which are part of the cluster. The data is aggregated for all instances.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average read size of each disk, the total number of bytes read is divided by the total number of reads during the collection interval. This data is aggregated by the disk group name to get the average read size of a disk group. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.8.6 Read Throughput

This metric shows the read throughput detail of a disk group mounted in an Automatic Storage Management (ASM) instance. This gives an indication for the total number of bytes read from the disk group with proportion to the total read time for this disk group in an instance.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average read throughput of each disk, the total number of bytes read is divided by the total read time during the collection interval. This data is aggregated by the disk group name to get the average read throughput of a disk group. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.8.7 Reads Per Second

This metric shows the detail of total read requests per second for the disk group. This metric shows the read performance of the disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average reads per second for each disk, the total number of read responses is divided by the total read time during the collection interval. This data is aggregated by the disk group name to get the average read operations per second of a disk group. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.8.8 Response Time (MS)

This metric shows the I/O response time detail of mounted disk groups. For this disk group, this metric indicates the response time in terms of total I/O requests for all the disks included in the disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average I/O response time for each disk, the total I/O time is divided by the total number of I/O responses during the collection interval. This data is aggregated by the disk group name to get the average I/O response time of a disk group. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.8.9 Write Response Time (MS)

This metric shows the write response time detail for a disk group in an Automatic Storage Management (ASM) instance. This gives an indication for the disk group response time in terms of total write requests for the disks included in a disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average write response time for each disk, the total write time is divided by the total number of write responses during the collection interval. This data is aggregated by the disk group name to get the average write response time of a disk group. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.8.10 Write Size (MB)

This metric shows the sum of all disk write size for all disks within the disk group which are part of the cluster. The data is aggregated for all instances.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average write size of each disk, the total number of bytes written is divided by the total number of writes during the collection interval. This data is aggregated by the disk group name to get the average write size of a disk group. The data is then aggregated for all instances that are part of the cluster

User Action

No user action is required.

1.8.11 Write Throughput

This metric shows the write throughput detail of a disk group mounted in an Automatic Storage Management (ASM) instance. This gives an indication for the total number of bytes written from the disk group with proportion to the total write time for this disk group in an instance.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average write throughput of each disk, the total number of bytes written is divided by the total write time during the collection interval. This data is aggregated by the disk group name to get the average write throughput of a disk group. The data is then aggregated for all instances that are part of the cluster

User Action

No user action is required.

1.8.12 Writes Per Second

This metric shows the detail of total write requests per second for a disk group in an Automatic Storage Management (ASM) instance. This metric shows the write performance of the disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average writes per second for each disk, the total number of write responses is divided by the total write time during the collection interval. This data is aggregated by the disk group name to get the average write operations per second of a disk group. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.9 Cluster Volume Performance Metrics

The Cluster Volume Performance metrics show the cluster volume performance parameters for all the volumes. These metrics are used to collect information, for example, total I/O and read/write requests, failed read/write and I/O for the disks, total I/O and read/write time, and total number of bytes read/written to the volumes. These metrics also show the response of the volumes for read, write, and I/O throughput.

1.9.1 I/O Per Second

This metric shows the Volumes I/O performance per second in terms of total I/O requests for all the Volumes, which are part of the cluster.

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Metric Summary for Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average I/Os per second for each volume, the total number of I/O responses is divided by the total I/O time during the collection interval. The data is aggregated for all instances that are part of the cluster

User Action

No user action is required.

1.9.2 I/O Size (MB)

This metric shows the volume I/O size of volumes present in a cluster. The data is aggregated for all instances that are part of the cluster.

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Metric Summary for Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average I/O size of each volume, the total number of bytes read and written is divided by the total number of I/Os during the collection interval. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.9.3 I/O Throughput

This metric shows the I/O throughput detail of a volume in a cluster. The data is aggregated for all instances that are part of the cluster. This gives an indication of the volume I/O performance in terms of reads and writes.

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Metric Summary for Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average throughput of each volume, the total number of bytes read and written is divided by the total I/O time during the collection interval. The data is aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.9.4 Read Response Time (MS)

This metric shows the read response time detail of volumes present in a cluster. This gives an indication of a volume response time in terms of total read requests for volumes in a cluster.

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Metric Summary for Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average I/O response time for each volume, the total I/O time is divided by the total number of I/O responses during the collection interval. The data is then aggregated for all instances that are part of the cluster

User Action

No user action is required.

1.9.5 Read Size (MB)

This metric shows the read size in megabytes of volumes present in a cluster. The data is aggregated for all volumes that are part of the cluster.

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Metric Summary for Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average read size of each volume, the total number of bytes read is divided by the total number of reads during the collection interval. The data is aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.9.6 Read Throughput

This metric shows the read throughput detail of volumes present in a cluster. This gives an indication of the total number of bytes read from the volume with proportion to the total read time for read requests for this volume.

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Metric Summary for Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average read throughput of each volume, the total number of bytes read is divided by the total read time during the collection interval. The data is then aggregated for all instances that are part of the cluster

User Action

No user action is required.

1.9.7 Read Write Errors

This metric shows the detail of the total number of failed reads and writes of volumes present in a cluster. This gives an indication of the total number of failed attempts of reads and writes for the volume.

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Metric Summary for Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average read response time for each volume, the total read time is divided by the total number of read responses during the collection interval. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.9.8 Reads Per Second

This metric shows the reads per second detail of volumes present in a cluster.

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Metric Summary for Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average reads per second for each volume, the total number of read responses is divided by the total read time during the collection interval. The data is then aggregated for all instances that are part of the cluster

User Action

No user action is required.

1.9.9 Response Time (MS)

This metric displays the I/O response time details of volumes present in a cluster. This provides an indication of the volume response time in terms of total I/O requests for this volume.

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Metric Summary for Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric, which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average I/O response time for each volume, the total I/O time is divided by the total number of I/O responses during the collection interval. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.9.10 Write Response Time (MS)

This metric shows the write response time detail of volumes present in a cluster. This gives an indication for the volume response time in terms of total write requests for the volume in a cluster.

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Metric Summary for Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average write response time for each volume, the total write time is divided by the total number of write responses during the collection interval. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.9.11 Write Size (MB)

This metric shows the sum of all volume writes for all volumes which are part of the cluster. The data is aggregated for all instances.

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Metric Summary for Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average write size of each volume, the total number of bytes written is divided by the total number of writes during the collection interval. The data is then aggregated for all instances that are part of the cluster

User Action

No user action is required.

1.9.12 Write Throughput

This metric shows the write throughput detail of volumes present in a cluster. This gives an indication for the total number of bytes written to a volume with proportion to the total write time for write requests for the volume in a cluster.

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Metric Summary for Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average write throughput of each volume, the total number of bytes written is divided by the total write time during the collection interval. The data is then aggregated for all instances that are part of the cluster.

User Action

No user action is required.

1.9.13 Writes Per Second

This metric shows the detail of total write requests per second for volumes in the cluster.

Metric Summary for Database Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every Hour

Metric Summary for Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average writes per second for each volume, the total number of write responses is divided by the total write time during the collection interval. The data is aggregated for all instances that are part of the cluster

User Action

No user action is required.

1.10 Database Disk Group Usage Metric

The Database Disk Group Usage metric show the detail of the disk group space used by a database. With the help of this metric, you can know the space used in a disk group by different database instances.

1.10.1 Total Bytes

This metric shows the total bytes of the disk group space used by a database. With the help of this metric one can know the space used in a disk group by different database instance.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes

Data Source

We get the space used by a file using the V$OSM_FILE view and then it is joined with the V$ASM_ALIAS and V$ASM_DISKGROUP views for 10g Release 1 and the V$ASM_ALIAS, V$ASM_DISKGROUP_STAT views for 10g Release 2 to get the disk group space used by a database instance

User Action

No user action is required.

1.11 Disk Group Imbalance Status Metrics

The Disk Group Imbalance Status metrics check if any disk groups are out of balance. Under normal operations, ASM automatically rebalances disk groups. These metrics detect conditions where manual rebalances may be required or the power level of a rebalance in progress may need to be raised to give it the necessary resources to complete faster.

1.11.1 Actual Imbalance (%)

Actual Imbalance (%) measures the difference in space allocated to the fullest and emptiest disks in the disk group. Comparison is in percent full since ASM tries to keep all disks equally full as a percent of their size. The imbalance is relative to the space allocated not the space available. An imbalance of a couple percent is reasonable.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.2.0.x; 11.1.0.x; 11 2.0.x	Every 15 Minutes

Data Source

Actual Imbalance (%) is calculated as:

100 * (max((total_mb - free_mb) / total_mb) - min((total_mb - free_mb)
/ total_mb)) / max((total_mb - free_mb) / total_mb)
where total_mb and free_mb are columns in V$ASM_DISK_STAT

User Action

An imbalance of more than a couple percent may signal the need to initiate a manual rebalance of the disk group.

1.11.2 Actual Minimum Percent Free

Actual Minimum Percent Free lists the amount of free disk space on the fullest disk as a percentage of the disk size. If the imbalance is zero, then this represents the total free space. Since all allocations are done evenly across all disks, the minimum free space limits how much space can be used.

If one disk has only one percent free, then only one percent of the space in the disk group is really available for allocation, even if the rest of the disks are only half full

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.2.0.x; 11.1.0.x; 11 2.0.x	Every 15 Minutes

Data Source

Actual Minimum Percent Free is calculated as 100 * (min(free_mb / total_mb)), where free_mb and total_mb are columns in V$ASM_DISK_STAT.

User Action

If the actual minimum percent free is a low number, a configuration change may be required in order to provide an even distribution of file extents and space usage across all disks in a disk group.

1.11.3 Disk Count

Disk count is the number of disks in the disk group which gives a sense of how widely files can be spread.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.2.0.x; 11.1.0.x; 11 2.0.x	Every 15 Minutes

Data Source

Disk Count is calculated using count(*) on all disks (V$ASM_DISK_STAT) in a disk group (V$ASM_DISKGROUP_STAT).

User Action

No user action is required.

1.11.4 Disk Group Imbalance (%) without Rebalance

Disk Group Imbalance (%) without Rebalance is used to determine if a disk group requires rebalance. Temporary imbalances (caused by a rebalance in progress) are ignored.

Metric Summary for Database Control and Grid 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.

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.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes	After Every Sample	>	10	Not Defined	1	Disk Group %diskGroup% requires rebalance because the space usage imbalance between disks is high.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Disk Group" object.

If warning or critical threshold values are currently set for any "Disk Group" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Disk Group" object, use the Edit Thresholds page.

Data Source

Disk Group Imbalance (%) without Rebalance is the same value as Actual Imbalance (%) if a rebalance operation is not in progress, 0 otherwise.

User Action

A warning alert will be generated if Disk Group Imbalance (%) without Rebalance is greater than or equal to 10%. In this case, a rebalance is necessary because the space usage imbalance between disks is high. The user should manually initiate a rebalance operation.

1.11.5 Disk Maximum Used (%) with Rebalance

Disk Maximum Used (%) with Rebalance is used to determine if a rebalance in progress needs a power boost to complete in a timely manner and prevent other errors from occurring due to space constraints.

Metric Summary for Database Control and Grid 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.

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.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes	After Every Sample	>	Not Defined	95	1	Increase the rebalance power for Disk Group %diskGroup% because at least one disk is critically low on space.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Disk Group" object.

If warning or critical threshold values are currently set for any "Disk Group" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Disk Group" object, use the Edit Thresholds page.

Data Source

If a rebalance is in progress and the power value is greater than 0, then Disk Maximum Used (%) with Rebalance is calculated as (100 - Actual Minimum Percent Free), 0 otherwise.

User Action

A critical alert will be generated if Disk Maximum Used (%) with Rebalance is greater than or equal to 95%. In this case the rebalance power for the disk group must be increased because at least one disk is critically low on space. Increase the rebalance power (maximum power level is 11).

1.11.6 Disk Minimum Free (%) without Rebalance

Disk Minimum Free (%) without Rebalance is used to determine if a disk group requires rebalance. Temporary imbalances (caused by a rebalance in progress) are ignored.

Metric Summary for Database Control and Grid 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.

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.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes	After Every Sample	<	20	10	1	Disk Group %diskGroup% requires rebalance because at least one disk is low on space.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Disk Group" object.

If warning or critical threshold values are currently set for any "Disk Group" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Disk Group" object, use the Edit Thresholds page.

Data Source

Disk Minimum Free (%) without Rebalance is the same value as Actual Minimum Percent Free if a rebalance operation is not in progress, 100 otherwise.

User Action

A warning alert will be generated if Disk Minimum Free (%) without Rebalance is less than or equal to 20%. In this case a rebalance is necessary because at least one disk is low on space. The user should manually initiate a rebalance operation.

1.11.7 Disk Size Variance (%)

Disk Size Variance (%) lists the percentage difference in size between the largest and smallest disks in the disk group. This will be zero if best practices have been followed and all disks are the same size.

Small differences in size are acceptable. Large differences can result in some disks getting much more I/O than others. With normal or high redundancy disk groups, a large size variance can make it impossible to reduce the percent imbalance to a small value.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.2.0.x; 11.1.0.x; 11 2.0.x	Every 15 Minutes

Data Source

Disk Size Variance (%) is calculated as 100 * 
(max(total_mb) - min(total_mb)) / max(total_mb), 
where total_mb is a column in V$ASM_DISK_STAT

User Action

A large size variance may require a configuration change to provide an even distribution of file extents and space usage across all disks in a disk group.

1.11.8 Rebalance In Progress

Rebalance In Progress returns "Yes" if a rebalance operation is in progress, "No" otherwise.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.2.0.x; 11.1.0.x; 11 2.0.x	Every 15 Minutes

Data Source

Rebalance In Progress is retrieved from the operation column of V$ASM_OPERATION.

User Action

No user action is required.

1.12 Disk Group Usage Metrics

The Disk Group Usage metrics show the space used by all the disk groups having the state as 'MOUNTED'. These metrics are used to collect information about the disk usage and is used to show the trend of disk group space usage in the application. This information is used to determine the following metrics: Free MB, Total MB, Total Safely Usable MB, Type, Safely Usable File MB, Used %, and Used % of Safely Usable of a disk group for 10g Release 2 and Free MB, Total MB, Type, and Used % for 10g Release 1.

These metrics generate a warning alert if the disk group is 75% used and a critical warning if 90% used. The thresholds for the Disk Group Usage alert should not be fixed at 75% and 90%, since the value depends on the redundancy. In version 10g Release 2, these metrics use the USABLE_FILE_MB column of the V$ASM_DISKGROUP_STAT view to indicate usable mirrored free space. This column displays the amount of free space that can be safely utilized taking mirroring into account, and yet is able to restore redundancy after disk failure.

Enterprise Manager issues alerts for the following:

Critical alert when USABLE_FILE_MB <= 0
Warning alert when USABLE_FILE_MB < 0.1 * REQUIRED_MIRROR_FREE_MB

This metric is collected at a time interval of 15 minutes. You can change the threshold limit as required.

This metric is collected with the help of a SQL query which queries the V$ASM_DISKGROUP view for 10g Release 1 and the V$ASM_DISKGROUP_STAT view for 10g Release 2.

1.12.1 Disk Group Free (MB)

This metric shows the unused capacity of the disk group in megabytes. It gives an indication of the free space available in a disk group.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes	After Every Sample	<=	Not Defined	Not Defined	1	Total free size for Disk Group %dg_name% has fallen to %value% (MB).

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Disk Group Name" object.

If warning or critical threshold values are currently set for any "Disk Group Name" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Disk Group Name" object, use the Edit Thresholds page.

Data Source

This metric is collected from the column FREE_MB in the view V$ASM_DISKGROUP for 10g Release 1 and the V$ASM_DISKGROUP_STAT view for 10g Release 2.

User Action

Consider adding more disks to the disk group or deleting existing files in the disk group.

1.12.2 Disk Group Usable (Free MB)

The usable free space of a disk group depends on the redundancy, so in 10g Release 2 it uses the USABLE_FILE_MB column of the V$ASM_DISKGROUP_STAT view to indicate usable mirrored free space. This column indicates the amount of free space that can be "safely" utilized taking mirroring into account, and yet is able to restore redundancy after disk failure. This column is used to determine the usable free megabytes of a disk group.

Metric Summary for Database Control and Grid 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.

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.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes	After Every Sample	<=	Not Defined	Not Defined	1	Usable free size for Disk Group %dg_name% has fallen to %value% (MB).

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Disk Group Name" object.

If warning or critical threshold values are currently set for any "Disk Group Name" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Disk Group Name" object, use the Edit Thresholds page.

Data Source

This metric is collected from the column USABLE_FILE_MB in the V$ASM_DISKGROUP_STAT view for 10g Release 2.

User Action

Consider adding more disks to the disk group or removing existing files from the disk group.

1.12.3 Disk Group Usable (MB)

This metric shows the capacity of the disk group based on the type of the disk group. This column indicates the amount of free space that can be "safely" utilized taking mirroring into account, and yet is able to restore redundancy after disk failure.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes

Data Source

This metric is collected using the V$ASM_DISKGROUP_STAT view.

Total Safely Usable MB = (total_mb - required_mirror_free_mb)/redundancy_factor

Where total_mb and required_mirror_free_mb come from the view column, and redundancy factor is 1 for External Redundancy Disk Group, 2 for Normal Redundancy Disk Group, and 3 for High Redundancy Disk Group.

User Action

Consider adding more disks to the disk group or removing existing files from the disk group

1.12.4 Disk Group Used %

This metric shows the percentage of space used by a disk group. It generates a warning alert if the disk group is 75% used and a critical warning if 90 % used. The threshold limit can be changed to generate alerts at different values.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes	After Every Sample	>	75	90	1	Disk Group %dg_name% is %value%%% used.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Disk Group Name" object.

If warning or critical threshold values are currently set for any "Disk Group Name" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Disk Group Name" object, use the Edit Thresholds page.

Data Source

This metric is collected from the V$ASM_DISKGROUP view for 10g Release 1 and the V$ASM_DISKGROUP_STAT view for 10g Release 2.

Used % = (total_mb-free_mb)/total_mb)*100

User Action

New disks can be added in a disk group to avoid the alerts. Go to the Disk Group general page and click Add to add a new disk to a disk group. Also, you can remove existing files from the disk group.

1.12.5 Redundancy

This metric shows the Redundancy Type of the disk group. It can be one of the three values: External, Normal, and High. This property determines the restore redundancy after disk failure.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes

Data Source

This metric is collected from the column TYPE in the V$ASM_DISKGROUP view for 10g Release 1 and the V$ASM_DISKGROUP_STAT view for 10g Release 2.

User Action

No user action is required.

1.12.6 Size (MB)

This metric shows the total capacity of the disk group in megabytes. It gives an indication of the size or the space used by the disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes

Data Source

This metric is collected from the column TOTAL_MB in the V$ASM_DISKGROUP view for 10g Release 1 and the V$ASM_DISKGROUP_STAT view for 10g Release 2.

User Action

Consider adding more disks to the disk group.

1.12.7 Used % of Safely Usable

This metric shows the percentage of safely usable space used by a disk group. Usable free space of a disk group depends on the redundancy. In 10g Release 2, it uses the USABLE_FILE_MB column of the V$ASM_DISKGROUP_STAT view to indicate usable mirrored free space. This column displays the amount of free space that can be safely utilized taking mirroring into account and restores redundancy after disk failure. This column is used to determine the "Used % of Safely Usable" for a disk group.

This metric generates a warning alert if the disk group is using 90% of the safely usable space and critical warning for 100%. The threshold limit can be changed to generate an alert at different values.

Metric Summary for Database Control and Grid 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.

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.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes	After Every Sample	>	75	90	1	Disk group %dg_name% has used %value%%% of safely usable free space (space that can be allocated while still having enough space to recover from failure group failures).

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Disk Group Name" object.

If warning or critical threshold values are currently set for any "Disk Group Name" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Disk Group Name" object, use the Edit Thresholds page.

Data Source

This metric is collected from the V$ASM_DISKGROUP_STAT view for 10g Release 2.

Used % of Safely Usable = 100 - (usable_file_mb/usable_total_mb)*100 
 
Where usable_total_mb = total_mb - required_mirror_free_mb)/redundancy_factor

total_mb and required_mirror_free_mb are derived from the view column and redundancy factor is 1 for External Redundancy Disk Group, 2 for Normal Redundancy Disk Group, and 3 for High Redundancy Disk Group.

User Action

New disks can be added in a disk group to avoid the alerts. Go to the Disk Group general page and click Add to add a new disk to a disk group. Also, you can remove existing files from the disk group.

1.13 Disk Path Metrics

The Disk Path metrics show the disk name and disk path of all the disks. This information is collected at a time interval of 12 Hours.

These metrics are collected with the help of the V$ASM_DISK view for 10g Release 1 and the V$ASM_DISK_STAT view for 10g Release 2.

1.13.1 Disk Name

This metric is the name of the disk.

This metric is available in Database Control and Grid Control; in target versions 10.2.0.x, 11.1.0.x, and 11 2.0.x.

Data Source

Name column value in the V$ASM_DISK_STAT and V$ASM_DISK views

User Action

No user action is required.

1.13.2 Disk Path

This metric is the physical path of the disk

This metric is available in Database Control and Grid Control; in target versions 10.2.0.x, 11.1.0.x, and 11 2.0.x.

Data Source

Path column value. For databases prior to 10g Release 2, this metric uses the GV$ASM_DISK view. For databases 10g Release 2 and higher, this metric uses the GV$ASM_DISK_STAT view.

User Action

No user action is required.

1.13.3 Group Name

This metric provides the name of the group.

This metric is available in Database Control and Grid Contro; in target versions 10.2.0.x, 11.1.0.x, and 11 2.0.x.

Data Source

Path column value. For databases prior to 10g Release 2, this metric uses the GV$ASM_DISK view. For databases 10g Release 2 and higher, this metric uses the GV$ASM_DISK_STAT view.

User Action

No user action is required.

1.14 Disk Status Metric

The Disk Status metric provides disk mode status (offline and online). A critical warning alert is generated if any of the disks are offline.

This metric is collected at a time interval of 15 minutes. You can change the time limit and threshold limit as required.

1.14.1 Disk Mode Status

This metric displays disk mode status (offline and online). A critical warning alert is generated if any of the disks go offline.

You can change the threshold limit.

Metric Summary for Database Control and Grid 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.

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 15 Minutes	After Every Sample	=	Not Defined	OFFLINE	1	Disk %dg_name%.%disk_name% is offline.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Disk Group Name" and "Disk Name" objects.

If warning or critical threshold values are currently set for any unique combination of "Disk Group Name" and "Disk Name" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Disk Group Name" and "Disk Name" objects, use the Edit Thresholds page.

Data Source

This metric is collected with the help view column mode status from GV$ASM_DISK for 10gRelease 1 and GV$ASM_DISK_STAT for 10g Release 2.

User Action

Try to bring the disk online. Currently Enterprise Manager does not support this feature

1.15 Failure Group Imbalance Status Metrics

The Failure Group Imbalance Status metrics check how even failure group disks are laid out for ASM disk groups. ASM strives for an even distribution of file extents and space usage across all disks in a disk group. It accomplishes this through rebalancing. If the disks are different sizes or the failure groups are different sizes then effective rebalancing cannot be achieved. In this situation, configuration changes are required.

These metrics only apply to disk groups with normal or high redundancy. These metrics will not return data for disk groups with external redundancy, since failure groups are not used in this configuration.

1.15.1 Disk Count Imbalance Variance

Failure groups are used to store mirror copies of data, two copies for normal redundancy, three copies for high redundancy. Disk Count Imbalance Variance gives the difference in the failure group disk count for the disk in the disk group with the highest failure group disk count and the disk with the lowest.

It may not be possible for every disk to have the same failure group disk count even when all the failure groups are the same size. However an imbalance of more than one indicates that the failure groups are different sizes.

Metric Summary for Database Control and Grid 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.

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.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes	After Every Sample	>=	2	Not Defined	1	Disk Group %diskGroup% has failure groups with different numbers of disks which may lead to suboptimal space usage. Changing the configuration may alleviate this problem.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Disk Group" object.

If warning or critical threshold values are currently set for any "Disk Group" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Disk Group" object, use the Edit Thresholds page.

Data Source

Disk Count Imbalance Variance is calculated using the V$ASM_DISKGROUP_STAT and V$ASM_DISK_STAT views, along with some internal ASM fixed tables.

User Action

A warning alert will be generated when the Disk Count Imbalance Variance is greater than 1 (by default). Disk groups that have failure groups with different numbers of disks may lead to suboptimal space usage. To alleviate this problem, try changing the configuration.

1.15.2 Disk Size Imbalance (%)

Disk Size Imbalance (%) checks if some disks have more space in their failure group disks than others. The space is calculated as a ratio between the size of a disk and the sum of the sizes of its active failure group disks. This ratio is compared for all the disks. The difference in the highest and lowest failure group disk space is reported as a percentage. An imbalance of 10% is acceptable.

Metric Summary for Database Control and Grid 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.

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.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes	After Every Sample	>	10	Not Defined	1	Disk Group %diskGroup% has failure groups with disks of different sizes which may lead to suboptimal space usage. Changing the configuration may alleviate this problem.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each "Disk Group" object.

If warning or critical threshold values are currently set for any "Disk Group" object, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each "Disk Group" object, use the Edit Thresholds page.

Data Source

Disk Size Imbalance is calculated using the V$ASM_DISKGROUP_STAT and V$ASM_DISK_STAT views, along with some internal ASM fixed tables.

User Action

A warning alert will be generated when the Disk Size Imbalance (%) is greater than 10% (by default). Disk groups that have failure groups with disks of different sizes may lead to suboptimal space usage. To alleviate this problem, try changing the configuration.

1.15.3 Failure Group Count

Failure Group Count reports the number of failure groups per disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes

Data Source

Failure Group Count is retrieved from a calculation involving the V$ASM_DISKGROUP_STAT and V$ASM_DISK_STAT views, and some internal ASM fixed tables.

User Action

No user action is required.

1.16 Failure Group Status Metrics

The Failure Group Status metrics check to see if all the member disks of any failure group are offline. This is an undesirable condition which risks data loss, since mirror copies of data cannot be stored.

These metrics only apply to disk groups with normal or high redundancy.

1.16.1 Available Disks

Available Disks reports the number of disks in the failure group that are online.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes

Data Source

Available Disks is calculated by subtracting the number of offline disks in the failure group from the number of total disks.

User Action

No user action is required.

1.16.2 Disk Count for Alerts

Disk Count for Alerts will have the same value as Available Disks if there is more than one disk in the failure group. If there is exactly one disk in the failure group, Disk Count for Alerts will be 1, regardless if that one disk is offline. The reason for this is to avoid duplicate alerts being generated for the same root cause. The disk_status metric will generate a critical alert when a disk goes offline.

Metric Summary for Database Control and Grid 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.

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.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes	After Every Sample	=	Not Defined	0	1	Failure Group %diskGroup%.%failureGroup% is offline.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Disk Group" and "Failure Group" objects.

If warning or critical threshold values are currently set for any unique combination of "Disk Group" and "Failure Group" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Disk Group" and "Failure Group" objects, use the Edit Thresholds page.

Data Source

Disk Count for Alerts is set to 1 if there is only one disk in the disk group, otherwise it is set to the value of Available Disks.

User Action

A critical alert will be generated if all disks comprising a failure group are taken offline. In this situation, data is not being mirrored, despite the disk group having been configured with normal or high redundancy. Action must be taken to bring some of the disks in the failure group back online, or to add more disks to the disk group and assign them to that failure group.

1.16.3 Total Disks

Total Disks reports the number of disks in the failure group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes

Data Source

Total Disks is retrieved from the V$ASM_DISKGROUP_STAT and V$ASM_DISK_STAT views.

User Action

No user action is required.

1.17 Incident Metrics

The Incident metrics represent incidents, for example, generic internal error, access violation, and so on as recorded in the ASM alert log file. The alert log file has a chronological log of messages and errors.

Each metric signifies that the ASM being monitored has detected a critical error condition about the ASM and has generated an incident to the alert log file since the last sample time. The Support Workbench in Enterprise Manager contains more information about each generated incident.

1.17.1 Access Violation

This metric signifies that the ASM has generated an incident due to some memory access violation. This type of incident is typically related to Oracle Exception messages such as ORA-3113 and ORA-7445. The ASM can also generate this type of incident when it detects a SIGSEGV or SIGBUS signals.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x 11.2.0.x	Every 5 Minutes	After Every Sample	MATCH	Not Defined	.^Foot 1	1^Foot 2	An access violation detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1Once an alert is triggered for this metric, it must be manually cleared.

^Footnote 2Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

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, those 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.

Data Source

The data comes from the alert log files. It is collected using the Perl script $ORACLE_HOME/sysman/admin/scripts/alertlogAdr.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incident.

1.17.2 Alert Log Error Trace File

This metric is the name of the trace file (if any) associated with the logged incident.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.1.0.x; 11.2.0.x	Every 5 Minutes

Data Source

The data comes from the alert log files. It is collected using the Perl script $ORACLE_HOME/sysman/admin/scripts/alertlogAdr.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

No user action is required.

1.17.3 Alert Log Name

This metric is the name of the alert log file.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.1.0.x; 11.2.0.x	Every 5 Minutes

Data Source

The data comes from the alert log files. It is collected using the Perl script: $ORACLE_HOME/sysman/admin/scripts/alertlogAdr.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

No user action is required.

1.17.4 ASM Block Corruption

ASM Block corruption can happen due to many reasons over lifetime (for example head misalignment, dust spec, and so on). If the disk groups are mirrored, ASM automatically repairs the corrupted blocks from the mirror.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x 11.2.0.x	Every 5 Minutes	After Every Sample	MATCH	Not Defined	.^Foot 1	1^Foot 2	An ASM data block was corrupted at time/line number: %timeLine%.

^Footnote 1Once an alert is triggered for this metric, it must be manually cleared.

^Footnote 2Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

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, those 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.

Data Source

Incident metric

User Action

User can execute check and remap commands which have been implemented in Enterprise Manager.

Check

This checks the consistency of disk group metadata and logs the result in alert log and may repair depending upon repair/norepair option provided. In case of corruptions, the result would look like: "cache read a corrupted block group=NORM3 fn=1 blk=0 from disk 0" and so on.
Remap

This repairs a range of physical blocks that maps to a valid ASM file.

In addition, you can use Support Workbench in Enterprise Manager to examine the details of the incidents.

1.17.5 Cluster Error

This metric signifies that the ASM has generated an incident due to a member evicted from the group by a member of the cluster database. This type of incident is typically related to Oracle Exception message ORA-29740.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x 11.2.0.x	Every 5 Minutes	After Every Sample	MATCH	Not Defined	.^Foot 1	1^Foot 2	A cluster error detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1Once an alert is triggered for this metric, it must be manually cleared.

^Footnote 2Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

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, those 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.

Data Source

The data comes from the alert log files. It is collected using the Perl script $ORACLE_HOME/sysman/admin/scripts/alertlogAdr.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incident.

1.17.6 Deadlock

This metric signifies that the ASM has generated an incident due to a deadlock detected while trying to lock a library object. This type of incident is typically related to Oracle Exception message ORA-4020.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x 11.2.0.x	Every 5 Minutes	After Every Sample	MATCH	Not Defined	.^Foot 1	1^Foot 2	A deadlock error detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1Once an alert is triggered for this metric, it must be manually cleared.

^Footnote 2Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

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, those 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.

Data Source

The data comes from the alert log files. It is collected using the Perl script $ORACLE_HOME/sysman/admin/scripts/alertlogAdr.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incident.

1.17.7 File Access Error

This metric signifies that the ASM has generated an incident due to failure to read a file at the time. This type of incident is typically related to Oracle Exception message ORA-376.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x 11.2.0.x	Every 5 Minutes	After Every Sample	MATCH	Not Defined	.^Foot 1	1^Foot 2	A file access error detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1Once an alert is triggered for this metric, it must be manually cleared.

^Footnote 2Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

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, those 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.

Data Source

The data comes from the alert log files. It is collected using the Perl script $ORACLE_HOME/sysman/admin/scripts/alertlogAdr.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incident.

1.17.8 Generic Incident

This metric signifies that the ASM has generated an incident due to some error.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x 11.2.0.x	Every 5 Minutes	After Every Sample	MATCH	Not Defined	.^Foot 1	1^Foot 2	Incident (%errCodes%) detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1Once an alert is triggered for this metric, it must be manually cleared.

^Footnote 2Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

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, those 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.

Data Source

The data comes from the alert log files. It is collected using the perl script $ORACLE_HOME/sysman/admin/scripts/alertlogAdr.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incident.

1.17.9 Generic Internal Error

This metric signifies that the ASM has generated an incident due to an internal ASM error. This type of incident is typically related to Oracle Exception message ORA-600 or ORA-0060*.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x 11.2.0.x	Every 5 Minutes	After Every Sample	MATCH	Not Defined	.^Foot 1	1^Foot 2	Internal error (%errCodes%) detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1Once an alert is triggered for this metric, it must be manually cleared.

^Footnote 2Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

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, those 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.

Data Source

The data comes from the alert log files. It is collected using the perl script $ORACLE_HOME/sysman/admin/scripts/alertlogAdr.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incident.

1.17.10 Impact

This metric is the impact of an incident. For a Generic Internal Error incident, the impact describes how the incident may affect the ASM.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.1.0.x; 11.2.0.x	Every 5 Minutes

Data Source

The data comes from the alert log files. It is collected using the Perl script $ORACLE_HOME/sysman/admin/scripts/alertlogAdr.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

No user action is required.

1.17.11 Incident ID

This metric is a number identifying an incident. The Support Workbench in Enterprise Manager uses this ID to specify an incident.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.1.0.x; 11.2.0.x	Every 5 Minutes

Data Source

The data comes from the alert log files. It is collected using the Perl script $ORACLE_HOME/sysman/admin/scripts/alertlogAdr.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

No user action is required.

1.17.12 Internal SQL Error

This metric signifies that the ASM has generated an incident due to an internal SQL error. This type of incident is typically related to Oracle Exception message ORA-604.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x 11.2.0.x	Every 5 Minutes	After Every Sample	MATCH	Not Defined	.^Foot 1	1^Foot 2	An internal SQL error detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1Once an alert is triggered for this metric, it must be manually cleared.

^Footnote 2Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

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, those 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.

Data Source

The data comes from the alert log files. It is collected using the Perl script $ORACLE_HOME/sysman/admin/scripts/alertlogAdr.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incident.

1.17.13 Out of Memory

This metric signifies that the ASM has generated an incident due to failure to allocate memory. This type of incident is typically related to Oracle Exception message ORA-4030 or ORA-4031.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x 11.2.0.x	Every 5 Minutes	After Every Sample	MATCH	Not Defined	.^Foot 1	1^Foot 2	Out of memory detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1Once an alert is triggered for this metric, it must be manually cleared.

^Footnote 2Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

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, those 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.

Data Source

The data comes from the alert log files. It is collected using the Perl script $ORACLE_HOME/sysman/admin/scripts/alertlogAdr.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incident.

1.17.14 Redo Log Corruption

This metric signifies that the ASM has generated an incident due to an error with the redo log. This type of incident is typically related to Oracle Exception message ORA-353, ORA-355, or ORA-356.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x 11.2.0.x	Every 5 Minutes	After Every Sample	MATCH	Not Defined	.^Foot 1	1^Foot 2	A data block was corrupted at time/line number: %timeLine%.

^Footnote 1Once an alert is triggered for this metric, it must be manually cleared.

^Footnote 2Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

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, those 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.

Data Source

The data comes from the alert log files. It is collected using the Perl script $ORACLE_HOME/sysman/admin/scripts/alertlogAdr.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incident.

1.17.15 Session Terminated

This metric contains the information about different ORA- errors, which indicate the presence of Session Terminated problems in the alert log files. The ORA- 00603 error in the alert log indicates Session Terminated problems. This also generates a warning alert when these problems are found in alert logs.

You can edit the metric threshold and change the value of the error you want to collect under a different head. Also, the warning and critical alert values can be modified or set.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x 11.2.0.x	Every 5 Minutes	After Every Sample	MATCH	Not Defined	.^Foot 1	1^Foot 2	A session termination detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1Once an alert is triggered for this metric, it must be manually cleared.

^Footnote 2Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

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, those 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.

Data Source

The data comes from the alert log files. It is collected using the Perl script $ORACLE_HOME/sysman/admin/scripts/alertlogAdr.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent. The alert log file is scanned for the ORA- 00603 error.

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incident.

1.18 Incident Status Metrics

The Incident Status metrics represent whether the last scan of the alert log identified each type of incident and, if so, how many.

1.18.1 Access Violation Status

This metric reflects the number of Access Violation incidents witnessed the last time Enterprise Manager scanned the alert log.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x; 11.2.0.x	Every 5 Minutes	After Every Sample	>	Not Defined	0	1	Access violation errors have been found in the alert log.

Data Source

Incident metric

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incidents.

1.18.2 ASM Block Corruption Error Status

This metric reflects the number of ASM Block Corruption incidents witnessed the last time Enterprise Manager scanned the alert log

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x; 11.2.0.x	Every 5 Minutes	After Every Sample	>	Not Defined	0	1	ASM data block corruption errors have been found in the alert log.

Data Source

Incident metric

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incidents.

1.18.3 Cluster Error Status

This metric reflects the number of Cluster Error incidents witnessed the last time Enterprise Manager scanned the alert log.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x; 11.2.0.x	Every 5 Minutes	After Every Sample	>	Not Defined	0	1	Cluster errors have been found in the alert log.

Data Source

Incident metric

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incidents.

1.18.4 Deadlock Error Status

This metric reflects the number of Deadlock incidents witnessed the last time Enterprise Manager scanned the alert log.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x; 11.2.0.x	Every 5 Minutes	After Every Sample	>	Not Defined	0	1	Deadlock errors have been found in the alert log.

Data Source

Incident metric

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incidents.

1.18.5 File Access Error Status

This metric reflects the number of File Access Error incidents witnessed the last time Enterprise Manager scanned the alert log.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x; 11.2.0.x	Every 5 Minutes	After Every Sample	>	Not Defined	0	1	File access errors have been found in the alert log.

Data Source

Incident metric

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incidents.

1.18.6 Generic Incident Status

This metric reflects the number of Generic Incident incidents witnessed the last time Enterprise Manager scanned the alert log.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x; 11.2.0.x	Every 5 Minutes	After Every Sample	>	Not Defined	0	1	%value% distinct types of incidents have been found in the alert log.

Data Source

Incident metric

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incidents.

1.18.7 Generic Internal Error Status

This metric reflects the number of Generic Internal Error incidents witnessed the last time Enterprise Manager scanned the alert log.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x; 11.2.0.x	Every 5 Minutes	After Every Sample	>	Not Defined	0	1	Generic internal errors have been found in the alert log.

Data Source

Incident metric

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incidents.

1.18.8 Internal SQL Error Status

This metric reflects the number of Internal SQL Error incidents witnessed the last time Enterprise Manager scanned the alert log.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x; 11.2.0.x	Every 5 Minutes	After Every Sample	>	Not Defined	0	1	Internal SQL errors have been found in the alert log.

Data Source

Incident metric

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incidents.

1.18.9 Out of Memory Status

This metric reflects the number of Out of Memory incidents witnessed the last time Enterprise Manager scanned the alert log.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x; 11.2.0.x	Every 5 Minutes	After Every Sample	>	Not Defined	0	1	Out of memory errors have been found in the alert log.

Data Source

Incident metric

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incidents.

1.18.10 Redo Log Corruption Error Status

This metric reflects the number of Redo Log Corruption incidents witnessed the last time Enterprise Manager scanned the alert log.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x; 11.2.0.x	Every 5 Minutes	After Every Sample	>	Not Defined	0	1	Redo log corruption errors have been found in the alert log.

Data Source

Incident metric

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incidents.

1.18.11 Session Terminated Status

This metric reflects the number of Session Terminated incidents witnessed the last time Enterprise Manager scanned the alert log.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x; 11.2.0.x	Every 5 Minutes	After Every Sample	>	Not Defined	0	1	Session terminations have been found in the alert log.

Data Source

Incident metric

User Action

Use Support Workbench in Enterprise Manager to examine the details of the incidents.

1.19 Instance Disk Group Performance Metrics

The Instance Disk Group Performance metrics indicate the performance of the disk groups present in an Automatic Storage Management (ASM) instance. These metrics show the disk group performance parameters for all the disk groups mounted on an ASM Instance.

These metrics are used to collect information, for example, total I/O and read/write requests, total I/O and read/write time, and the total number of bytes read/written to the disk group. These metrics also show the response of the disk group for read, write, and I/O throughput.

1.19.1 I/O per Second

This metric shows the sum of disks I/O performance per second in terms of total I/O requests for all the disks within the disk group. The data is displayed for all instances that are part of the cluster.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average I/Os per second for each disk, the total number of I/O responses is divided by the total I/O time during the collection interval. This data is aggregated by the disk group name to get the average I/O operations per second of a disk group. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.19.2 I/O Size (MB)

This metric shows the sum of all disk I/O for all disks within the disk group. The data is not aggregated for all instances.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average I/O size of each disk, the total number of bytes read and written is divided by the total number of I/Os during the collection interval. This data is aggregated by the disk group name to get the average I/O size of a disk group. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.19.3 I/O Throughput

This metric shows the sum of I/O throughput for all disks within the disk group. The data is aggregated for all instances that are part of the cluster. This gives an indication of the disk group I/O performance in terms of read and write.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average throughput of each disk, the total number of bytes read and written is divided by the total I/O time during the collection interval. This data is aggregated by the disk group name to get the average I/O throughput of a disk group. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.19.4 Read Response Time (MS)

This metric shows the read response time detail for a disk group in an Automatic Storage Management (ASM) instance. This gives an indication for the disk group response time in terms of read requests for the disks included in the disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average read response time for each disk, the total read time is divided by the total number of read responses during the collection interval. This data is aggregated by the disk group name to get the average read response time of a disk group. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.19.5 Read Size (MB)

This metric shows the sum of all disk reads for all disks within the disk group which are part of the cluster. The data is not aggregated for all instances.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average read size of each disk, the total number of bytes read are divided by the total number of reads during the collection interval. This data is aggregated by the disk group name to get the average read size of a disk group. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.19.6 Read Throughput

This metric shows the read throughput detail of a disk group mounted in an Automatic Storage Management (ASM) instance. This gives an indication for the total number of bytes read from the disk group with proportion to the total read time for this disk group in an instance.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average read throughput of each disk, the total number of bytes read is divided by the total read time during the collection interval. This data is aggregated by the disk group name to get the average read throughput of a disk group. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.19.7 Reads per Second

This metric shows the detail of total read requests per second for a disk group in an Automatic Storage Management (ASM) instance. This metric shows the read performance of all the disks included in the disk group of an instance.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average reads per second for each disk, the total number of read responses is divided by the total read time during the collection interval. This data is aggregated by the disk group name to get the average reads per second of a disk group. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.19.8 Response Time (MS)

This metric shows the I/O response time detail of mounted disk groups. For this disk group, this metric indicates the response time in terms of total I/O requests for all the disks included in the disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average I/O response time for each disk, the total I/O time is divided by the total number of I/O responses during the collection interval. This data is aggregated by the disk group name to get the average I/O response time of a disk group. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.19.9 Write Response Time (MS)

This metric shows the write response time detail for a disk group in an Automatic Storage Management (ASM) instance. This gives an indication for the disk group response time in terms of total write requests for the disks included in a disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average write response time for each disk, the total write time is divided by the total number of write responses during the collection interval. This data is aggregated by the disk group name to get the average write response time of a disk group. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.19.10 Write Size (MB)

This metric shows the sum of all disk writes for all disks within the disk group which are part of the cluster. The data is not aggregated for all instances.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average write size of each disk, the total number of bytes written is divided by the total number of writes during the collection interval. This data is aggregated by the disk group name to get the average write size of a disk group. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.19.11 Write Throughput

This metric shows the write throughput detail of a disk group mounted in an Automatic Storage Management (ASM) instance. This gives an indication for the total number of bytes written from the disk group with proportion to the total write time for this disk group in an instance.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average write throughput of each disk, the total number of bytes written is divided by the total write time during the collection interval. This data is aggregated by the disk group name to get the average write throughput of a disk group. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.19.12 Writes per Second

This metric shows the detail of total write requests per second for a disk group in an Automatic Storage Management (ASM) Instance. This metric shows the write performance of the disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average writes per second for each disk, the total number of write responses is divided by the total write time during the collection interval. This data is aggregated by the disk group name to get the average writes per second of a disk group. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.20 Instance Disk Performance Metrics

The Instance Disk Performance metrics indicate the performance of the disks present in an Automatic Storage Management (ASM) instance. These metrics show the disk performance parameters for all the disks mounted on an ASM Instance.

These metrics are used to collect information, for example, total I/O and read/write requests, total I/O and read/write time, and the total number of bytes read/written to the disk. These metrics also show the response of the disk for read, write, and I/O throughput.

1.20.1 I/O Size (MB)

This metric shows the sum of all disk I/O for all disks. The data is not aggregated for all instances.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average I/O size of each disk, the total number of bytes read and written is divided by the total number of I/Os during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.20.2 I/O Throughput

This metric shows the sum of I/O throughput for all disks. The data is displayed for all instances that are part of the cluster. This gives an indication of the disk group I/O performance in terms of read and write.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average throughput of each disk, the total number of bytes read and written is divided by the total I/O time during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.20.3 IOPS

This metric shows the sum of disks I/O performance per second in terms of total I/O requests for all the disks. The data is displayed for all instances that are part of the cluster.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average I/Os per second for each disk, the total number of I/O responses is divided by the total I/O time during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.20.4 Read Response Time (MS)

This metric shows the disk read response time detail of the disks. This gives an indication for the disk response time in terms of total read requests for this disk.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average read response time for each disk, the total read time is divided by the total number of read responses during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.20.5 Read Size (MB)

This metric shows the sum of all disk reads for all disks which are part of the cluster. The data is not aggregated for all instances.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average read size of each disk, the total number of bytes read are divided by the total number of reads during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.20.6 Read Throughput

This metric shows the read throughput detail of a disk mounted in an Automatic Storage Management (ASM) instance. This gives an indication for the total number of bytes read from the disk with proportion to the total read time for this disk in an instance.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average read throughput of each disk, the total number of bytes read is divided by the total read time during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.20.7 Read Write Errors

This metric shows the detail of the total number of failed read/writes for the disk. This provides information about the total number of failed attempts of reads and writes for the disk.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes	After Every Sample	>	Not Defined	0	1	Disk %dg_name%.%disk_name% has %value% Read/Write errors.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of "Instance ID", "Disk Group Name", and "Disk Name" objects.

If warning or critical threshold values are currently set for any unique combination of "Instance ID", "Disk Group Name", and "Disk Name" objects, those thresholds can be viewed on the Metric Detail page for this metric.

To specify or change warning or critical threshold values for each unique combination of "Instance ID", "Disk Group Name", and "Disk Name" objects, use the Edit Thresholds page.

Data Source

It is calculated using the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2. From these views, the total number of failed read/writes for the disk is added to calculate the read write errors detail.

User Action

Investigate the issues behind read/write errors.

1.20.8 Reads Per Second

This metric shows the detail of total read requests per second for a disk in an Automatic Storage Management (ASM) instance. This metric shows the read performance of all the disks included in an instance.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average reads per second for each disk, the total number of read responses is divided by the total read time during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.20.9 Response Time (MS)

This metric shows the I/O response time detail of mounted disks. For this disk, this metric indicates the response time in terms of total I/O requests for all the disks.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average I/O response time for each disk, the total I/O time is divided by the total number of I/O responses during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.20.10 Write Response Time (MS)

This metric shows the write response time detail of the disks. This gives an indication for the disk response time in terms of total write requests for this disk.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average write response time for each disk, the total write time is divided by the total number of write responses during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.20.11 Write Size (MB)

This metric shows the sum of all disk writes for all disks which are part of the cluster. The data is not aggregated for all instances.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average write size of each disk, the total number of bytes written is divided by the total number of writes during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.20.12 Write Throughput

This metric shows the write throughput detail of a disk mounted in an Automatic Storage Management (ASM) instance. This gives an indication for the total number of bytes written from the disk with proportion to the total write time for this disk in an instance.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average write throughput of each disk, the total number of bytes written is divided by the total write time during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.20.13 Writes Per Second

This metric shows the detail of total write requests per second for a disk in an Automatic Storage Management (ASM) Instance. This metric shows the write performance of the disk.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
10.1.0.x; 10.2.0.x; 11.1.0.x; 11.2.0.x	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average writes per second for each disk, the total number of write responses is divided by the total write time during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.21 Instance Volume Performance Metrics

The Instance Volume Performance metrics indicate the performance of the volumes present in an Automatic Storage Management (ASM) instance. These metrics show the volume performance parameters for all the volumes created on all disk groups mounted on an ASM Instance.

These metrics are used to collect information, for example, total I/O and read/write requests, total I/O and read/write time, and the total number of bytes read/written to the volume. These metrics also show the response of the volume for read, write, and I/O throughput and the Read Write Errors.

1.21.1 I/O Per Second

This metric shows the sum of ASM volume I/O performance per second in terms of total I/O requests for all the ASM Volumes. The data is displayed for all instances that are part of the cluster.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average I/Os per second for each volume, the total number of I/O responses is divided by the total I/O time during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.21.2 I/O Size (MB)

This metric shows the sum of all volume I/O for all volumes. The data is not aggregated for all instances.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average I/O size of each volume, the total number of bytes read and written is divided by the total number of I/Os during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.21.3 I/O Throughput

This metric shows the sum of I/O throughput for all volumes. The data is displayed for all instances that are part of the cluster.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average throughput of each volume, the total number of bytes read and written is divided by the total I/O time during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.21.4 Read Response Time (MS)

This metric shows the volume read response time detail of the volumes. This gives an indication of the volume response time in terms of total read requests for this volume.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average read response time for each volume, the total read time is divided by the total number of read responses during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.21.5 Read Size (MB)

This metric shows the sum of all volume reads for all volumes which are part of the cluster. The data is not aggregated for all instances.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average read size of each volume, the total number of bytes read are divided by the total number of reads during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.21.6 Read Throughput

This metric shows the read throughput detail of a volume created in an Automatic Storage Management (ASM) instance. This gives an indication for the total number of bytes read from the volume in proportion to the total read time for this volume in an instance.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average read throughput of each volume, the total number of bytes read is divided by the total read time during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.21.7 Read Write Errors

This metric shows the detail of the total number of failed read/writes for the volume. This provides information about the total number of failed attempts of reads and writes for the volume.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views. From these views, the total number of failed read/writes for the volume is added to calculate the read write errors detail.

User Action

Investigate the issues behind read/write errors.

1.21.8 Reads Per Second

This metric shows the detail of total read requests per second for a volume in a disk group in an Automatic Storage Management (ASM) instance. This metric shows the read performance of all the volumes included in an instance.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average reads per second for each volume, the total number of read responses is divided by the total read time during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.21.9 Response Time (MS)

This metric shows the I/O response time detail of volumes. For this volume, this metric indicates the response time in terms of total I/O requests for all the volumes.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average I/O response time for each volume, the total I/O time is divided by the total number of I/O responses during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.21.10 Write Response Time (MS)

This metric shows the write response time detail of the volumes. This gives an indication for the volume response time in terms of total write requests for this volume.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average write response time for each volume, the total write time is divided by the total number of write responses during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.21.11 Write Size (MB)

This metric shows the sum of all volume writes for all volumes which are part of the cluster. The data is not aggregated for all instances.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average write size of each volume, the total number of bytes written is divided by the total number of writes during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.21.12 Write Throughput

This metric shows the write throughput detail of a volume created on a disk group in an Automatic Storage Management (ASM) instance. This gives an indication for the total number of bytes written from the volume with proportion to the total write time for this volume in an instance.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average write throughput of each volume, the total number of bytes written is divided by the total write time during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.21.13 Writes Per Second

This metric shows the detail of total write requests per second for a Volume in an Automatic Storage Management (ASM) Instance. This metric shows the write performance of the volume.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.2.0.x	Every Hour

Data Source

It is calculated using the Instance Volume Performance metric which in turn collects data from the GV$ASM_DISKGROUP_STAT and GV$ASM_VOLUME_STAT views.

To calculate the average writes per second for each volume, the total number of write responses is divided by the total write time during the collection interval. The data is displayed for all instances that are part of the cluster.

User Action

No user action is required.

1.22 Offline Disk Count Metric

The Offline Disk Count metric provides the count of the disk with mode status offline.

User can change the time limit and threshold limit.

1.22.1 Offline Disk Count

This metric provides the count of the disk with mode status offline. A critical alert is generated if the offline disk count changes or any of the disks go offline.

You can change the time limit and threshold limit as required.

Metric Summary for Database Control and Grid 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.

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 15 Minutes	After Every Sample	>	Not Defined	0	1	%offline_count% disks are offline.

Data Source

This metric is collected with the help of Disk Status metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

User Action

Try to bring the disk online. Currently Enterprise Manager does not support this administration feature so it needs to be done manually.

1.23 Operational Error Metrics

The Operational Error metrics represent errors that may affect the operation of the ASM, for example, data block corruption, media failure, and so on as recorded in the ASM alert log file. The alert log file has a chronological log of messages and errors.

Each metric signifies that the ASM being monitored has detected a critical error condition that may affect the normal operation of the ASM and has generated an error message to the alert log file since the last sample time. The Support Workbench in Enterprise Manager may contain more information about the error.

1.23.1 Alert Log Error Trace File

This metric is the name of the trace file (if any) associated with the logged error.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.1.0.x; 11.2.0.x	Every 5 Minutes

Data Source

The data comes from the alert log files. It is collected using the Perl script $ORACLE_HOME/sysman/admin/scripts/alertlogAdr.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

No user action is required.

1.23.2 Alert Log Name

This metric is the name of the alert log file.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
11.1.0.x; 11.2.0.x	Every 5 Minutes

Data Source

The data comes from the alert log files. It is collected using the Perl script $ORACLE_HOME/sysman/admin/scripts/alertlogAdr.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

No user action is required.

1.23.3 Data Block Corruption

This metric signifies that the ASM being monitored has generated a corrupted block error (ORA-01157 or ORA-27048) to the alert file since the last sample time. The alert file is a special trace file containing a chronological log of messages and errors. An alert event is triggered when data block corrupted messages are written to the alert file.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x; 11.2.0.x	Every 5 Minutes	After Every Sample	MATCH	Not Defined	.^Foot 1	1^Foot 2	A data block was corrupted at time/line number: %timeLine%.

^Footnote 1Once an alert is triggered for this metric, it must be manually cleared.

^Footnote 2Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

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, those 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.

Data Source

The data comes from the alert log files. It is collected using the Perl script $ORACLE_HOME/sysman/admin/scripts/alertlogAdr.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

Use Support Workbench in Enterprise Manager to examine the details of the error.

1.23.4 Generic Operational Error

This metric signifies that the ASM being monitored has generated some error that may affect the normal operation of the ASM to the alert file since the last sample time. The alert file is a special trace file containing a chronological log of messages and errors. An alert event is triggered when data block corrupted messages are written to the alert file.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x; 11.2.0.x	Every 5 Minutes	After Every Sample	MATCH	Not Defined	.^Foot 1	1^Foot 2	Operational error (%errCodes%) detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1Once an alert is triggered for this metric, it must be manually cleared.

^Footnote 2Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

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, those 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.

Data Source

The data comes from the alert log files. It is collected using the Perl script $ORACLE_HOME/sysman/admin/scripts/alertlogAdr.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

Use Support Workbench in Enterprise Manager to examine the details of the error.

1.23.5 Media Failure

This metric signifies that the ASM being monitored has generated a media failure error (ORA-01242 or ORA-01243) to the alert file since the last sample time. The alert file is a special trace file containing a chronological log of messages and errors. An alert event is triggered when data block corrupted messages are written to the alert file.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x; 11.2.0.x	Every 5 Minutes	After Every Sample	MATCH	Not Defined	.^Foot 1	1^Foot 2	Media failure detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1Once an alert is triggered for this metric, it must be manually cleared.

^Footnote 2Once an alert is triggered for this metric, it must be manually cleared.

Multiple Thresholds

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, those 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.

Data Source

The data comes from the alert log files. It is collected using the Perl script $ORACLE_HOME/sysman/admin/scripts/alertlogAdr.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

Use Support Workbench in Enterprise Manager to examine the details of the error.

1.24 Operational Error Status Metrics

The Operational Error Status metrics place all the types of alert log errors into the following categories: Data Block Corruption, Media Failure, and Generic Operational Error. These metrics represent whether the last scan of the alert log identified any of the aforementioned categories of error and, if so, how many.

1.24.1 Data Block Corruption Error Status

This metric reflects the number of Data Block Corruption alert log errors witnessed the last time Enterprise Manager scanned the Alert Log.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x; 11.2.0.x	Every 5 Minutes	After Every Sample	>	Not Defined	0	1	Data block corruption errors have been found in the alert log.

Data Source

Alert Log metric

User Action

Examine the Alert Log.

1.24.2 Generic Operational Error Status

This metric reflects the number of Generic Operation Error errors witnessed the last time Enterprise Manager scanned the alert log file.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x; 11.2.0.x	Every 5 Minutes	After Every Sample	>	Not Defined	0	1	%value% distinct types of operational errors have been found in the alert log.

Data Source

Operational Error metric

User Action

Use Support Workbench in Enterprise Manager to examine the details of the error.

1.24.3 Media Failure Status

This metric reflects the number of Media Failure errors witnessed the last time Enterprise Manager scanned the alert log file.

Metric Summary for Database Control and Grid 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.

Target Version	Evaluation and Collection Frequency	Upload Frequency	Operator	Default Warning Threshold	Default Critical Threshold	Consecutive Number of Occurrences Preceding Notification	Alert Text
11.1.0.x; 11.2.0.x	Every 5 Minutes	After Every Sample	>	Not Defined	0	1	Media failure errors have been found in the alert log.

Data Source

Operational Error metric

User Action

Use Support Workbench in Enterprise Manager to examine the details of the error.

1.25 Response Metric

The Response metric shows the status of the Automatic Storage Management (ASM) instance. It shows whether the instance is up or down. The check is performed every five minutes and returns the status of the connection as successful or it displays the ORA error for connection failure. This generates a critical alert if the ASM instance is down.

1.25.1 Status

This metric shows the status of the Automatic Storage Management (ASM) instance. It displays whether the instance is up or down. This check is performed every five minutes and returns the status of the connection as successful or it displays the ORA error for connection failure. This generates a critical alert if the ASM instance is down.

Metric Summary for Database Control and Grid 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.

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	Failed to connect to ASM instance %oraerr%.

Data Source

You can establish a connection to the ASM instance with instance properties, and if the connection succeeds then the status is shown as Up, otherwise is displays as Down. It may also display as Down if there is an error in the metric collection.

User Action

Perform one of the following:

Check that the configuration property saved for the ASM instance is correct.
If it displays as Down, the ASM instance is down. Try to reestablish the connection using the startup/shutdown feature using the Enterprise Manager application. Alternately, you can restart the application manually.

1.26 Single Instance Disk Group Performance Metrics

The Single Instance Disk Group Performance metrics indicate the performance of the single instance disk group present in an Automatic Storage Management (ASM) instance. These metrics are used to collect information, for example, total I/O and read/write requests, total I/O and read/write time, and the total number of bytes read/written to the disk group. These metrics also show the response of the disk group for read, write, and I/O throughput.

1.26.1 I/O Per Second

This metric shows the sum of disks I/O performance per second in terms of total I/O requests for all the disks within the disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average I/Os per second for each disk, the total number of I/O responses is divided by the total I/O time during the collection interval. This data is aggregated by the disk group name to get the average I/O per second of a disk group.

User Action

No user action is required.

1.26.2 I/O Size (MB)

This metric shows the sum of all disk I/O for all disks within the disk group for one and only one instance. This is the instance that the user connects to using the UI navigation path.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average I/O size of each disk, the total number of bytes read and written is divided by the total number of I/Os during the collection interval. This data is aggregated by the disk group name to get the average I/O size of a disk group.

User Action

No user action is required.

1.26.3 I/O Throughput

This metric shows the sum of I/O throughput for all disks within the disk group. This gives an indication of the disk group I/O performance in terms of reads and writes for the instance.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average throughput of each disk, the total number of bytes read and written is divided by the total I/O time during the collection interval. This data is aggregated by the disk group name to get the average I/O throughput of a disk group.

User Action

No user action is required.

1.26.4 Read Response Time (MS)

This metric shows the read response time detail for the disk group mounted on the Automatic Storage Management (ASM) instance. This gives an indication for the disk group response time in terms of total read requests for this disk.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average read response time for each disk, the total read time is divided by the total number of read responses during the collection interval. This data is aggregated by the disk group name to get the average read response time of a disk group.

User Action

No user action is required.

1.26.5 Read Size (MB)

This metric shows the sum of all disk reads for all disks within the disk group which are part of the cluster.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average read size of each disk, the total number of bytes read are divided by the total number of reads during the collection interval. This data is aggregated by the disk group name to get the average read size of a disk group.

User Action

No user action is required.

1.26.6 Read Throughput

This metric shows the read throughput detail of a disk group mounted in an Automatic Storage Management (ASM) instance. This gives an indication for the total number of bytes read from the disk group with proportion to the total read time for this disk group in an instance.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average read throughput of each disk, the total number of bytes read is divided by the total read time during the collection interval. This data is aggregated by the disk group name to get the average read throughput of a disk group.

User Action

No user action is required.

1.26.7 Reads Per Second

This metric shows the detail of total read requests per second for the single instance disk group in an Automatic Storage Management (ASM) instance. This metric shows the read performance of all the disks included in the disk group of an instance.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average reads per second for each disk, the total number of read responses is divided by the total read time during the collection interval. This data is aggregated by the disk group name to get the average reads per second of a disk group.

User Action

No user action is required.

1.26.8 Response Time (MS)

This metric shows the I/O response time detail of a mounted single instance disk group. For this disk group, this metric indicates the response time in terms of total I/O requests for all the disks included in the disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average I/O response time for each disk, the total I/O time is divided by the total number of I/O responses during the collection interval. This data is aggregated by the disk group name to get the average I/O response time of a disk group.

User Action

No user action is required.

1.26.9 Write Response Time (MS)

This metric shows the write response time detail for a disk group in an Automatic Storage Management (ASM) instance. This gives an indication for the disk group response time in terms of total write requests for the disks included in the disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average write response time for each disk, the total write time is divided by the total number of write responses during the collection interval. This data is aggregated by the disk group name to get the average write response time of a disk group.

User Action

No user action is required.

1.26.10 Write Size (MB)

This metric shows the sum of all disk writes for all disks within the disk group which are part of the cluster. This is the instance that the user connects to using the UI navigation path.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average write size of each disk, the total number of bytes written is divided by the total number of writes during the collection interval. This data is aggregated by the disk group name to get the average write size of a disk group.

User Action

No user action is required.

1.26.11 Write Throughput

This metric shows the write throughput detail of a disk group mounted in an Automatic Storage Management (ASM) instance. This gives an indication for the total number of bytes written from the disk group with proportion to the total write time for this disk group in an instance.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average write throughput of each disk, the total number of bytes written is divided by the total write time during the collection interval. This data is aggregated by the disk group name to get the average write throughput of a disk group.

User Action

No user action is required.

1.26.12 Writes Per Second

This metric shows the details of total write requests per second for the disk group mounted on the Automatic Storage Management (ASM) instance. This metric shows the write performance of the disk group.

Metric Summary for Database Control and Grid Control

The following table shows how often the metric's value is collected.

Target Version	Collection Frequency
All Versions	Every 15 Minutes

Data Source

It is calculated using the Instance Disk Performance metric which in turn collects data from the GV$ASM_DISKGROUP and GV$ASM_DISK views for 10g Release 1 and the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views for 10g Release 2.

To calculate the average writes per second for each disk, the total number of write responses is divided by the total write time during the collection interval. This data is aggregated by the disk group name to get the average writes per second of a disk group.

User Action

No user action is required.

1 Automatic Storage Management

1.1 Alert Log

1.1.1 Alert Log Error Stack

1.1.2 Alert Log Error Stack Trace File Name

1.1.3 Alert Log Name

1.1.4 Archive Hung Error Stack

1.1.5 Data Block Corruption Error Stack

1.1.6 Media Failure Error Stack

1.1.7 Session Terminated Error Stack

1.2 Alert Log Error Status

1.2.1 Archiver Hung Alert Log Error Status

1.2.2 Data Block Corruption Alert Log Error Status

1.2.3 Generic Alert Log Error Status

1.2.4 Media Failure Alert Log Error Status

1.2.5 Session Terminated Alert Log Error Status

1.3 ASM Cluster File System Metrics

1.3.1 Corrupt

1.3.2 Disk Group Allocated Space (GB)

1.3.3 Free (GB)

1.3.4 Size (GB)

1.3.5 Used (GB)

1.3.6 Used (%)

1.3.7 Volume Name

1.4 ASM Cluster File System State Metrics

1.4.1 ASM Cluster File System Availability

1.4.2 ASM Cluster File System Available Time

1.4.3 ACM Cluster File System Mount Point

1.4.4 ASM Cluster File System Mount State

1.5 ASM Volumes Metrics

1.5.1 Disk Group Allocated Space (GB)

1.5.2 Mount Point

1.5.3 Redundancy

1.5.4 Size (GB)

1.5.5 Status

1.5.6 Usage

1.5.7 Volume Name

1.6 Checker Failure

1.6.1 Alert Log Name

1.6.2 Checker Failure Detected

1.7 Cluster Disk Group Performance Metrics

1.7.1 I/O Per Second

1.7.2 I/O Size (MB)

1.7.3 I/O Throughput

1.7.4 Read Response Time (MS)

1.7.5 Read Size (MB)

1.7.6 Read Throughput

1.7.7 Reads Per Second

1.7.8 Response Time (MS)

1.7.9 Write Response Time (MS)

1.7.10 Write Size (MB)

1.7.11 Write Throughput

1.7.12 Writes Per Second

1.8 Cluster Disk Performance Metrics

1.8.1 I/O Per Second

1.8.2 I/O Size (MB)

1.8.3 I/O Throughput

1.8.4 Read Response Time (MS)

1.8.5 Read Size (MB)

1.8.6 Read Throughput

1.8.7 Reads Per Second

1.8.8 Response Time (MS)

1.8.9 Write Response Time (MS)

1.8.10 Write Size (MB)

1.8.11 Write Throughput

1.8.12 Writes Per Second

1.9 Cluster Volume Performance Metrics

1.9.1 I/O Per Second

1.9.2 I/O Size (MB)

1.9.3 I/O Throughput

1.9.4 Read Response Time (MS)

1.9.5 Read Size (MB)

1.9.6 Read Throughput

1.9.7 Read Write Errors

1.9.8 Reads Per Second

1.9.9 Response Time (MS)

1.9.10 Write Response Time (MS)

1.9.11 Write Size (MB)

1.9.12 Write Throughput

1.9.13 Writes Per Second

1.10 Database Disk Group Usage Metric