My Oracle Support Banner

OPSS - Unable to Start OMS Server Observing JPS-01055 and JPS-01013 Errors (Doc ID 2476438.1)

Last updated on DECEMBER 07, 2018

Applies to:

Oracle Platform Security for Java - Version 12.1.3.0.0 and later
Information in this document applies to any platform.

Symptoms

Starting OMS Admin Server fails with the following error:

<Error> <Security> <xxxx> <EMGC_ADMINSERVER> <[STANDBY] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <e80cd45c-7fbe-4f75-bd7f-b3459fd4e98b-00000001> <1543031153839> <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>

<Critical> <WebLogicServer> <xxxxx> <EMGC_ADMINSERVER> <main> <> <> <> <1543031153866> <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

at org.jvnet.hk2.internal.Collector.throwIfErrors(Collector.java:88)

at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:269)

Caused By: 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

at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1487)

at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.preInitialize(CommonSecurityServiceManagerDelegateImpl.java:1090)

Caused By: java.lang.reflect.InvocationTargetException

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

Caused By: oracle.security.jps.JpsException: JPS-01055: Could not create credential store instance. Reason oracle.security.jps.service.credstore.CredStoreException: JPS-01013: The credential store DN cn=CredentialStore,cn=opssSecurityStore,cn=JPSContext,cn=opssRoot is missing in the store; the target DN must be pre-configured.

at oracle.security.jps.internal.config.OpssCommonStartup.start(OpssCommonStartup.java:216)

at oracle.security.jps.wls.JpsWlsStartup.start(JpsWlsStartup.java:90) 

 

Generally, this error comes if the OPSS schema has got corrupted (Ref: Doc ID 2066916.1)

However in this scenario the credential store DN was present in the DB as shown by the following query executed from the OPSS schema

SQL> select * from JPS_DN where rdn like '%cn=credentialstore%';

ENTRYID RDN   PARENTDN     RFU1        RFU2

-----------------------------------------------------------------------------

 3004 cn=credentialstore cn=oracleschemaversion,cn=opss,

 5004 cn=credentialstore cn=opssroot,cn=jpscontext,cn=opsssecuritystore,

 

 Additionally able to connect to DB as OPSS schema account and there was no recent password change  happened

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.