Oacore Managed Servers Started In ADMIN State after clone
(Doc ID 2609826.1)
Last updated on DECEMBER 19, 2023
Applies to:
Oracle E-Business Suite Technology Stack - Version 12.2 to 12.2.8 [Release 12.2]Information in this document applies to any platform.
Symptoms
Attempting to start the oacore_server3 managed server in the external Application node after the clone, resulted in error
The following error messages are seen the oacore logfiles
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:263)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: javax.naming.NameNotFoundException: While trying to lookup 'jdbc.preprod' didn't find subcontext 'jdbc'. Resolved ''; remaining name 'jdbc/preprod'
at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1148)
at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:253)
at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
Changes
Cloned the source instance to target instance
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 |
| Changes |
| Cause |
| Solution |
| References |