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

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

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

5 Database Instance

This chapter provides information about the Database Instance metrics.

5.1 Alert Log

Note:

Oracle recommends using the DB Alert Log metrics instead of the Alert Log metrics.

For information about the DB Alert Log metrics, see Section 5.25, "DB Alert Log".

The metrics in this category are used to create the alert log, for example, data block corruption, terminated session, and so on. The Alert Log metrics raise an alert containing the Error text and, when relevant, a link to the trace file for each ORA error that is reported in the alert log that matches the warning or critical thresholds defined for each category of error returned by the metric as defined in Metrics and Policy Settings but does not match the Alert Log Filter Expression.

Note:

The Alert Log and Alert Log Error Status metrics only return ORA errors from the Alert log. If the error is not an ORA error it will not be recognized by this metric. If you need to alert for non-ORA errors in the Alert Log it is suggested that you create a UDM for these purposes. See My Oracle Support Note 735137.1 for details.

Alert Log Filtering Expression

The Alert Log Filter Expression is used (at the discretion of the Grid Control administrator responsible for that target) to prevent errors that can be ignored resulting in alerts being raised in Grid Control. It is a Perl regular expression that is used to filter all rows returned by the Alert Log metric.

The filtering takes place during the retrieval of errors from the Alert log and therefore no errors that match the expression are considered by either the Alert Log metric or, by definition, the Alert Log Error Status metric. Only those errors that do not match the Alert Log Filter Expression are compared against the Alert Log metric thresholds or counted for the Alert Log Error Status metric.

The Alert Log Filter Expression can be configured in several locations in Cloud Control for each target. It can be configured by clicking on the link next to 'Alert Log' under 'Diagnostic Summary' from the DB Target home page and then clicking 'Generic Alert Log Error Monitoring Configuration' under 'Related Links' or it can be configured from any of the 'Metrics and Policy Settings' pages for configuring the thresholds for each category of each metric.

Note:

The Alert Log Filter Expression is set at target level. No matter which page you use to configure it, you are configuring the same expression.

5.1.1 Alert Log Error Trace File

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

Target Version Collection Frequency
All versions Every 15 minutes

Data Source

The following command is the data source for this metric where $ORACLE_HOME refers to the home of the Oracle Management Agent:

$ORACLE_HOME/sysman/admin/scripts/alertlog.pl

User Action

No user action is required.

5.1.2 Alert Log Name

This metric reports the name of the alert log file.

Target Version Collection Frequency
All versions Every 15 minutes

Data Source

The following command is the data source for this metric where $ORACLE_HOME refers to the home of the Oracle Management Agent:

$ORACLE_HOME/sysman/admin/scripts/alertlog.pl

User Action

No user action is required.

5.1.3 Archiver Hung Alert Log Error

This metric signifies that the archiver of the database being monitored has been temporarily suspended since the last sample time.

If the database is running in ARCHIVELOG mode, an alert is displayed when archiving is hung (ORA-00257 and ORA-16038) messages are written to the ALERT file. The ALERT file is a special trace file containing a chronological log of messages and errors.

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

Footnote 1 After 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 following command is the data source for this metric where $ORACLE_HOME refers to the home of the Oracle Management Agent:

$ORACLE_HOME/sysman/admin/scripts/alertlog.pl

User Action

Examine the ALERT log and archiver trace file for additional information. However, the most likely cause of this message is that the destination device is out of space to store the redo log file. Verify the device specified in the initialization parameter ARCHIVE_LOG_DEST is set up properly for archiving. Note: This event does not automatically clear because there is no automatic way of determining when the problem has been resolved. Therefore, you must manually clear the event after the problem is fixed.

5.1.4 Data Block Corruption Alert Log Error

This metric signifies that the database being monitored has generated a corrupted block error 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 (ORA-01157, ORA-01578, and ORA-27048) are written to the ALERT file.

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

Footnote 1 After 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 following command is the data source for this metric where $ORACLE_HOME refers to the home of the Oracle Management Agent:

$ORACLE_HOME/sysman/admin/scripts/alertlog.pl

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 must manually clear the event after the problem is fixed.

5.1.5 Generic Alert Log Error

This metric signifies that the database 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. An alert event is triggered when Oracle Exception (ORA-006xx) messages are written to the ALERT log file. A warning is displayed when other ORA messages are written to the ALERT log file.

  • For all supported databases monitored by Enterprise Manager release 10.2.0.4 Management Agent:

    Alert Log Filter - up to 1024 characters

    Warning or Critical Threshold - up to 256 characters

  • For all supported databases monitored by Enterprise Manager release 10.2.0.5 Management Agent:

    Alert Log Filter - up to 4000 characters

    Warning or Critical Threshold - up to 4000 characters

Archiver hung (ORA-00257) and data block corrupted (ORA-01578) messages are sent out as separate metrics.

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

Footnote 1 After 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 following command is the data source for this metric where $ORACLE_HOME refers to the home of the Oracle Management Agent:

$ORACLE_HOME/sysman/admin/scripts/alertlog.pl

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 must manually clear the event after the problem is fixed.

5.1.6 Media Failure Alert Log Error

This metric represents the media failure alert log error. An alert event is triggered when messages ORA-01242 and ORA-01243 are written to the ALERT file.

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

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

Not available.

User Action

No user action is required.

5.1.7 Session Terminated Alert Log Error

This metric signifies that a session terminated unexpectedly since the last sample time. The ALERT file is a special trace file containing a chronological log of messages and errors. An alert is displayed when session unexpectedly terminated (ORA-00603) messages are written to the ALERT file.

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

Footnote 1 After 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 for this metric is $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 and the session trace file 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 must manually clear the event after the problem is fixed.

5.2 Alert Log Error Status

Note:

Oracle recommends that you use DB Alert Log Error Status metrics instead of Alert Log Error Status metrics.

For information about the DB Alert Log Error Status metrics, see Section 5.26, "DB Alert Log Error Status".

The metrics in this category count the number of errors returned in each category by the Alert Log Error metric after the Alert Log Filter expression has been taken into account but without taking the thresholds of the Alert Log Error metric into account and raises an alert if the number is greater than that specified in the Warning or Critical thresholds for that category. Therefore, it is possible for no alert to be raised by the Alert Log Error metric but still for the Alert Log Error Status metric to fire (even if the thresholds defined for the Alert Log Error metric are not matched). For more information on the Alert Log Filter Expression, see Alert Log Filtering Expression.

5.2.1 Archiver Hung Alert Log Error Status

This metric reflects the number of Archiver Hung alert log errors witnessed the last time Enterprise Manager scanned the Alert Log.

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

Data Source

The source of this metric is the Alert Log metric.

User Action

Examine the Alert Log.

5.2.2 Data Block Corruption Alert Log Error Status

This metric reflects the number of Data Block Corruption alert log errors witnessed the last time Enterprise Manager scanned the Alert Log.

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

Data Source

The source of this metric is the Alert Log metric.

User Action

Examine the Alert Log.

5.2.3 Generic Alert Log Error Status

This metric reflects the number of Generic alert log errors witnessed the last time Enterprise Manager scanned the Alert Log.

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

Data Source

The source of this metric is the Alert Log metric.

User Action

Examine the Alert Log.

5.2.4 Media Failure Alert Log Error Status

This metric represents the media failure alert log error status.

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

Data Source

Not available.

User Action

No user action is required.

5.2.5 Session Terminated Alert Log Error Status

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

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

Data Source

The source of this metric is the Alert Log metric.

User Action

Examine the Alert Log.

5.3 Archive Area

This metric category contains the metrics representing the utilization of the archive areas.

If the database is running in ARCHIVELOG mode, these metrics check for available redo log destinations. If the database is not running in ARCHIVELOG mode, these metrics fail to register. For each destination, this metric category returns the total, used, and free space.

5.3.1 Archive Area Used (%)

The Archive Full (%) metric returns the percentage of space used on the archive area destination. If the space used is more than the threshold value given in the threshold arguments, then a warning or critical alert is generated.

If the database is running in ARCHIVELOG mode, these metrics check the space in the available local redo log destinations. If the database is not running in ARCHIVELOG mode, these metrics are not applicable. For each local destination, this metric category returns the total, used, and free space.

Note:

For databases that are configured to archive to the Fast Recovery Area, the Archive Area metrics (Archive Area Used(%), Archive Area Used (KB), Free Archive Area (KB), and Total Archive Area (KB)) are not applicable. Instead, use the Recovery Area Free Space(%) metric to monitor Fast Recovery Area usage.
Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 15 Minutes After Every Sample > 80 Not Defined 1 %value%%% of archive area %archDir% is used.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each Archive Area Destination object.

If warning or critical threshold values are currently set for any Archive Area Destination 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 Archive Area Destination object, use the Edit Thresholds page.

Data Source

If no quota is set for archive area, the percentage is calculated using the UNIX df -k command.

If a quota is set, the following formula is used:

archive area used (%) = (total area used / total archive area) * 100

User Action

Verify the device specified in the initialization parameter LOG_ARCHIVE_DEST is set up properly for archiving.

There are two methods you can use to specify archive destinations. These destinations can be setup using Enterprise Manager. For each database target, you can drill-down to the database Availability tab, and access the Recovery Settings page.

  • The first method is to use the LOG_ARCHIVE_DEST_n parameter (where n is an integer from 1 to 10) to specify from one to ten different destinations for archival. Each numerically-suffixed parameter uniquely identifies an individual destination, for example, LOG_ARCHIVE_DEST_1, LOG_ARCHIVE_DEST_2, and so on.

  • The second method, which allows you to specify a maximum of two locations, is to use the LOG_ARCHIVE_DEST parameter to specify a primary archive destination and the LOG_ARCHIVE_DUPLEX_DEST parameter to determine an optional secondary location.

If the LOG_ARCHIVE_DEST initialization parameter is set up correctly and this metric triggers, then free up more space in the destination specified by the archive destination parameters.

5.3.2 Archive Area Used (KB)

This metric represents the total space used (in KB) on the device containing the archive destination directory.

Note:

For databases that are configured to archive to the Fast Recovery Area, the Archive Area metrics (Archive Area Used(%), Archive Area Used (KB), Free Archive Area (KB), and Total Archive Area (KB)) are not applicable. Instead, use the Recovery Area Free Space(%) metric to monitor Fast Recovery Area usage.
Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

If no quota is set for archive area, this is calculated through the UNIX df -k command.

total area used = quota_used * db_block_size (in KB)

User Action

Verify the device specified in the initialization parameter LOG_ARCHIVE_DEST is set up properly for archiving.

There are two methods you can use to specify archive destinations. These destinations can be setup using Enterprise Manager. For each database target, you can drill-down to the database Availability tab, and access the Recovery Settings page.

  • The first method is to use the LOG_ARCHIVE_DEST_n parameter (where n is an integer from 1 to 10) to specify from one to ten different destinations for archival. Each numerically-suffixed parameter uniquely identifies an individual destination, for example, LOG_ARCHIVE_DEST_1, LOG_ARCHIVE_DEST_2, and so on.

  • The second method, which allows you to specify a maximum of two locations, is to use the LOG_ARCHIVE_DEST parameter to specify a primary archive destination and the LOG_ARCHIVE_DUPLEX_DEST parameter to determine an optional secondary location.

If the LOG_ARCHIVE_DEST initialization parameter is set up correctly and this metric triggers, then free up more space in the destination specified by the archive destination parameters.

5.3.3 Free Archive Area (KB)

When running a database in ARCHIVELOG mode, the archiving of the online redo log is enabled. Filled groups of the online redo log are archived, by default, to the destination specified by the LOG_ARCHIVE_DEST initialization parameter. If this destination device becomes full, the database operation is temporarily suspended until disk space is available.

If the database is running in ARCHIVELOG mode, this metric checks for available redo log destination devices.

If the database is not running in ARCHIVELOG mode, this metric fails to register.

Note:

For databases that are configured to archive to the Fast Recovery Area, the Archive Area metrics (Archive Area Used(%), Archive Area Used (KB), Free Archive Area (KB), and Total Archive Area (KB)) are not applicable. Instead, use the Recovery Area Free Space(%) metric to monitor Fast Recovery Area usage.
Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 15 Minutes After Every Sample < Not Defined Not Defined 1 Archive area %archDir% has %value% free KB remaining.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each Archive Area Destination object.

If warning or critical threshold values are currently set for any Archive Area Destination 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 Archive Area Destination object, use the Edit Thresholds page.

Data Source

If the database is in NOARCHIVELOG mode, then nothing is collected.

If the database is in ARCHIVELOG mode, log_archive_destination from v$parameter is queried to obtain the current list of archivelog destinations. The results are obtained by directly checking the disk usage (df -kl).

User Action

Verify the device specified in the initialization parameter LOG_ARCHIVE_DEST is set up properly for archiving.

There are two methods you can use to specify archive destinations. These destinations can be setup using Enterprise Manager. For each database target, you can drill-down to the database Availability tab, and access the Recovery Settings page.

  • The first method is to use the LOG_ARCHIVE_DEST_n parameter (where n is an integer from 1 to 10) to specify from one to ten different destinations for archival. Each numerically-suffixed parameter uniquely identifies an individual destination, for example, LOG_ARCHIVE_DEST_1, LOG_ARCHIVE_DEST_2, and so on.

  • The second method, which allows you to specify a maximum of two locations, is to use the LOG_ARCHIVE_DEST parameter to specify a primary archive destination and the LOG_ARCHIVE_DUPLEX_DEST parameter to determine an optional secondary location.

If the LOG_ARCHIVE_DEST initialization parameter is set up correctly and this metric triggers, then free up more space in the destination specified by the archive destination parameters.

5.3.4 Total Archive Area (KB)

This metric represents the total space (in KB) on the device containing the archive destination directory.

Note:

For databases that are configured to archive to the Fast Recovery Area, the Archive Area metrics (Archive Area Used(%), Archive Area Used (KB), Free Archive Area (KB), and Total Archive Area (KB)) are not applicable. Instead, use the Recovery Area Free Space(%) metric to monitor Fast Recovery Area usage.
Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

If no quota is set for archive area, the data is calculated through the UNIX df -k command.

If a quota is set, the following formula is used:

total archive area = quota_size * db_block_size (in KB)

User Action

Oracle recommends that multiple archivelog destinations across different disks be configured. When at least one archivelog destination gets full, Oracle recommends the following:

  • If tape is being used, back up archive logs to tape and delete the archive logs.

  • If tape is not being used, back up the database and remove obsolete files. This also removes archive logs that are no longer needed based on the database retention policy.

  • If archivelog destination quota_size is being used, raise the quota_size.

5.4 Collect SQL Response Time

The metrics in the this category represent the SQL response time.

5.4.1 SQL Response Time (%)

This metric represents the SQL response time.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

Not available.

User Action

No user action is required.

5.5 Data Failure

The metrics in this category report data failures.

5.5.1 Alert Log Name

This metric reports the name of the alert log file.

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

Data Source

The source for the data is $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.

5.5.2 Data Failure Detected

This metric signifies that a database health checker has detected one or more persistent data failures. Examples of data failures include missing files, corrupt files, inconsistent files, and corrupt blocks. The alert shows the number of data failures detected by a checker run. Details of individual data failures can be accessed from the Perform Recovery page in Enterprise Manager.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 5 Minutes After Every Sample MATCH Not Defined .Foot 1  1Foot 2  Checker run found %numberOfFailures% new persistent data failures.

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

Footnote 2 After 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 for the data is $ORACLE_HOME/sysman/admin/scripts/alertlogAdr.pl where $ORACLE_HOME refers to the home of the Oracle Management Agent.

User Action

Details of individual data failures can be accessed from the Perform Recovery page in Enterprise Manager. Note: This event does not automatically clear because there is no automatic way of determining when the problem has been resolved. Therefore, you must manually clear the event after the problem is fixed.

5.6 Data Guard Status

The metrics in this category check the status, data not received, and data not applied for the databases in the Data Guard configuration.

5.6.1 Data Guard Status

This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.

Use the Data Guard Status metric to check the status of each database in the Data Guard configuration.

By default, a critical and warning threshold value was set for this metric column. Alerts will be generated when threshold values are reached. You can edit the value for a threshold as required.

Table 5-1 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

10gR2, 11g, 12c

Every 5 Minutes

After Every Sample

CONTAINS

Warning

Error

1

The Data Guard status of %dg_name% is %value%.


User Action

  1. Check the Edit Properties General page for the primary and standby databases for detailed information.

  2. Examine the database alert logs and the Data Guard broker logs for additional information.

5.7 Data Guard - 9.2 Database

The metrics in this category check the status, data not received, and data not applied for the databases in the Data Guard configuration. The metrics run on the primary database and cover conditions for all databases in the Data Guard configuration, including the primary and all physical and logical standby databases. They are applicable to both broker and non-broker Data Guard configurations.

5.7.1 Data Not Applied (logs)

This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.

The broker computes the highest applied SCN and uses its value to find the last continuous log that was successfully archived to the standby database. Redo data in all subsequent log files are counted as logs not applied. If the primary database goes down at this point, the redo data from these log files can be applied on the standby database. If there is a gap in the log files received on the standby database, any log files received after the gap cannot be applied.

For example, if log files 1, 2, 3, 6, 7, and 9 are received on the standby database and log apply services is currently applying log 1, log apply services can continue to apply up to log 3. Log apply services cannot apply any more log files because log 4 is missing.

Even though log files 6, 7, and 9 are received, they cannot be applied and they will not be counted as data not applied.

If all the archived log files on the standby database are continuous, and standby redo logs are used, the standby redo logs are also counted as data not applied, unless real-time apply is turned on and log apply services is already working on the standby redo log files.

If the standby redo logs are multithreaded, the broker computes the highest applied SCN for every thread and totals the numbers. If there are multiple incarnations and the standby database is in a different incarnation from the primary database, each incarnation is computed separately and the results are then totaled.

Table 5-2 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

9iR2

Every 5 Minutes

After Every Sample

>

1

3

-

Standby database %dg_name% has not applied the last %value% received logs.


5.7.2 Data Not Received (logs)

This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.

The broker computes the highest applied SCN and uses its value to find the last continuous log file that was successfully archived to the standby database. Redo data in all subsequent log files, including the current online redo log file, are counted as log files for potential data loss and will be unrecoverable if the primary database goes down at this point.

For example, if log files 1, 2, 3, 6, 7, and 9 are received on the standby database, and if log 10 is the current online log file, and if log apply services are currently applying log 1, the last continuous log after the highest applied SCN is log 3. All log files after log 3, that is log files 4 through 10, are counted as data not received. If the primary database goes down at this point, all redo data in log files 4 through 10 are lost on the standby database.

If the primary database is multithreaded (in a RAC database), the broker computes the highest applied SCN for every thread and totals the numbers. If the primary database has multiple incarnations (for example, due to a flashback operation) and the standby database is in a different incarnation from the primary database, the computation is done on each incarnation and the results are then totaled.

Table 5-3 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

9iR2

Every 5 Minutes

After Every Sample

>

1

3

-

Standby database %dg_name% has not received the last %value% logs from the primary database.


5.7.3 Data Guard Status - 9.2 Database

This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.

Use the Data Guard Status metric to check the status of each database in the Data Guard configuration.

By default, a critical and warning threshold value was set for this metric column. Alerts will be generated when threshold values are reached. You can edit the value for a threshold as required.

Table 5-4 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

9iR2

Every 5 Minutes

After Every Sample

CONTAINS

Warning

Error

-

The Data Guard status of %dg_name% is %value%.


5.8 Data Guard - 10.1 Database

The metrics in this category check the status, data not received, and data not applied for the databases in the Data Guard configuration. The metrics run on the primary database and cover conditions for all databases in the Data Guard configuration, including the primary and all physical and logical standby databases. It is applicable to both broker and non-broker Data Guard configurations.

For non-broker configurations, the metrics are limited to monitoring primary database redo transport destination errors (as reflected in the ERRORS column of v$archive_dest).

For broker configurations, the metrics are based on the Data Guard broker health check, which covers a much broader range of issues.

5.8.1 Data Guard Status - 10.1 Database

This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.

Use the Data Guard Status metric to check the status of each database in the Data Guard configuration.

By default, a critical and warning threshold value was set for this metric column. Alerts will be generated when threshold values are reached. You can edit the value for a threshold as required.

Table 5-5 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

10gR1

Every 5 Minutes

After Every Sample

CONTAINS

Warning

Error

1

The Data Guard status of %dg_name% is %value%.


Data Source

The source of the data is:

Non-broker: v$archive_dest on primary database

Broker: Data Guard broker on primary database

User Action

  1. Check the Edit Properties General page for the primary and standby databases for detailed information.

  2. Examine the database alert logs and the Data Guard broker logs for additional information.

5.8.2 Data Not Applied (logs)

This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.

The broker computes the highest applied SCN and uses its value to find the last continuous log that was successfully archived to the standby database. Redo data in all subsequent log files are counted as logs not applied. If the primary database goes down at this point, the redo data from these log files can be applied on the standby database. If there is a gap in the log files received on the standby database, any log files received after the gap cannot be applied.

For example, if log files 1, 2, 3, 6, 7, and 9 are received on the standby database and log apply services is currently applying log 1, log apply services can continue to apply up to log 3. Log apply services cannot apply any more log files because log 4 is missing. Even though log files 6, 7, and 9 are received, they cannot be applied and they will not be counted as data not applied.

If all the archived log files on the standby database are continuous, and standby redo logs are used, the standby redo logs are also counted as data not applied, unless real-time apply is turned on and log apply services is already working on the standby redo log files.

If the standby redo logs are multithreaded, the broker computes the highest applied SCN for every thread and totals the numbers. If there are multiple incarnations and the standby database is in a different incarnation from the primary database, each incarnation is computed separately and the results are then totaled.

Table 5-6 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

10gR1

Every 5 Minutes

After Every Sample

>

1

3

-

Standby database %dg_name% has not applied the last %value% received logs.


Data Source

The source of the data is:

Non-broker: v$archive_dest on primary database

Broker: Data Guard broker on primary database

5.8.3 Data Not Applied (MB)

This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.

The broker computes the highest applied SCN and uses its value to find the last continuous log that was archived to the standby database. The size of redo data in all subsequent log files are counted as data not applied. If the primary database goes down at this point, redo from these log files can be applied on the standby database. If there is a gap in the log files received on the standby database, any log files received after the gap cannot be applied.

For example, if log files 1, 2, 3, 6, 7, and 9 are received on the standby database and log apply services is currently applying log 1, log apply services can continue to apply up to log 3. Log apply services cannot apply any more log files because log 4 is missing. Even though log files 6, 7, and 9 are received, they cannot be applied and they will not be counted as data not applied. In this case, the total size of log files 1, 2, and 3 is the size of Data Not Applied.

If all the archived log files on the standby database are continuous, and standby redo log files are used, the standby redo log files are also counted as data not applied, unless real-time apply is turned on and log apply services is already working on the standby redo log files. The size of an archived log file is its file size. However, the size of a standby redo log is the size of the actual redo in the log and not the file size.

If the standby redo log files are multithreaded, the broker computes the highest applied SCN for every thread and totals the numbers. If there are multiple incarnations and the standby database is in a different incarnation from the primary database, each incarnation is computed separately and the results are then totaled.

Table 5-7 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

10gR1

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

-

Standby database %dg_name% has not applied the last %value% megabytes of data received.


Data Source

The source of the data is:

Non-broker: v$archive_dest on primary database

Broker: Data Guard broker on primary database

5.8.4 Data Not Received (logs)

This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.

The broker computes the highest applied SCN and uses its value to find the last continuous log file that was successfully archived to the standby database. Redo data in all subsequent log files, including the current online redo log file, are counted as log files for potential data loss and will be unrecoverable if the primary database goes down at this point.

