2 Automatic Storage Management

This chapter provides information about the Automatic Storage Management (ASM) metrics.

2.1 Alert Log

The metrics in this category signify 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 you 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.

2.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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10g, 11g, 12c	Every 5 Minutes	ORA-0*(600?\|7445\|4[0-9][0-9][0-9])[^0-9]	Not Defined	ORA-error stack (%errCodes%) logged in %alertLogName%.

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 the ALERT log for additional information.

2.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.

Target Version	Evaluation and Collection Frequency
10g, 11g, 12c	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.

2.1.3 Alert Log Name

This metric provides 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.

Target Version	Evaluation and Collection Frequency
10g, 11g, 12c	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 the ALERT log for additional information.

2.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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10g, 11g, 12c	Every 5 Minutes	Not Defined	ORA-	The archiver hung at time/line number:%timeLine%.

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 the ALERT log for additional information.

2.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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10g, 11g, 12c	Every 5 Minutes	Not Defined	ORA-	The data block was corrupted at time/line number: %timeLine%.

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 the ALERT log for additional information.

2.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. You can also set or modify the warning and critical alert values.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10g, 11g, 12c	Every 5 Minutes	Not Defined	ORA-	Media failure was detected at time/line number: %timeLine%.

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 the ALERT log for additional information.

2.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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10g, 11g, 12c	Every 5 Minutes	ORA-	Not Defined	A session was terminated at time/line number: %timeLine%.

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

User Action

Examine the ALERT log for additional information.

2.2 Alert Log Error Status

The metrics in this category display 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.

2.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 you an idea about the current status of the Archiver Hung error present in the alert log file. This also generates a warning alert when this count is greater than zero.

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

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10g, 11g, 12c	Every 5 Minutes	0	Not Defined	Archiver hung errors have been found in the alert log.

Data Source

This metric is calculated based on the Archive Hung Error Stack Metric rollup.

User Action

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

2.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 you an idea about the current status of Data Block Corruption errors present in the alert log file. This also generates a warning alert when this count is greater than zero.

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

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10g, 11g, 12c	Every 5 Minutes	0	Not Defined	Data block corruption errors have been found in the alert log.

Data Source

This metric is calculated based on the Data Block Corruption Error Stack Metric rollup.

User Action

2.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 you an idea about the current status of the Generic Alert (ORA-) error present in the alert log file. This also generates a warning alert when this count is greater than zero.

You can edit the metric threshold and change the value of the error if you want to collect data under a different heading. You can also set or modify the warning alert and critical alert values.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10g, 11g, 12c	Every 5 Minutes	0	Not Defined	%value% distinct types of ORA- errors have been found in the alert log.

Data Source

This metric is calculated based on the Generic Alert Error Stack Metric rollup.

User Action

Examine the ALERT log for additional information.

2.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 the 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.

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

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10g, 11g, 12c	Every 5 Minutes	0	Not Defined	Media failure errors have been found in the alert log.

Data Source

This metric is calculated based on the Media Failure Alert Error Stack Metric rollup.

User Action

2.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 you 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.

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

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10g, 11g, 12c	Every 5 Minutes	0	Not Defined	Session terminations have been found in the alert log.

Data Source

This metric is calculated based on the Session Terminated Alert Error Stack Metric rollup.

User Action

2.3 ASM 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.

2.3.1 Alert Log Error Stack

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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10g, 11g, 12c	Every 5 Minutes	ORA-0*(600?\|7445\|4[0-9][0-9][0-9])[^0-9]	Not Defined	ORA-error stack (%errCodes%) logged in %alertLogName%.

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

User Action

Examine the ALERT log for additional information.

2.3.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.

Target Version	Evaluation and Collection Frequency
10g, 11g, 12c	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.

2.3.3 Alert Log Name

This metric provides 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.

Target Version	Evaluation and Collection Frequency
10g, 11g, 12c	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 the ALERT log for additional information.

