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
