This metric represents the time (in milliseconds) that it takes for the Listener to respond to a network request (ping).
The rest of the information in this section is only valid for this metric when it appears in either the Enterprise Manager Grid Control or the Enterprise Manager Database Control (if applicable).
The following table shows how often the metric's value is collected and compared against the default thresholds. The 'Consecutive Number of Occurrences Preceding Notification' column indicates the consecutive number of times the comparison against thresholds should hold TRUE before an alert is generated.
|
Target Version |
Evaluation and Collection Frequency |
Upload Frequency |
Operator |
Default Warning Threshold |
Default Critical Threshold |
Consecutive Number of Occurrences Preceding Notification |
Alert Text |
|
All Versions |
Every 5 Minutes |
After Every Sample |
> |
400 |
1000 |
1 |
Listener response to a TNS ping is %value% msecs |
The value of this metric is derived using the TNSPING command. For more information about the TNSPING command, see the OracleŽ Database Net Services Administrator's Guide 10g Release 2 (10.2).
If the Listener response time consistently exceeds the threshold, users are likely experiencing performance issues while accessing the database or other services on this host. Use the Enterprise Manager Central Console to review other performance indicators, such as the overall health of your database and the response time of your hosts and Web Applications.
Related Topics
About Alerts
About the Metric Detail Page
Editing Thresholds
Understanding Line Charts
Copyright © 1996, 2009, Oracle and/or its affiliates. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates.
Other names may be trademarks of their respective owners.