For example, if log files 1, 2, 3, 6, 7, and 9 are received on the standby database, and if log 10 is the current online log file, and if log apply services are currently applying log 1, the last continuous log after the highest applied SCN is log 3. All log files after log 3, that is log files 4 through 10, are counted as data not received. If the primary database goes down at this point, all redo data in log files 4 through 10 are lost on the standby database.

If the primary database is multithreaded (in a RAC database), the broker computes the highest applied SCN for every thread and totals the numbers. If the primary database has multiple incarnations (for example, due to a flashback operation) and the standby database is in a different incarnation from the primary database, the computation is done on each incarnation and the results are then totaled.

Table 5-8 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

10gR1

Every 5 Minutes

After Every Sample

>

1

3

-

Standby database %dg_name% has not received the last %value% logs from the primary database.


Data Source

The source of the data is:

Non-broker: v$archive_dest on primary database

Broker: Data Guard broker on primary database

5.8.5 Data Not Received (MB)

This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.

The broker computes the highest applied SCN and uses its value to find the last continuous log file that was successfully archived to the standby database. The size of redo data in all subsequent log files, including the current online redo log file, are counted as data for potential data loss and will be unrecoverable if the primary database goes down at this point. The size of an archived log file is its file size, and the size of the online redo log file is the size of the actual redo in the online log file, not the file size of the online redo log file.

For example, if log files 1, 2, 3, 6, 7, and 9 are received on the standby database, and if log 10 is the current online log file, and if log apply services is currently applying log 1, the last continuous log after the highest applied SCN is log 3. All log files after log 3, that is log files 4 through 10, are counted as data not received and the total size of redo data in these log files is the size of Data Not Received.

If the primary database is multithreaded (in a RAC database), the broker computes the highest applied SCN for every thread and totals the numbers. If the primary database has multiple incarnations (for example, due to a flashback operation) and the standby database is in a different incarnation from the primary database, the computation is done on each incarnation and the results are then totaled.

Table 5-9 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

10gR1

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

-

Standby database %dg_name% has not received the last %value% megabytes of data from the primary database.


Data Source

The source of the data is:

Non-broker: v$archive_dest on primary database

Broker: Data Guard broker on primary database

5.9 Data Guard Fast-Start Failover

The metrics in this category are database-level metrics. For cluster databases, these metrics are monitored at the cluster database target level and not by member instances.

5.9.1 Fast-Start Failover Occurred

This metric indicates the time that a fast-start failover occurred when the primary database became unavailable.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10gR2 Every 5 minutes After every sample EQUAL Not Defined 1 - A fast-start failover occurred at %dg_fs_time%.

5.10 Data Guard Fast-Start Failover Observer

The metrics in this category monitor the state of the fast-start failover observer.

5.10.1 Observer Status

This metric generates a critical alert on the primary database if the fast-start failover (FSFO) configuration is in an unobserved condition, indicating that FSFO is not currently possible.

Table 5-10 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

11g, 12c

Every 1 Minute

After Every Sample

CONTAINS

Not Defined

Error

-

The Data Guard fast-start failover observer status is %value%.


User Action

If the Data Guard configuration was configured in Cloud Control to use the automatic Observer restart feature, the alert will clear after a new observer process is restarted. Otherwise, determine the cause of the unobserved condition, and restart the Observer process if necessary.

5.11 Data Guard Fast-Start Failover Observer - 10.2 Database

The metrics in this category monitor the state of the fast-start failover observer.

5.11.1 Observer Status - 10.2 Database

This metric generates a critical alert on the primary database if the fast-start failover (FSFO) configuration is in an unobserved condition, indicating that FSFO is not currently possible.

Table 5-11 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

10gR2

Every 5 Minutes

After Every Sample

CONTAINS

Not Defined

Error

-

The Data Guard fast-start failover observer status is %value%.


User Action

If the Data Guard configuration was configured in Cloud Control to use the automatic Observer restart feature, the alert will clear after a new observer process is restarted. Otherwise, determine the cause of the unobserved condition, and restart the Observer process if necessary.

5.12 Data Guard Performance

The metrics in this category report on Data Guard performance.

5.12.1 Apply Lag (seconds)

This metric displays (in seconds) how far the standby is behind the primary.

This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.

Table 5-12 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

11gR2, 12c

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

-

The standby database is approximately %value% seconds behind the primary database.


Data Source

The source of the data is the v$dataguard_stats('apply lag') view.

5.12.2 Estimated Failover Time (seconds)

This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.

This metric shows the approximate number of seconds required to failover to this standby database. This accounts for the startup time, if necessary, plus the remaining time required to apply all the available redo on the standby. If a bounce is not required, it is only the remaining apply time.

Table 5-13 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

11gR2, 12c

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

-

The estimated time to failover is approximately %value% seconds.


Data Source

The data is derived from the following formula:

v$dataguard_stats ('estimated startup time','apply finish time','standby has been open')

5.12.3 Redo Apply Rate (KB/second)

This metric displays the Redo Apply Rate in KB/second on this standby.

This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.

Table 5-14 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

11gR2, 12c

Every 5 Minutes

After Every Sample

<

Not Defined

Not Defined

-

The redo apply rate is %value% KB/sec.


5.12.4 Redo Generation Rate (KB/second)

This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.

Table 5-15 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

10gR2,11g, 12c

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

-

The redo generation rate is %value% KB/sec.


5.12.5 Transport Lag (seconds)

The approximate number of seconds of redo not yet available on this standby database. This may be because the redo has not yet been shipped or there may be a gap.

This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.

Data Source

The data is derived from the following formula:

v$dataguard_stats('transport lag')

Table 5-16 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

11gR2, 12c

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

-

The standby database is approximately %value% seconds behind the primary database.


5.13 Data Guard Performance - 11.1 and Prior Database

The metrics in this category report on Data Guard performance.

5.13.1 Estimated Failover Time (seconds) - 11.1 and Prior Database

This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.

This metric shows the approximate number of seconds required to failover to this standby database. This accounts for the startup time, if necessary, plus the remaining time required to apply all the available redo on the standby. If a bounce is not required, it is only the remaining apply time.

Table 5-17 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

10gR2, 11gR1

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

-

The estimated time to failover is approximately %value% seconds.


5.13.2 Apply Lag (seconds) - 11.1 and Prior Database

This metric displays (in seconds) how far the standby is behind the primary.

This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.

Table 5-18 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

10gR2, 11gR1

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

-

The standby database is approximately %value% seconds behind the primary database.


5.13.3 Transport Lag (seconds) - 11.1 and Prior Database

The approximate number of seconds of redo not yet available on this standby database. This may be because the redo has not yet been shipped or there may be a gap.

This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.

Table 5-19 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

10gR2, 11gR1

Every 5 Minutes

After Every Sample

>

Not Defined

Not Defined

-

There are approximately %value% seconds of redo not yet available on this standby database.


5.13.4 Redo Apply Rate (KB/second) - 11.1 and Prior Database

This metric displays the Redo Apply Rate in KB/second on this standby.

This is a database-level metric. For cluster databases, this metric is monitored at the cluster database target level and not by member instances.

Table 5-20 Metric Summary Table

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text

10gR2, 11gR1

Every 5 Minutes

After Every Sample

<

Not Defined

Not Defined

-

The redo apply rate is %value% KB/sec.


5.14 Database Files

The metrics in this category represent the average file read time and average file write time for the database files.

5.14.1 Average File Read Time (centi-seconds)

This metric represents the average file read time, measured in hundredths of a second.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 10 Minutes Not Defined After Every Sample > Not Defined Not Defined 1 Generated By Database Server

Multiple Thresholds

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

If warning or critical threshold values are currently set for any File 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 File Name object, use the Edit Thresholds page.

Data Source

Not available.

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.14.2 Average File Write Time (centi-seconds)

This metric represents the average file write time, measured in hundredths of a second.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 10 Minutes Not Defined After Every Sample > Not Defined Not Defined 1 Generated By Database Server

Multiple Thresholds

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

If warning or critical threshold values are currently set for any File 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 File Name object, use the Edit Thresholds page.

Data Source

Not available.

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.15 Database Job Status

The metrics in this category represent the health of database jobs registered through the DBMS_SCHEDULER interface.

5.15.1 Broken Job Count

The Oracle Server job queue is a database table that stores information about local jobs such as the PL/SQL call to execute for a job such as when to run a job. Database replication is also managed by using the Oracle job queue mechanism using jobs to push deferred transactions to remote master sites, to purge applied transactions from the deferred transaction queue or to refresh snapshot refresh groups.

A job can be broken in two ways:

  • Oracle has failed to successfully execute the job after sixteen attempts.

  • The job has been explicitly marked as broken by using the procedure DBMS_ JOB.BROKEN.

This metric checks for broken DBMS jobs. A critical alert is generated if the number of broken jobs exceeds the value specified by the threshold argument.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 5 Minutes Not Uploaded > 0 Not Defined 1 %value% job(s) are broken.

Data Source

The data is derived from the following formula:

SELECT COUNT(*)
  FROM dba_jobs
  WHERE broken [less] [greater] 'N'

User Action

Check the ALERT log and trace files for error information. Correct the problem that is preventing the job from running. Force immediate re-execution of the job by calling DBMS_SCHEDULER.RUN.

5.15.2 Failed Job Count

The Oracle Server job queue is a database table that stores information about local jobs such as the PL/SQL call to execute for a job such as when to run a job. Database replication is also managed by using the Oracle job queue mechanism using jobs to push deferred transactions to remote master sites, to purge applied transactions from the deferred transaction queue or to refresh snapshot refresh groups.

If a job returns an error while Oracle is attempting to execute it, the job fails. Oracle repeatedly tries to execute the job doubling the interval of each attempt. If the job fails sixteen times, Oracle automatically marks the job as broken and no longer tries to execute it.

This metric checks for failed DBMS jobs. An alert is generated if the number of failed job exceeds the value specified by the threshold argument.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 5 Minutes Not Uploaded > 0 Not Defined 1 %value% job(s) are broken.

Data Source

The data is derived from the following formula:

SELECT COUNT(*) 
  FROM dba_jobs 
  WHERE NVL(failures, 0) <  > 0

User Action

Check the ALERT log and trace files for error information. Correct the problem that is preventing the job from running.

5.16 Database Limits

The metrics in this category represent the percentage of resource limitations at which the Oracle Server is operating.

5.16.1 Current Logons Count

This metric represents the current number of logons.

Note: Unlike most metrics, which accept thresholds as real numbers, this metric can only accept an integer as a threshold.

Target Version Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 10 minutes After Every Sample > Not Defined Not Defined 3 Generated By Database Server

Data Source

The data is derived from the current logins.

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.16.2 Current Open Cursors Count

This metric represents the current number of opened cursors.

Note: Unlike most metrics, which accept thresholds as real numbers, this metric can only accept an integer as a threshold.

Target Version Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 10 minutes After Every Sample > Not Defines Not Defined 3 Generated By Database Server

Data Source

The data is derived from the current open cursors.

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.16.3 Lock Limit Usage (%)

The DML_LOCKS initialization parameter specifies the maximum number of DML locks. The purpose of DML locks is to guarantee the integrity of data being accessed concurrently by multiple users. DML locks prevent destructive interference of simultaneous conflicting DML and/or DDL operations.

This metric checks for the utilization of the lock resource against the values (percentage) specified by the threshold arguments. If the percentage of all active DML locks to the limit set in the DML_LOCKS initialization parameter exceeds the values specified in the threshold arguments, then a warning or critical alert is generated.

If DML_LOCKS is 0, this test fails to register. A value of 0 indicates that enqueues are disabled.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 15 Minutes After Every Sample > Not Defined Not Defined 1 %target% has reached %value%%% of the lock limit.

Data Source

The data is derived from the following formula:

SELECT resource_name name, 
  100*DECODE(initial_allocation, ' UNLIMITED', 0, current_utilization / 
  initial_allocation) usage 
FROM v$resource_limit 
WHERE LTRIM(limit_value) 
  != '0' AND LTRIM(initial_allocation) != '0' AND resource_name = 'dml_locks'

User Action

Increase the DML_LOCKS instance parameter by 10%.

5.16.4 Process Limit Usage (%)

The PROCESSES initialization parameter specifies the maximum number of operating system user processes that can simultaneously connect to a database at the same time. This number also includes background processes utilized by the instance.

This metric checks for the utilization of the process resource against the values (percentage) specified by the threshold arguments. If the percentage of all current processes to the limit set in the PROCESSES initialization parameter exceeds the values specified in the threshold arguments, then a warning or critical alert is generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 15 Minutes After Every Sample > Not Defined Not Defined 1 %target% has reached %value%%% of the process limit.

Target Version Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g,11g, 12c Every 10 Minutes After Every Sample > Not Defined Not Defined 3 Generated By Database Server

Data Source

The data is derived from the following formula:

SELECT resource_name name, 
  100*DECODE(initial_allocation, ' UNLIMITED', 0, current_utilization) != '0' 
  AND resource_name = 'processes'

User Action

Verify that the current PROCESSES instance parameter setting has not exceeded the operating system-dependent maximum. Increase the number of processes to be at least 6 + the maximum number of concurrent users expected to log in to the instance.

5.16.5 Session Limit Usage (%)

The SESSIONS initialization parameter specifies the maximum number of concurrent connections that the database will allow.

This metric checks for the utilization of the session resource against the values (percentage) specified by the threshold arguments. If the percentage of the number of sessions, including background processes, to the limit set in the SESSIONS initialization parameter exceeds the values specified in the threshold arguments, then a warning or critical alert is generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 15 Minutes After Every Sample > Not Defined Not Defined 1 %target% has reached %value%%% of the session limit.

Target Version Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 10 Minutes After Every Sample > Not Defined Not Defined 3 Generated By Database Server

Data Source

The data is derived from the following formula:

SELECT resource_name name, 
  100*DECODE(initial_allocation, ' UNLIMITED', 0, current_utilization) != '0' 
  AND resource_name = 'sessions' 

User Action

Increase the SESSIONS instance parameter. For XA environments, confirm that SESSIONS is at least 2.73 * PROCESSES. For shared server environments, confirm that SESSIONS is at least 1.1 * maximum number of connections.

5.16.6 User Limit Usage (%)

The LICENSE_MAX_SESSIONS initialization parameter specifies the maximum number of concurrent user sessions allowed simultaneously.

This metric checks whether the number of users logged on is reaching the license limit. If the percentage of the number of concurrent user sessions to the limit set in the LICENSE_MAX_SESSIONS initialization parameter exceeds the values specified in the threshold arguments, then a warning or critical alert is generated. If LICENSE_MAX_SESSIONS is not explicitly set to a value, the test does not trigger.

Note: This metric is most useful when session licensing is enabled. Refer to the Oracle Server Reference Manual for more information on LICENSE_MAX_SESSIONS and LICENSE_MAX_USERS.

Note: Unlike most metrics, which accept thresholds as real numbers, this metric can only accept an integer as a threshold.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 15 Minutes After Every Sample > Not Defined Not Defined 1 %target% has reached %value%%% of the user limit.

Target Version Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 10 Minutes After Every Sample > Not Defined Not Defined 3 Generated By Database Server

Data Source

The data is derived from the following formula:

SELECT 'user' name, 
  100*DECODE(session_max, 0, 0, sessions_current/session_max) usage 
  FROM v$license 

User Action

This typically indicates that the license limit for the database has been reached. You must acquire additional licenses, then increase LICENSE_MAX_ SESSIONS to reflect the new value.

5.17 Database Replay

The metrics in this category show the current status (on/off) of database workload capture and replay.

5.17.1 Workload Capture Status

This metric shows if the database workload capture is in progress.

This metric is available for Oracle Database 11g Release 2 and Oracle Database 12c.

Data Source

The source of the data is the server-generated alert triggered by the target database when a capture is started.

User Action

No user action is required.

5.17.2 Workload Replay Status

This metric shows if database workload replay is in progress.

This metric is available for Oracle Database 11g Release 2 and Oracle Database 12c.

Data Source

The source of the data is the server-generated alert triggered by the target database when a replay is started.

User Action

No user action is required.

5.18 Database Replay Client

The metrics in this category show the resource usage of the replay clients during database workload replay.

5.18.1 Average I/O Latency (milliseconds)

This metric reflects the average response time for a single I/O for a database replay client.

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

Target Version Collection Frequency
11gR2, 12c null

Data Source

The source of the data is the server-generated alert triggered by the target database when an alarming condition is detected in a replay client.

User Action

Run the calibrate utility of the replay client and restart a replay with the suggested number of replay clients, distributed between machines with the necessary capacity.

5.18.2 Replay Threads (%) Performing I/O

This metric represents the number of replay client connections performing I/O operation concurrently.

The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Cloud Control or the Enterprise Manager Database Control (if applicable).The following table shows how often the metric's value is collected.

Target Version Collection Frequency
11gR2, 12c null

Data Source

The source of the data is the server-generated alert triggered by the target database when an alarming condition is detected in a replay client.

User Action

Run the calibrate utility of the replay client and restart a replay with the suggested number of replay clients, distributed between machines with the necessary capacity.

5.18.3 Replay Threads (%) Using CPU

This metric represents the number of replay client connections using the CPU concurrently.

Target Version Collection Frequency
11gR2, 12c null

Data Source

The source of the data is the server-generated alert triggered by the target database when an alarming condition is detected in a replay client.

User Action

Run the calibrate utility of the replay client and restart a replay with the suggested number of replay clients, distributed between machines with the necessary capacity.

5.19 Database Services

The metrics in this category include the service CPU time and service response time.

5.19.1 Service CPU Time (per user call) (microseconds)

This metric represents the average CPU time, in microseconds, for calls to a particular database service.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute 10 minutes After Every Sample > Not Defined Not Defined 3 Generated By Database Server

Multiple Thresholds

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

If warning or critical threshold values are currently set for any Service 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 Service Name object, use the Edit Thresholds page.

Data Source

Not available.

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.19.2 Service Response Time (per user call) (microseconds)

This metric represents the average elapsed time, in microseconds, for calls to a particular database service.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute 10 minutes After Every Sample > Not Defined Not Defined 3 Generated By Database Server

Multiple Thresholds

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

If warning or critical threshold values are currently set for any Service 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 Service Name object, use the Edit Thresholds page.

Data Source

Not available.

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.20 Database Vault Attempted Violations - Command Rules

The metrics in this category monitor violation attempts against the Database Vault database.

5.20.1 Database Vault Attempted Violations Count - Command Rules

This metric is used to enable Database Vault Security Analyst to keep a watch on the violation attempts against the Database Vault database. Database Vault Security Analyst can pick the command rules he would like to get alerted on and even further filter them based on the different types of attempts by using error codes. This metric is not enabled out of the box. You must enable it from Metrics and Policy Settings page. By default, this metric is collected every 1 hour, but you can change the collection frequency.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
9iR2, 10g, 11g, 12c Every Hour Not Uploaded MATCH Not Defined Not Defined - %ACTION_OBJECT_NAME% got violated at %VIOLATIONTIMESTAMP%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of Database Vault Command Rule and Violation Time objects.

If warning or critical threshold values are currently set for any unique combination of Database Vault Command Rule and Violation Time 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 Database Vault Command Rule and Violation Time objects, use the Edit Thresholds page.

Data Source

The attempted violations are picked up from the target's database vault audit trail. Only audit entries related to command rule, which represent failed attempts to execute a SQL, are selected.

User Action

To know more about the violations, for example, the command that was violated, which database user triggered the violation, what action triggered this violation, and at what time this violation happened, login to the target's Database Vault Home Page and use the Attempted Violations charts.

5.21 Database Vault Attempted Violations - Realms

The metrics in this category monitor the violation attempts against the Database Vault database.

5.21.1 Database Vault Attempted Violations - Realms

This metric is used to enable Database Vault Security Analyst to keep a watch on the violation attempts against the Database Vault database. Database Vault Security Analyst can pick the realms he would like to get alerted on and even further filter them based on the different types of attempts by using error codes. This metric is not enabled out of the box. You must enable it from Metrics and Policy Settings page. By default, this metric is collected every 1 hour, but you can specify the collection frequency.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
9iR2, 10g, 11g, 12c Every Hour Not Uploaded MATCH Not Defined Not Defined - %ACTION_OBJECT_NAME% got violated at %VIOLATIONTIMESTAMP%

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of Database Vault Realm and Violation Time objects.

If warning or critical threshold values are currently set for any unique combination of Database Vault Realm and Violation Time 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 Database Vault Realm and Violation Time objects, use the Edit Thresholds page.

Data Source

The attempted violations are picked up from the target's Database Vault audit trail. Only audit entries related to realms, which represent failed attempts to execute a SQL, are selected.

User Action

To know more about the violations, for example, the realm that was violated, which database user triggered the violation, what action triggered this violation, and at what time this violation happened, login to the target's Database Vault Home Page and use the Attempted Violations charts.

5.22 Database Vault Configuration Issues - Command Rules

The metrics in this category track users' actions and raise alerts when there is a misconfiguration on a command rule that requires administrator attention.

5.22.1 DV (Command Rule) - Configuration Issue Count

After the Database Vault policies are defined and configured to protect the database, further user actions over the course of time can disturb these configurations. This metric tracks the users' actions and raises an alert when there is a misconfiguration on a Command Rule that needs administrator attention. This metric is enabled out of the box. By default this metric is collected every 1 hour, but you can change the collection frequency.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
9iR2, 10g, 11g, 12c Every Hour After Every Sample > Not Defined 0 1 %ACTION_OBJECT_NAME% has configuration issues.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each Database Vault Command Rule object.

If warning or critical threshold values are currently set for any Database Vault Command Rule 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 Database Vault Command Rule object, use the Edit Thresholds page.

Data Source

The configuration issues are picked from scanning the realm and command rule definitions.

User Action

To know the cause of the command rule misconfiguration, navigate to the target's Database Vault Home page, launch Database Vault Administrator, and view the Database Vault Configuration Issues Reports. These alerts are automatically cleared when the configuration issue is resolved.

5.23 Database Vault Configuration Issues - Realms

The metrics in this category track users' actions and raise alerts when there is a misconfiguration on a realm that requires administrator attention.

5.23.1 Database Vault Configuration Issues Count - Realms

After the Database Vault policies are defined and configured to protect the database, further user actions over the course of time can disturb these configurations. This metric tracks the users' actions and raises an alert when there is a misconfiguration on a Realm that needs administrator attention. This metric is enabled out of the box. By default this metric is collected every 1 hour, but you can change the collection frequency.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
9iR2, 10g, 11g, 12c Every Hour After Every Sample > Not Defined 0 1 %ACTION_OBJECT_NAME% has configuration issues.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each Database Vault Realm object.

If warning or critical threshold values are currently set for any Database Vault Realm 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 Database Vault Realm object, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page.

Data Source

The configuration issues are picked from scanning the realm and ruleset definitions.

User Action

To know the cause of the realm misconfiguration, navigate to the target's Database Vault Home page, launch Database Vault Administrator, and view the Database Vault Configuration Issues Reports. These alerts are automatically cleared when the configuration issue is resolved.

5.24 Database Vault Policy Changes

The metrics in this category track the Database Vault policies.

5.24.1 Database Vault Policy Changes Count

After the Database Vault policies are defined, further changes to it is tracked by this metric. On any changes to the Database Vault policies, this metric will raise an alert. This metric is enabled out of the box. By default this metric is collected every 1 hour, but you can change the collection frequency.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
9iR2, 10g, 11g, 12c Every Hour After Every Sample > Not Defined 0 1Foot 1  %POLICY_CATEGORY_NAMES% has Policy changes

Footnote 1 After 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 unique combination of DV Policy Change Category and DV Policy Change Time objects.

If warning or critical threshold values are currently set for any unique combination of DV Policy Change Category and DV Policy Change Time 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 DV Policy Change Category and DV Policy Change Time objects, use the Edit Thresholds page. See Editing Thresholds for information on accessing the Edit Thresholds page

Data Source

The policy changes are picked up from scanning the records in the Database Audit Trail related to Database Vault Schemas.

User Action

To know more about the policy changes, for example which object was changed, which database user changed the policy, what was the user action, and at what time this policy was changed, login to the target's Database Vault Home Page and view the Policy Changes Report.

5.25 DB Alert Log

The metrics in this category are used to create the alert log, for example, data block corruption, terminated session, and so on. The DB alert log metrics raise an alert containing the error text and, when relevant, a link to the trace file for each ORA error that is reported in the alert log that matches the warning or critical thresholds defined for each category of error returned by the metric as defined in the Metrics and Policy Settings but does not match the Alert Log Filter Expression.

Alert Log Filtering Expression

The Alert Log Filter Expression is used (at the discretion of the Cloud Control administrator responsible for that target) to prevent errors that can be ignored resulting in alerts being raised in Cloud Control. It is a Perl regular expression that is used to filter all rows returned by the Alert Log metric

The filtering takes place during the retrieval of errors from the Alert log and therefore no errors that match the expression are considered by either the Alert Log metric or, by definition, the Alert Log Error Status metric. Only those errors that do not match the Alert Log Filter Expression are compared against the Alert Log metric thresholds or counted for the Alert Log Error Status metric.

The Alert Log Filter Expression can be configured in several locations in Cloud Control for each target. It can be configured by clicking the link next to Alert Log under Diagnostic Summary from the DB Target home page and then clicking Generic Alert Log Error Monitoring Configuration under Related Links or it can be configured from any of the Metrics and Policy Settings pages for configuring the thresholds for each category of each metric.

5.25.1 Archiver Hung Alert Log Error

This metric signifies that the archiver of the database being monitored has been temporarily suspended since the last sample time.

If the database is running in ARCHIVELOG mode, an alert is displayed when archiving is hung (ORA-00257 and ORA-16038) messages are written to the ALERT file. The ALERT file is a special trace file containing a chronological log of messages and errors.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All versions Every 15 minutes After Every Sample CONTAINS Not Defined ORA- - The archiver hung at time/line number: %timeLine%.

Data Source

The source of the data is $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 and archiver trace file for additional information. However, the most likely cause of this message is that the destination device is out of space to store the redo log file. Verify the device specified in the initialization parameter ARCHIVE_LOG_DEST is set up properly for archiving.

Note:

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

5.25.2 Data Block Corruption Alert Log Error

This metric signifies that the database being monitored has generated a corrupted block error 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 (ORA-01157, ORA-01578, and ORA-27048) are written to the ALERT file.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All versions Every 15 minutes After Every Sample CONTAINS Not Defined ORA- - A data block was corrupted at time/line number: %timeLine%.

Data Source

The source of the data is $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.

Note:

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

5.25.3 Generic Alert Log Error

This metric signifies that the database 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. An alert event is triggered when Oracle Exception (ORA-006xx) messages are written to the ALERT log file. A warning is displayed when other ORA messages are written to the ALERT log file.

  • For all supported databases monitored by Enterprise Manager release 10.2.0.4 Management Agent:

    Alert Log Filter - up to 1024 characters

    Warning or Critical Threshold - up to 256 characters

  • For all supported databases monitored by Enterprise Manager release 10.2.0.5 Management Agent:

    Alert Log Filter - up to 4000 characters

    Warning or Critical Threshold - up to 4000 characters

Archiver hung (ORA-00257) and data block corrupted (ORA-01578) messages are sent out as separate metrics.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All versions Every 15 minutes After Every Sample MATCH ORA-0*(600?|7445|4[0-9][0-9][0-9])[^0-9] Not Defined - ORA-error stack (%errCodes%) logged in %alertLogName%.

5.25.4 Media Failure Alert Log Error

This metric indicates that the database being monitored has generated a media failure error to the ALERT file since the last sample time.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All versions Every 15 minutes After Every Sample CONTAINS Not Defined ORA- - Media failure was detected at time/line number: %timeLine%.

5.25.5 Session Terminated Alert Log Error

This metric indicates that the database being monitored has generated a session terminated message to the ALERT file since the last sample time.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All versions Every 15 minutes After Every Sample CONTAINS ORA- Not Defined - A session was terminated at time/line number: %timeLine%.

5.26 DB Alert Log Error Status

The metrics in this category count the number of errors returned in each category by the DB Alert Log Error metric after the Alert Log Filter expression has been taken into account but without taking the thresholds of the DB Alert Log Error metric into account and raises an alert if the number is greater than that specified in the Warning or Critical thresholds for that category. Therefore, it is possible for no alert to be raised by the metrics in the DB Alert Log Error category but still for the DB Alert Log Error Status metric to fire (even if the thresholds defined for the DB Alert Log Error metric are not matched).

5.26.1 Archiver Hung Alert Log Error Status

This metric reflects the number of Archiver Hung alert log errors witnessed the last time Enterprise Manager scanned the Alert Log.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All versions Every 15 minutes After every sample > 0 Not Defined - %value% distinct types of ORA- errors have been found in the alert log.

5.26.2 Data Block Corruption Alert Log Error Status

This metric reflects the number of Data Block Corruption alert log errors witnessed the last time Enterprise Manager scanned the Alert Log.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All versions Every 15 minutes After every sample > 0 Not Defined - Data block corruption errors have been found in the alert log.

5.26.3 Generic Alert Log Error Status

This metric reflects the number of Generic alert log errors witnessed the last time Enterprise Manager scanned the Alert Log.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All versions Every 15 minutes After every sample > 0 Not Defined - %value% distinct types of ORA- errors have been found in the alert log.

5.26.4 Media Failure Alert Log Error Status

This metric represents the media failure alert log error status.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All versions Every 15 minutes After every sample > 0 Not Defined - Media failure errors have been found in the alert log.

5.26.5 Session Terminated Alert Log Error Status

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

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All versions Every 15 minutes After every sample > 0 Not Defined - Session terminations have been found in the alert log.

5.27 DB Managed by Single Instance

The metrics in this category collect the configuration information for an Oracle Database for Single Instance High Availability (HA) registration.

5.27.1 CRS Home Directory

This metric reports on the Oracle Home directory if a Single Instance HA is installed on the machine.

5.27.2 DB Managed by Single Instance HA

This metric indicates whether the database is managed by Single Instance HA. If the Oracle Database is not managed by Single Instance HA, indicates if a Single Instance HA is available for Oracle Database registration.

5.28 Deferred Transactions

The metrics in this category are associated with this distributed database's deferred transactions.

5.28.1 Deferred Transaction Count

Oracle uses deferred transactions to propagate data-level changes asynchronously among master sites in an advanced replication system as well as from an updatable snapshot to its master table.

This metric checks for the number of deferred transactions. An alert is generated if the number of deferred transactions exceeds the value specified by the threshold argument.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 5 Minutes Not Uploaded > 100 Not Defined 3 Number of deferred transactions is %value%.

Data Source

The source of the data is the following formula:

SELECT count(*) FROM sys.deftran 

User Action

When the advanced replication facility pushes a deferred transaction to a remote site, it uses a distributed transaction to ensure that the transaction has been properly committed at the remote site before the transaction is removed for the queue at the local site. If transactions are not being pushed to a given remote site, verify that the destination for the transaction was correctly specified. If you specify a destination database when calling DBMS_DEFER_SYS.SCHEDULE_EXECUTION using the DBLINK parameter or DBMS_DEFER_SYS.EXECUTE using the DESTINATION parameter, make sure the full database link is provided.

Wrong view destinations can lead to erroneous deferred transaction behavior. Verify the DEFCALLEST and DEFTRANDEST views are the definitions from the CATREPC.SQL not the ones from CATDEFER.SQL.

5.28.2 Deferred Transaction Error Count

Oracle uses deferred transactions to propagate data-level changes asynchronously among master sites in an advanced replication system as well as from an updatable snapshot to its master table. If a transaction is not successfully propagated to the remote site, Oracle rolls back the transaction, logs the transaction in the SYS.DEFERROR view in the remote destination database.

This metric checks for the number of transactions in SYS.DEFERROR view and raises an alert if it exceeds the value specified by the threshold argument.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 5 Minutes Not Uploaded > 0 Not Defined 3 Number of deferred transactions with errors is %value%.

Data Source

The source of the data is the following formula:

SELECT count(*) FROM sys.deferror 

User Action

An error in applying a deferred transaction may be the result of a database problem, such as a lack of available space in the table is to be updated or may be the result of an unresolved insert, update or delete conflict. The SYS.DEFERROR view provides the ID of the transaction that could not be applied. Use this ID to locate the queued calls associated with the transaction. These calls are stored in the SYS.DEFCALL view. You can use the procedures in the DBMS_DEFER_QUERY package to determine the arguments to the procedures listed in the SYS.DEFCALL view.

5.29 Dump Area

The metrics in this category check for the percentage of used space of the dump destination devices.

5.29.1 Dump Area Directory

This metric reports the directory represented by this metric index's dump destination.

Each server and background process can write to an associated trace file to log messages and errors.

Background processes and the ALERT file are written to the destination specified by BACKGROUND_DUMP_DEST. Trace files for server processes are written to the destination specified by USER_ DUMP_DEST.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The source of the data is the v$parameter view.

User Action

Verify the device specified in the initialization parameters BACKGROUND_DUMP_DEST, USER_DUMP_DEST, and CORE_DUMP_DEST are set up properly for archiving.

If the BACKGROUND_DUMP_DEST, USER_DUMP_DEST, and CORE_DUMP_DEST initialization parameters are set up correctly and this metric triggers, then free up more space in the destination specified by the dump destination parameters.

5.29.2 Dump Area Used (%)

This metric returns the percentage of used space of the dump area destinations.

If the space used is more than the threshold value given in the threshold arguments, then a warning or critical alert is generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
Not Available Every 15 Minutes After Every Sample > 95 Not Defined 1 %value%%% of %dumpType% dump area is used.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each Type of Dump Area object.

If warning or critical threshold values are currently set for any Type of Dump Area 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 Type of Dump Area object, use the Edit Thresholds page.

Data Source

Calculated using the UNIX df -k command.

  • Critical threshold: Percentage of free space threshold for critical alert.

  • Warning threshold: Percentage of free space threshold for warning alert.

User Action

Verify the device specified in the initialization parameters BACKGROUND_DUMP_DEST, USER_DUMP_DEST, and CORE_DUMP_DEST are set up properly for archiving.

If the BACKGROUND_DUMP_DEST, USER_DUMP_DEST, and CORE_DUMP_DEST initialization parameters are set up correctly and this metric triggers, then free up more space in the destination specified by the dump destination parameters.

5.29.3 Dump Area Used (KB)

This metric represents the total space used (in KB) on the device containing the dump destination directory.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The the data is calculated using the UNIX df -k command.

User Action

Verify the device specified in the initialization parameters BACKGROUND_DUMP_DEST, USER_DUMP_DEST, and CORE_DUMP_DEST are set up properly for archiving.

If the BACKGROUND_DUMP_DEST, USER_DUMP_DEST, and CORE_DUMP_DEST initialization parameters are set up correctly and this metric triggers, then free up more space in the destination specified by the dump destination parameters.

5.29.4 Free Dump Area (KB)

Each server and background process can write to an associated trace file in order to log messages and errors. Background processes and the ALERT file are written to the destination specified by BACKGROUND_DUMP_DEST.

Trace files for server processes are written to the destination specified by USER_DUMP_DEST.

This metric checks for available free space on these dump destination devices. If the space available is less than the threshold value given in the threshold arguments, then a warning or critical alert is generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 15 Minutes After Every Sample < Not Defined Not Defined - %value% free KB remains in %dumpType% dump area.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each Type of Dump Area object.

If warning or critical threshold values are currently set for any Type of Dump Area 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 Type of Dump Area object, use the Edit Thresholds page.

Data Source

The data is calculated using the UNIX df -k command.

User Action

Verify the device specified in the initialization parameters BACKGROUND_DUMP_DEST, USER_DUMP_DEST, and CORE_DUMP_DEST are set up properly for archiving.

If the BACKGROUND_DUMP_DEST, USER_DUMP_DEST, and CORE_DUMP_DEST initialization parameters are set up correctly and this metric triggers, then free up more space in the destination specified by the dump destination parameters.

5.29.5 Total Dump Area (KB)

This metric represents the total space (in KB) available on the device containing the dump destination directory.

Target Version Collection Frequency
All Versions Every 15 Minutes

Data Source

The data is calculated using the UNIX df -k command.

User Action

Verify the device specified in the initialization parameters BACKGROUND_DUMP_DEST, USER_DUMP_DEST, and CORE_DUMP_DEST are set up properly for archiving.

If the BACKGROUND_DUMP_DEST, USER_DUMP_DEST, and CORE_DUMP_DEST initialization parameters are set up correctly and this metric triggers, then free up more space in the destination specified by the dump destination parameters.

5.30 Efficiency

This metric category contains the metrics that have traditionally been considered to represent the efficiency of some resource. Interpreting the wait interface is generally accepted as a much more accurate approach to measuring efficiency, and is recommended as an alternative to these hit ratios.

5.30.1 Buffer Cache Hit (%)

This metric represents the data block buffer cache efficiency, as measured by the percentage of times the data block requested by the query is in memory.

Effective use of the buffer cache can greatly reduce the I/O load on the database. If the buffer cache is too small, frequently accessed data will be flushed from the buffer cache too quickly which forces the information to be re-fetched from disk. Because disk access is much slower than memory access, application performance will suffer. In addition, the extra burden imposed on the I/O subsystem could introduce a bottleneck at one or more devices that would further degrade performance.

This test checks the percentage of buffer requests that were already in buffer cache. If the value is less than or equal to the threshold values specified by the threshold arguments, and the number of occurrences exceeds the value specified in the Number of Occurrences parameter, then a warning or critical alert is generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 10 Minutes After Every Sample < Not Defined Not Defined 1 Buffer cache hit ratio is %value%%%.

Target Version Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 10 minutes After Every Sample < Not Defined Not Defined 2 Generated By Database Server

Data Source

The data is derived from the ((DeltaLogicalGets - (DeltaPhysicalReads - DeltaPhysicalReadsDirect)) / DeltaLogicalGets) * 100 formula where:

  • DeltaLogicalGets: difference in 'select value from v$sysstat where name='session logical reads'' between sample end and start

  • DeltaPhysicalReads: difference in 'select value from v$sysstat where name='physical reads'' between sample end and start

  • DeltaPhysicalReadsDirect: difference in 'select value from v$sysstat where name='physical reads direct'' between sample end and start (Oracle8i)

User Action

A low buffer cache hit ratio means that the server must often go to disk to retrieve the buffers required to satisfy a query. The queries that perform the most physical reads lower the numerical value of this statistic. Typically queries that perform full table scans force large amounts of buffers into the cache, aging out other buffers that may be required by other queries later. The Top Sessions page sorted by Physical Reads will show the sessions performing the most reads and through further drilldown their associated queries can be identified. Similarly, the Top SQL page sorted by Physical Reads shows which SQL statements are performing the most physical reads. The statements performing the most I/O should be looked at for tuning.

The difference between the two is that the Top Sessions chart shows the sessions that are responsible for the physical reads at any given moment. The Top SQL view shows all SQL that is still in the cache. The top statement may not be executing currently, and thus not responsible for the current poor buffer cache hit ratio.

If the queries seem to be well tuned, the size of the buffer cache also determines how often buffers must be fetched from disk. The DB_BLOCK_BUFFERS initialization parameter determines the number of database buffers available in the buffer cache. It is one of the primary parameters that contribute to the total memory requirements of the SGA on the instance. The DB_BLOCK_BUFFERS parameter, together with the DB_BLOCK_SIZE parameter, controls the total size of the buffer cache. Because DB_BLOCK_SIZE can only be specified when the database is first created, normally the size of the buffer cache size is controlled using the DB_BLOCK_BUFFERS parameter.

Consider increasing the DB_BLOCK_BUFFERS initialization parameter to increase the size of the buffer cache. This increase allows the Oracle Server to keep more information in memory, thus reducing the number of I/O operations required to do an equivalent amount of work using the current cache size.

5.30.2 CPU Usage (per second)

This metric represents the CPU usage per second by the database processes, measured in hundredths of a second. A change in the metric value may occur because of a change in either workload mix or workload throughput being performed by the database. Although there is no correct value for this metric, it can be used to detect a change in the operation of a system. For example, an increase in Database CPU usage from 500 to 750 indicates that the database is using 50% more CPU. (No correct value means that there is no single value that can be applied to any database. The value is a characteristic of the system and the applications running on the system.)

Target Version Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

Not available.

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. ADDM can help to identify database operations that are consuming CPU. ADDM reports are available from a number of locations including the Database Home page and Advisor Central.

5.30.3 CPU Usage (per transaction)

This metric represents the average CPU usage per transaction expressed as a number of seconds of CPU time. A change in this metric can occur either because of changing workload on the system, such as the addition of a new module, or because of a change in the way that the workload is performed in the database, such as changes in the plan for a SQL statement. The threshold for this metric should be set based on the actual values observed on your system.

Target Version Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

Not available.

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. ADDM will provide information about which operations are using the CPU resources.

5.30.4 Cursor Cache Hit (%)

This metric represents the percentage of soft parses satisfied within the session cursor cache.

Target Version Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 10 Minutes After Every Sample < Not Defined Not Defined 2 Generated By Database Server

Data Source

The source of the data is the following formula:

session cursor cache hits / (parse count (total) - parse count (hard))

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.30.5 Data Dictionary Hit (%)

This metric represents dictionary cache efficiency as measured by the percentage of requests against the dictionary data that were already in memory. It is important to determine whether the misses on the data dictionary are actually affecting the performance of the Oracle Server. The shared pool is an area in the SGA that contains the library cache of shared SQL requests, the dictionary cache, and the other cache structures that are specific to a particular instance configuration.

Misses on the data dictionary cache are to be expected in some cases. Upon instance startup, the data dictionary cache contains no data, so any SQL statement issued is likely to result in cache misses. As more data is read into the cache, the likelihood of cache misses should decrease. Eventually the database should reach a steady state in which the most frequently used dictionary data is in the cache. At this point, very few cache misses should occur. To tune the cache, examine its activity only after your application has been running.

This test checks the percentage of requests against the data dictionary that were found in the Shared Pool. If the value is less than or equal to the threshold values specified by the threshold arguments, and the number of occurrences exceeds the value specified in the Number of Occurrences parameter, then a warning or critical alert is generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i, Every 10 Minutes After Every Sample < Not Defined Not Defined 1 Data dictionary hit ratio is %value%%%.

Target Version Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 10 Minutes After Every Sample < Not Defined Not Defined 2 Generated By Database Server

Data Source

The source of the data is (1 - Misses/Gets) * 100 where:

  • Misses: select sum(getmisses) from v$rowcache

  • Gets: select sum(gets) from v$rowcache

User Action

If the percentage of gets is below 90% to 85%, consider increasing SHARED_POOL_SIZE to decrease the frequency in which dictionary data is being flushed from the shared pool to make room for new data. To increase the memory available to the cache, increase the value of the initialization parameter SHARED_POOL_SIZE.

5.30.6 Database CPU Time (%)

This metric represents the percentage of database call time that is spent on the CPU. Although there is no correct value for this metric, it can be used to detect a change in the operation of a system, for example, a drop in Database CPU time from 50% to 25%. (No correct value means that there is no single value that can be applied to any database. The value is a characteristic of the system and the applications running on the system.)

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 10 Minutes After Every Sample < Not Defined Not Defined 2 Generated By Database Server

Data Source

Not available.

User Action

Investigate if the change is CPU usage by using Automatic Database Diagnostic Monitor (ADDM). ADDM reports are available from a number of locations including the Database Home page and Advisor Central. Examine the report for increased time spent in wait events.

5.30.7 Library Cache Hit (%)

This metric represents the library cache efficiency, as measured by the percentage of times the fully parsed or compiled representation of PL/SQL blocks and SQL statements are already in memory.

The shared pool is an area in the SGA that contains the library cache of shared SQL requests, the dictionary cache and the other cache structures that are specific to a particular instance configuration.

The shared pool mechanism can greatly reduce system resource consumption in at least three ways: Parse time is avoided if the SQL statement is already in the shared pool.

Application memory overhead is reduced, because all applications use the same pool of shared SQL statements and dictionary resources.

I/O resources are saved, because dictionary elements that are in the shared pool do not require access.

If the shared pool is too small, users will consume additional resources to complete a database operation. For library cache access, the overhead is primarily the additional CPU resources required to re-parse the SQL statement.

This test checks the percentage of parse requests where cursor already in cache If the value is less than or equal to the threshold values specified by the threshold arguments, and the number of occurrences exceeds the value specified in the Number of Occurrences parameter, then a warning or critical alert is generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 10 Minutes After Every Sample < Not Defined Not Defined 1 Library cache hit ratio is %value%%%.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 10 Minutes After Every Sample < Not Defined Not Defined 2 Generated By Database Server

Data Source

The source of the data is the (DeltaPinHits / DeltaPins) * 100 formula where:

  • DeltaPinHits: difference in 'select sum(pinhits) from v$librarycache' between sample end and start

  • DeltaPins: difference in 'select sum(pins) from v$librarycache' between sample end and start

User Action

The Top Sessions page sorted by Hard Parses lists the sessions incurring the most hard parses. Hard parses occur when the server parses a query and cannot find an exact match for the query in the library cache. You can avoid hard parses by sharing SQL statements efficiently. The use of bind variables instead of literals in queries is one method to increase sharing.

By showing you which sessions are incurring the most hard parses, this page can identify the application or programs that are the best candidates for SQL rewrites.

Also, examine SQL statements that can be modified to optimize shared SQL pool memory use and avoid unnecessary statement reparsing. This type of problem is commonly caused when similar SQL statements are written which differ in space, case, or some combination of the two. You may also consider using bind variables rather than explicitly specified constants in your statements whenever possible.

The SHARED_POOL_SIZE initialization parameter controls the total size of the shared pool. Consider increasing the SHARED_POOL_SIZE to decrease the frequency in which SQL requests are being flushed from the shared pool to make room for new requests.

To take advantage of the additional memory available for shared SQL areas, you may also need to increase the number of cursors permitted per session. You can increase this limit by increasing the value of the initialization parameter OPEN_CURSORS.

5.30.8 Library Cache Miss (%)

This metric represents the percentage of parse requests where the cursor is not in the cache.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The source of the data is the following formula:
1 - pinhits / pins 

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.30.9 Parallel Execution Downgraded (per second)

This metric represents the number of times per second parallel execution was requested and the degree of parallelism was reduced because of insufficient parallel execution servers.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The source of the data is the following formula:

(parallel operations downgraded 1 to 25 percent 
+ parallel operations downgraded 25 to 50 percent 
+ parallel operations downgraded 50 to 75 percent 
+ parallel operations downgraded 75 to 99 percent) 
/ time

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.30.10 Parallel Execution Downgraded 25% or more (per second)

Number of times per second parallel execution was requested and the degree of parallelism was reduced to 25% and more because of insufficient parallel execution servers.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The source of the data is the following formula:

(parallel operations downgraded 25 to 50 percent 
+ parallel operations downgraded 50 to 75 percent 
+ parallel operations downgraded 75 to 99 percent) 
/ time

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.30.11 Parallel Execution Downgraded 50% or more (per second)

This metric reports the number of times per second parallel execution was requested and the degree of parallelism was reduced to 50% and more because of insufficient parallel execution servers.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The source of the data is the following formula:

