My Oracle Support Banner

EM 13c: DB Alert Log Filter Suppression Is Not Working When White Spaces in ORA-Errors (Doc ID 2681254.1)

Last updated on OCTOBER 15, 2020

Applies to:

Enterprise Manager for Oracle Database - Version 13.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

In  Enterprise Manager (EM) Cloud Control, an alert log filter expression is set on a Database target to filter ORA- errors but certain ORA- errors are not being filtered, and a notification is sent.

The navigation path for updating the settings is shown below:

Targets > Databases > Click on Database > from database drop-down menu > Monitoring > Metrics & Collection Settings > DB Alert log > Click on Edit for 'Genetic Alert Log Error' > bottom of page 'Alert Log Filter Expression' field is available which can be used to suppress ORA- errors from warning/critical threshold alerts.

Sample Filter Expression:

.*ORA-0*(54|60|1142|1146)\D.*|.*ORA-00600:.*\[Cursor not typechecked]*\].|.*ORA-00600:.*\[17182][^\]]*\].|.*ORA-07445:.*\[kghfrf\(\)\+193][^\]]*\].|.*ORA-07445:.*\[kgherrordmp\(\)\+81][^\]]*\].* 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.