EM 13.5: Condition Based Alert Log Monitoring - Send Mail Alerts Based on Comparison Result of Two ORA- Errors in Alert Log
(Doc ID 2815540.1)
Last updated on OCTOBER 26, 2021
Applies to:
Enterprise Manager for Oracle Database - Version 13.5.0.0.0 and laterInformation in this document applies to any platform.
Goal
So far alert log monitoring detects any ORA- error logged in database alert log. These ORA- errors will be sent through email notifications depending on threshold settings on 'Alert Log/DB Alert' Log metric. At certain times the ORA- errors occurs in pair and noted in database alert log. There is a requirement to compare these ORA- error pairs, and send the alert only if certain condition matches.
For example, below are the entries from DB alert log.
/u02/app/oracle/diag/rdbms/p19004a/p19004a1/trace/p19004a1_j003_384842.trc
(incident=9598) (PDBNAME=P04A):
ORA-4031: unable to allocate 20504 bytes of shared memory ("shared pool", "unknown object","sga heap(1,0)","KTI SGA freeable small po")
ORA-2063: preceding line from A09040A_ODBS
In this case, if there is 'ORA-4031' is followed by 'ORA-2063', the alert should not trigger by OEM. This ORA- pair indicates some known issue over remote DB in customer setup. Similarly there might be other requirements for comparing two ORA- errors before sending the mail notification.
Solution
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Goal |
Solution |
References |