2.3.4 Archive Hung Error Stack

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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10g, 11g, 12c	Every 5 Minutes	Not Defined	ORA-	The archiver hung at time/line number:%timeLine%.

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 the ALERT log for additional information.

2.3.5 Data Block Corruption Error Stack

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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10g, 11g, 12c	Every 5 Minutes	Not Defined	ORA-	The data block was corrupted at time/line number: %timeLine%.

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 the ALERT log for additional information.

2.3.6 Media Failure Error Stack

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

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10g, 11g, 12c	Every 5 Minutes	Not Defined	ORA-	Media failure was detected at time/line number: %timeLine%.

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 the ALERT log for additional information.

2.3.7 Session Terminated Error Stack

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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10g, 11g, 12c	Every 5 Minutes	ORA-	Not Defined	A session was terminated at time/line number: %timeLine%.

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

User Action

Examine the ALERT log for additional information.

2.4 ASM Cluster File System

The metrics in the ASM Cluster File System metric category show the space used by all of 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 about 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 such as the 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 and the metrics will be collected at the cluster level if the target is Cluster ASM otherwise they will be collected at the instance level as a part of the ASM target type metrics. You can change the threshold limit as required.

2.4.1 ASM Cluster File System 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 therefore 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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
11gR2, 12c	Every 30 Minutes	Not Defined	TRUE	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.

2.4.2 ASM Cluster File System Used (%)

This metric shows if the percent of the ASM cluster file system that is used.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
11gR2, 12cR1	Every 30 Minutes	Not Defined	TRUE	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.

2.4.3 Allocated Space (GB)

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

Target Version	Collection Frequency
11gR2, 12c	Every 30 Minutes

Data Source

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

User Action

No user action is required.

2.4.4 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.

Target Version	Collection Frequency
11gR2, 12c	Every 30 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.

2.4.5 Size (GB)

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

Target Version	Collection Frequency
11gR2, 12c	Every 30 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.

2.4.6 Snapshot Space Used (MB)

This metric shows the percentage of snapshot 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.

Target Version	Collection Frequency
11gR2, 12c	Every 30 Minutes

2.4.7 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.

Target Version	Collection Frequency
11gR2, 12c	Every 30 Minutes

Data Source

This metric is calculated from the columns TOTAL_SIZE and TOTAL_FREE in the V$ASM_FILESYSTEM view. This metric is calculated using the following formula:

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.

2.4.8 Used (MB)

This metric shows the space in MB 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.

Target Version	Collection Frequency
11gR2, 12c	Every 30 Minutes

Data Source

This metric is calculated from the columns TOTAL_SIZE and TOTAL_FREE in the V$ASM_FILESYSTEM view. This metric is calculated using the following formula:

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.

2.4.9 Volume Name

This metric shows the volume name of the volume device used to create the ASM Cluster File System.

Target Version	Collection Frequency
11gR2, 12c	Every 30 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.

2.5 ASM Cluster File System State

The metrics in the ASM Cluster File System State metric category show the state of the ASM Cluster File System, whether it is MOUNTED or DISMOUNTED on a given host.

2.5.1 ASM Cluster File System Availability

This metric shows the availability of the ASM cluster file system.

Target Version	Collection Frequency
11g, 12c	Every 15 Minutes

2.5.2 ASM Cluster File System Mount State

This metric shows the mount state of the ASM cluster file system.

Target Version	Collection Frequency
11g, 12c	Every 15 Minutes

2.5.3 Mount Point

This metric shows the mount point of the ASM cluster file system.

Target Version	Collection Frequency
11g, 12c	Every 15 Minutes

2.5.4 ASM Cluster File System Available Time

This metric shows the amount of time that the ASM cluster file system has been available.

Target Version	Collection Frequency
11g, 12c	Every 15 Minutes

2.6 ASM Volumes

The metrics in the ASM Volumes metric category 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. The metrics are collected at the cluster level if the target is Cluster ASM. Otherwise, they are collected at the instance level as a part of ASM target type metrics.

2.6.1 Allocated Space (GB)

This metric shows the space in MB allocated to the ASM Cluster File System on a given host in a cluster.

Target Version	Collection Frequency
11gR2, 12c	Every 24 hours

Data Source

The source of this metric is the MOUNTPATH column in the V$ASM_VOLUME view.

User Action

No user action is required.

2.6.2 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.

Target Version	Collection Frequency
11gR2, 12c	Every 24 hours

Data Source

The source of this metric is the REDUNDANCY column in the V$ASM_VOLUME view.

User Action

No user action is required.

2.6.3 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.

Target Version	Collection Frequency
11gR2, 12c	Every 24 hours

Data Source

The source of this metric is the column SIZE_MB from the V$ASM_VOLUME view.

User Action

No user action is required.

2.6.4 Usage

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

Target Version	Collection Frequency
11gR2, 12c	Every 24 hours

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.

2.6.5 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.

Target Version	Collection Frequency
11gR2, 12c	Every 24 hours

Data Source

The source of this metric is the VOLUME_NAME column in the V$ASM_VOLUME view.

User Action

No user action is required.

2.7 Checker Failure

The metrics in this category are used to alert you to checker failures reported in the alert log. It contains the number of checker failures detected. It also generates a critical alert when these problems are found in the alert log.

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. Alert log file is scanned for messages similar to ASM Health Checker found 1 new failures.

2.7.1 Alert Log Name

This metric returns the name of the Alert Log file.

Target Version	Collection Frequency
11g, 12cR1	Every 5 Minutes

Data Source

User Action

Examine the alert log for additional information.

Note:

This event does not automatically clear because there is no automatic way of determining when the problem has been resolved. Therefore, you need to manually clear the event after the problem is fixed.

2.7.2 Checker Failure Detected

This metric is used to alert you to checker failures reported in the alert log. It contains the number of checker failures detected.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
11g, 12cR1	Every 5 Minutes	Not Defined	.^Foot 1	Health checker runs found %numberOfFailures% new failures in %alertLogName% at time/line number: %timeLine%.

^Footnote 1After 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

User Action

Examine the alert log for additional information.

Note:

2.7.3 Number of Failures

This metric shows the number of failures detected in the alert log.

Target Version	Collection Frequency
11g, 12c	Every 5 minutes

2.8 Cluster Volume Performance

The metrics in the Cluster Volume Performance metric category indicate the performance of the cluster volumes present in an ASM instance.

2.8.1 I/O Response Time

This metric shows the total read errors for the cluster volume.

Target Version	Collection Frequency
11gR2, 12c	Every hour

2.8.2 I/O Per Second

This metric shows I/O per second for the cluster volume.

Target Version	Collection Frequency
11gR2, 12c	Every hour

2.8.3 I/O Size (MB)

This metric shows the I/O size in MB for the cluster volume.

Target Version	Collection Frequency
11gR2, 12c	Every hour

2.8.4 I/O Throughput

This metric shows the I/O throughput for the cluster volume.

Target Version	Collection Frequency
11gR2, 12c	Every hour

2.8.5 Read Errors

This metric shows the total read errors for the cluster volume.

Target Version	Collection Frequency
11gR2, 12c	Every hour

2.8.6 Read Response Time (MS)

This metric shows the total read response time in milliseconds for the volume cluster.

Target Version	Collection Frequency
11gR2, 12c	Every hour

2.8.7 Read Size (MB)

This metric shows the total read size for the volume cluster.

Target Version	Collection Frequency
11gR2, 12c	Every hour

2.8.8 Read Throughput

This metric shows the total read throughput for the volume cluster.

Target Version	Collection Frequency
11gR2, 12c	Every hour

2.8.9 Reads Per Second

This metric shows the reads per second for the volume cluster.

Target Version	Collection Frequency
11gR2, 12c	Every hour

2.8.10 Write Errors

This metric shows the detail of the total number of failed writes for the volume cluster.

Target Version	Collection Frequency
11gR2, 12c	Every hour

2.8.11 Write Response Time (MS)

This metric shows the total I/O time (in seconds) for write requests for the volume cluster if the TIMED_STATISTICS initialization parameter is set to true, or 0 if set to false.

Target Version	Collection Frequency
11gR2, 12c	Every hour

Data Source

This metric is calculated using the data from the GV$ASM_DISKGROUP_STAT and GV$ASM_DISK_STAT views.

User Action

No user action is required.

2.8.12 Write Size (MB)

This metric shows the total size of the writes in MB for the cluster volume.

Target Version	Collection Frequency
11gR2, 12c	Every hour

2.8.13 Write Throughput

This metric shows the total write throughput for the cluster volume.

Target Version	Collection Frequency
11gR2, 12c	Every hour

2.8.14 Writes Per Second

This metric shows the total size of the writes per second the cluster volume.

Target Version	Collection Frequency
11gR2, 12c	Every hour

2.9 Database Disk Group Usage

The metrics in this category 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. The metrics will be collected at cluster level if the target is Cluster ASM else they will be collected at instance level as a part of Automatic Storage Management target type metrics.

2.9.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.

Target Version	Collection Frequency
10g, 11g, 12cR1	Every 15 Minutes

Data Source

This metric is calculated by taking the space used by a file using the V$ASM_FILE view and joining it 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.

2.10 Disk Group Imbalance Status

The metrics in the Disk Group Imbalance Status metric category 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. The metrics are collected at the cluster level if the target is Cluster ASM. Otherwise, they are collected at the instance level as a part of ASM target type metrics.

2.10.1 Actual Imbalance (%)

Actual Imbalance (%) measures the difference in space allocated to the fullest and emptiest disks in the disk group. The comparison is in percent full because 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.

Target Version	Collection Frequency
10gR2, 11g, 12c	Every 15 minutes

Data Source

This metric is calculated using the following formula:

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.

2.10.2 Actual Minimum Percent Free

The Actual Minimum Percent Free metric 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. Because all allocations are performed 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.

Target Version	Collection Frequency
10gR2, 11g, 12c	Every 15 minutes

Data Source

The metric is calculated as 100 * (min(FREE_MB / TOTAL_MB)), where FREE_MB and TOTAL_MB are columns in the $ASM_DISK_STAT view.

User Action

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

2.10.3 Disk Count

The Disk Count metric reports the number of disks in the disk group which gives a sense of how widely files can be spread.

Target Version	Collection Frequency
10gR2, 11g, 12c	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.

2.10.4 Disk Group Percent Imbalance

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

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10gR2, 11g, 12c	Every 15 Minutes	10	Not Defined	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

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

User Action

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

2.10.5 Disk Maximum Used (%) with Rebalance

The Disk Maximum Used (%) with Rebalance metric 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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10gR2, 11g, 12c	Every 15 Minutes	Not Defined	95	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 the value of the Disk Maximum Used (%) with Rebalance metric is calculated as (100 - Actual Minimum Percent Free), otherwise the value is 0.

User Action

A critical alert is generated if the value of the Disk Maximum Used (%) with Rebalance metric 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).

2.10.6 Disk Minimum Free (%) without Rebalance

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

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10gR2, 11g, 12c	Every 15 Minutes	20	10	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

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

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. You should manually initiate a rebalance operation.

2.10.7 Rebalance In Progress

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

Target Version	Collection Frequency
10gR2, 11g, 12c	Every 15 Minutes

Data Source

The value of the Rebalance In Progress metric is retrieved from the operation column of the V$ASM_OPERATION.view

User Action

No user action is required.

2.10.8 Resync In Progress

The Resync In Progress metric returns Yes if a resync operation is in progress, No otherwise.

Target Version	Collection Frequency
10gR2, 11g, 12c	Every 15 Minutes

2.11 Disk Group Status

This configuration metric category collects ASM disk group status information.

2.11.1 State

This metric shows the state of the ASM disk group.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.11.2 Disk Group Name

This metric shows the disk group name.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

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.

2.12 Disk Group Usage

The metrics in this category show the space used by all the disk groups having the state as &rsquor;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%, because 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. The metrics will be collected at cluster level if the target is Cluster ASM else they will be collected at instance level as a part of Automatic Storage Management target type metrics.

2.12.1 Disk Group Name

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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10g, 11g, 12cR1	Every 15 Minutes	Not Defined	Not Defined	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.

2.12.2 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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10g, 11g, 12cR1	Every 15 Minutes	Not Defined	Not Defined	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.

2.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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10gR2, 11g, 12cR1	Every 15 Minutes	Not Defined	Not Defined	Usable free size for Disk Group %dg_name% has fallen to %value% (MB).

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

2.12.4 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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10gR2, 11g, 12cR1	Every 15 Minutes	Not Defined	Not Defined	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.

2.12.5 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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10g, 11g, 12cR1	Every 15 Minutes	75	90	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.

2.12.6 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.

Target Version	Collection Frequency
10g, 11g, 12cR1	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.

2.12.7 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.

Target Version	Collection Frequency
10g, 11g, 12cR1	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.

2.12.8 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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10gR2, 11g, 12cR1	Every 15 Minutes	75	90	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.

2.13 Disk Path

This configuration metric category collects ASM disk path.

2.13.1 Disk Name

This metric shows the name of the ASM disk.

Target Version	Collection Frequency
10g, 11g, 12c	Every 24 hours

2.13.2 Disk Path

This metric shows the path of the ASM disk.

Target Version	Collection Frequency
10g, 11g, 12c	Every 24 hours

2.13.3 Group Name

This metric shows the group name of the ASM disk.

Target Version	Collection Frequency
10g, 11g, 12c	Every 24 hours

2.14 Disk Status

This configuration metric category collects ASM disk status information.

2.14.1 Disk Mode Status

This metric shows the disk mode status of the ASM disk.

Target Version	Collection Frequency
10g, 11g, 12cR1	Every 15 minutes

2.15 Disks

The metrics in this category collect ASM Disk configuration data such as disk group name. Default collection time is 24 hours and the metrics will be collected at cluster level if the target is Cluster ASM else they will be collected at instance level as a part of Automatic Storage Management target type metrics.

2.15.1 Disk

This metric shows the disk name of the ASM disk.

Target Version	Collection Frequency
10g, 11g, 12cR1	Every 24 hours

Data Source

The source for this metric is the NAME column in the V$ASM_DISK_STAT view.

User Action

No user action is required.

2.15.2 Disk Creation Date

This metric shows the disk creation date of the ASM disk.

Target Version	Collection Frequency
10g, 11g, 12cR1	Every 24 hours

Data Source

The source for this metric is the CREATE_DATE column in the V$ASM_DISK_STAT view.

User Action

No user action is required.

2.15.3 Disk Group

This metric shows the disk group name of the ASM disk.

Target Version	Collection Frequency
10g,11g, 12cR1	Every 24 hours

Data Source

This metric is collected from V$ASM_DISKGROUP_STAT view.

User Action

No user action is required.

2.15.4 Disk Path

This metric shows the disk path of the ASM disk.

Target Version	Collection Frequency
10g, 11g, 12cR1	Every 24 hours

Data Source

The source for this metric is the PATH column in the V$ASM_DISK_STAT view.

User Action

No user action is required.

2.15.5 Failure Group Name

This metric shows the failure group name of the ASM disk.

Target Version	Collection Frequency
10g, 11g, 12cR1	Every 24 hours

Data Source

The source for this metric is the SPACE column in the V$ASM_DISK_STAT view.

User Action

No user action is required.

2.15.6 Failure Group Type

This metric shows the failure group type, REGULAR or QUORUM.

Target Version	Collection Frequency
10g, 11g, 12cR1	Every 24 hours

Data Source

The source for this metric is the FAILUREGROUP column in the V$ASM_DISK_STAT view.

User Action

No user action is required.

2.15.7 Redundancy

This metric shows the level of redundancy of the ASM disk.

Target Version	Collection Frequency
10g, 11g, 12cR1	Every 24 hours

Data Source

The source for this metric is the REDUNANCY column in the V$ASM_DISK_STAT view.

User Action

No user action is required.

2.15.8 Size (MB)

This metric shows the disk size in MB of the ASM disk.

Target Version	Collection Frequency
10g, 11g, 12cR1	Every 24 hours

Data Source

The source for this metric is the TOTAL_MB column in the V$ASM_DISK_STAT view.

User Action

No user action is required.

2.16 Failure Group Imbalance Status

The metrics in the Failure Group Imbalance Status metric category 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, because failure groups are not used in this configuration. The metrics are collected at the cluster level if the target is Cluster ASM. Otherwise, they are collected at the instance level as a part of ASM target type metrics.

2.16.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. The Disk Count Imbalance Variance metric reports 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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10gR2, 11g, 12c	Every 15 Minutes	2	Not Defined	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

The value of the Disk Count Imbalance Variance metric 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 is generated when the Disk Count Imbalance Variance value is greater than 1 (the default value). 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.

2.16.2 Disk Size Imbalance (%)

Disk Size Imbalance (%) checks whether 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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
10gR2, 11g, 12c	Every 15 Minutes	10	Not Defined	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

The value of the Disk Size Imbalance metric 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 is generated when the Disk Size Imbalance (%) is greater than 10% (the 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.

2.16.3 Failure Group Count

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

Target Version	Collection Frequency
10gR2, 11g, 12c	Every 15 Minutes

Data Source

The value of the Failure Group Count metric 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.

2.17 Failure Group Status

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

These metrics only apply to disk groups with normal or high redundancy. The metrics are collected at the cluster level if the target is Cluster ASM. Otherwise, they are collected at the instance level as a part of ASM target type metrics.

2.17.1 Available Disks

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

Target Version	Collection Frequency
10gR2, 11g, 12c	Every 15 Minutes

Data Source

The value of the Available Disks metric 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.

2.17.2 Disk Count

The Disk Count metric reports the number of disks in the failure group.

Target Version	Collection Frequency
10gR2, 11g, 12c	Every 15 Minutes

Data Source

The value of the Total Disks metric is retrieved from the V$ASM_DISKGROUP_STAT and V$ASM_DISK_STAT views.

User Action

No user action is required.

2.17.3 Online Disk Count for Failure Group with More than 1 Disk

This metric shows the online disk count for failure group with more than one disk.

Target Version	Collection Frequency
10g, 11g, 12cR1	Every 15 minutes

2.18 Incident

The metrics in this category represent incidents, for example, generic internal error, access violation, and so on as recorded in the ASM alert log file. Incidents refer to problems for which Automatic Diagnostic Repository (ADR) incidents are created. These type of problems usually require investigation, diagnostic data to be collected, and perhaps require interaction with Oracle Support for resolution. 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.

Note:

For more information about Incident metrics and Operational Error metrics, log in to My Oracle Support and search for the following Oracle Support Note:

Database Alert log monitoring in 12c explained (Doc ID 1538482.1)

https://support.oracle.com/

Setting Thresholds for Incident Metrics

To edit the thresholds for any of the following metrics, from the Cloud Control UI, right-click the target name, select Monitoring, then Metric and Collection Settings. The following settings provide examples of some of the possible settings:

Warning Threshold: Not Defined; Critical Threshold: .*

In this case, the Management Agent generates a critical error alert in Enterprise Manager when the incident occurs.
Warning Threshold: .*; Critical Threshold: Not Defined

In this case, the Management Agent generates a warning alert in Enterprise Manager when the incident occurs.
Warning Threshold: Not Defined; Critical Threshold: Not Defined

In this case, the Management Agent does not generate an alert in Enterprise Manager when the incident occurs.

2.18.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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
11g, 12cR1	Every 5 Minutes	Not Defined	.^Foot 1	An access violation detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1After 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.

2.18.2 Alert Log Error Trace File

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

Target Version	Collection Frequency
11g, 12cR1	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.

2.18.3 Alert Log Name

This metric is the name of the alert log file.

Target Version	Collection Frequency
11g, 12cR1	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.

2.18.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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
11g, 12cR1	Every 5 Minutes	Not Defined	.^Foot 1	An ASM data block was corrupted at time/line number: %timeLine%.

^Footnote 1After 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 source of this metric is the Incident metric.

User Action

You 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.

2.18.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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
11g, 12cR1	Every 5 Minutes	Not Defined	.^Foot 1	A cluster error detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1After 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.

2.18.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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
11g, 12cR1	Every 5 Minutes	Not Defined	.^Foot 1	A deadlock error detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1After 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.

2.18.7 ECID

The Execution Context ID (ECID) tracks requests as they move through the application server. This information is useful for diagnostic purposes because it can be used to correlate related problems encountered by a single user attempting to accomplish a single task.

Target Version	Collection Frequency
11g, 12c	Every 5 Minutes

Data Source

The ECID is extracted from the database alert log.

User Action

Diagnostic incidents usually indicate software errors and should be reported to Oracle through the Enterprise Manager Support Workbench. When you package problems using Support Workbench, the Support Workbench uses ECID to correlate and include any additional problems in the package.

2.18.8 File Access Error

This metric signifies that the ASM has generated an incident due to failure to read a file at the time.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
11g, 12cR1	Every 5 Minutes	Not Defined	.^Foot 1	A file access error detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1After 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.

2.18.9 Generic Incident

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

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
11g, 12cR1	Every 5 Minutes	Not Defined	.^Foot 1	Incident (%errCodes%) detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1After 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.

2.18.10 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*.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
11g, 12cR1	Every 5 Minutes	Not Defined	.^Foot 1	Internal error (%errCodes%) detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1After 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.

2.18.11 Impact

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

Target Version	Collection Frequency
11g, 12cR1	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.

2.18.12 Incident ID

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

Target Version	Collection Frequency
11g, 12cR1	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.

2.18.13 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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
11g, 12cR1	Every 5 Minutes	Not Defined	.^Foot 1	An internal SQL error detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1After 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.

2.18.14 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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
11g, 12cR1	Every 5 Minutes	Not Defined	.^Foot 1	Out of memory detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1After 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.

2.18.15 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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
11g	Every 5 Minutes	Not Defined	.^Foot 1	A data block was corrupted at time/line number: %timeLine%.

^Footnote 1After 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.

2.18.16 Session Terminated

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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
11g	Every 5 Minutes	Not Defined	.^Foot 1	A session termination detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1After 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.

2.19 Instance Disk Performance

The metrics in this category collect ASM instance disk performance data.

2.19.1 Bytes Read

This metric shows the number of bytes read.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.19.2 Bytes Written

This metric shows the number of bytes written.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.19.3 I/O Response Time (MS)

This metric shows the I/O response time in milliseconds.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.19.4 Last Read Errors

This metric shows the last read errors.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.19.5 Read Errors

This metric shows the number of read errors.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.19.6 Read Response Time (MS)

This metric shows the read response time in milliseconds.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.19.7 Read Time (MS)

This metric shows the read time in milliseconds.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.19.8 Total I/O Time (MS)

This metric shows the total I/O time in milliseconds.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.19.9 Write Errors

This metric shows the write errors.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.19.10 Write Response Time (MS)

This metric shows the write response time in milliseconds.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.19.11 Write Time (MS)

This metric shows the write time in milliseconds.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.20 Instance Diskgroup Database Performance

The metrics in this category collect ASM instance disk group database performance data.

2.20.1 Bytes Read

This metric shows the number of bytes read.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.20.2 Bytes Written

This metric shows the number of bytes written.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.20.3 Read Time (MS)

This metric shows the read time in milliseconds.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.20.4 Reads

This metric shows the number of reads.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.20.5 Writes

This metric shows the number of writes.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.20.6 Write Time (MS)

This metric shows the write time in milliseconds.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.21 Instance Diskgroup Performance

The metrics in this category collect ASM instance disk group performance data.

2.21.1 Bytes Read

This metric shows the number of bytes read.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.21.2 Bytes Written

This metric shows the number of bytes written.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.21.3 Read Time (MS)

This metric shows the read time in milliseconds.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.21.4 Reads

This metric shows the number of reads.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.21.5 Write Time (MS)

This metric shows the write time in milliseconds.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.21.6 Writes

This metric shows the number of writes.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.22 Instance Volume Performance

The metrics in this category 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.

2.22.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.

Target Version	Collection Frequency
11g, 12cR1	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.

2.22.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.

Target Version	Collection Frequency
11g, 12cR1	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.

2.22.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.

Target Version	Collection Frequency
11g, 12cR1	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.

2.22.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.

Target Version	Collection Frequency
11g, 12cR1	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.

2.22.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.

Target Version	Collection Frequency
11g, 12cR1	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.

2.22.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.

Target Version	Collection Frequency
11g, 12cR1	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.

2.22.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.

Target Version	Collection Frequency
11g, 12cR1	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.

2.22.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.

Target Version	Collection Frequency
11g, 12cR1	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.

2.22.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.

Target Version	Collection Frequency
11g, 12cR1	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.

2.22.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.

Target Version	Collection Frequency
11g, 12cR1	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.

2.22.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.

Target Version	Collection Frequency
11g, 12cR1	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.

2.22.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.

Target Version	Collection Frequency
11g, 12cR1	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.

2.22.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.

Target Version	Collection Frequency
11g, 12cR1	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.

2.23 Offline Disk Count

The metrics in this category collect ASM offline disk count information.

2.23.1 Offline Disk Count

This metric collects ASM offline disk count information.

Target Version	Collection Frequency
10g, 11g, 12c	Every 15 minutes

2.24 Operational Error

The metrics in this category 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. These errors are not triggered by ADR incidents but are day to day issues which you can handle without interaction with Oracle Support. 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.

Note:

For more information about Incident metrics and Operational Error metrics, log in to My Oracle Support and search for the following Oracle Support Note:

Database Alert log monitoring in 12c explained (Doc ID 1538482.1)

https://support.oracle.com/

2.24.1 Setting Thresholds for Operational Error Metrics

Warning Threshold: Not Defined; Critical Threshold.

In this case, the Management Agent generates a critical error alert in Enterprise Manager when the error occurs.
Warning Threshold: Critical Threshold: Not Defined

In this case, the Management Agent generates a warning alert in Enterprise Manager when the error occurs.
Warning Threshold: Not Defined; Critical Threshold: Not Defined

In this case, the Management Agent does not generate an alert in Enterprise Manager when the error occurs.

2.24.2 Alert Log Error Trace File

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

Target Version	Collection Frequency
11g, 12c	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.

2.24.3 Alert Log Name

This metric is the name of the alert log file.

Target Version	Collection Frequency
11g, 12c	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.

2.24.4 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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
11g, 12cR1	Every 5 Minutes	Not Defined	.^Foot 1	A data block was corrupted at time/line number: %timeLine%.

^Footnote 1After 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.

2.24.5 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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
11g, 12cR1	Every 5 Minutes	Not Defined	.^Foot 1	Operational error (%errCodes%) detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1After 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.

2.24.6 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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
11g, 12cR1	Every 5 Minutes	Not Defined	.^Foot 1	Media failure detected in %alertLogName% at time/line number: %timeLine%.

^Footnote 1After 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.

2.25 Response

The metrics in this category show 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.

2.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.

Target Version	Evaluation and Collection Frequency	Default Warning Threshold	Default Critical Threshold	Alert Text
All Versions	Every 5 Minutes	Not Defined	0	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.