EM 12c, 13c : OMS Startup Fails After Adding or Making Changes To An LDAP Authenticator Provider: JPS-02592 (Doc ID 2221196.1)

Last updated on JANUARY 20, 2017

Applies to:

Enterprise Manager Base Platform - Version 12.1.0.4.0 and later
Information in this document applies to any platform.

Symptoms

OMS startup fails with:

$ emctl start oms
Oracle Enterprise Manager Cloud Control 13c Release 1
Copyright (c) 1996, 2015 Oracle Corporation. All rights reserved.
Starting Oracle Management Server...
WebTier Successfully Started
Oracle Management Server Could Not Be Started
Check EM Server log file for details: <gc_inst>/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.out
AdminServer Could Not Be Started
Check Admin Server log file for details: <gc_inst>/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/logs/EMGC_ADMINSERVER.out
Oracle Management Server is Down
JVMD Engine is Down
Starting BI Publisher Server ...
BI Publisher Server Could Not Be Started. Check BIP Server log file for details.
BI Publisher Server Logs: <gc_inst>/user_projects/domains/GCDomain/servers/BIP/logs/
AdminServer Could Not Be Started
Check Admin Server log file for details: <gc_inst>/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/logs/EMGC_ADMINSERVER.out
BI Publisher Server is Down

 -  LDAP Adapter had been configured recently, from the WLS Console directly instead of the "emctl config auth ad" command.

-   The <gc_inst>/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/logs/EMGC_ADMINSERVER.out file shows the below errors:

SEVERE: Failed to push ldap config data to libOvd for service instance "idstore.ldap" in JPS context "default", cause: java.lang.NullPointerException
Dec 30, 2016 5:07:18 PM oracle.security.opss.internal.runtime.ServiceContextManagerImp"emctl config auth ad" command.l createContextInternal
WARNING: Service instance "idstore.ldap" cannot be instantiated. Reason: oracle.security.jps.service.idstore.IdentityStoreException: JPS-02592: Failed to push ldap config data to 
libOvd for service instance "idstore.ldap" in JPS context "default", cause: java.lang.NullPointerException.
Dec 30, 2016 5:07:18 PM oracle.security.jps.internal.config.OpssCommonStartup start
INFO: Jps startup failed.
<30/12/2016 5:07:18 PM AEDT> <Error> <Security> <BEA-090892> <The loading of an OPSS java security policy provider failed due to an exception. See the exception stack trace or the 
server log file for the root cause. If there is no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: null>
<30/12/2016 5:07:18 PM AEDT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: A MultiException has 10 exceptions. They are:
1. weblogic.security.SecurityInitializationException: The loading of an OPSS java security policy provider failed due to an exception. See the exception stack trace or the server 
log file for the root cause. If there is no obvious cause, enable the debug flag -Djava.security.debug=jpspolicy to get more information. Error message: null
2. java.lang.IllegalStateException: Unable to perform operation: post construct on weblogic.security.PreSecurityService
3. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.security.SecurityService errors were found
4. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.security.SecurityService
5. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.jndi.internal.RemoteNamingService errors were found
6. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.jndi.internal.RemoteNamingService
7. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.management.mbeanservers.runtime.internal.RuntimeServerService errors were found
8. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.management.mbeanservers.runtime.internal.RuntimeServerService
9. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.cacheprovider.CacheProviderServerService errors were found
10. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.cacheprovider.CacheProviderServerService

Similar errors are seen for the EMGC_OMS1 managed server as well.

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