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. Since 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. The user can manually clear these alerts, they will not automatically clear after the next collection.
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 30 Minutes |
After Every Sample |
>= |
150 |
300 |
1* |
There have been %value% failed login attempts in the last %failed_login_interval_min% minutes. |
* Once an alert is triggered for this metric, it must be manually cleared.
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. See Editing Thresholds for information on accessing the Edit Thresholds page.
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
No user action is required.
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.