How to - Monitor Non Critical 11g Database Alert Log Errors Using a SQL UDM
Last updated on JANUARY 31, 2018
Applies to:Enterprise Manager Base Platform - Version 10.2.0.5 to 220.127.116.11 [Release 10.2 to 11.2]
Information in this document applies to any platform.
As of Enterprise Manager 10g, Grid Control, version 10.2.0.5.0 (and Database control for 11g databases), 11g databases no longer use the 'Generic Alert Log' metric to raise alerts for errors logged in the database alert log. Instead, alerts are raised for specific errors that have been categorized as being important in the ADR framework via a set of new metrics. See Note 949858.1 Monitoring 11g Database Alert Log Errors in Enterprise Manager for more details.
Although this adds a lot of value with the integration of these alerts within the Support Workbench, the downside is that the new metrics do not allow alerts to be raised for ALL errors that can potentially be logged in the alert log.
This note gives details of how to create a SQL UDM that raises alerts when ORA errors are recorded in the 11g database log.xml file.
NOTE: The note is provided as an example of how it is possible to monitor the alert log using an SQL UDM. The code provided in the note is not supported as part of the product so please do not log an SR if you have problems implementing the UDM. Instead, please provide feedback or suggestions by adding a comment to the note. The author commits to assisting with any problems experienced but there can be no guarantees of service level/response time. Likewise, this mechanism should NOT replace the robust mechanisms provided for monitoring critical alerts in 11g databases as detailed in Note 949858.1 Monitoring 11g Database Alert Log Errors in Enterprise Manager.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms