The Configuration Wizard config.sh Fails With Exit Code 11 At Starting Up OPMN Phase (Doc ID 1274392.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle Fusion Middleware - Version: 11.1.1.2.0 and later   [Release: and later ]
Generic UNIX

Symptoms

In a FMW 11.1.1.2.0 installation on Red Hat 4 x86-64 the Configuration Wizard fails when configuring OID, or in general configuring an opmn managed component. The failure under the covers is the opmnctl start commands fail. This is the excerpt from the install<timestamp>.log file:


opmnctl start: failed.
oracle.as.provisioning.util.ConfigException:
Error creating ASInstance asinst_1.
Cause:
An internal operation has failed: Error in starting opmn server
Unexpected exit code (11) returned by opmnctl.
Action:
See logs for more details.
at oracle.as.provisioning.util.ConfigException.createConfigException(ConfigException.java:123)
at oracle.as.provisioning.fmwadmin.ASInstanceProv._createInstance(ASInstanceProv.java:317)
at oracle.as.provisioning.fmwadmin.ASInstanceProv.createInstance(ASInstanceProv.java:166)
at oracle.as.provisioning.fmwadmin.ASInstanceProv.createInstanceAndComponents(ASInstanceProv.java:116)
at oracle.as.provisioning.engine.WorkFlowExecutor._createASInstancesAndComponents(WorkFlowExecutor.java:525)
at oracle.as.provisioning.engine.WorkFlowExecutor.executeWLSWorkFlow(WorkFlowExecutor.java:441)
at oracle.as.provisioning.engine.Config.executeConfigWorkflow_WLS(Config.java:866)
at oracle.as.idm.install.config.BootstrapConfigManager.doExecute(BootstrapConfigManager.java:1287)
at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:335)
at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:87)
at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:104)
at oracle.as.install.engine.modules.configuration.action.ActionRequest.perform(ActionRequest.java:15)
at oracle.as.install.engine.modules.configuration.action.RequestQueue.perform(RequestQueue.java:63)
at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:158)
at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:83)
at java.lang.Thread.run(Thread.java:619)
Caused by: oracle.as.management.opmn.optic.OpticException: Error in starting opmn server

Starting up manually opmn from the command line with $ORACLE_INSTANCE/bin/opmnctl start fails as well with the error:


$ORACLE_INSTANCE/bin/opmnctl start
opmnctl start: failed.

Checking the logs directory under $ORACLE_INSTANCE/diagnostics/logs/OPMN/opmn there are no log files created.

Trying to manually startup the opmn binary fails as well with a SIGSEGV core dump, e.g.:


ORACLE_HOME=/app/oracle/Middleware/Oracle_IDM1
LD_LIBRARY_PATH=$ORACLE_HOME/lib:$ORACLE_HOME/opmn/lib:$LD_LIBRARY_PATH
export ORACLE_HOME LD_LIBRARY_PATH
cd $ORACLE_HOME/opmn/bin
./opmn
Segmentation fault


Analyzing the core dump fails in a RDBMS Client library function:


$ gdb opmn core.19788
(gdb) where
#0 0x0000002a95ba6f67 in call_gmon_start ()
from /app/oracle/Middleware/Oracle_IDM1/lib/libclntsh.so.11.1



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