Creating an Additional System Component in Fusion Middleware 11g Fails with org.omg.CORBA.COMM_FAILURE
(Doc ID 1293253.1)
Last updated on AUGUST 10, 2020
Applies to:
Oracle Fusion Middleware - Version 11.1.1.0.0 to 11.1.1.4.0 [Release Oracle11g]Information in this document applies to any platform.
Symptoms
When attempting to create an additional Reports component in Fusion Middleware 11g by running the following command:
the component creation fails and the following error is written to the
<ORACLE_INSTANCE>/diagnostics/logs/OPMN/opmn/provision.log
:
Caused by: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.COMM_FAILURE: vmcid: SUN minor code: 203 completed: Maybe]
at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:83)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:624)
at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:566)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:85)
at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:31)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:46)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:177)
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 |