Database Administration (MOSC)

MOSC Banner

Disabling OEM monitoring for specific alert log errors

in Database Administration (MOSC) 2 commentsAnswered ✓

Hi all,

Please excuse if this is a dumb question but I haven't yet been able to find any good answers. We recently started upgrading our production databases from 11g to 19c. All is fine but since the upgrade, we've been getting messages like this in the alert log, which are triggering alerts from our OEM monitoring:

KILL SESSION for sid=(1629, 31461):
 Reason = alter system kill session
 Mode = KILL HARD SAFE -/-/-
 Requestor = USER (orapid = 234, ospid = 666524, inst = 1)
 Owner = Process: USER (orapid = 1081, ospid = 3327021)
 Result = ORA-31

We don't wish to be alerted for each of these messages. Is there a way to either exclude them from the alert logs, or to disable OEM alerting for this specific message (it seems to be matching on the "Result = ORA-31" piece)?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center