If I recall correctly then the metric that catches these does regexp matching so you *ought* to be able to prevent the ignorables from firing the alert (I've never actually done this of course, I'm just recommending it on a public forum :( ). Assuming you can do this and it works then you could add that rule into your monitoring templates. On Tue, Apr 30, 2013 at 3:30 PM, Rich Jesse < rjoralist2@xxxxxxxxxxxxxxxxxxxxx> wrote: > Howdy, > > In EM12c BP1, I've got a few databases throwing some of the many errors > that > Support says "oh, just ignore those" (then why generate them in the first > place?!?!?). So these ignorables get turned into EM incidents as generic > operational errors. It would seem to be a bad idea to disable a generic > "catchall" metric and removing the incidents manually via the EM web is > time > consuming. > > Is there a supported way of removing the incidents en masse via command > line > (and, therefore, script)? I've tried to check MOS, but it's still not > letting me look at more than one article per search (BUG filed). > > And, yes, I'm attempting to prevent the ignorables from being generated by > Oracle, but I'll never be able to get it 100%. Lovely... > > TIA! > Rich > > -- > //www.freelists.org/webpage/oracle-l > > > -- Niall Litchfield Oracle DBA http://www.orawin.info -- //www.freelists.org/webpage/oracle-l