My Oracle Support Banner

OPSS - OMS Not Starting , After Failed Attempt To Upgrade Repository Database From 12.1. To 13c ->Internal Exception: java.sql.SQLException: ORA-01017: invalid username/password; logon denied (Doc ID 2444159.1)

Last updated on OCTOBER 16, 2019

Applies to:

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

Symptoms


Tried to upgrade our repository database from 12.1. to 12.2 but the upgrade failed. The database was restored successfully  and all changes were reverted back but the OMS is not starting.

Running OEM 13c and repository database 12.1 is on Windows server 2012 R2 with OMS on other windows server 2012 R2.


The listener and the repository database is up and running and I can connect to it remotely using SYSMAN.

Get the following message when  try to access OEM -- Enterprise Manager Cloud Control is not currently available. The <SERVER_NAME> server where Cloud Control runs, or some other component, might be down. Retry

Attempting to start Adminserver it fails with the following error:

Caused By: oracle.security.jps.JpsException: oracle.security.jps.service.policystore.PolicyStoreException: javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: ORA-01017: invalid username/password; logon denied
....

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.rmi.cluster.RemoteBinderFactoryService errors were found
8. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.rmi.cluster.RemoteBinderFactoryService
9. java.lang.IllegalArgumentException: While attempting to resolve the dependencies of weblogic.cluster.ClusterServiceActivator errors were found
10. java.lang.IllegalStateException: Unable to perform operation: resolve on weblogic.cluster.ClusterServiceActivator

at org.jvnet.hk2.internal.Collector.throwIfErrors(Collector.java:88)
at org.jvnet.hk2.internal.ClazzCreator.resolveAllDependencies(ClazzCreator.java:269)
at org.jvnet.hk2.internal.ClazzCreator.create(ClazzCreator.java:413)
at org.jvnet.hk2.internal.SystemDescriptor.create(SystemDescriptor.java:456)
at org.glassfish.hk2.runlevel.internal.AsyncRunLevelContext.findOrCreate(AsyncRunLevelContext.java:225)
Truncated. see log file for complete stacktrace
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)
at weblogic.security.service.SecurityServiceManager.preInitialize(SecurityServiceManager.java:925)
at weblogic.security.PreSecurityService.start(PreSecurityService.java:139)
at weblogic.server.AbstractServerService.postConstruct(AbstractServerService.java:78)
Truncated. see log file for complete stacktrace
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)
at java.lang.reflect.Method.invoke(Method.java:606)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.startJPS(CommonSecurityServiceManagerDelegateImpl.java:1499)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.JpsException: oracle.security.jps.service.policystore.PolicyStoreException: javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: ORA-01017: invalid username/password; logon denied

Error Code: 1017
at oracle.security.jps.internal.config.OpssCommonStartup.start(OpssCommonStartup.java:211)
at oracle.security.jps.wls.JpsWlsStartup.start(JpsWlsStartup.java:80)
at oracle.security.jps.JpsStartup.start(JpsStartup.java:186)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
Truncated. see log file for complete stacktrace
Caused By: oracle.security.jps.service.policystore.PolicyStoreException: javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: ORA-01017: invalid username/password; logon denied
....

<Aug 31, 2018 10:59:33 AM CDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down.>
<Aug 31, 2018 10:59:33 AM CDT> <INFO> <NodeManager> <The server '<DOMAIN_NAME>' with process id <PROCESS_ID> is no longer alive; waiting for the process to die.>
<Aug 31, 2018 10:59:33 AM CDT> <FINEST> <NodeManager> <Process died.>
<Aug 31, 2018 10:59:33 AM CDT> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Aug 31, 2018 10:59:33 AM CDT> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>

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.