Re: OEM 12c ( generating too many alerts on Metrics "Logons Per Sec"

From: Mladen Gogala <>
Date: Wed, 27 Dec 2017 07:45:46 -0500
Message-ID: <>

On 12/26/2017 04:49 PM, Jonathan Lewis wrote:
> Ashoke,
> The correct way to fix this problem is to find out what is logging on 146 times per second and stop it - it can't possibly be necessary and it's probably having an appalling effect on the performance of the database. I'd expect to see lots of time lost on library cache latch and dictionary cache latch activity, probably with plenty of mutex sleeps as well and "connection management" showing up with a significant (though relatively small) amount of time in the Time Model report.
> If you want to avoid too many messages flooding your inbox (until you've fixed the important problem) create a rule that redirects the incoming alert messages to a separate file based on the subject and some aspect of the message content.
> Regards
> Jonathan Lewis

I agree completely. In my opinion, the best way of finding out what is going on and where is it coming from is auditing, in particular "AUDIT NETWORK".  I have excellent experience with the AUDIT NETWORK command.

Mladen Gogala
Oracle DBA

Received on Wed Dec 27 2017 - 13:45:46 CET

Original text of this message