How to filter out ORA-3137 errors from creating incidents in EM?

From: Rich J <>
Date: Mon, 7 Dec 2020 10:06:14 -0600
Message-ID: <>

Hey all,

One of our vendor apps insists on using the 12.1 client, which has a known bug that is causing daily ORA-3137 errors in one of our 19.6 DBs. The errors create incidents in ADR, which EM 13.4 picks up and dutifully alerts me.

There may be a patch to the client to fix the errors, but that'll take weeks/months to test and implement. In the meantime, I'd like to prevent EM from alerting me for ORA-3137s from this particular DB.

In EM, this alert shows to be from the Incident:Generic Incident metric. So under the "Metric and Collection Settings" for the DB target, I added "ORA*3137" under the Warning Threshold for the "Generic Incident" metric, and left the Critical as ".*" and the Comparison as "Matches". I'm guessing that the Critical threshold should also be modified, as it's still creating critical incidents (and, therefore, notifications) for ORA-3137 errors. But as this doesn't appear to be a full regex implementation (or is it?), I'm not sure what value it could be. I also couldn't find any help in the EM docs on setting these values.

Anyone set EM to ignore a specific ORA error?


Received on Mon Dec 07 2020 - 17:06:14 CET

Original text of this message