(parallel operations downgraded 50 to 75 percent 
+ parallel operations downgraded 75 to 99 percent) 
/ time 

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.30.12 Parallel Execution Downgraded 75% or more (per second)

This metric reports the number of times per second parallel execution was requested and the degree of parallelism was reduced to 75% or more because of insufficient parallel execution servers.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The source of the data is the following formula:

(parallel operations downgraded 75 to 99 percent) / time 

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.30.13 Parallel Execution Downgraded to Serial (per second)

This metric reports the number of times per second parallel execution was requested but execution was serial because of insufficient parallel execution servers.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The source of the data is the following formula:

parallel operations downgraded to serial / time

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.30.14 Parallel Execution Downgraded to Serial (per transaction)

This metric reports the number of times per transaction parallel execution was requested but execution was serial because of insufficient parallel execution servers.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 10 minutes After Every Sample > Not Defined Not Defined 2 Not Defined

Data Source

The source of the data is the following formula:

parallel operations downgraded to serial / transactions

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.30.15 PGA Cache Hit (%)

This metric represents the total number of bytes processed in the PGA versus the total number of bytes processed plus extra bytes read/written in extra passes.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every10 Minutes After Every Sample < Not Defined Not Defined 2 Generated By Database Server

Data Source

Not available.

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.30.16 Redo Log Allocation Hit (%)

Redo log entries contain a record of changes that have been made to the database block buffers. The log writer (LGWR) process writes redo log entries from the log buffer to a redo log file. The log buffer should be sized so that space is available in the log buffer for new entries, even when access to the redo log is heavy. When the log buffer is undersized, user process will be delayed as they wait for the LGWR to free space in the redo log buffer.

The redo log buffer efficiency, as measured by the hit ratio, records the percentage of times users did not have to wait for the log writer to free space in the redo log buffer.

This metric monitors the redo log buffer hit ratio (percentage of success) against the values specified by the threshold arguments. If the number of occurrences is smaller than the values specified, then a warning or critical alert is generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i, Every 10 Minutes After Every Sample < Not Defined Not Defined 1 Redo log allocation hit ratio is %value%%%.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 10 Minutes After Every Sample < Not Defined Not Defined 2 Generated By Database Server

Data Source

The source of the data is the following formula:

100 * (redo_entries_delta - redo_space_requests_delta) 
/redo_entries_delta 
where: 
  • redo_enties_delta = difference between "SELECT value FROM v$sysstat WHERE name = 'redo entries'" at the beginning and ending of the interval

  • redo_space_requests_delta = difference between "SELECT value FROM v$sysstat WHERE name = 'redo log space requests'" at the beginning and ending of the interval

User Action

The LOG_BUFFER initialization parameter determines the amount of memory that is used when buffering redo entries to the redo log file.

Consider increasing the LOG_BUFFER initialization parameter in order to increase the size of the redo log buffer. Redo log entries contain a record of the changes that have been made to the database block buffers. The log writer process (LGWR) writes redo log entries from the log buffer to a redo log. The redo log buffer should be sized so space is available in the log buffer for new entries, even when access to the redo log is heavy.

Note: For Oracle Management Agent release 9i, this metric has been obsoleted. It is recommended that you use the Redo NoWait Ratio metric. This metric is kept for backward compatibility with older versions of the Management Agent.

5.30.17 Response Time (per transaction)

This metric represents the time spent in database operations per transaction. It is derived from the total time that user calls spend in the database (DB time) and the number of commits and rollbacks performed. A change in this value indicates that either the workload has changed or that the database�s ability to process the workload has changed because of either resource constraints or contention.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

Not available.

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page. Changes in the response time per transaction will appear as increased time spent in the database, either on CPU or in wait events and ADDM will report the sources of contention for both hardware and software resources.

5.30.18 Row Cache Miss Ratio (%)

This metric represents the percentage of row cache miss ratio.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

Not available.

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.30.19 Sorts in Memory (%)

This metric represents the sort efficiency as measured by the percentage of times sorts were performed in memory as opposed to going to disk.

For best performance, most sorts should occur in memory because sorts to disks are less efficient. If the sort area is too small, extra sort runs will be required during the sort operation. This increases CPU and I/O resource consumption.

This test checks the percentage of sorts performed in memory rather than to disk. If the value is less than or equal to the threshold values specified by the threshold arguments, and the number of occurrences exceeds the value specified in the Number of Occurrences parameter, then a warning or critical alert is generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every10 Minutes After Every Sample < Not Defined Not Defined 1 %value%%% of sorts are performed in memory.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute After Every Sample < Not Defined Not Defined 2 Generated By Database Server

Data Source

The source of the data is (DeltaMemorySorts / (DeltaDiskSorts + DeltaMemorySorts)) * 100 where:

  • DeltaMemorySorts: difference in 'select value from v$sysstat where name='sorts (memory)'' between sample end and start

  • DeltaDiskSorts: difference in 'select value from v$sysstat where name='sorts (disk)'' between sample end and start

User Action

The sessions that are performing the most sorts should be identified such that the SQL they are executing can be further identified. The sort area sizes for the database may be sized correctly, and the application SQL may be performing unwanted or excessive sorts. The sessions performing the most sorts are available through the Top Sessions page sorted by Disk Sorts.

Further drilldown into the session performing the most disk sorts with the Current SQL page shows you the SQL statement responsible for the disk sorts.

The Top SQL page sorted by Sorts provides a mechanism to quickly display the SQL statements in the cache, presented in sorted order by their number sort operations. This is an alternative to viewing a sort of current sessions. It allows you to view sort activity via SQL statements and contains cumulative statistics for all executions of that statement.

If excessive sorts are taking place on disk and the queries are correct, consider increasing the SORT_AREA_SIZE initialization parameter to increase the size of the sort area. A larger sort area allows the Oracle Server to maintain sorts in memory, reducing the number of I/O operations required to do an equivalent amount of work using the current sort area size.

5.31 Exadata Module Version Failure

This metric category provides information about the amount of times an Exadata module version error occurs.

5.31.1 Error Count

This metric displays the number of times that the error occurred.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 24 Hours After Every Sample >= 0 Not Defined 1 %errorCode% occurrences of %errorCount%.

5.32 Failed Logins

The metrics in this category check for the number of failed logins on the target database. This check is performed every ten minutes and returns the number of failed logins for that ten-minute interval. These metrics will only work for databases where the audit_trail initialization parameter is set to DB or XML and the session is being audited.

5.32.1 Failed Login Count

This metric checks for the number of failed logins on the target database. This check is performed every ten minutes and returns the number of failed logins for that ten-minute interval. This metric will only work for databases where the audit_trail initialization parameter is set to DB or XML and the session is being audited.

If the failed login count crosses the values specified in the threshold arguments, then a warning or critical alert is generated. Because it is important to know every time a significant number of failed logins occurs on a system, this metric will fire a new alert for any ten-minute interval where the thresholds are crossed. You can manually clear these alerts.They will not automatically clear after the next collection.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 30 Minutes After Every Sample >= 150 300 1Foot 1  There have been %value% failed login attempts in the last %failed_login_interval_min% minutes.

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

If warning or critical threshold values are currently set for any Time 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 object, use the Edit Thresholds page.

Data Source

The database stores login information in different views, based on the audit_trail setting. The database views used are:

  • DB or DB_EXTENDED: DBA_AUDIT_SESSION

  • XML (10g Release 2 only): DBA_COMMON_AUDIT_TRAIL

User Action

No user action is required.

5.33 Fast Recovery

The Fast Recovery metrics relate to the fast recovery area.

5.33.1 Fast Recovery Area

Formerly referred to as flash recovery area, the metrics in this category return an optional disk location that you can use to store recovery-related files such as control file and online redo log copies, archived redo log files, flashback logs, and RMAN backups.

Oracle Database and RMAN manage the files in the fast recovery area automatically. You can specify the disk quota, which is the maximum size of the fast recovery area.

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

Data Source

The source of the data is the following formula:

SELECT value 
  FROM v$parameter 
  WHERE name='db_recovery_file_dest';

User Action

No user action is required.

5.33.2 Fast Recovery Area Size

This metric returns the Fast Recovery Area Size.

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

Data Source

The source of the data is the following formula:

SELECT value 
  INTO 1_fast_recovery_size
  FROM v$parameter 
  WHERE name='db_recovery_file_dest_size';

User Action

No user action is required.

5.33.3 Flashback On

This metric returns whether or not flashback logging is enabled - YES, NO, or RESTORE POINT ONLY. For the RESTORE POINT ONLY option, flashback is ON but you can only flashback to guaranteed restore points.

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

Data Source

The source of the data is the following formula:

SELECT flashback_on 
  FROM v$database;

User Action

No user action is required.

5.33.4 Log Mode

This metric returns the log mode of the database - ARCHIVELOG or NOARCHIVELOG.

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

Data Source

The source of the data is the following formula:

SELECT log_mode 
  FROM v$database;

User Action

No user action is required.

5.33.5 Non-Reclaimable Fast Recovery Area (%)

This metric represents the percentage of space non-reclaimable (spaced used minus space reclaimable) in the fast recovery area.

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

Data Source

The source of the data is the following formula:

Non-reclaimable = space used - space reclaimable

Space Used:
  SELECT SUM(PERCENT_SPACE_USED 
     FROM v$fast_recovery_area_usage;

Space Reclaimable:
  SELECT SUM(PERCENT_SPACE_RECLAIMABLE) 
     FROM v$fast_recovery_area_usage;

User Action

No user action is required.

5.33.6 Oldest Flashback Time

This metric returns the oldest point-in-time to which you can flashback your database.

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

Data Source

The source of the data is the following formula:

SELECT to_char(oldest_flashback_time, 'YYYY-MM-DD HH24:MI:SS') 
  FROM v$flashback_database_log;

User Action

No user action is required.

5.33.7 Reclaimable Fast Recovery Area (%)

This metric represents the percentage of space reclaimable in the fast recovery area.

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

Data Source

The source of the data is the following formula:

Space Reclaimable:
  SELECT SUM(PERCENT_SPACE_RECLAIMABLE) 
     FROM v$fast_recovery_area_usage;

User Action

No user action is required.

5.33.8 Usable Fast Recovery Area (%)

This metric represents the percentage of space usable in the fast recovery area. The space usable is composed of the space that is free in addition to the space that is reclaimable.

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

Data Source

The source of the data is the following formula:

SELECT (CASE WHEN PERCENT_USED > 100 THEN 0 ELSE (100-PERCENT_USED) END) 
PERCENT_FREE
   FROM (SELECT (SUM(PERCENT_SPACE_USED)-SUM(PERCENT_SPACE_RECLAIMABLE)) 
PERCENT_USED
   FROM V$FAST_RECOVERY_AREA_USAGE);

User Action

No user action is required.

5.34 Global Cache Statistics

The metrics in this category are associated with global cache statistics.

5.34.1 Global Cache Average Convert Time (centi-seconds)

This metric represents the average convert time, measured in hundredths of a second.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 5 Minutes After Every 3 Samples > 0.3 0.6 2 Global cache converts time is %value% cs.

Data Source

The source of the data is the following formula:

global cache convert time * 10 / global cache converts

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.34.2 Global Cache Average CR Block Request Time (centi-seconds)

This metric represents the average time, measured in hundredths of a second, that CR block was received.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 5 Minutes After Every Sample > 0.5 1 1 Global cache CR Block request time is %value% cs.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 5 Minutes After Every Sample > 1 2 2 Generated By Database Server

Data Source

The source of the data is the following formula:

global cache CR block receive time * 10 / global cache current blocks received

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.34.3 Global Cache Average Current Block Request Time (centi-seconds)

This metric represents the average time, measured in hundredths of a second, to get a current block.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 5 Minutes After Every Sample > 0.5 1 1 Global cache Current Block request time is %value% cs.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 5 Minutes After Every Sample > 1 2 2 Generated By Database Server

Data Source

The source of the data is the following formula:

global cache current block send time * 10 / global cache current blocks served

User Action

The required actions are specific to your site.

5.34.4 Global Cache Average Get Time (centi-seconds)

This metric represents the average get time, measured in hundredths of a second.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 5 Minutes After Every Sample > 0.3 0.6 2 Global cache gets time is %value% cs.

Data Source

The source of the data is the following formula:

global cache get time * 10 / global cache gets

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.34.5 Global Cache Blocks Corrupt

This metric represents the number of blocks that encountered a corruption or checksum failure during interconnect over the user-defined observation period.

Note: Unlike most metrics, which accept thresholds as real numbers, this metric can only accept an integer as a threshold.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 5 Minutes After Every Sample > 0 0 1Foot 1  Total global cache blocks corrupt is %value%.

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

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 5 Minutes After Every Sample > 0 0 2 Generated By Database Server

Data Source

The source of the data is the following formula:

global cache blocks corrupted

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.34.6 Global Cache Blocks Lost

This metric represents the number of global cache blocks lost over the user-defined observation period.

Note: Unlike most metrics, which accept thresholds as real numbers, this metric can only accept an integer as a threshold.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
9.0.1.x, 9.2.0.x Every 5 Minutes After Every 3 Samples > 1 3 1Foot 1  Total global cache block lost is %value%.

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

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 5 Minutes After Every Sample > 1 3 2 Generated By Database Server

Data Source

The source of the data is global cache blocks lost.

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.35 Idle Events

This metrics category reports on the following idle events:

  • ARCH random i/o

  • ARCH sequential i/o

  • KXFX: execution message dequeue - Slaves

  • LGWR random i/o

  • LGWR sequential i/o

  • LGWR wait for redo copy

  • Null event

  • PL/SQL lock timer

  • PX Deq Credit: need buffer

  • PX Deq: Execute Reply

  • PX Deq: Execution Msg

  • PX Deq: Index Merge Close

  • PX Deq: Index Merge Execute

  • PX Deq: Index Merge Reply

  • PX Deq: Join ACK

  • PX Deq: Msg Fragment

  • PX Deq: Par Recov Change Vector

  • PX Deq: Par Recov Execute

  • PX Deq: Par Recov Reply

  • PX Deq: Parse Reply

  • PX Deq: Table Q Normal

  • PX Deq: Table Q Sample

  • PX Deq: Txn Recovery Reply

  • PX Deq: Txn Recovery Start

  • PX Deque wait

  • PX Idle Wait

  • Queue Monitor Shutdown Wait

  • Queue Monitor Slave Wait

  • Queue Monitor Wait

  • RFS random i/o

  • RFS sequential i/o

  • RFS write

  • SQL*Net message from client

  • SQL*Net message from dblink

  • STREAMS apply coord waiting for slave message

  • STREAMS apply coord waiting for some work to finish

  • STREAMS apply slave idle wait

  • STREAMS capture process filter callback wait for ruleset

  • STREAMS fetch slave waiting for txns

  • WMON goes to sleep

  • async disk IO

  • client message

  • control file parallel write

  • control file sequential read

  • control file single write

  • db file single write

  • db file parallel write

  • dispatcher timer

  • gcs log flush sync

  • gcs remote message

  • ges reconfiguration to start

  • ges remote message

  • io done

  • jobq slave wait

  • lock manager wait for remote message

  • log file parallel write

  • log file sequential read

  • log file single write

  • parallel dequeue wait

  • parallel recovery coordinator waits for cleanup of slaves

  • parallel query dequeue

  • parallel query idle wait - Slaves

  • pipe get

  • pmon timer

  • queue messages

  • rdbms ipc message

  • recovery read

  • single-task message

  • slave wait

  • smon timer

  • statement suspended, wait error to be cleared

  • unread message

  • virtual circuit

  • virtual circuit status

  • wait for activate message

  • wait for transaction

  • wait for unread message on broadcast channel

  • wait for unread message on multiple broadcast channels

  • wakeup event for builder

  • wakeup event for preparer

  • wakeup event for reader

  • wakeup time manager

5.36 Incident

This metric category contains the metrics representing incidents, for example, generic internal error, access violation, and so on as recorded in the database alert log file. The alert log file has a chronological log of messages and errors.

Each metric signifies that the database being monitored has detected a critical error condition about the database 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.

5.36.1 Access Violation

This metric signifies that the database 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 database can also generate this type of incident when it detects a SIGSEGV or SIGBUS signals.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 5 Minutes After Every Sample MATCH Not Defined .* - An access violation detected in %alertLogName% at time/line number: %tmeLine%.

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 source of the data is $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. Note: This event does not automatically clear because there is no automatic way of determining when the problem has been resolved. Therefore, you must manually clear the event after the problem is fixed.

5.36.2 Alert Log Error Trace File

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

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

Data Source

The source of the data is $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.

5.36.3 Alert Log Name

This metric reports the name of the alert log file.

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

Data Source

The source of the data is $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.

5.36.4 Cluster Error

This metric signifies that the database 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 Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 5 Minutes After Every Sample MATCH Not Defined .* - A cluster error detected in %alertLogName% at time/line number: %timeLine%.

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 source of the data is t$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. Note: This event does not automatically clear because there is no automatic way of determining when the problem has been resolved. Therefore, you must manually clear the event after the problem is fixed.

5.36.5 Deadlock

This metric signifies that the database 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 Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 5 Minutes After Every Sample MATCH Not Defined .* - A deadlock detected in $alertLogName% at time/line number: %timeLine%.

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 source of the data is $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. Note: This event does not automatically clear because there is no automatic way of determining when the problem has been resolved. Therefore, you must manually clear the event after the problem is fixed.

5.36.6 File Access Error

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

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 5 Minutes After Every Sample MATCH Not Defined .* - A file access error detected in %alertLogName% at time/line number: %timeLine%.

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 source of the data is $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. Note: This event does not automatically clear because there is no automatic way of determining when the problem has been resolved. Therefore, you must manually clear the event after the problem is fixed.

5.36.7 Generic Incident

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

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 5 Minutes After Every Sample MATCH Not Defined .* - Incident (%adr_problemKey%) detected in %alertLogName% at time/line number: %timeLine%.

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 source of the data is $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. Note: This event does not automatically clear because there is no automatic way of determining when the problem has been resolved. Therefore, you must manually clear the event after the problem is fixed.

5.36.8 Generic Internal Error

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

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 5 Minutes After Every Sample MATCH Not Defined .* - Internal error (%adr_problemKey%) detected in %alertLogName% at time/line number: %timeLine%.

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 source of the data is $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. Note: This event does not automatically clear because there is no automatic way of determining when the problem has been resolved. Therefore, you must manually clear the event after the problem is fixed.

5.36.9 Impact

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

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

Data Source

The source of the data is $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.

5.36.10 Incident ID

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

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

Data Source

The source of the data is $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.

5.36.11 Inconsistent DB State

This metric signifies that the database has generated an incident due to an inconsistent database state such an invalid ROWID. This type of incident is typically related to Oracle Exception message ORA-1410.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g,12c Every 5 Minutes After Every Sample MATCH Not Defined .* - An inconsistent DB state detected in %alertLogName% at time/line number: %timeLine%.

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 source of the data is $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. Note: This event does not automatically clear because there is no automatic way of determining when the problem has been resolved. Therefore, you must manually clear the event after the problem is fixed.

5.36.12 Internal SQL Error

This metric signifies that the database 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 Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 5 Minutes After Every Sample MATCH Not Defined .* - An internal SQL error detected in %alertLogName% at time/line number: %timeLine%.

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 source of the data is $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. Note: This event does not automatically clear because there is no automatic way of determining when the problem has been resolved. Therefore, you must manually clear the event after the problem is fixed.

5.36.13 Oracle Data Block Corruption

This metric signifies that the database has generated an incident due to an ORACLE data block corruption. This type of incident is typically related to Oracle Exception message ORA-1578.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 5 Minutes After Every Sample MATCH Not Defined .* - An Oracle data block corruption detected in %alertLogName% at time/line number: %timeLine%.

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 source of the data is $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. Note: This event does not automatically clear because there is no automatic way of determining when the problem has been resolved. Therefore, you must manually clear the event after the problem is fixed.

5.36.14 Out of Memory

This metric signifies that the database 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 Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 5 Minutes After Every Sample MATCH Not Defined .* - Out of memory detected in %alertLogName% at tme/line number: %timeLine%.

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 source of the data is $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. Note: This event does not automatically clear because there is no automatic way of determining when the problem has been resolved. Therefore, you must manually clear the event after the problem is fixed.

5.36.15 Redo Log Corruption

This metric signifies that the database 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 Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 5 Minutes After Every Sample MATCH Not Defined .* - A redo log corruption detected in %alertLogName% at time/line number: %timeLome%/

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 source of the data is $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. Note: This event does not automatically clear because there is no automatic way of determining when the problem has been resolved. Therefore, you must manually clear the event after the problem is fixed.

5.36.16 Session Terminated

This metric signifies that the database has generated an incident due to an unexpected session termination. This type of incident is typically related to Oracle Exception message ORA-603.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 5 Minutes After Every Sample MATCH Not Defined .* - A session termination detected in %alertLogName% at time/line number: %timeLine%.

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 source of the data is $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. Note: This event does not automatically clear because there is no automatic way of determining when the problem has been resolved. Therefore, you must manually clear the event after the problem is fixed.

5.37 Incident Status

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

5.37.1 Access Violation Status

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

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

Data Source

The source of the data is the Incident metric.

User Action

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

5.37.2 Cluster Error Status

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

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

Data Source

The source of the data is the Incident metric.

User Action

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

5.37.3 Deadlock Status

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

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

Data Source

The source of the data is the Incident metric.

User Action

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

5.37.4 File Access Error Status

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

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

Data Source

The source of the data is the Incident metric.

User Action

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

5.37.5 Generic Incident Status

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

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

Data Source

The source of the data is the Incident metric.

User Action

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

5.37.6 Generic Internal Error Status

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

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

Data Source

The source of the data is the Incident metric.

User Action

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

5.37.7 Inconsistent DB State Status

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

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g Every 5 Minutes After Every Sample > Not Defined 0 1 Incident DB state errors have been found in the alert log.

Data Source

The source of the data is the Incident metric.

User Action

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

5.37.8 Internal SQL Error Status

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

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

Data Source

The source of the data is the Incident metric.

User Action

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

5.37.9 Oracle Data Block Corruption Status

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

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

Data Source

The source of the data is the Incident metric.

User Action

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

5.37.10 Out of Memory Status

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

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

Data Source

The source of the data is the Incident metric.

User Action

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

5.37.11 Redo Log Corruption Status

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

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

Data Source

The source of the data is the Incident metric.

User Action

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

5.37.12 Session Terminated Status

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

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

Data Source

The source of the data is the Incident metric.

User Action

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

5.38 Interconnect

The metrics in this category collect the information about network interfaces used by cluster database instances as internode communication.

5.38.1 Interface Type

Cluster database instances should use private interconnects for internode communication. This metric monitors whether the network interface used by the cluster instance is a private one. If the network interface is known to be public, a critical alert is generated. If the network interface type is unknown, a warning alert is generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10gR2, 11g, 12c Every 12 Hours After Every Sample = Unknown Public - The instance is using interface '%if_name%' of type '%value%'.

Multiple Thresholds

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

If warning or critical threshold values are currently set for any Interface 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 Interface Name object, use the Edit Thresholds page.

Data Source

The data is derived from the following views:

V$CLUSTER_INTERCONNECTS

V$CONFIGURED_INTERCONNECTS

User Action

Use oifcfg in the CRS home to correctly configure the private interfaces in OCR.

5.39 Interconnect Traffic

The metrics in this category monitor the internode data transfer rate of cluster database instances.

5.39.1 Transfer Rate (MB/s)

This metric collects the internode communication traffic of a cluster database instance. This is an estimation using the following formula:

(gc cr blocks received/sec + gc current blocks received/sec + gc cr blocks served/sec + gc current blocks served/sec) * db_block_size 
+
( messages sent directly/sec + messages send indirectly/sec + messages received/sec ) * 200 bytes

The critical and warning thresholds of this metric are not set by default. Users can set them according to the speed of their cluster interconnects.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10gR2, 11g, 12c Every 5 Minutes After Every Sample > Not Defined Not Defined 1 Not Defined

Multiple Thresholds

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

If warning or critical threshold values are currently set for any Instance 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 Instance Name object, use the Edit Thresholds page.

Data Source

The data is derived from the following views:

V$SYSSTAT

V$DLM_MISC

V$PARAMETER

User Action

No user action is required.

5.40 Invalid Objects

The metrics in this category represent the metrics associated with invalid objects.

5.40.1 Total Invalid Object Count

This metric represents the total invalid object count.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 24 Hours Not Uploaded > Not Defined Not Defined - %value% object(s) are invalid in the database.

Data Source

The data is derived from the SYS.OBJ$ and SYS.USER$ tables.

User Action

The required actions are specific to your site.

5.41 Invalid Objects by Schema

The metrics in this category represent the number of invalid objects in each schema.

5.41.1 Owner's Invalid Object Count

This metric represents the invalid object count by owner.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 24 Hours Not Uploaded > Not Defined Not Defined 1 %value% object(s) are invalid in the %owner% schema.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each Invalid Object Owner object.

If warning or critical threshold values are currently set for any Invalid Object Owner 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 Invalid Object Owner object, use the Edit Thresholds page.

Data Source

The data is derived from the SYS.OBJ$ and SYS.USER$ tables.

User Action

View the status of the database objects in the schema identified by the Invalid Object Owner metric. Recompile objects as necessary.

5.42 Key Profiles

The metrics in this category provide information about key profiles.

5.42.1 Key Profiles Count

This metric provides the count of key profiles.

Target Version Collection Frequency
11.2.0.x Every 60 Minutes

Data Source

Not available.

User Action

The required actions are specific to your site.

5.42.2 Key Profiles Enabled

This metric denotes the key profiles enabled.

Target Version Collection Frequency
11.2.0.x Every 60 Minutes

Data Source

Not available.

User Action

The required actions are specific to your site.

5.43 Messages Per Buffered Queue

The metrics in this category monitor the age and state of the first (top of the queue) message for each buffered queue in the database except for the system queues. Queues that are in the schema of SYS, SYSTEM, DBSNMP, and SYSMAN are defined as system level queues.

5.43.1 Average Age of Messages Per Buffered Queue (Seconds)

This metric provides the average age (in seconds) of the messages in the buffered queue for all nonsystem queues in the database.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample >= Not Defined Not Defined 1 Average age of messages in %schema%.%queue_name% queue is %value% seconds.

5.43.2 First Message Age in Buffered Queue Per Queue (Seconds)

This metric gives the age (in seconds) of the first message in the buffered queue for all non-system queues in the database.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample >= Not Defined Not Defined 1 Age of first message in %schema%.%queue_name% buffered queue is %value% seconds.

Multiple Thresholds

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

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

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

Data Source

This metric is calculated by finding the age of the first message in all the subscribers of the queue and then the oldest amongst all is taken.

The following views and tables are used for the calculation:

  1. <SCHEMA>.AQ$<QUEUE_TABLE>

  2. v$buffered_queues

User Action

When using buffered queues for storing and propagating messages, monitor this metric to get the age of first message in the queue.

5.43.3 Messages processed per buffered queue (%)

This metric gives the messages processed percentage per minute per buffered queue in the last collection interval of the metric.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample <= Not Defined Not Defined 1 Messages processed for queue %schema%.%queue_name% is %value% percent.

Multiple Thresholds

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

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

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

Data Source

This is calculated as the percent of total number of messages processed per minute and total number of messages received per minute in the last collection interval per buffered queue.

User Action

When using queues for storing/propagating messages, monitor this metric to get the messages processed percent (or throughput) per minute in the last collection interval for the queue.

5.43.4 Messages Processed Per Buffered Queue (%) Per Minute

This metric gives the messages processed percentage per minute in the last interval per buffered queue in the last collection interval of the metric.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample <= Not Defined Not Defined 1 Messages processed per minute in the last interval for queue %schema%.%queue_name% is %value% .

5.43.5 Spilled Messages

This metric displays the current number of overflow messages spilled to disk from the buffered queue.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample >= Not Defined Not Defined 1 Current number of overflow messages spilled to disk from the buffered queue %schema%.%queue_name% is %value%

5.43.6 Total Messages Processed per Buffered Queue per Minute

This metric gives the total number of messages processed per minute per buffered queue in the last collection interval of the metric.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample <= Not Defined Not Defined 1 Total messages processed per minute in the last interval for queue %schema%.%queue_name% is %value% .

5.43.7 Total Messages Received per Buffered Queue per Minute

This metric gives the total number of messages received or enqueued into the buffered queue per minute in the last collection interval of the metric.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample <= Not Defined Not Defined 1 Total messages received per minute in the last interval for queue %schema%.%queue_name% is %value% .

5.44 Message Per Buffered Queue Per Subscriber

This metric category monitors the messages for buffered queues per subscriber in the database.

5.44.1 Average Age of Messages Per Buffered Queue Per Subscriber (Seconds)

This metric display's the average age of messages in the buffered queue per queue in seconds.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample >= Not Defined Not Defined 1 Average age of messages for the subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value% seconds.

5.44.2 First Message Age in Buffered Queue per Subscriber (Seconds)

This metric displays the age of the first message in the buffered queue per queue per subscriber in seconds.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample >= Not Defined Not Defined 1 Age of first message for subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value% seconds.

5.44.3 Messages Processed Per Buffered Queue Per Subscriber (%)

This metric gives the messages processed percentage for the buffered queue per subscriber. Messages processed percent is calculated as the percent of the total number messages processed or dequeued to the total number of messages received or enqueued.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample <= Not Defined Not Defined 1 Messages processed for the subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value% percent.

5.44.4 Messages Processed Per Buffered Queue (%) Per Subscriber Per Minute

This metric gives the total number of messages processed per minute per buffered queue subscriber in the last collection interval of the metric.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample <= Not Defined Not Defined 1 Messages processed per minute in the last interval for the subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value%

5.44.5 Total Messages Processed Per Buffered Queue Per Subscriber Per Minute

This metric gives the total number of messages processed per minute per buffered queue subscriber in the last collection interval of the metric.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample <= Not Defined Not Defined 1 Total messages processed per minute in the last interval for the subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value% .

5.44.6 Total Messages Received Per Buffered Queue Per Subscriber Per Minute

This metric gives the total number of messages received or enqueued into the queue per subscriber per minute in the last collection interval of the metric.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample <= Not Defined Not Defined 1 Total messages received per minute in the last interval for the subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value% .

5.45 Messages Per Persistent Queue

The metrics in this category monitor the age and state of the first (top of the queue) message for each persistent queue in the database except for the system queues. Queues that are in the schema of SYS, SYSTEM, DBSNMP, and SYSMAN are defined as system level queues.

5.45.1 Age of the First Message in Persistent Queue Per Queue

This metric gives the age (in seconds) of the first message in the persistent queue for all non-system queues in the database.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample >= Not Defined Not Defined 1 Age of first message in %schema%.%queue_name% queue is %value% seconds.

Multiple Thresholds

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

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

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

Data Source

This metric is calculated by finding the age of the first message in all the subscribers of the queue and then the oldest amongst all is taken.

The following views/tables are used for the calculation:

  1. <SCHEMA>.AQ$_<QUEUE_TABLE>_S

  2. <SCHEMA>.AQ$_<QUEUE_TABLE>_I

  3. <SCHEMA>.AQ$<QUEUE_TABLE>

User Action

When using persistent queues for storing and propagating messages, monitor this metric to get the age of first message in the queue.

5.45.2 Average Age of Messages Per Persistent Queue (Seconds)

This metric displays the average age of messages in the persistent queue per queue in seconds.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample >= Not Defined Not Defined 1 Average age of messages in %schema%.%queue_name% queue is %value% seconds.

5.45.3 Messages Processed Per Persistent Queue (%)

This metric gives the messages processed percentage for the persistent queue. Messages processed percent is calculated as the percent of the total number messages processed or dequeued to the total number of messages received or enqueued.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample <= Not Defined Not Defined 1 Messages processed for queue %schema%.%queue_name% is %value% percent.

5.45.4 Messages Processed Per Persistent Queue (%) Per Minute

This metric gives the messages processed percentage per minute per persistent queue in the last collection interval of the metric.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample <= Not Defined Not Defined 1 Messages processed per minute in the last interval for queue %schema%.%queue_name% is %value%

5.45.5 Total Messages Processed per Persistent Queue per Minute

This metric gives the total number of messages processed per minute per persistent queue in the last collection interval of the metric.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample <= Not Defined Not Defined 1 Total messages processed per minute in the last interval for queue %schema%.%queue_name% is %value% .

5.45.6 Total Messages Received per Persistent Queue per Minute

This metric gives the total number of messages received or enqueued into the queue per minute in the last collection interval of the metric.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample <= Not Defined Not Defined 1 Total messages received per minute in the last interval for queue %schema%.%queue_name% is %value% .

5.46 Messages Per Persistent Queue Per Subscriber

The metrics in this category monitor the age and state of the first (top of the queue) message for each persistent queue per queue subscriber in the database except for the system queues. Queues that are in the schema of SYS, SYSTEM, DBSNMP, and SYSMAN are defined as system level queues.

5.46.1 Average Age of Messages Per Persistent Queue Per Subscriber (Seconds)

This metric display's the average age of messages in the persistent queue per queue in seconds.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample >= Not Defined Not Defined 1 Average age of messages for the subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value% seconds.

5.46.2 Age of the First Message in Persistent Queue Per Subscriber

This metric gives the age (in seconds) of the first message in the persistent queue per subscriber for all non-system queues in the database.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample >= Not Defined Not Defined 1 Age of first message for subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value% seconds.

5.46.3 Messages Processed Per Persistent Queue Per Subscriber (%)

This metric gives the messages processed percentage for the persistent queue per subscriber. Messages processed percent is calculated as the percent of the total number messages processed or dequeued to the total number of messages received or enqueued.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample <= Not Defined Not Defined 1 Messages processed for the subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value% percent.

5.46.4 Messages Processed Per Persistent Queue (%) Per Subscriber Per Minute

This metric gives the messages processed percentage per minute per persistent queue subscriber in the last collection interval of the metric.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample <= Not Defined Not Defined 1 Messages processed per minute in the last interval for the subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value% .

5.46.5 Total Messages Processed Per Persistent Queue Per Subscriber Per Minute

This metric gives the messages processed percentage per minute per persistent queue subscriber in the last collection interval of the metric.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample <= Not Defined Not Defined 1 Total messages processed per minute in the last interval for the subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value% .

5.46.6 Total Messages Received Per Persistent Queue Per Subscriber Per Minute

This metric gives the total number of messages received or enqueued into the queue per subscriber per minute in the last collection interval of the metric.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample <= Not Defined Not Defined 1 Total messages received per minute in the last interval for the subscriber %subs_name% %subs_address% in %schema%.%queue_name% queue is %value% .

5.47 OCM Instrumentation

The metrics in this category determine whether the database has been instrumented with Oracle Configuration Manager (OCM). Oracle Configuration Manager is used to personalize the support experience by collecting configuration information and uploading it to the Oracle repository.When customer configuration data is uploaded on a regular basis, customer support representatives can analyze this data and provide better service to the customers. For example, when a customer logs a service request, he can associate the configuration data directly with that service request. The customer support representative can then view the list of systems associated with the customer and solve problems accordingly.

5.47.1 Instrumentation Present

This metric determines whether the database has been instrumented with Oracle Configuration Manager.

Target Version Collection Frequency
All Versions Every 24 Hours

Data Source

Not available.

User Action

No user action is required.

5.47.2 Need to Instrument with OCM

This metric determines that Oracle Configuration Manager needs to be instrumented in the database.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 24 Hours After Every Sample = 1 Not Defined 1 OCM Instrumentation should be installed in database. Please use $ORACLE_HOME/ccr/admin/scripts/installCCRSQL script with collectconfig parameter.

Data Source

Not available.

User Action

Install Oracle Configuration Manager (OCM) in the database.

5.47.3 OCM Configured

This metric determines how the Oracle Configuration Manager is configured.

Target Version Collection Frequency
All Versions Every 24 Hours

Data Source

Not available.

User Action

No user action is required.

5.48 Operational Error

This metric category contains the metrics representing errors that may affect the operation of the database, for example, archiver hung, media failure, and so on as recorded in the database alert log file. The alert log file has a chronological log of messages and errors.

Each metric signifies that the database being monitored has detected a critical error condition that may affect the normal operation of the database and has generated an error message to the alert log file since the last sample time. The Support Workbench in Enterprise Manager may contain more information about the error.

5.48.1 Alert Log Error Trace File

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

Target Version Collection Frequency
11g Every 5 Minutes

Data Source

The source for the data is $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.

5.48.2 Alert Log Name

This metric reports the name of the alert log file.

Target Version Collection Frequency
11g Every 5 Minutes

Data Source

The source for the data is $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.

5.48.3 Archiver Hung

This metric signifies that the archiver of the database being monitored has been temporarily suspended since the last sample time.

If the database is running in ARCHIVELOG mode, an alert is displayed when archiving is hung (ORA-00257 or ORA-16038) messages are written to the alert file. The alert file is a special trace file containing a chronological log of messages and errors.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 5 Minutes After Every Sample MATCH Not Defined .* - Archiver hang detected in %alertLogName% at time/line number: %timeLine%.

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 for the data is $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. However, the most likely cause of this message is that the destination device is out of space to store the redo log file. Verify the device specified in the initialization parameter ARCHIVE_LOG_DEST is set up properly for archiving. Note: This event does not automatically clear because there is no automatic way of determining when the problem has been resolved. Therefore, you must manually clear the event after the problem is fixed.

5.48.4 Data Block Corruption

This metric signifies that the database 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 Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 5 Minutes After Every Sample MATCH Not Defined .* - A datablock corruption detected in %alertLogName% at time/line number: %timeLine%.

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 for the data is $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. Note: This event does not automatically clear because there is no automatic way of determining when the problem has been resolved. Therefore, you must manually clear the event after the problem is fixed.

5.48.5 Generic Operational Error

This metric signifies that the database being monitored has generated some error that may affect the normal operation of the database 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 Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 5 Minutes After Every Sample MATCH Not Defined .* - Operational error (%errorCodes%) detected in %alertLogName% at time/line number: %timeLine%.

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 for the data is $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. Note: This event does not automatically clear because there is no automatic way of determining when the problem has been resolved. Therefore, you must manually clear the event after the problem is fixed.

5.48.6 Media Failure

This metric signifies that the database 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 Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 5 Minutes After Every Sample MATCH Not Defined .* - Media Failure detected in %alertLogName% at time/line number: %timeLine%.

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 for the data is $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. Note: This event does not automatically clear because there is no automatic way of determining when the problem has been resolved. Therefore, you must manually clear the event after the problem is fixed.

5.48.7 User-Defined Error

This metric displays the user-defined error.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 5 Minutes After Every Sample MATCH Not Defined .* - Warning (%errorCodes%) detected in %alertLogName% at time/line number: %timeLine%.

5.48.8 User-Defined Text

This metric displays the user-defined text.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 5 Minutes After Every Sample MATCH Not Defined - - Matching text (%errorCodes%) detected in %alertLogName% at time/line number: %timeLine%.

5.49 Recovery

The metrics in this category are related to database recovery.

5.49.1 Corrupt Data Block Count

This metric represents the count of corrupt data blocks.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i, 10g Every 15 Minutes After Every Sample > Not Defined 0 - Number of corrupt data blocks is %value%.

Data Source

The data is derived from the following formula:

SELECT nvl(sum(blocks), 0)
  FROM v$database_block_corruption;

User Action

Perform a database recovery.

5.49.2 Datafiles Need Media Recovery

This metric represents the count of data files that require recovery.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i, 10g Every 15 Minutes After Every Sample > Not Defined 0 - Number of data files needing media recovery is %value%.

Data Source

The data is derived from the following formula:

SELECT count(file#) 
  INTO 1_datafiles_need_recovery
  FROM v$datafile_header 
  WHERE recover ='YES';

User Action

Perform a database recovery.

5.49.3 Missing Media File Count

This metric returns the count of missing media files.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i, 10g Every 15 Minutes After Every Sample > Not Defined 0 - Number of missing media files is %value%.

Data Source

The data is derived from the following formula:

SELECT count(file#) 
  INTO 1_missing_media_files
  FROM v$datafile_header 
  WHERE error is not null AND error is 'OFFLINE NORMAL';

User Action

Perform a database recovery.

5.50 Response

The metrics in this category represent the responsiveness of the Oracle Server, with respect to a client.

5.50.1 State

This metric represents the state of the database.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 15 Seconds After Every Sample MATCH MOUNTED DOWN|UNKNOWN.* - The database status is %value%..

Data Source

Not available.

User Action

The required actions are specific to your site. The required actions are specific to your site.

5.50.2 Status

This metric checks whether a new connection can be established to a database. If the maximum number of users is exceeded or the listener is down, this test is triggered.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 15 Seconds After Every Sample = Not Defined 0 - Failed to connect to database instance %oraerr%.

Data Source

Perl returns 1 when a connection can be made to the database (using Management Agent monitoring connection details), 0 otherwise.

User Action

Check the status of the listener to make sure it is running on the node where the event was triggered. If the listener is running, check to see if the number of users is at the session limit. Note: The choice of user credentials for the Probe metric should be considered. If the preferred user has the RESTRICED SESSION privilege, the user will be able to connect to a database even if the LICENSE_MAX_SESSIONS limit is reached.

5.51 SCN Growth Statistics

This metric category provides information about the Systems Change Number (SCN) in the database environment and reports on the health of the SCN growth in the database.

5.51.1 SCN Health

This metric displays the status of the SCN health.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Hour After Every Sample <= 62 10 1 The SCN health is %scn_health%.

5.51.2 Current SCN

This metric displays the value of the current SCN.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Hour After Every Sample > Not Defined Not Defined 1 The current SCN is %current_scn%.

5.51.3 SCN Total Growth Rate (per sec)

This metric displays the total SCN growth rate over the previous 24 hours.

SCNs occur in a monotonically increasing sequence (that is, each SCN is greater than or equal to the one before it), and there is a very large upper limit to how many SCNs Oracle Database can use. Because there is an upper limit, it is important that Oracle Database does not run out of available SCNs and therefore it is important to monitor the SCN growth rate.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Hour After Every Sample > Not Defined Not Defined 1 The total SCN Growth rate per second (last 24 hours) is %scn_total_growth%.

5.52 SCN Instance Statistics

This metric category provides information about the SCN growth rate due to intrinsic activity.

5.52.1 SCN Intrinsic Growth Rate (per sec)

This metric displays the intrinsic SCN growth rate per second.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Hour After Every Sample > Not Defined Not Defined 1 The intrinsic SCN Growth rate per second is %scn_intrinsic_growth_rate%.

5.53 SCN Max Statistics

This metric category provides information about the maximum value of the SCN.

5.53.1 Max SCN Jump in one second (last 24 hours)

This metric displays the maximum SCN jump in one second over the previous 24 hours.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Hour After Every Sample > Not Defined Not Defined 1 The maximum SCN jump in one second (last 24 hours) is %scn_max_jump%.

5.54 Segment Advisor Recommendations

The metrics in this category provide segment advisor recommendations. Oracle uses the Automatic Segment Advisor job to detect segment issues regularly within maintenance windows. It determines whether the segments have unused space that can be released. The Number of recommendations is the number of segments that have Reclaimable Space. The recommendations come from all runs of the automatic segment advisor job and any user scheduled segment advisor jobs.

5.54.1 Number of Recommendations

Oracle uses the Automatic Segment Advisor job to detect segment issues regularly within maintenance windows. It determines whether the segments have unused space that can be released. The Number of recommendations is the number of segments that have Reclaimable Space. The recommendations come from all runs of the automatic segment advisor job and any user scheduled segment advisor jobs.

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

Data Source

Not available.

User Action

Oracle recommends shrinking or reorganizing these segments to release unused space.

5.55 Session Suspended

The metrics in this category represent the number of resumable sessions that are suspended due to some correctable error.

5.55.1 Session Suspended by Data Object Limitation

This metric represents the session suspended by data object limitation.

This metric is collected for the following targets: 10g, 11g.

Data Source

Not available.

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.55.2 Session Suspended by Quota Limitation

This metric represents the session suspended by quota limitation.

This metric is collected for the following targets: 10g, 11g.

Data Source

Not available.

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.55.3 Session Suspended by Rollback Segment Limitation

This metric represents the session suspended by rollback segment limitation.

This metric is collected for the following targets: 10g, 11g.

Data Source

Not available.

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.55.4 Session Suspended by Tablespace Limitation

This metric represents the session suspended by a tablespace limitation.

This metric is collected for the following targets: 10g, 11g.

Data Source

Not available.

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.56 SGA Pool Wastage

The metrics in this category represent the percentage of the various pools in the SGA that are being wasted.

5.56.1 Java Pool Free (%)

This metric represents the percentage of the Java Pool that is currently marked as free.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 15 Minutes After Every Sample < Not Defined Not Defined 2 %value%%% of the Java pool is free.
10g, 11g, 12c Every 15 Minutes After Every Sample < Not Defined Not Defined 2 %value%%% of the Java pool is free.

Data Source

The data is derived from the formula ((Free/Total)*100) where:

  • Free: select sum(decode(name,'free memory',bytes)) from v$sgastat where pool = 'java pool'

  • Total: select sum(bytes) from v$sgastat where pool = 'java pool'

User Action

If this pool size is too small, the database JVM (Java Virtual Machine) may not have sufficient memory to satisfy future calls, leading potentially to unexpected database request failures.

5.56.2 Large Pool Free (%)

This metric represents the percentage of the Large Pool that is currently marked as free.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 15 Minutes After Every Sample < Not Defined Not Defined 2 %value%%% of the Java pool is free.
10g, 11g, 12c Every 15 Minutes After Every Sample < Not Defined Not Defined 2 %value%%% of the Java pool is free.

Data Source

The data is derived from the formula ((Free/Total)*100) where:

  • Free: select sum(decode(name,'free memory',bytes)) from v$sgastat where pool = 'large pool'

  • Total: select sum(bytes) from v$sgastat where pool = 'large pool'

User Action

Consider enlarging the large pool or utilizing it more sparingly. This reduces the possibility of large memory areas competing with the library cache and dictionary cache for available memory in the shared pool.

5.56.3 Shared Pool Free (%)

This metric represents the percentage of the Shared Pool that is currently marked as free.

This test checks the percentage of Shared Pool that is currently free. If the value is less than or equal to the threshold values specified by the threshold arguments, and the number of occurrences exceeds the value specified in the Number of Occurrences parameter, then a warning or critical alert is generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 15 Minutes After Every Sample < Not Defined Not Defined 2 %value%%% of the shared pool is free.
10g, 11g, 12c Every 15 Minutes After Every Sample < Not Defined Not Defined 2 Generated By Database Server

Data Source

The data is derived from the formula ((Free/Total)*100) where:

  • free: select sum(decode(name,'free memory',bytes)) from v$sgastat where pool = 'shared pool'

  • total: select sum(bytes) from v$sgastat where pool = 'shared pool'

User Action

If the percentage of Free Memory in the Shared Pool rises above 50%, too much memory has been allocated to the shared pool. This extra memory could be better utilized by other applications on the machine. In this case the size of the Shared Pool should be decreased. This can be accomplished by modifying the shared_pool_size initialization parameter.

5.57 Snapshot Too Old

The metrics in this category represent the snapshots that are too old due to rollback segment limit or tablespace limit.

5.57.1 Snapshot Too Old Due to Rollback Segment Limit

This metric represents the snapshot too old because of the rollback segment limit.

This metric is collected for the following targets: 10g, 11g.

Data Source

Not available.

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.57.2 Snapshot Too Old Due to Tablespace Limit

This metric represents the snapshot too old because of the tablespace limit.

This metric is collected for the following targets: 10g, 11g.

Data Source

Not available.

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.58 Space Usage by Buffered Queues

The metrics in this category monitor the space usage of buffered queues with respect to the streams pool size.

5.58.1 Queue Size (MB)

This metric display's the size of buffered queue, which is the total number of Mega bytes allocated for all messages and metadata.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample >= Not Defined Not Defined 1 Size of buffered queue %schema%.%queue_name% is %value% MB.

Multiple Thresholds

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

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

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

Data Source

The data is derived from the INSTANCE_NAME column in the GV$INSTANCE view.

User Action

When using queues for storing or propagating messages, monitor this metric to get the instance in which the buffered queue is available.

5.58.2 Space Usage of Buffered Queue With Respect to Streams Pool Size (%)

This metric gives the space usage percentage of buffered queue with respect to streams pool size per buffered queue.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11gR2, 12c Every 30 Minutes After Every Sample >= Not Defined Not Defined 1 Buffered queue %schema%.%queue_name% has consumed %value% percent of streams pool size.

Multiple Thresholds

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

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

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

Data Source

The data is derived from the QUEUE_SIZE AND CURRENT_SIZE columns from GV$BUFFERED_QUEUES and GV$SGA_DYNAMIC_COMPONENTS views.

User Action

When using buffered queues for storing or propagating messages, monitor this metric to get the space usage percentage of buffered queue with respect to the allocated streams pool size.

5.59 SQL Response Time

The metrics in this category approximate the responsiveness of SQL.

5.59.1 Baseline SQL Response Time

This metric contains the response time of the baseline.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

Not available.

User Action

No user action is required.

5.59.2 Current SQL Response Time

This metric contains the response time of the latest collection.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

Not available.

User Action

No user action is required.

5.59.3 SQL Response Time (%)

SQL Response Time is the average elapsed time per execution of a representative set of SQL statements, relative to a baseline. It is expressed as a percentage.

This metric is not available in versions 8.1.7 and earlier.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every10 Minutes After Every Sample > Not Defined Not Defined 2 SQL response time is %value%%% of baseline.

Data Source

The data is derived from the PL/SQL packaged procedure mgmt_response.get_metric_curs.

User Action

If the SQL Response Time is less than 100%, then SQL statements are taking less time to execute when compared to the baseline. Response Time greater than 100% indicates that the database is not performing well when compared to the baseline.

SQL Response Time is a percentage of the baseline, not a simple percentage. So, for example, 100% of baseline means the SQL Response Time is the same as the baseline. 200% of baseline means the SQL Response Time is two times slower than the baseline. 50% of baseline means SQL Response Time is two times faster than baseline. A warning threshold of 200% indicates that the database is two times slower than the baseline, while a critical threshold of 500% indicates the database is 5 times slower than the baseline.

Representative statements are selected when two V$SQL snapshots are taken. All calculations are based on the deltas between these two snapshots. First, the median elapsed_time/execution for all statements that were executed in the time interval between the two snapshots are calculated. Then all statements that have an elapsed_time/execution > median elapsed_time/execution are taken, and the top 25 most frequently executed statements are displayed.

Pre-requisites for Monitoring SQL Response Time

Some tables and a PL/SQL package must be installed on the monitored database. This can be done by going to the database targets page and pressing the Configure button for your database. If a database has not been configured, the message Not Configured will be displayed for SQL Response Time.

Configuring the Baseline

The baseline is configured on demand, automatically. The first time the agent calls the stored procedure to get the value of the metric, a snapshot of V$SQL is taken. The second time, another snapshot is taken. Then the representative statements are picked and stored in a table. The next time the agent requests the value of the metric, the relative SQL response time is calculated and returned.

Because of baseline configuration, there will be a delay between the time the database is configured and the value of the metric is displayed. During this period, the message of the collection status will be displayed for SQL Response Time.

Enterprise Manager will automatically configure the baseline against which SQL Response Time will be compared. However, in order for the SQL Response Time metric to be truly representative, the DBA must reconfigure the baseline at a time when the load on the database is typical.

To reconfigure the baseline, click on the link titled Edit Reference Collection located next to the SQL Response Time value on the Database Home Page. The SQL statements used for tracking the SQL Response Time and baseline values are displayed. Click Reset Reference Collection. This clears the list of statements and the baseline values. Enterprise Manager will then automatically reconfigure the baseline within minutes.

If the database was lightly loaded at the time the baseline was taken, then the metric can indicate that the database is performing poorly under typical load when such is not the case. In this case, the DBA must reset the baseline. If the DBA has never manually reset the baseline, then the metric value will not be representative.

5.60 Streams Apply Aborted

The metrics in this category check for the Streams Apply processes.

5.60.1 Streams Apply Process Aborted

This metric detects when a Streams Apply process configured on this database aborts. This metric indicates a critical error.

Data Source

The DBA_APPLY view STATUS column indicates ABORTED if the apply process has aborted.

User Action

Obtain the exact error message in dba_apply, take the appropriate action for this error, then restart the apply process using dbms_apply_adm.start_apply.

Using the DBA_APPLY_ERROR view, identify the specific change record which encountered an error(MESSAGE_NUMBER) within a failed transaction and the complete error message (ERROR_MESSAGE). Detailed information about the transaction can be found using Enterprise Manager or by using the scripts described in the documentation Displaying Detailed Information about Apply Errors.

If DBA_APPLY error message is ORA-26714, then consider setting the 'DISABLE_ON_ERROR' apply parameter to 'N' to avoid aborting on future user errors.

5.60.2 Streams Apply Process Error

This metric indicates that the apply process encountered an error when it was applying a transaction.

Data Source

Not available.

User Action

Look at the contents of the error queue as well as dba_apply_error to determine the cause of the error. After the errors are resolved, reexecute them using dbms_apply_adm.execute_error or dbms_apply_adm.execute_all_errors.

5.61 Streams Apply Coordinator Statistics

The metrics in this category show statistics about the transactions processed by the coordinator process of each apply process. The Total Number of Transactions Received field shows the total number of transactions received by a coordinator process. The Number of Transactions Assigned field shows the total number of transactions assigned by a coordinator process to apply servers. The Total Number of Transactions Applied field shows the total number of transactions successfully applied by the apply process.

The values for an apply process are reset to zero if the apply process is restarted.

5.61.1 Total Number of Transactions Assigned

This metric shows statistics about the total number of transactions assigned by the coordinator process to apply servers since the apply process last started. For target version 10gR1, the collection frequency for this metric is every 10 minutes.

Target Version Collection Frequency
9i, 10g, 11g Every 5 Minutes

Data Source

The data is derived from the TOTAL_ASSIGNED column in the following query shows this metric for an apply process:

SELECT APPLY_NAME, TOTAL_RECEIVED, TOTAL_ASSIGNED, TOTAL_APPLIED 
  FROM V$STREAMS_APPLY_COORDINATOR; 

User Action

When an apply process is enabled, monitor this metric to ensure that the apply process assigning transactions to apply servers.

5.61.2 Rate of Transactions Applied (per Sec)

This metric reports the rate (per second) at which transactions are applied by the apply process.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

The data is derived from the target database, gv%streams_apply_coordinator table.

User Action

No user action is required.

5.61.3 Rate of Transactions Assigned (per Sec)

This metric reports the rate (per second) at which transactions are assigned to the apply servers.

Target Version Collection Frequency
All Versions Every 5 Minutes

Data Source

The data is derived from the target database, gv%streams_apply_coordinator table.

User Action

No user action is required.

5.61.4 Rate of Transactions Received (per Sec)

This metric reports the rate (per second) at which apply coordinator is receiving the transactions.

Target Version Collection Frequency
9iR2, 10g, 11g Every 5 Minutes

Data Source

The data is derived from the target database, gv%streams_apply_coordinator table.

User Action

No user action is required.

5.61.5 Total Number of Transactions Applied

This metric shows statistics about the total number of transactions applied by the apply process since the apply process last started.

Target Version Collection Frequency
9iR2, 10g, 11g Every 5 Minutes

Data Source

The TOTAL_APPLIED column in the following query shows this metric for an apply process:

SELECT APPLY_NAME, TOTAL_RECEIVED, TOTAL_ASSIGNED, TOTAL_APPLIED 
  FROM V$STREAMS_APPLY_COORDINATOR; 

User Action

When an apply process is enabled, monitor this metric to ensure that the apply process is applying transactions.

5.61.6 Total Number of Transactions Received

This metric shows statistics about the total number of transactions received by the coordinator process since the apply process last started.

Target Version Collection Frequency
9iR2, 10g, 11g Every 5 Minutes

Data Source

The TOTAL_RECEIVED column in the following query shows this metric for an apply process:

SELECT APPLY_NAME, TOTAL_RECEIVED, TOTAL_ASSIGNED, TOTAL_APPLIED 
  FROM V$STREAMS_APPLY_COORDINATOR; 

User Action

When an apply process is enabled, monitor this metric to ensure that the apply process is receiving transactions.

5.62 Streams Apply Errors

The metrics in this category collect information about Apply Errors and Error transactions.

5.62.1 Error Message

This metric reports the error message of the error raised by the transaction.

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

Data Source

The data source for this metric is target database, dba_apply_error table.

User Action

No user action is required.

5.62.2 Error Number

This metric reports the error code of the error raised by the transaction.

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

Data Source

The data source for this metric is target database, dba_apply_error table.

User Action

No user action is required.

5.62.3 Local Transaction ID

This metric reports the local transaction ID for the error transaction.

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

Data Source

Data source for this metric is the target database, dba_apply_error table.

User Action

No user action is required.

5.62.4 Message Count

This metric reports the total number of events inside the error transaction.

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

Data Source

The data source for this metric is the target database, dba_apply_error table.

User Action

No user action is required.

5.62.5 Source Transaction ID

This metric reports the original transaction ID at the source database, for the error transaction.

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

Data Source

The data source for this metric is the target database, dba_apply_error table.

User Action

No user action is required.

5.63 Streams Apply Queue - Buffered

The metrics in this category show the current total number of messages in a buffered queue to be dequeued by each apply process and the total number of messages to be dequeued by each apply process that have spilled from memory into the persistent queue table.

5.63.1 Streams Apply - (%) Spilled Messages

This metric usually indicates that transactions are staying longer in memory.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 30 Minutes After Every Sample > Not Defined Not Defined 1 Spilled messages for Apply process [%APPLY_NAME%] queue is %value% percent.

Multiple Thresholds

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

If warning or critical threshold values are currently set for any Apply 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 Apply Name object, use the Edit Thresholds page.

Data Source

The data source for this metric is the target database, gv$buffered_queues, gv$buffered_subscribers tables.

User Action

Either increase Streams Pool size and /or increase Apply Parallelism to speed up Apply processing.

5.64 Streams Apply Queue - Persistent

The metrics in this category show the number of messages in a persistent queue in READY state and WAITING state for each apply process.

5.64.1 Streams Apply - (%) Messages in Waiting State

This metric shows the percentage of messages in a wait state.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
9iR2, 10g, 11g, 12c Every 30 Minutes After Every Sample > Not Defined Not Defined 1 Messages waiting for Apply process [%APPLY_NAME%] queue is %value% percent.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of Apply Name and Messages Delivery Mode objects.

If warning or critical threshold values are currently set for any unique combination of Apply Name and Messages Delivery Mode 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 Apply Name and Messages Delivery Mode objects, use the Edit Thresholds page.

Data Source

The data source for this metric is Target Database and Apply Queue.

User Action

No user action is required.

5.65 Streams Apply Reader Statistics

The reader server for an apply process dequeues messages from the queue. The reader server computes dependencies between LCRs and assembles messages into transactions. The reader server then returns the assembled transactions to the coordinator, which assigns them to idle apply servers.

The metrics in this category shows the total number of messages dequeued by the reader server for the apply process since the last time the apply process was started.

5.65.1 Rate at Which Messages Are Getting Spilled (per Sec)

The reader server for an apply process dequeues messages from the queue. The reader server computes dependencies between LCRs and assembles messages into transactions. The reader server then returns the assembled transactions to the coordinator, which assigns them to idle apply servers.

This metric shows the rate at which message are getting spilled (per second) by the reader server for the apply process since the last time the apply process was started.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
9iR2, 10g, 11g, 12c Every 30 Minutes After Every Sample > Not Defined Not Defined 1 Total number of spilled messages for Apply Process [%APPLY_NAME%] is %value% .

Multiple Thresholds

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

If warning or critical threshold values are currently set for any Apply 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 Apply Name object, use the Edit Thresholds page.

Data Source

For this metric, the data source is Target database, gv$streams_apply_reader view.

User Action

No user action is required.

5.65.2 Total Number of Messages Dequeued

The reader server for an apply process dequeues messages from the queue. The reader server computes dependencies between LCRs and assembles messages into transactions. The reader server then returns the assembled transactions to the coordinator, which assigns them to idle apply servers.

This metric shows the total number of messages dequeued by the reader server for the apply process since the last time the apply process was started.

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

Data Source

The TOTAL_MESSAGES_DEQUEUED column in the following query shows this metric for an apply process:

SELECT APPLY_NAME, TOTAL_MESSAGES_DEQUEUED FROM V$STREAMS_APPLY_READER; 

User Action

When an apply process is enabled, monitor this metric to ensure that the apply process is dequeuing messages.

5.65.3 Total Number of Spilled Messages

The reader server for an apply process dequeues messages from the queue. The reader server computes dependencies between LCRs and assembles messages into transactions. The reader server then returns the assembled transactions to the coordinator, which assigns them to idle apply servers.

This metric shows the total number of messages spilled by the reader server for the apply process since the last time the apply process was started.

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

Data Source

For this metric, the data source is Target database, gv$streams_apply_reader view.

User Action

No user action is required.

5.66 Streams Capture Message Statistics

The metrics in this category show the number of messages captured and the number of messages enqueued by each capture process since the capture process last started.

The Total Messages Captured field shows the total number of redo entries passed by LogMiner to the capture process for detailed rule evaluation. A capture process converts a redo entry into a message and performs detailed rule evaluation on the message when capture process prefiltering cannot discard the redo entry. After detailed rule evaluation, the message is enqueued if it satisfies the capture process rule sets, or the message is discarded if it does not satisfy the capture process rule sets. The Total Messages Enqueued field shows the total number of messages enqueued. The number of captured messages captured can be higher than the number of enqueued messages.

The total messages enqueued includes enqueued logical change records (LCRs) that encapsulate data manipulation language (DML) and data definition language (DDL) changes. The total messages enqueued also includes messages that contain transaction control statements. These messages contain directives such as COMMIT and ROLLBACK. Therefore, the total messages enqueued is higher than the number of row changes and DDL changes enqueued by a capture process.

5.66.1 Message Capture Rate (per Sec)

This metric shows the number of messages captured by each capture process since the capture process last started.

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

Data Source

For this metric, the data source is Target database, gv$streams_capture view.

User Action

No user action is required.

5.66.2 Messages Enqueue Rate (per Sec)

This metric shows the number of messages enqueued by each capture process since the capture process last started.

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

Data Source

Not available.

User Action

The required actions are specific to your site.

5.66.3 Total Messages Captured

This metric shows information about the number of redo entries passed by LogMiner to the capture process for detailed rule evaluation. A capture process converts a redo entry into a message and performs detailed rule evaluation on the message when capture process prefiltering cannot discard the change.

After detailed rule evaluation, the message is enqueued if it satisfies the capture process rule sets, or the message is discarded if it does not satisfy the capture process rule sets.

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

Data Source

The TOTAL_MESSAGES_CAPTURED column in the following query shows this metric for a capture process:

SELECT CAPTURE_NAME, TOTAL_MESSAGES_CAPTURED, TOTAL_MESSAGES_ENQUEUED   FROM V$STREAMS_CAPTURE;

User Action

When a capture process is enabled, monitor this metric to ensure that the capture process is scanning redo entries.

5.66.4 Total Messages Enqueued

This metric shows information about the number of messages enqueued by a capture process. The number of messages enqueued includes logical change records (LCRs) that encapsulate data manipulation language (DML) and data definition language (DDL) changes. The number of messages enqueued also includes messages that contain transaction control statements. These messages contain directives such as COMMIT and ROLLBACK. Therefore, the number of messages enqueued is higher than the number of row changes and DDL changes enqueued by a capture process.

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

Data Source

The TOTAL_MESSAGES_ENQUEUED column in the following query shows this metric for a capture process:

SELECT CAPTURE_NAME, TOTAL_MESSAGES_CAPTURED, TOTAL_MESSAGES_ENQUEUED   FROM V$STREAMS_CAPTURE;

User Action

When a capture process is enabled, monitor this metric to ensure that the capture process is enqueuing messages. If you know that there were source database changes that should be captured by the capture process, and the capture process is not capturing these changes, then there might be a problem with the rules used by the capture process.

5.67 Streams Capture Queue Statistics

The metrics in this category show the current total number of messages in a buffered queue that were enqueued by each capture process and the total number of messages enqueued by each capture process that have spilled from memory into the queue spill table.

If queue publishers other than the capture process enqueue messages into a buffered queue, then the values shown can include messages from these other queue publishers.

5.67.1 Capture Queue - Cumulative Number of Messages

This metric shows information about the cumulative number of messages enqueued by a capture process in a buffered queue.

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

Data Source

Not available.

User Action

The required actions are specific to your site.

5.67.2 Capture Queue - Cumulative Number of Spilled Messages

This metric shows information about the cumulative number of spilled messages enqueued by a capture process in a buffered queue.

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

Data Source

Not available.

User Action

The required actions are specific to your site.

5.67.3 Capture Queue - Number of Messages

This metric shows information about the number of messages enqueued by a capture process in a buffered queue. This number includes both messages in memory and messages spilled from memory.

If queue publishers other than the capture process enqueue messages into a buffered queue, then the values shown can include messages from these other queue publishers.

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

Data Source

The NUM_MSGS column in the following query shows this metric for a capture process:

SELECT CAPTURE_NAME, P.NUM_MSGS NUM_MSGS, Q.SPILL_MSGS SPILL_MSGS 
  FROM V$BUFFERED_PUBLISHERS P, V$BUFFERED_QUEUES Q, DBA_CAPTURE C 
  WHERE C.QUEUE_NAME = P.QUEUE_NAME 
    AND C.QUEUE_OWNER = P.QUEUE_SCHEMA 
    AND C.QUEUE_NAME = Q.QUEUE_NAME 
    AND C.QUEUE_OWNER = Q.QUEUE_SCHEMA 
    AND C.CAPTURE_NAME = P.SENDER_NAME 
    AND P.SENDER_ADDRESS IS NULL 
    AND P.SENDER_PROTOCOL = 1;

User Action

When a capture process is enabled, monitor this metric to ensure that the capture process enqueuing messages.

5.67.4 Capture Queue - Number of Spilled Messages

This metric shows information about the number of messages enqueued by a capture process that have spilled from memory to the queue spill table. Messages in a buffered queue can spill from memory into the queue spill table if they have been staged in the buffered queue for a period of time without being dequeued, or if there is not enough space in memory to hold all of the messages.

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

Data Source

The SPILL_MSGS column in the following query shows this metric for a capture process:

SELECT CAPTURE_NAME, P.NUM_MSGS NUM_MSGS, Q.SPILL_MSGS SPILL_MSGS 
  FROM V$BUFFERED_PUBLISHERS P, V$BUFFERED_QUEUES Q, DBA_CAPTURE C 
  WHERE C.QUEUE_NAME = P.QUEUE_NAME 
    AND C.QUEUE_OWNER = P.QUEUE_SCHEMA 
    AND C.QUEUE_NAME = Q.QUEUE_NAME 
    AND C.QUEUE_OWNER = Q.QUEUE_SCHEMA 
    AND C.CAPTURE_NAME = P.SENDER_NAME 
    AND P.SENDER_ADDRESS IS NULL 
    AND P.SENDER_PROTOCOL = 1; 

User Action

The number of spilled messages should be kept as low as possible for the best performance. A high number of spilled messages can result in the following cases:

  • There might be a problem with a propagation that propagates the messages captured by the capture process, or there might be a problem with an apply process that applies messages captured by the capture process. When this happens, the number of messages can build in a queue because they are not being consumed. In this case, make sure the relevant propagations and apply processes are enabled, and correct any problems with these propagations and apply processes.

  • The Streams pool might be too small to hold the captured messages. In this case, increase the size of the Streams pool. If the database is Oracle Database 10g release 2 (10.2) or higher, then you can configure Automatic Shared Memory Management to manage the size of the Streams pool automatically. Set the SGA_TARGET initialization parameter to use Automatic Shared Memory Management.

5.67.5 Streams Capture - (%) Cumulative Spilled Messages

The percentage of Cumulative spilled messages indicate the messages are staying in memory longer. It can also indicate that the Propagation or Apply Process is slow to consume the enqueued messages.

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

Data Source

The data source for this metric is the target database, gv$buffered_queues table.

User Action

No user action is required.

5.67.6 Streams Capture - (%) Spilled Messages

Queue spill indicates the messages are staying in memory longer. It can also indicate that the Propagation or Apply Process is slow to consume the enqueued messages.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 30 Minutes After Every Sample > Not Defined Not Defined 1 Spilled messages for Capture process %CAPTURE_NAME% queue is %value% percent.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each Capture Name object. If warning or critical threshold values are currently set for any Capture 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 Capture Name object, use the Edit Thresholds page.

Data Source

The data source for this metric is the target database, gv$buffered_queues table.

User Action

Increase Streams Pool Size to avoid queue spills.

5.68 Streams Latency and Throughput

The metrics in this category collect information about latency and throughput for each capture, propagation and apply component in the database. Latency and throughput are important indicators for the overall performance of the streams path.

5.68.1 Latency

This metric reports latency. High Latency indicates that the components are slow.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10gR2, 11g, 12c Every 30 Minutes After Every Sample > Not Defined Not Defined - Latency for Streams %streams_process_type% Process %streams_process_name% is %value% seconds.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of Streams Process Name and Streams Process Type objects.

If warning or critical threshold values are currently set for any unique combination of Streams Process Name and Streams Process Type 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 Streams Process Name and Streams Process Type objects, use the Edit Thresholds page.

Data Source

The data source for this metric is the target database, gv$streams_capture, gv$propagation_sender, and gv$streams_apply_server views.

User Action

Identify and correct the least performing component in the streams configuration.

5.68.2 Throughput (per sec)

This metric collects information about throughput for each capture, propagation and apply component in the database

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10gR2, 11g, 12c Every 30 Minutes After Every Sample < Not Defined Not Defined - Throughput for Streams %streams_process_type% Process %streams_process_name% is %value% messages/sec.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of Streams Process Name and Streams Process Type objects.

If warning or critical threshold values are currently set for any unique combination of Streams Process Name and Streams Process Type 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 Streams Process Name and Streams Process Type objects, use the Edit Thresholds page.

Data Source

Not available.

User Action

The required actions are specific to your site.

5.68.3 Total Messages

This metric collects the total number of messages for each capture, propagation and apply component in the database.

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

Data Source

Not available.

User Action

The required actions are specific to your site.

5.69 Streams Pool Usage

The metrics in this category check for the memory usage of the Streams pool.

5.69.1 Streams Pool Full

This alert is generated when the memory usage of the Streams pool has exceeded the percentage specified by the STREAMS_POOL_USED_PCT metric. This alert can be raised only if the database is not using Automatic Memory Management or Automatic Shared Memory Management.

Data Source

Not available.

User Action

If the currently running workload is typical, consider increasing the size of the Streams pool.

5.70 Streams Processes Count

The metrics in this category show the total number of Streams capture processes, propagations, and apply processes at the local database. This metric also shows the number of capture processes, propagations, and apply processes that have encountered errors.

5.70.1 Number of Apply Processes Having Errors

This metric shows the number of apply processes that have encountered errors at the local database.

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

Data Source

The information in this metric is in the DBA_APPLY data dictionary view.

User Action

If an apply process has encountered errors, then correct the conditions that caused the errors.

5.70.2 Number of Capture Processes Having Errors

This metric shows the number of capture processes that have encountered errors at the local database.

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

Data Source

The information in this metric is in the DBA_CAPTURE data dictionary view.

User Action

If a capture process has encountered errors, then correct the conditions that caused the errors.

5.70.3 Number of Apply Processes

This metric shows the number of apply processes at the local database.

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

Data Source

The information in this metric is in the DBA_APPLY data dictionary view.

User Action

Use this metric to determine the total number of apply processes at the local database.

5.70.4 Number of Capture Processes

This metric shows the number of capture processes at the local database.

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

Data Source

The information in this metric is in the DBA_CAPTURE data dictionary view.

User Action

Use this metric to determine the total number of capture processes at the local database.

5.70.5 Number of Propagation Jobs

This metric shows the number of propagations at the local database.

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

Data Source

The information in this metric is in the DBA_PROPAGATION data dictionary view.

User Action

Use this metric to determine the total number of propagations at the local database.

5.70.6 Number of Propagations Having Errors

This metric shows the number of propagations that have encountered errors at the local database.

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

Data Source

The information in this metric is in the DBA_PROPAGATION data dictionary view.

User Action

If a propagation has encountered errors, then correct the conditions that caused the errors.

5.70.7 Total Number of Propagation Errors

This metric provides the total number of propagation errors.

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

Data Source

The data source for this metric is the target database, DBA_Propagation view.

User Action

No user action is required.

5.71 Streams Processes Status

The metrics in this category collect the current status and number of errors for each capture, propagation and apply process in the database.

5.71.1 Streams Process Errors

This metric collects the number of errors for each capture, propagation and apply process in the database.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 30 Minutes After Every Sample > 0 Not Defined 1 Stream component %streams_process_name% has %value% errors.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of Streams Process Name and Streams Process Type objects.

If warning or critical threshold values are currently set for any unique combination of Streams Process Name and Streams Process Type 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 Streams Process Name and Streams Process Type objects, use the Edit Thresholds page.

Data Source

Not available.

User Action

The required actions are specific to your site.

5.71.2 Streams Process Status

This metric collects the current status and number of errors for each capture, propagation, and apply process in the database.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 30 Minutes After Every Sample = DISABLED ABORTED 1 Status for Streams process %streams_process_name% is %streams_process_status%.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of Streams Process Name and Streams Process Type objects.

If warning or critical threshold values are currently set for any unique combination of Streams Process Name and Streams Process Type 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 Streams Process Name and Streams Process Type objects, use the Edit Thresholds page.

Data Source

The data source for this metric is the target database, DBA_CAPTURE, dba_propagation, dba_apply views.

User Action

Analyze status change reason and enable the disabled/aborted component.

5.72 Streams Propagation - Messages State Stats

The metrics in this category collect the number of messages in Ready and Waiting state for each Propagation process.

5.72.1 Number of Ready Messages

This metric collects the number of messages in Ready state for each Propagation process.

Target Version Collection Frequency
9iR2, 10g, 11g, 12c Every 30 Minutes

Data Source

The data source for this metric is the target database, source and destination queues.

User Action

No user action is required.

5.72.2 Number of Waiting Messages

This metric collects the number of messages in Waiting state for each Propagation process.

Target Version Collection Frequency
9iR2, 10g, 11g, 12c Every 30 Minutes

Data Source

The data source for this metric is the target database, source and destination queues.

User Action

No user action is required.

5.72.3 Streams Prop - (%) Messages in Waiting State

This metric collects the percentage of messages in Waiting state for each Propagation process.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
9iR2, 10g, 11g, 12c Every 30 Minutes After Every Sample > Not Defined Not Defined 1 Messages waiting for %PROPAGATION_NAME% queue is %value% percent.

Multiple Thresholds

For this metric you can set different warning and critical threshold values for each unique combination of Propagation Name and Messages Delivery Mode objects.

If warning or critical threshold values are currently set for any unique combination of Propagation Name and Messages Delivery Mode 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 Propagation Name and Messages Delivery Mode objects, use the Edit Thresholds page.

Data Source

The data source for this metric is the target database, source and destination queues.

User Action

No user action is required.

5.73 Streams Propagation - Queue Propagation

The metrics in this category collect propagation statistics in terms of number of messages and number of Kbytes propagated by each propagation process.

5.73.1 Message Propagation Rate (per Sec)

This metric collects propagation statistics in terms of the rate of messages propagated by each propagation process.

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

Data Source

The data source for this metric is the target database - DBA_PROPAGATION.

User Action

No user action is required.

5.73.2 Rate of KBytes Propagated (per Sec)

This metric collects propagation statistics in terms of the rate of Kbytes propagated by each propagation process.

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

Data Source

The data source for this metric is the target database - DBA_PROPAGATION.

User Action

No user action is required.

5.73.3 Total Number of KBytes Propagated

This metric collects propagation statistics in terms of total number of Kbytes propagated by each propagation process.

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

Data Source

The data source for this metric is the target database - DBA_PROPAGATION.

User Action

No user action is required.

5.73.4 Total Number of Messages Propagated

This metric collects propagation statistics in terms of the total number of messages propagated by each propagation process.

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

Data Source

The data source for this metric is the target database - DBA_PROPAGATION.

User Action

No user action is required.

5.74 Streams Propagation Aborted

The metrics in this category check for the Streams Propagation processes.

5.74.1 Streams Propagation Process Aborted

This metric detected when a Streams Propagation process configured on this database aborts. This alert indicates a critical error.

Data Source

Not Available

User Action

Obtain the exact error message in dba_queue_schedules, take the appropriate action for this error, and restart the propagation process using dbms_propagation_adm.start_propagation.

5.75 Suspended Session

This metric category contains the metrics that represent the number of resumable sessions that are suspended due to some correctable error.

5.75.1 Suspended Session Count

This metric represents the number of resumable sessions currently suspended in the database.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
9i Every 5 Minutes Not Uploaded > 0 Not Defined - %value% session(s) are suspended.

Data Source

The data source for this metric is the following formula:

SELECT count(*) 
  FROM v$resumable 
  WHERE status = 'SUSPENDED' and enabled = 'YES'

User Action

Query the v$resumable view to see what the correctable errors are that are causing the suspension. The way to correct each error depends on the nature of the error.

5.76 System Response Time Per Call

The metrics in this category represent the system response time.

5.76.1 Response Time (centi-seconds per call)

This metric represents the average time taken for each call (both user calls and recursive calls) within the database. A change in this value indicates that either the workload has changed or that the database's ability to process the workload has changed because of either resource constraints or contention.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g,12c Every 10 Minutes After Every Sample > Not Defined Not Defined 3 Not Defined

Data Source

Not available.

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.77 System Sessions Waiting

The metrics in this category represent the number of sessions waiting.

5.77.1 Waiting Session Count

This metric represents the number of sessions waiting at the sample time.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 5 Minutes After Every Sample > Not Defined Not Defined 2 %value% sessions are waiting.

Data Source

The data source for this metric is the following formula:

SELECT count(*) 
  FROM v$session_wait 
  WHERE wait_time = 0 and event not in IdleEvents

See the Section 5.35, "Idle Events" for additional information.

User Action

When this count is high, the system is doing more waiting than anything else. Evaluate the various types of wait activity using the real-time and historical performance monitoring capabilities of Enterprise Manager.

5.78 Tablespace Allocation

The metrics in this category check the amount of space used and the amount of space allocated to each tablespace. The used space can then be compared to the allocated space to determine how much space is unused in the tablespace. This metric is not intended for alerts. Rather it is intended for reporting. Historical views of unused allocated free space can help DBAs to correctly size their tablespaces, eliminating wasted space.

5.78.1 Tablespace Allocated Space (MB)

The allocated space of a tablespace is the sum of the current size of its datafiles. A portion of this allocated space is used to store data while some may be free space. If segments are added to a tablespace, or if existing segments grow, they will use the allocated free space. The allocated free space is only available to segments within the tablespace. If, over time, the segments within a tablespace are not using this free space, then the allocated free space is being unused.

This metric calculates the space allocated for each tablespace. It is not intended to generate alerts. Rather it should be used in conjunction with the Allocated Space Used (MB) metric to produce an historical view of the amount of space being used and unused by each tablespace.

Target Version Collection Frequency
All Versions Every 7 Hours

Data Source

Tablespace Allocated Space (MB) is calculated by looping through the tablespace's data files and totalling the size of the data files.

User Action

Specific to you site.

5.78.2 Tablespace Used Space (MB)

The allocated space of a tablespace is the sum of the current size of its datafiles. Some of this allocated space is used to store data and some of it may be free space. If segments are added to a tablespace, or if existing segments grow, they will use the allocated free space. The allocated free space is only available to segments within the tablespace. If, over time, the segments within a tablespace are not using this free space, then the allocated free space is being wasted.

This metric calculates the space used for each tablespace. It is not intended to generate alerts. Rather it should be used in conjunction with the Tablespace Allocated Space (MB) metric to produce an historical view of the amount of space being used and unused by each tablespace.

Target Version Collection Frequency
All Versions Every 7 Hours

Data Source

Tablespace Used Space (MB) is Tablespace Allocated Space (MB) - Tablespace Allocated Free Space (MB) where:

  • Tablespace Allocated Space (MB) is calculated by looping through the tablespace's data files and totaling the size of the data files.

  • Tablespace Allocated Free Space (MB) is calculated by looping through the tablespace's data files and totaling the size of the free space in each data file.

User Action

Specific to you site.

5.79 Tablespaces Full

The metrics in this category check for the amount of space used by each tablespace. The used space is then compared to the available free space to determine tablespace fullness. The available free space takes into account the maximum data file size as well as available disk space. This means that a tablespace will not be flagged as full if datafiles can extend and there is enough disk space available for them to extend.

5.79.1 Tablespace Free Space (MB)

As segments within a tablespace grow, the available free space decreases. If there is no longer any available free space, meaning datafiles have hit their maximum size or there is no more disk space, then the creation of new segments or the extension of existing segments will fail.

This metric checks for the total available free space in each tablespace. This metric is intended for larger tablespaces, where the Available Space Used (%) metric is less meaningful. If the available free space falls below the size specified in the threshold arguments, then a warning or critical alert is generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 30 Minutes After Every Sample <= Not Defined Not Defined - Tablespace [%name%] has [%value% mbytes] free
10gR2 11g, 12c Every 30 Minutes After Every Sample <= Not Defined Not Defined - Not Defined

Multiple Thresholds

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

If warning or critical threshold values are currently set for any Tablespace 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 Tablespace Name object, use the Edit Thresholds page.

Data Source

The data for this metric is derived from the MaximumSize - Total Used Space formula where:

  • TotalUsedSpace: total used space in MB of tablespace.

  • MaximumSize: Maximum size (in MB) of the tablespace. The maximum size is determined by looping through the tablespaces data files, as well as additional free space on the disk that would be available for the tablespace should a data file autoextend.

User Action

Perform one of the following:

  • Increase the size of the tablespace by: Enabling automatic extension for one of its existing data files, manually resizing one of its existing data files, or adding a new data file.

  • If the tablespace is suffering from tablespace free space fragmentation problems, consider reorganizing the entire tablespace.

  • Relocate segments to another tablespace, thus increasing the free space in this tablespace.

  • Run the Segment Advisor on the tablespace.

5.79.2 Tablespace Space Used (%)

As segments within a tablespace grow, the available free space decreases. If there is no longer any available free space, meaning datafiles have hit their maximum size or there is no more disk space, then the creation of new segments or the extension of existing segments will fail.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 30 Minutes After Every Sample >= 85 97 - Tablespace [%name%] is [%value% percent] full

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 30 Minutes Not Defined After Every Sample >= 85 97 - Generated By Database Server

Multiple Thresholds

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

If warning or critical threshold values are currently set for any Tablespace 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 Tablespace Name object, use the Edit Thresholds page.

Data Source

he data for this metric is derived from the (TotalUsedSpace / MaximumSize) * 100 formula where:

  • TotalUsedSpace: total used space in MB of tablespace.

  • MaximumSize: Maximum size (in MB) of the tablespace. The maximum size is determined by looping through the tablespace's data files.

For additional information about the data source, refer to the fullTbsp.pl Perl script located in the sysman/admin/scripts directory.

User Action

Perform one of the following:

  • Increase the size of the tablespace by: Enabling automatic extension for one of its existing data files, manually resizing one of its existing data files, or adding a new data file.

  • If the tablespace is suffering from tablespace free space fragmentation problems, consider reorganizing the entire tablespace.

  • Relocate segments to another tablespace, thus increasing the free space in this tablespace.

  • Run the Segment Advisor on the tablespace.

5.80 Tablespaces Full (Dictionary Managed)

The metrics in this category check for the amount of space used by each tablespace. The used space is then compared to the available free space to determine tablespace fullness. The available free space takes into account the maximum data file size as well as available disk space. This means that a tablespace will not be flagged as full if datafiles can extend and there is enough disk space available for them to extend.

5.80.1 Tablespace Free Space (MB) (Dictionary Managed)

As segments within a tablespace grow, the available free space decreases. If there is no longer any available free space, meaning datafiles have hit their maximum size or there is no more disk space, then the creation of new segments or the extension of existing segments will fail.

This metric checks for the total available free space in each tablespace. This metric is intended for larger tablespaces, where the Available Space Used (%) metric is less meaningful. If the available free space falls below the size specified in the threshold arguments, then a warning or critical alert is generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every 30 Minutes After Every Sample <= Not Defined Not Defined - Tablespace [%name%] has [%value% mbytes] free

Multiple Thresholds

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

If warning or critical threshold values are currently set for any Tablespace 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 Tablespace Name object, use the Edit Thresholds page.

Data Source

The data for this metric is derived from the MaximumSize - Total Used Space formula where:

  • TotalUsedSpace: total used space in MB of tablespace

  • MaximumSize: Maximum size (in MB) of the tablespace. The maximum size is determined by looping through the tablespaces data files, as well as additional free space on the disk that would be available for the tablespace should a data file autoextend.

User Action

Perform one of the following:

  • Increase the size of the tablespace by: Enabling automatic extension for one of its existing data files, manually resizing one of its existing data files, or adding a new data file.

  • If the tablespace is suffering from tablespace free space fragmentation problems, consider reorganizing the entire tablespace.

  • Relocate segments to another tablespace, thus increasing the free space in this tablespace.

  • Run the Segment Advisor on the tablespace.

5.80.2 Tablespace Space Used (%) (Dictionary Managed)

As segments within a tablespace grow, the available free space decreases. If there is no longer any available free space, meaning datafiles have hit their maximum size or there is no more disk space, then the creation of new segments or the extension of existing segments will fail.

This metric checks the Available Space Used (%) for each tablespace. If the percentage of used space is greater than the values specified in the threshold arguments, then a warning or critical alert is generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g,12c Every 30 Minutes After Every Sample >= 85 97 1 Tablespace [%name%] is [%value% percent] full

Multiple Thresholds

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

If warning or critical threshold values are currently set for any Tablespace 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 Tablespace Name object, use the Edit Thresholds page.

Data Source

The data for this metric is derived from the Total Used Space / MaximumSize * 100 formula where:

  • TotalUsedSpace: total used space in MB of tablespace.

  • MaximumSize: Maximum size (in MB) of the tablespace. The maximum size is determined by looping through the tablespaces data files.

User Action

Perform one of the following:

  • Increase the size of the tablespace by: Enabling automatic extension for one of its existing data files, manually resizing one of its existing data files, or adding a new data file.

  • If the tablespace is suffering from tablespace free space fragmentation problems, consider reorganizing the entire tablespace.

  • Relocate segments to another tablespace, thus increasing the free space in this tablespace.

  • Run the Segment Advisor on the tablespace.

5.81 Tablespaces With Problem Segments

The metrics in this category check for the following:

  • The largest chunk-free space in the tablespace. If any table, index, cluster, or rollback segment within the tablespace cannot allocate one additional extent, then an alert is generated.

  • Whether any of the segments in the tablespace are approaching their maximum extents. If, for any segment, the maximum number of extents minus the number of existing extents is less than 2, then an alert is generated.

Only the tablespaces with problem segments are returned as results.

5.81.1 Segments Approaching Maximum Extents

This metric reports segments which are nearing the upper limit of maximum extents.

Target Version Collection Frequency
All Versions Every 24 Hours

Data Source

The data for this metric is derived from the first 10 segments names which are approaching their MaxExtent in the tablespace.

User Action

If possible, increase the value of the segments MAXEXTENTS storage parameter.

Otherwise, rebuild the segment with a larger extent size ensuring the extents within a segment are the same size by specifying STORAGE parameters where NEXT=INITIAL and PCTINCREASE = 0.

For segments that are linearly scanned, choose an extent size that is a multiple of the number of blocks read during each multiblock read. This will ensure that the Oracle multiblock read capability is used efficiently.

5.81.2 Segments Approaching Maximum Extents Count

This metric checks for segments which are nearing the upper limit of the number of maximum extents. If the number of segments is greater than the values specified in the threshold arguments, then a warning or critical alert is generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 24 Hours After Every Sample > 0 Not Defined - %value% segments in %name% tablespace approaching max extents.

Multiple Thresholds

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

If warning or critical threshold values are currently set for any Tablespace 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 Tablespace Name object, use the Edit Thresholds page.

Data Source

The data for this metric is derived by calculating the number of segments for which the maximum number of extents minus the number of existing extents is less than 2.

For additional information about the data source, refer to the problemTbsp.pl Perl script located in the sysman/admin/scripts directory.

User Action

If possible, increase the value of the segments MAXEXTENTS storage parameter.

Otherwise, rebuild the segment with a larger extent size ensuring the extents within a segment are the same size by using a locally managed tablespace. In the case of a dictionary managed tablespace, specify STORAGE parameters where NEXT=INITIAL and PCTINCREASE = 0.

5.81.3 Segments Not Able to Extend

This metric identifies which segments cannot allocate an additional extent.

Target Version Collection Frequency
All Versions Every 24 Hours

Data Source

The data source for this metric is the first 10 segments names which cannot allocate an additional extent in the tablespace.

User Action

Perform one of the following:

  • Increase the size of the tablespace by enabling automatic extension for one of its existing data files, manually resizing one of its existing data files. or adding a new data file.

  • If the tablespace is suffering from tablespace free space fragmentation problems, consider reorganizing the entire tablespace.

5.81.4 Segments Not Able to Extend Count

This metric checks for segments which cannot allocate an additional extent. If the number of segments is greater than the values specified in the threshold arguments, then a warning or critical alert is generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
All Versions Every 24 Hours After Every Sample > 0 Not Defined - %value% segments in %name% tablespace unable to extend.

Multiple Thresholds

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

If warning or critical threshold values are currently set for any Tablespace 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 Tablespace Name object, use the Edit Thresholds page.

Data Source

After checking for the largest chunk free space in the tablespace, this is the number of segments which cannot allocate an additional extent.

For additional information about the data source, refer to the problemTbsp.pl Perl script located in the sysman/admin/scripts directory.

User Action

Perform one of the following:

  • Increase the size of the tablespace by enabling automatic extension for one of its existing data files, manually resizing one of its existing data files. or adding a new data file.

  • If the tablespace is suffering from tablespace free space fragmentation problems, consider reorganizing the entire tablespace.

  • Relocate segments to another tablespace thus increasing the free space in this tablespace.

5.82 Temporary File Status

The metrics in this category provide the name and status of temporary files.

5.82.1 Status

This metric displays the status of a temporary file.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
9i, 10g, 11g, 12c Every 15 Minutes After Every Sample MATCH OFFLINE Not Defined - The temporary file %NAME% is %STATUS%.

5.83 Throughput

The metrics in this category represent rates of resource consumption or throughput.

5.83.1 Average Active Sessions

This metric represents the average active sessions at a point in time. It is the number of sessions that are either working or waiting.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Not Defined

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Not Defined

Data Source

Not available.

User Action

No user action is required.

5.83.2 Average Synchronous Single-Block Read Latency (ms)

The average latency in milliseconds of a synchronous single-block read. Synchronous single-block reads are a reasonably accurate way of assessing the performance of the storage subsystem. High latencies are typically caused by a high I/O request load. Excessively high CPU load can also cause the latencies to increase.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g Not Defined After Every Sample > Not Defined Not Defined 2 Not Defined

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Not Defined

Data Source

The source of the data is the v$sysmetric view.

User Action

First, verify that your storage subsystem is not operating with component failures, for example, disk, network, or HBA failures. If no issues are found, consider upgrading your storage subsystem.

5.83.3 BG Checkpoints (per second)

This metric represents the BG checkpoints per second.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

Not available.

User Action

The required actions are specific to your site.

5.83.4 Branch Node Splits (per second)

Number of times per second an index branch block was split because of the insertion of an additional value.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

the branch node splits / time

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.5 Branch Node Splits (per transaction)

Number of times per transaction an index branch block was split because of the insertion of an additional value.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

branch node splits / transaction

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.6 Consistent Read Blocks Created (per second)

This metric represents the number of current blocks per second cloned to create consistent read (CR) blocks.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 5 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

CR blocks created / time

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.7 Consistent Read Blocks Created (per transaction)

This metric represents the number of current blocks per transaction cloned to create consistent read (CR) blocks.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

CR blocks created / transactions

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.8 Consistent Read Changes (per second)

This metric represents the number of times per second a user process has applied rollback entries to perform a consistent read on the block.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

consistent changes / time

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.9 Consistent Read Changes (per transaction)

This metric represents the number of times per transaction a user process has applied rollback entries to perform a consistent read on the block.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

consistent changes / transactions

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.10 Consistent Read Gets (per second)

This metric represents the number of times per second a consistent read was requested for a block.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

consistent gets/time

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.11 Consistent Read Gets (per transaction)

This metric represents the number of times per transaction a consistent read was requested for a block.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

consistent gets/transactions

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.12 Consistent Read Undo Records Applied (per second)

This metric represents the number of undo records applied for consistent read per second.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

current blocks converted for CR/time

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.13 Consistent Read Undo Records Applied (per transaction)

This metric represents the consistent read undo records applied per transaction.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

Not available.

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.14 Cumulative Logons (per second)

This metric represents the number of logons per second during the sample period.

This test checks the number of logons that occurred per second during the sample period. If the value is greater than or equal to the threshold values specified by the threshold arguments, and the number of occurrences exceeds the value specified in the Number of Occurrences parameter, then a warning or critical alert is generated.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 5 Minutes After Every Sample > 100 Not Defined 2 Cumulative logon rate is %value%/sec.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample >= 100 Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following tables show how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 5 Minutes After Every Sample > Not Defined Not Defined 2 Cumulative logon rate is %value%/sec.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample >= Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

DeltaLogons / Seconds where:

  • DeltaLogons: difference in 'select value from v$sysstat where name='logons cumulative'' between end and start of sample period

  • Seconds: number of seconds in sample period

User Action

A high logon rate may indicate that an application is inefficiently accessing the database. Database logon's are a costly operation. If an application is performing a logon for every SQL access, that application will experience poor performance as well as affect the performance of other applications on the database. If there is a high logon rate, try to identify the application that is performing the logons to determine if it could be redesigned such that session connections could be pooled, reused, or shared.

5.83.15 Cumulative Logons (per transaction)

This metric represents the number of logons per transaction during the sample period.

The value of this statistic will be zero if there have not been any write or update transactions committed or rolled back during the last sample period. If the bulk of the activity to the database is read only, the corresponding per second metric of the same name will be a better indicator of current performance.

This test checks the number of logons that occurred per transaction. If the value is greater than or equal to the threshold values specified by the threshold arguments, and the number of occurrences exceeds the value specified in the Number of Occurrences parameter, then a warning or critical alert is generated.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 5 Minutes After Every Sample > Not Defined Not Defined 2 Cumulative logon rate is %value% / transaction.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following tables show how often the metric's value is collected and compared against the default thresholds.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Cumulative logon rate is %value%/ transaction.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

DeltaLogons/Transactions where:

  • DeltaLogons: difference in 'select value from v$sysstat where name='logons cumulative'' between end and start of sample period

  • Transactions: number of transactions in sample period

User Action

A high logon rate may indicate that an application is inefficiently accessing the database. Database logon's are a costly operation. If an application is performing a logon for every SQL access, that application will experience poor performance as well as affect the performance of other applications on the database. If there is a high logon rate try to identify the application that is performing the logons to determine if it could be redesigned such that session connections could be pooled, reused or shared.

5.83.16 Database Block Changes (per second)

This metric represents the total number of changes per second that were part of an update or delete operation that were made to all blocks in the SGA.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12g Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

db block changes/time

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.17 Database Block Changes (per transaction)

This metric represents the total number of changes per transaction that were part of an update or delete operation that were made to all blocks in the SGA.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

db block changes/transactions

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.18 Database Block Gets (per second)

This metric represents the number of times per second a current block was requested.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

db block gets/time

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.19 Database Block Gets (per transaction)

This metric represents the number of times per transaction a current block was requested.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

db block gets/transactions

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.20 Database Time (centiseconds per second)

This metric denotes the database time.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10gR2, 11g, 12c Not Defined After Every Sample > Not Defined Not Defined 2 Not Defined

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10gR2, 11g, 12c Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Not Defined

Data Source

Not available.

User Action

The required actions are specific to your site.

5.83.21 DBWR Checkpoints (per second)

This metric represents the number of times, per second, during this sample period DBWn was asked to scan the cache and write all blocks marked for a checkpoint.

The database writer process (DBWn) writes the contents of buffers to datafiles. The DBWn processes are responsible for writing modified (dirty) buffers in the database buffer cache to disk.

When a buffer in the database buffer cache is modified, it is marked dirty. The primary job of the DBWn process is to keep the buffer cache clean by writing dirty buffers to disk. As user processes dirty buffers, the number of free buffers diminishes. If the number of free buffers drops too low, user processes that must read blocks from disk into the cache are not able to find free buffers. DBWn manages the buffer cache so that user processes can always find free buffers.

When the Oracle Server process cannot find a clean reusable buffer after scanning a threshold of buffers, it signals DBWn to write. When this request to make free buffers is received, DBWn writes the least recently used (LRU) buffers to disk. By writing the least recently used dirty buffers to disk, DBWn improves the performance of finding free buffers while keeping recently used buffers resident in memory. For example, blocks that are part of frequently accessed small tables or indexes are kept in the cache so that they do not need to be read in again from disk. The LRU algorithm keeps more frequently accessed blocks in the buffer cache so that when a buffer is written to disk, it is unlikely to contain data that may be useful soon.

Additionally, DBWn periodically writes buffers to advance the checkpoint that is the position in the redo log from which crash or instance recovery must begin.

This test checks the number of times DBWR was asked to advance the checkpoint. If the value is greater than or equal to the threshold values specified by the threshold arguments, and the number of occurrences exceeds the value specified in the Number of Occurrences parameter, then a warning or critical alert is generated.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 5 Minutes After Every Sample > Not Defined Not Defined 2 DBWR checkpoint rate is %value%/sec.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following tables show how often the metric's value is collected and compared against the default thresholds.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 5 Minutes After Every Sample > Not Defined Not Defined 2 DBWR checkpoint rate is %value%/sec.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

DeltaCheckpoints/Seconds where:

  • DeltaCheckpoints: difference in 'select value from v$sysstat where name='DBWR checkpoints'' between sample end and start

  • Seconds: number of seconds in sample period

User Action

A checkpoint tells the DBWR to write out modified buffers to disk. This write operation is different from the make free request in that the modified buffers are not marked as free by the DBWR process. Dirty buffers may also be written to disk at this time and freed.

The write size is dictated by the _db_block_checkpoint_batch parameter. If writing, and subsequently waiting for checkpoints to complete is a problem, the checkpoint completed event displays in the Top Waits page sorted by Time Waited or the Sessions Waiting for this Event page.

If the database is often waiting for checkpoints to complete you may want to increase the time between checkpoints by checking the init.ora parameter db_block_checkpoint_batch: select name, value, is default from v$parameter where name = db_block_checkpoint_batch. The value should be large enough to take advantage of parallel writes. The DBWR uses a write batch that is calculated like this: (db_files * db_file_simultaneous_writes)/2 The write_batch is also limited by two other factors:

  • A port specific limit on the numbers of I/Os (compile time constant).

  • 1/4 of the number of buffers in the SGA.

The db_block_checkpoint_batch is always smaller or equal to the _db_block_write_batch. You can also consider enabling the check point process.

5.83.22 Enqueue Deadlocks (per second)

This metric represents the number of times per second that a process detected a potential deadlock when exchanging two buffers and raised an internal, restartable error.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

enqueue deadlocks/time

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.23 Enqueue Deadlocks (per transaction)

This metric represents the number of times per transaction that a process detected a potential deadlock when exchanging two buffers and raised an internal, restartable error.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

enqueue deadlocks/transactions

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.24 Enqueue Requests (per second)

This metric represents the total number of table or row locks acquired per second.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

enqueue requests/time

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.25 Enqueue Requests (per transaction)

This metric represents the total number of table or row locks acquired per transaction.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

enqueue requests/transactions

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.26 Enqueue Timeout (per second)

This metric represents the total number of table and row locks (acquired and converted) per second that time out before they could complete.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

enqueue timeouts/time

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.27 Enqueue Timeout (per transaction)

This metric represents the total number of table and row locks (acquired and converted) per transaction that timed out before they could complete.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

enqueue timeouts/transactions

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.28 Enqueue Waits (per second)

This metric represents the total number of waits per second that occurred during an enqueue convert or get because the enqueue get was deferred.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

enqueue waits/time

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.29 Enqueue Waits (per transaction)

This metric represents the total number of waits per transaction that occurred during an enqueue convert or get because the enqueue get was deferred.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

enqueue waits / transaction

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.30 Executes (per second)

This metric represents the rate of SQL command executions over the sampling interval.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10gR2, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

DeltaExecutions / Seconds where:

  • DeltaExecutions: difference in 'select value from v$sysstat where name='execute count'' between end and start of sample period

  • Seconds: number of seconds in sample period

User Action

No user action is necessary.

5.83.31 Executes Performed without Parses (%)

This metric represents the percentage of statement executions that do not require a corresponding parse. A perfect system would parse all statements once and then execute the parsed statement over and over without reparsing. This ratio provides an indication as to how often the application is parsing statements as compared to their overall execution rate. A higher number is better.

This test checks the percentage of executes that do not require parses. If the value is less than or equal to the threshold values specified by the threshold arguments, and the number of occurrences exceeds the value specified in the Number of Occurrences parameter, then a warning or critical alert is generated.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 5 Minutes After Every Sample > Not Defined Not Defined 2 Only %value%%% of executes are performed without parses.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 5 Minutes After Every Sample > Not Defined Not Defined 2 Only %value%%% of executes are performed without parses.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

((DeltaExecuteCount - (DeltaParseCountTotal)) / DeltaExecuteCount) * 100 where:

  • DeltaParseCountTotal: difference in 'select value from v$sysstat where name='parse count (total)'' between sample end and start

  • DeltaExecuteCount: difference in 'select value from v$sysstat where name='execute count'' between sample end and start

User Action

An execute to parse ratio of less than 70% indicates that the application may be parsing statements more often than it should. Reparsing the statement, even if it is a soft parse, requires a network round trip from the application to the database, as well as requiring the processing time to locate the previously compiled statement in the cache. Reducing network round trips and unnecessary processing improves application performance.

Use the Top Sessions page sorted by Parses to identify the sessions responsible for the bulk of the parse activity within the database. Start with these sessions to determine whether the application could be modified to make more efficient use of its cursors.

5.83.32 Full Index Scans (per second)

This metric represents the number of fast full index scans per second.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 5 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

index fast full scans (full)/time

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.33 Full Index Scans (per transaction)

This metric represents the number of fast full index scans per transaction.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

index fast full scans (full)/transactions

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.34 Hard Parses (per second)

This metric represents the number of hard parses per second during this sample period. A hard parse occurs when a SQL statement has to be loaded into the shared pool. In this case, the Oracle Server has to allocate memory in the shared pool and parse the statement.

Each time a particular SQL cursor is parsed, this count will increase by one. There are certain operations that will cause a SQL cursor to be parsed. Parsing a SQL statement breaks it down into atomic steps, which the optimizer will evaluate when generating an execution plan for the cursor.

This test checks the number of parses of statements that were not already in the cache. If the value is greater than or equal to the threshold values specified by the threshold arguments, and the number of occurrences exceeds the value specified in the Number of Occurrences parameter, then a warning or critical alert is generated.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 5 Minutes After Every Sample > Not Defined Not Defined 2 Hard parse rate is %value%/sec.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following tables show how often the metric's value is collected and compared against the default thresholds.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 5 Minutes After Every Sample > Not Defined Not Defined 2 Hard parse rate is %value%/sec.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

DeltaParses / Seconds where:

  • DeltaParses: difference in 'select value from v$sysstat where name='parse count (hard)'' between end and start of sample period

  • Seconds: number of seconds in sample period

User Action

If there appears to be excessive time spent parsing, evaluate SQL statements to determine those that can be modified to optimize shared SQL pool memory use and avoid unnecessary statement reparsing. This type of problem is commonly caused when similar SQL statements are written which differ in space, case, or some combination of the two. You may also consider using bind variables rather than explicitly specified constants in your statements whenever possible.

The Top Sessions page sorted by Hard Parses will show you which sessions are incurring the most hard parses. Hard parses happen when the server parses a query and cannot find an exact match for the query in the library cache. Hard parses can be avoided by sharing SQL statements efficiently. The use of bind variables instead of literals in queries is one method to increase sharing.

By showing you which sessions are incurring the most hard parses, this page may lead you to the application or programs that are the best candidates for SQL rewrites.

Also, examine SQL statements which can be modified to optimize shared SQL pool memory use and avoid unnecessary statement reparsing. This type of problem is commonly caused when similar SQL statements are written which differ in space, case, or some combination of the two. You may also consider using bind variables rather than explicitly specified constants in your statements whenever possible.

The SHARED_POOL_SIZE initialization parameter controls the total size of the shared pool. Consider increasing the SHARED_POOL_SIZE to decrease the frequency in which SQL requests are being flushed from the shared pool to make room for new requests.

To take advantage of the additional memory available for shared SQL areas, you may also need to increase the number of cursors permitted per session. You can increase this limit by increasing the value of the initialization parameter OPEN_CURSORS.

5.83.35 Hard Parses (per transaction)

This metric represents the number of hard parses per second during this sample period. A hard parse occurs when a SQL statement has to be loaded into the shared pool. In this case, the Oracle Server has to allocate memory in the shared pool and parse the statement.

Each time a particular SQL cursor is parsed, this count will increase by one. There are certain operations which will cause a SQL cursor to be parsed. Parsing a SQL statement breaks it down into atomic steps which the optimizer will evaluate when generating an execution plan for the cursor. The value of this statistic will be zero if there have not been any write or update transactions committed or rolled back during the last sample period. If the bulk of the activity to the database is read only, the corresponding per second metric of the same name will be a better indicator of current performance.

This test checks the number of hard parses per second during this sample period. If the value is greater than or equal to the threshold values specified by the threshold arguments, and the number of occurrences exceeds the value specified in the Number of Occurrences parameter, then a warning or critical alert is generated.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 5 Minutes After Every Sample > Not Defined Not Defined 2 Hard parse rate is %value% / transaction.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following tables show how often the metric's value is collected and compared against the default thresholds.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 5 Minutes After Every Sample > Not Defined Not Defined 2 Hard parse rate is %value%/ transaction.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data for this metric is derived by the following formula:

DeltaParses/Transactions where:

  • DeltaParses: difference in 'select value from v$sysstat where name='parse count (hard)'' between end and start of sample period

  • Transactions: number of transactions in sample period

User Action

If there appears to be excessive time spent parsing, evaluate SQL statements to determine which can be modified to optimize shared SQL pool memory use and avoid unnecessary statement reparsing. This type of problem is commonly caused when similar SQL statements are written which differ in space, case, or some combination of the two. You may also consider using bind variables rather than explicitly specified constants in your statements whenever possible.

The Top Sessions page sorted by Hard Parses will show you which sessions are incurring the most hard parses. Hard parses happen when the server parses a query and cannot find an exact match for the query in the library cache. Hard parses can be avoided by sharing SQL statements efficiently. The use of bind variables instead of literals in queries is one method to increase sharing.

By showing you which sessions are incurring the most hard parses, this page may lead you to the application or programs that are the best candidates for SQL rewrites.

Also, examine SQL statements which can be modified to optimize shared SQL pool memory use and avoid unnecessary statement reparsing. This type of problem is commonly caused when similar SQL statements are written which differ in space, case, or some combination of the two. You may also consider using bind variables rather than explicitly specified constants in your statements whenever possible.

The SHARED_POOL_SIZE initialization parameter controls the total size of the shared pool. Consider increasing the SHARED_POOL_SIZE to decrease the frequency in which SQL requests are being flushed from the shared pool to make room for new requests.

To take advantage of the additional memory available for shared SQL areas, you may also need to increase the number of cursors permitted per session. You can increase this limit by increasing the value of the initialization parameter OPEN_CURSORS.

5.83.36 I/O Megabytes (per second)

The total I/O throughput of the database for both reads and writes in megabytes per second. A very high value indicates that the database is generating a significant volume of I/O data.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Not Defined After Every Sample > Not Defined Not Defined 2 Not Defined

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Not Defined

Data Source

The source of the data is the v$sysmetric view.

User Action

A high I/O throughput value is not in itself problematic. However, if high I/O latencies (for example, Synchronous Single-Block Read Latencies are causing a performance problem, then reducing the total I/O throughput may help. The source of the I/O throughput can be investigated by viewing a breakdown by either Component or Resource Consumer Group.

5.83.37 I/O Requests (per second)

This metric represents the total rate of I/O read and write requests for the database.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Not Defined After Every Sample > Not Defined Not Defined 2 Not Defined

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
11g, 12c Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Not Defined

Data Source

The source of the data is the v$sysmetric view.

User Action

A high I/O request rate is not in itself problematic. However, if high I/O latencies (for example, Synchronous Single-Block Read Latencies are causing a performance problem, then reducing the total I/O request rate may help. The source of the I/O requests can be investigated by viewing a breakdown by either Component or Resource Consumer Group.

5.83.38 Leaf Node Splits (per second)

Number of times per second an index leaf node was split because of the insertion of an additional value.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data is derived from the following formula:

leaf node splits / time

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.39 Leaf Node Splits (per transaction)

This metric reports the number of times per transaction an index leaf node was split because of the insertion of an additional value.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data is derived from the following formula:

leaf node splits / transactions

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.40 Network Bytes (per second)

This metric represents the total number of bytes sent and received through the SQL Net layer to and from the database.

This test checks the network read/write per second. If the value is greater than or equal to the threshold values specified by the threshold arguments, and the number of occurrences exceeds the value specified in the Number of Occurrences parameter, then a warning or critical alert is generated.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 5 Minutes After Every Sample > Not Defined Not Defined 2 Bytes transmitted via SQL*Net is %value%/sec.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following tables show how often the metric's value is collected and compared against the default thresholds.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Bytes transmitted via SQL*Net is %value%/sec.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data is derived from the following formula:

(DeltaBytesFromClient+DeltaBytesFromDblink+DeltaBytesToClient+DeltaBytesToDblink) / Seconds where:

  • Delta Bytes From Client: difference in 'select s.value from v$sysstat s, visitation n where n.name='bytes received via SQL*Net from client' and n.statistic#=s.statistic#' between end and start of sample period

  • DeltaBytesFromClient: difference in 'select s.value from v$sysstat s, v$statname n where n.name='bytes received via SQL*Net from dblink' and n.statistic#=s.statistic#' between end and start of sample period

  • DeltaBytesFromClient: difference in 'select s.value from v$sysstat s, v$statname n where n.name='bytes sent via SQL*Net to client' and n.statistic#=s.statistic#' between end and start of sample period

  • DeltaBytesFromClient: difference in 'select s.value from v$sysstat s, v$statname n where n.name='bytes sent via SQL*Net to dblink' and n.statistic#=s.statistic#' between end and start of sample period

  • Seconds: number of seconds in sample period

User Action

This metric represents the amount of network traffic in and out of the database. This number may only be useful when compared to historical levels to understand network traffic usage related to a specific database.

5.83.41 Number of Transactions (per second)

This metric represents the total number of commits and rollbacks performed during this sample period.

This test checks the number of commits and rollbacks performed during sample period. If the value is greater than or equal to the threshold values specified by the threshold arguments, and the number of occurrences exceeds the value specified in the Number of Occurrences parameter, then a warning or critical alert is generated.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 5 Minutes After Every Sample > Not Defined Not Defined 2 Transaction rate is %value%/sec.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample >= Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following tables show how often the metric's value is collected and compared against the default thresholds.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Transaction rate is %value%/sec.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample >= Not Defined Not Defined 2 Generated By Database Server

Data Source

The data is derived from the following formula:

DeltaCommits + DeltaRollbacks where:

  • DeltaCommits: difference of 'select value from v$sysstat where name='user commits'' between sample end and start

  • DeltaRollbacks: difference of 'select value from v$sysstat where name='user rollbacks'' between sample end and start

User Action

This statistic is an indication of how much work is being accomplished within the database. A spike in the transaction rate may not necessarily be bad. If response times stay close to normal, it means your system can handle the added load. Actually, a drop in transaction rates and an increase in response time may be indicators of problems. Depending upon the application, transaction loads may vary widely across different times of the day.

5.83.42 Open Cursors (per second)

This metric represents the total number of cursors opened per second.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data is derived from the following formula:

opened cursors cumulative/time

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.43 Open Cursors (per transaction)

This metric represents the total number of cursors opened per transaction.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data is derived from the following formula:

opened cursors cumulative/transactions

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.44 Parse Failure Count (per second)

This metric represents the total number of parse failures per second.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data is derived from the following formula:

parse count (failures)/time

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.45 Parse Failure Count (per transaction)

This metric represents the total number of parse failures per transaction.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following table shows how often the metric's value is collected and compared against the default thresholds.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data is derived from the following formula:

parse count (failures)/transactions

User Action

View the latest Automatic Database Diagnostic Monitor (ADDM) report. For a more detailed analysis, run ADDM from the Advisor Central link on the Database Home page.

5.83.46 Physical Reads (per second)

This metric represents the number of data blocks read from disk per second during this sample period. When a user performs a SQL query, Oracle tries to retrieve the data from the database buffer cache (memory) first, then searches the disk if it is not already in memory. Reading data blocks from disk is much more inefficient than reading the data blocks from memory. The goal with Oracle should always be to maximize memory utilization.

This test checks the data blocks read from disk per second. If the value is greater than or equal to the threshold values specified by the threshold arguments, and the number of occurrences exceeds the value specified in the Number of Occurrences parameter, then a warning or critical alert is generated.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 5 Minutes After Every Sample > Not Defined Not Defined 2 Physical reads are %value%/sec.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following tables show how often the metric's value is collected and compared against the default thresholds.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Physical reads are %value%/sec.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Data Source

The data is derived from the following formula:

DeltaPhysicalReads/Seconds where:

  • DeltaPhysicalReads: difference in 'select s.value from v$sysstat s, v$statname n where n.name='physical reads' and n.statistic#=s.statistic#' between sample end and start

  • Seconds: number of seconds in sample period

User Action

Block reads are inevitable so the aim should be to minimize unnecessary IO. This is best achieved by good application design and efficient execution plans. Changes to execution plans can yield profound changes in performance. Tweaking at system level usually only achieves percentage gains.

To view I/O on a per session basis to determine which sessions are responsible for your physical reads, you should visit the Top Sessions page sorted by Physical Reads. This approach allows you to identify problematic sessions and then drill down to their current SQL statement and perform tuning from there.

To identify the SQL that is responsible for the largest portion of physical reads, visit the Top SQL page sorted by Physical Reads. This page allows you to quickly determine which SQL statements are the causing your I/O activity. From this display you can view the full text of the SQL statement.

The difference between the two methods for identifying problematic SQL is that the Top Sessions view displays sessions that are performing the most physical reads at the moment. The Top SQL view displays the SQL statements that are still in the SQL cache that have performed the most I/O over their lifetime. A SQL statement could show up in the Top SQL view that is not currently being executed.

If the SQL statements are properly tuned and optimized, consider the following suggestions. A larger buffer cache may help - test this by actually increasing DB_BLOCK_BUFFERS. Do not use DB_BLOCK_LRU_EXTENDED_STATISTICS, as this may introduce other performance issues. Never increase the SGA size if it may induce additional paging or swapping on the system.

A less obvious issue which can affect the I/Orates is how well data is clustered physically. For example, assume that you frequently fetch rows from a table where a column is between two values via an index scan. If there are 100 rows in each index block then the two extremes are: 1.Each of the table rows is in a different physical block (100 blocks must be read for each index block). 2.The table rows are all located in the few adjacent blocks (a handful of blocks must be read for each index block).

Pre-sorting or reorganizing data can improve this situation in severe situations as well.

5.83.47 Physical Reads (per transaction)

This metric represents the number of disk reads per transaction during the sample period. When a user performs a SQL query, Oracle tries to retrieve the data from the database buffer cache (memory) first, then goes to disk if it is not in memory already. Reading data blocks from disk is much more expensive than reading the data blocks from memory. The goal with Oracle should always be to maximize memory utilization.

The value of this statistic will be zero if there have not been any write or update transactions committed or rolled back during the last sample period. If the bulk of the activity to the database is read only, the corresponding per second metric of the same name will be a better indicator of current performance.

This test checks the data blocks read from disk per transaction. If the value is greater than or equal to the threshold values specified by the threshold arguments, and the number of occurrences exceeds the value specified in the Number of Occurrences parameter, then a warning or critical alert is generated.

Metric Summary for Database Control

For metrics available in Database Control, no data is collected. Only alerts are generated.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 5 Minutes After Every Sample > Not Defined Not Defined 2 Physical reads are %value% / transaction.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g, 12c Every Minute Not Defined After Every Sample > Not Defined Not Defined 2 Generated By Database Server

Metric Summary for Cloud Control

The following tables show how often the metric's value is collected and compared against the default thresholds.

Target Version Evaluation and Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
8i, 9i Every 10 Minutes After Every Sample > Not Defined Not Defined 2 Physical reads are %value%/ transaction.

Target Version Server Evaluation Frequency Collection Frequency Upload Frequency Operator Default Warning Threshold Default Critical Threshold Consecutive Number of Occurrences Preceding Notification Alert Text
10g, 11g</