Alerts (Alerts)
The Alerts
parameter provides information about the default Oracle errors or user-defined errors written to the alert log for this instance. By default, the Alerts parameter alarms only when it detects an ORA-006XX error. The ORA-006xx errors are used by Oracle to report internal exceptions. You can modify the errors that are monitored by the Alerts parameter by using the Error Log Filter menu command.
The first time that the parameter runs after discovery, it initializes the parameter value by setting it to zero. Once the parameter is initialized, it scans 1 MB of data in the alert log every 600 seconds (10 minutes) for new entries.
This parameter is not affected by tablespace, object, or user exclusions. This parameter has a default value of 1, that is, 1 is the OK state. The parameter reports the following values:
Value | Description |
---|---|
1 | The data in the Oracle instance alert log file was successfully read and contents do not match the user defined filters. A BMCPOK error occured while the SQL query was executed to read the alert log file path. |
2 | The alreader utility failed to start or failed to register the Oracle instance alert log file. |
3 | ORA- errors occured while the SQL query was executed to read the alert log file path. The data in the Oracle instance alert log file was successfully read and it contains matches to the user defined filters. |
5 | The Oracle instance alert log file is not accessible. No data was returned while the SQL query was executed to read the alert log file path. The user does not have permission to access the Oracle instance alert log file. The data in the Oracle instance alert log file was successfully read and ORA- errors exist. |
The annotation in the Alerts parameter shows the results of values 1, 2, 3, and 5.
Recommendations
Use the Oracle Server Admin > Oracle Error Code Lookup menu command to view the description of an error.
Do not adjust the alarm ranges for this parameter. These thresholds are not on a sliding scale; each alarm range is tied to specific errors in the alert log. If you want to suppress alarms and warnings, disable Border Alarm, Alarm1 and Alarm2. This allows the parameter to continue gathering data without going into an alert state. If you want to stop the parameter from gathering data, deactivate the parameter.
BMC PATROL properties
Attribute | Default value |
---|---|
Application class | ORACLE_AVAILABILITY |
Command type | PSL |
Platform | All |
Icon style | StopLight |
Unit | None |
Border range | Undefined |
Alarm1 range | 2-4 warn |
Alarm2 range | 4-6 alarm |
Scheduling(poll time) | 600 seconds Changing this poll time can result in missed alerts |
Active at installation | Yes |
Parameter type | Standard |
Value set by | Parameter collects its own data |
Annotation | Complete text for all Alert Log Entries which contain "ORA-" |
External Files: | PATROL for Oracle Database looks for Alert_<SID>.log in the directory <diagnostic_dest>/diag/rdbms/<dbname>/<instanceName>/trace |
BMC ProactiveNet Performance Management properties
Property | Default value |
---|---|
Monitor type | Oracle Database Availability |
Key Performance Indicator | Yes |
Monitor for abnormalities | Yes |
Graph by default | Yes |
Availability | No |
Response time | No |
Normal distribution | Yes |
Statistical | No |
Comments
Log in or register to comment.