My Oracle Support Banner

13.4: OMS Install/Upgrade Fails During Start Oracle Management Service Step While Trying to Start the Webtier (Doc ID 2631600.1)

Last updated on JANUARY 31, 2020

Applies to:

Enterprise Manager Base Platform - Version 13.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

Installing/Upgrading OMS to 13.4 fails during the Start Oracle Management Service step while starting the Webtier.

../gc_inst/em/EMGC_OMS1/sysman/log/emctl.log

2020-01-22 20:22:13,635 [Thread-1] INFO  commands.BaseCommand run.610 - <OUT>starting OHS:
2020-01-22 20:22:13,635 [Thread-1] INFO  commands.BaseCommand run.610 - <OUT>Not connected to Node Manager
2020-01-22 20:22:13,635 [Thread-1] INFO  commands.BaseCommand run.610 - <OUT>new status of OHS:
2020-01-22 20:22:13,635 [Thread-1] INFO  commands.BaseCommand run.610 - <OUT>Not connected to Node Manager
2020-01-22 20:22:13,635 [Thread-1] INFO  commands.BaseCommand run.610 - <OUT>status of node manager:
2020-01-22 20:22:13,635 [Thread-1] INFO  commands.BaseCommand run.610 - <OUT>Not connected to Node Manager
2020-01-22 20:22:13,635 [Thread-1] INFO  commands.BaseCommand run.610 - <OUT>0
2020-01-22 20:22:13,635 [Thread-1] INFO  commands.BaseCommand run.610 - <OUT>_END_
2020-01-22 20:22:13,713 [main] ERROR commands.BaseCommand logAndPrint.656 - WebTier Could Not Be Started.
2020-01-22 20:22:13,713 [main] ERROR wls.OMSController main.258 - OMSController failed for start oms
2020-01-22 20:22:13,714 [main] ERROR wls.OMSController main.259 - OMSController Error: WebTier Could Not Be Started.
java.lang.Exception: WebTier Could Not Be Started.
        at oracle.sysman.emctl.commands.StartCommand.startOMS(StartCommand.java:347)
        at oracle.sysman.emctl.commands.StartCommand.execute(StartCommand.java:202)
        at oracle.sysman.emctl.wls.OMSController.main(OMSController.java:239)

 

../gc_inst/user_projects/domains/GCDomain/system_components/OHS/ohs_nm.log

<2020-01-22 20:14:14> <INFO> <OHS-0> <$ORACLE_HOME/ohs/bin/launch httpd -DOHS_MPM_WORKER -d EM_INSTANCE_HOME/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/instances/ohs1 -k start -f EM_INSTANCE_HOME/user_projects/domains/GCDomain/config/fmwconfig/components/OHS/instances/ohs1/httpd.conf: exit status = 0>
<2020-01-22 20:14:14> <INFO> <OHS-4005> <Check the instance log file for more information: EM_INSTANCE_HOME/user_projects/domains/GCDomain/servers/ohs1/logs/ohs1.log>
<2020-01-22 20:20:31> <SEVERE> <OHS-0> <Cannot run program "$ORACLE_HOME/ohs/bin/launch": error=11, Resource temporarily unavailable>
<2020-01-22 20:20:31> <SEVERE> <OHS-0> <Cannot run program "$ORACLE_HOME/ohs/bin/launch": error=11, Resource temporarily unavailable>
<2020-01-22 20:20:31> <INFO> <OHS-0> <The server 'ohs1' with process id 27596 is no longer alive; waiting for the process to die.>
<2020-01-22 20:20:31> <SEVERE> <OHS-0> <Cannot run program "$ORACLE_HOME/ohs/bin/launch": error=11, Resource temporarily unavailable>
<2020-01-22 20:20:31> <SEVERE> <OHS-0> <Cannot run program "$ORACLE_HOME/ohs/bin/launch": error=11, Resource temporarily unavailable>

 

Changes

 

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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.