EM 12c : Login to the EM Console from Browser Intermittently Fails with "Authentication Failed"
Last updated on MARCH 28, 2016
Applies to:Enterprise Manager Base Platform - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Using a multi-OMS setup with an SLB and the repository in a 2-node RAC Database.
Login to console as SYSMAN user fails intermittently with the Error Message: 'Authentication failed. If problem persists, contact your system administrator'
- The SYSMAN account is not locked at the database nor has the password been modified recently.
- It is possible to login to Repository database as the SYSMAN user via sqlplus.
- Sometimes, login to the Console UI works fine but clicking on any link returns a pop-up with:
Internal Error has occurred. Check the log file for details. ADFC-0619: Authorization check failed: 'core.groups.sysDashBoardPageDef' 'VIEW'.
- The<gc_inst>/em/EMGC_OMS1/sysman/log/emoms.trc reports the below errors:
2016-02-16 20:48:00,306 [[ACTIVE] ExecuteThread: '26' for queue: 'weblogic.kernel.Default (self-tuning)'] WARN errPopup.ErrorPopupUtil logp.251 - oracle.adf.controller.security.AuthorizationException: ADFC-0619: Authorization check failed: 'core.groups.sysDashBoardPageDef' 'VIEW'. at oracle.adf.controller.internal.security.AuthorizationEnforcer.handleFailure(AuthorizationEnforcer.java:182) at oracle.adf.controller.internal.security.AuthorizationEnforcer.internalCheckPermission(AuthorizationEnforcer.java:162) at oracle.adf.controller.internal.security.AuthorizationEnforcer.checkPermission(AuthorizationEnforcer.java:116) at oracle.adfinternal.controller.state.ControllerState.checkPermission(ControllerState.java:683) at oracle.adfinternal.controller.state.ControllerState.synchronizeStatePart2(ControllerState.java:582)
- The <gc_inst>/em/EMGC_OMS1/sysman/log/emctl.msg file reports multiple OMS re-starts:
HealthMonitor Feb 16, 2016 9:44:33 PM OMS Heartbeat Recorder: error: Could not get id: java.sql.SQLRecoverableException: No more data to read from socket Critical error err=3 detected in module OMS Heartbeat Recorder: OMS will be restarted. A full thread dump will be generated in the log file /x/home/oracle/product/em/MW12104/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.out to help Oracle Support analyse the problem.
- The alert.log of one of the repository database instance repeatedly reports:
Exception [type: SIGSEGV, SI_KERNEL(general_protection)] [ADDR:0x0] [PC:0x151C6A9, kwqmncif()+31] [flags: 0x0, count: 1] Errors in file /x/home/oracle/diag/rdbms/oemoc_slc_live1/OEMOC_2/trace/OEMOC_2_ora_55328.trc (incident=472724): ORA-07445: exception encountered: core dump [kwqmncif()+31] [SIGSEGV] [ADDR:0x0] [PC:0x151C6A9] [SI_KERNEL(general_protection)]  Use ADRCI or Support Workbench to package the incident
The other DB instances however has no such errors. Each time the OMS connection is routed to the problematic instance, the login fails or the ADFC errors are reported. But the same work fine when the OMS connections are routed to the working DB instance.
This issue could also occur in case of a single OMS installation having repository in a RAC database.
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