My Oracle Support Banner

EM 12C Cloud Control: Logging in to the Console Fails with Error Message 'Authentication failed. If problem persists, contact your system administrator' (Doc ID 1369910.1)

Last updated on FEBRUARY 02, 2016

Applies to:

Enterprise Manager Base Platform - Version 12.1.0.1.0 and later
Information in this document applies to any platform.
Checked for relevance on 26-Jun-2014

Symptoms

1. Logging into 12C Cloud Control gives the following error message :

Authentication failed. If problem persists, contact your system administrator
As shown there :



- ..<Middleware_Home>/gc_inst/em/EMGC_OMS1/sysman/log/emoms_pbs.log file shows:

2011-10-22 22:51:23,607 [EventCoordinator] WARN jdbc.ConnectionCache _getConnection.374 - Got a fatal exeption when getting a connection; Error code = 17002; Cleaning up cache and retrying
2011-10-22 22:51:23,608 [Hung_EventCoordinator_1] WARN jdbc.ConnectionCache _getConnection.373 - IO Error: The Network Adapter could not establish the connection
java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection
at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:443)
at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:670)

2. After some time OMS comes down and accessing the 12C Cloud Control gives the error message:

Backend WLS or EM application seems to be down

- Verifying ../<Middleware_Home>/gc_inst/em/EMGC_OMS1/sysman/log/emoms_pbs.log at this point shows the following error message:
2011-10-22 22:51:57,747 [Thread-3360] ERROR healthMonitor.HealthMonitor executeQuery.1171 - java.lang.NullPointerException
java.lang.NullPointerException
at oracle.sysman.util.healthMonitor.HealthMonitor.executeQuery(HealthMonitor.java:1098)
at oracle.sysman.util.healthMonitor.HealthMonitor.dumpRepositoryInfo(HealthMonitor.java:1065)
at oracle.sysman.util.healthMonitor.HealthMonitor$OMSDiagnosticsThread.run(HealthMonitor.java:1399)
2011-10-22 22:51:57,748 [Job Dispatcher Thread] ERROR healthMonitor.HealthMonitor restart.662 - HealthMonitor Oct 22, 2011 10:51:16 PM Job Dispatcher error: Could not connect to repository
Critical error err=3 detected in module Job Dispatcher
OMS will be restarted. A full thread dump will be generated in the log file 
/u01/oracle/middleware/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.out
to help Oracle Support analyse the problem. 
Please consult My Oracle Support Note 964469.1 for additional information.

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

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