EM 12c: Failed Login Count Metric Alerts Frequently in Enterprise Manager 12c Cloud Control after Target Database Upgrade from 11.2.0.4 to 12.1.0.2 (Doc ID 1993580.1)

Last updated on APRIL 08, 2015

Applies to:

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

Symptoms

The Failed Login Count metric alerts frequently in EM 12c Cloud Control after target database upgrade from 11.2.0.4 to 12.1.0.2.

The login account which is failing can be identified as follows (with example data):

select username,
os_username,
userhost,
client_id,
trunc(timestamp),
count(*) failed_logins
from dba_audit_trail
where returncode=1017 and --1017 is invalid username/password
timestamp > sysdate -1
group by username,os_username,userhost, client_id,trunc(timestamp);


SYSMAN oracle host.com 16/03/2015 12793
SYSMAN oracle host.com 15/03/2015 23573


Find any orphan processes which could be trying to log in:

Checking for oc4j processes, on the target host (which may be related to Database Control):

$ ps -ef|grep -i oc4j
oracle 12948 12922 0 22:56 pts/0 00:00:00 grep -i oc4j
oracle 26500 8902 0 Mar09 ? 01:48:34 /u01/app/oracle/product/11.2.0/d bhome_1/jdk/bin/java
-server
-Xmx384M
-XX:MaxPermSize=400M
-XX:MinHeapFreeRatio=20
-XX:MaxHeapFreeRatio=40
-DORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1
-Doracle.home=/u01/app/oracle/product/11.2.0/dbhome_1/oc4j
-Doracle.oc4j.localhome=/u01/app/oracle/product/11.2.0/dbhome_1/<host>.com_orarep/sysman
-DEMSTATE=/u01/app/oracle/product/11.2.0/dbhome_1/<host>.com_orarep
-Doracle.j2ee.dont.use.memory.archive=true
-Djava.protoco l.handler.pkgs=HTTPClient
-Doracle.security.jazn.config=/u01/app/oracle/product/11.2.0/dbhome_1/oc4j/j2ee/OC4J_DBConsole_<host>.com_orarep/config/jazn.xml
-Djava.security.policy=/u01/app/oracle/product/11.2.0/dbhome_1 /oc4j/j2ee/OC4J_DBConsole_<host>.com_orarep/config/java2.policy
-Djavax.net.ssl.KeyStore=/u01/app/oracle/product/11.2.0/dbhome_1/sysman/c onfig/OCMTrustedCerts.txt
-Djava.security.properties=/u01/app/oracle/product/11.2.0/dbhome_1/oc4j/j2ee/home/config/jazn.security.props
-DEMDROOT=/u01/app/oracle/ product/11.2.0/dbhome_1/<host>.com_orarep
-Dsysman.md5pas sword=true
-Drepapi.oracle.home=/u01/app/oracle/product/11.2.0/dbhome_1
-Ddisable.checkForUpdate=true
-Doracle.sysman.ccr.ocmSDK.websvc.keystore=/u01/app/oracle/product/11.2.0/dbhome_1/jlib/emocmclnt.ks
-Dice.pilots.html4.ignoreNonGenericFo nts=true
-Djava.awt.headless=true
-jar /u01/app/oracle/product/11.2.0/dbhome_1/oc4j/j2ee/home/oc4j.jar
-config/u01/app/oracle/product/11.2.0/dbhome_1/oc4j/j2ee /OC4J_DBConsole_<host>.com_orarep/config/server.xml


Checking for java processes, on the target host (which may be related to Database Control):

$ ps -ef|grep -i java
oracle 11305 11252 0 Mar12 ? 00:19:24
/u01/app/oracle/product/EMGC/core/12.1.0.2.0/jdk/bin/java
-Xmx128M
-XX:MaxPermSize=96M
-server
-Djava.security.egd=file:///dev/./urandom
-Dsun.lang.ClassLoader.allowArraySyntax=true
-XX:+UseLinuxPosixThreadCPUClocks -XX:+UseConcMarkSweepGC
-XX:+CMSClassUnloadingEnabled -XX:+UseCompressedOops
-Dwatchdog.pid=11252 -cp /u01/app/oracle/product/EMGC/core/12.1.0.2.0/jdbc/lib/ojdbc5.jar:/u01/app/oracle/product/EMGC/core/12.1.0.2.0/ucp/lib/ucp.jar:/u01/app/oracle/product/EMGC/core/12.1.0.2.0/modules/oracle.http_client_11.1.1.jar:/u01/app/oracle/product/EMGC/core/12.1.0.2.0/lib/xmlparserv2.jar:/u01/app/oracle/product/EMGC/core/12.1.0.2.0/lib/jsch.jar:/u01

This java process is not associated with a Database Control instance, but with the 12.1.0.2 EM Agent.

Cause

Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms