OBIEE 11g: Installation of OBIEE 11g 11.1.1.7 Fails When the OBIEE Components are Being Started via Opmnctl. Error: "Time out while waiting for a managed process to start" (Doc ID 1570418.1)

Last updated on DECEMBER 03, 2014

Applies to:

Business Intelligence Server Enterprise Edition - Version 11.1.1.7.0 and later
Business Intelligence Suite Enterprise Edition - Version 11.1.1.7.0 and later
Information in this document applies to any platform.

Symptoms

During an Enterprise installation of OBIEE 11.1.1.7 (on AIX 7.1, however this might be true for all platforms), the installation failed at the following configuration step:

          Executing: opmnctl start coreapplication_obiccs1

 

The following error was observed in the install logs:

Error
--> Process (index=1,uid=449904665,pid=8782050)
 time out while waiting for a managed process to start
 Log:
 /dev/null

java.lang.Exception: opmnctl task failed
at oracle.as.install.bi.biconfig.standard.OpmnctlTask.doExecute(OpmnctlTask.java:117)
at oracle.as.install.bi.biconfig.standard.AbstractProvisioningTask.execute(AbstractProvisioningTask.java:70)
at oracle.as.install.bi.biconfig.standard.StandardProvisionTaskList.execute(StandardProvisionTaskList.java:66)
at oracle.as.install.bi.biconfig.BIConfigMain.doExecute(BIConfigMain.java:113)
at oracle.as.install.engine.modules.configuration.client.ConfigAction.execute(ConfigAction.java:375)
at oracle.as.install.engine.modules.configuration.action.TaskPerformer.run(TaskPerformer.java:88)
at oracle.as.install.engine.modules.configuration.action.TaskPerformer.startConfigAction(TaskPerformer.java:105)
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:96)
at oracle.as.install.engine.modules.configuration.standard.StandardConfigActionManager.start(StandardConfigActionManager.java:186)
at oracle.as.install.engine.modules.configuration.boot.ConfigurationExtension.kickstart(ConfigurationExtension.java:81)
at oracle.as.install.engine.modules.configuration.ConfigurationModule.run(ConfigurationModule.java:86)
at java.lang.Thread.run(Thread.java:738)


The following observations were made:

  1. The "AdminServer" and the "bi_server1" WebLogic Servers were both in a RUNNING status, and the "weblogic" administrator user could login to the WebLogic Administration Console and the Enterprise Manager Fusion Middleware Control (EM).
  2. The OBIEE System Components could not be started manually via EM or via the "opmnctl startall" command and the same "time out while waiting for a managed process to start" error is thrown.  Additionally, no errors were observed in the OBIEE logs.
  3. The "opmn" process was running and listening on port 9501 after an "opmnctl start" or "opmnctl startall" command was executed, as verified via "opmnctl debug" or "ps -ef | grep opmn" or "netstat -anp | grep 9501" commands.  However, there was the following unexpected response when the "opmnctl status" command was executed:
    $ ./opmnctl status
    Unable to connect to opmn.
    Opmn may not be up.
    opmnctl status: failed.

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