My Oracle Support Banner

EM 12c : Alerts are not Raised for "DB Alert Log" / "Alert Log" Metrics of Target Database if DB and Agent are Installed by Different OS users (Doc ID 2137632.1)

Last updated on JUNE 24, 2016

Applies to:

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

Symptoms

Using 12c EM to monitor a target database, whose alert.log reports multiple ORA- errors. However, no alerts are raised for the "DB Alert Log" or the "Alert Log" metric of this target database, though the thresholds match and the ORA- error is not part of the Filter expression for the "Generic alert log error" metric.

The <AGENT_INST>/sysman/log/emagent_perl.trc file reports the below errors:

alertlog.pl: Tue May 3 18:33:46 2016: WARN: target: FAD7524FDEE1E951D878EAA8FD6AAA8B; unable to open alert log at 
/u01/app/oracle/product/11.2.0/diag/rdbms/orcl/ORCL/trace/alert_orcl.log
.....................
alertlog_dedup.pl: Tue May 3 18:36:52 2016: WARN: target: FAD7524FDEE1E951D878EAA8FD6AAA8B; 
unable to open alert log at /u01/app/oracle/product/11.2.0/diag/rdbms/orcl/ORCL/trace/alert_orcl.log

- The Agent and the target DB have been installed by two different OS users and the Agent OS user.

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.