Note: As you edited a metric, a new file will be created in the Central Agent monitoring this target $ORACLE_HOME/sysman/emd/collection. The format of the file name is _.xml2. Update the Notification Rule “Database Availability and Critical States”1. Click Preferences from the top right Menu in the Grid Control Home Page.2. Choose Rules from the left side Menu.3. Choose the “Database Availability and Critical States” Rule, then click Edit.4. Go to “Metrics” Tab then select “Generic Alert Log Error”.5. Click the pen Edit Icon beside the metric, choose the severity warning to receive a notification when it reaches the warning threshold.Note: You can also create a new Notification Rule for this specific metric “Generic Alert Log Error” instead of updating the Out-of-Box Notification rule “Database Availability and Critical States”When you define the Warning or Critical Threshold for the metric “Generic Alert Log Error”, if you put any pattern behind the ORA- expression, the full ORA error will not be displayed in the alert (or in the notification if set). You will just get:“Message=1 distinct types of ORA- errors have been found in the alert log.”If you define the Warning or Critical Threshold for the metric “Generic Alert Log Error” with just ORA- without any pattern behind, then the full ORA error number will be displayed in the alert (or in the notification if set). You will get for example:“Message=ORA-error stack (00942) logged in ”However in that case, as you did not specify any filter you will be alerted for all ORA- error messages recorded in the alert.log file. This must be kept in mind.
Komentáře
