In this Document
Symptoms
Changes
Cause
Solution
APPLIES TO:
Enterprise Manager Base Platform - Version 13.4.0.0.0 to 13.4.0.0.0 [Release 13c]
Information in this document applies to any platform.
SYMPTOMS
Enterprise Manager (EM) 13.4.0.0.0 Cloud Control
EM 13.4 Installation got failed at BI Publisher Configuration with an error as "Failed to start Enterprise Manager. Diagnostic code 1".
CfmLogger_<timestamp>.log:
======================
INFO: oracle.sysman.top.oms: Starting BI Publisher ...
INFO: oracle.sysman.top.oms:
INFO: oracle.sysman.top.oms: Failed to start Enterprise Manager. Diagnostic code 1.
INFO: oracle.sysman.top.oms:See log at <OMS_HOME>/cfgtoollogs/bip/bipca_20200205061341.log for details.
INFO: oracle.sysman.top.oms:Error extending domain
INFO: oracle.sysman.top.oms:See log at <OMS_HOME>/cfgtoollogs/bip/bipca_20200205061341.log for details.
INFO: oracle.sysman.top.oms:The OutOfBox command execution completed with the status 1.
bipca_<timestamp>.log:
=================
[2020-02-05T06:19:54.942+00:00] [sysman] [NOTIFICATION] [] [oracle.sysman.bipca] [host:<HOSTNAME>.<DOMAIN_NAME>] [nwaddr: <host ip address> ] [tid: 46] [userId: oracle] [ecid: e206855f-284a-4bb8-b9e8-5775910dbac0-00000002,0] [SRC_CLASS: oracle.sysman.sdkImpl.core.ip.model.bipca.ProcessOutputReader] [SRC_METHOD: run] Starting BI Publisher Server ...
[2020-02-05T06:22:53.264+00:00] [sysman] [NOTIFICATION] [] [oracle.sysman.bipca] [host: <HOSTNAME>.<DOMAIN_NAME>] [nwaddr: <host ip address>] [tid: 46] [userId: oracle] [ecid: e206855f-284a-4bb8-b9e8-5775910dbac0-00000002,0] [SRC_CLASS: oracle.sysman.sdkImpl.core.ip.model.bipca.ProcessOutputReader] [SRC_METHOD: run] WebTier Could Not Be Started.
[2020-02-05T06:22:53.269+00:00] [sysman] [NOTIFICATION] [] [oracle.sysman.bipca] [host: <HOSTNAME>.<DOMAIN_NAME>] [nwaddr: <host ip address>] [tid: 46] [userId: oracle] [ecid: e206855f-284a-4bb8-b9e8-5775910dbac0-00000002,0] [SRC_CLASS: oracle.sysman.sdkImpl.core.ip.model.bipca.ProcessOutputReader] [SRC_METHOD: run] Error Occurred: WebTier Could Not Be Started.
ohs_nm.log:
========
<2020-02-05 06:02:07> <INFO> <OHS-0> <Domain initialized for <EM_INSTANCE_HOME>/user_projects/domains/GCDomain>
<2020-02-05 06:02:08> <INFO> <OHS-4112> <Creating instance ohs1>
<2020-02-05 06:02:09> <INFO> <OHS-4114> <Updating instance ohs1>
<2020-02-05 06:18:11> <INFO> <OHS-4114> <Updating instance ohs1>
<2020-02-05 06:20:10> <INFO> <OHS-0> <Domain initialized for <EM_INSTANCE_HOME>/user_projects/domains/GCDomain>
<2020-02-05 06:22:52> <INFO> <OHS-4018> <Starting server ohs1>
<2020-02-05 06:22:52> <INFO> <OHS-0> <Running <OMS_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>
<2020-02-05 06:22:52> <INFO> <OHS-0> <<OMS_HOME>/ohs/bin/httpd: error while loading shared libraries: libclntshcore.so.12.1: cannot open shared object file: No such file or directory>
<2020-02-05 06:22:52> <SEVERE> <OHS-0> <<OMS_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 = 127>
<2020-02-05 06:22:52> <INFO> <OHS-4005> <Check the instance log file for more information: <EM_INSTANCE_HOME>/user_projects/domains/GCDomain/servers/ohs1/logs/ohs1.log>
<2020-02-05 06:22:52> <SEVERE> <OHS-0> <Failed to start the server ohs1>
[OR]
ohs_nm.log:
========
<2020-10-12 16:25:25> <INFO> <OHS-4018> <Starting server ohs1>
<2020-10-12 16:25:25> <INFO> <OHS-0> <Running <OMS_HOME>/ohs/bin/launch httpd -DOHS_MPM_WORKER -d <EM_INSTANCE_HOME>/gc_inst/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>
<2020-10-12 16:25:25> <INFO> <OHS-0> <OMS_HOME>/ohs/bin/httpd: error while loading shared libraries: libclntsh.so.12.1: cannot enable executable stack as shared object requires: Permission denied>
<2020-10-12 16:25:26> <SEVERE> <OHS-0> <OMS_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 = 127>
<2020-10-12 16:25:26> <INFO> <OHS-4005> <Check the instance log file for more information: <EM_INSTANCE_HOME>t/user_projects/domains/GCDomain/servers/ohs1/logs/ohs1.log>
<2020-10-12 16:25:26> <SEVERE> <OHS-0> <Failed to start the server ohs1>
Starting the EM 13.4 OMS (<OMS_HOME>/bin/emctl start oms) also fails with this error
WebTier Could Not Be Started
CHANGES
CAUSE
libclntshcore.so.12.1: Package file is missing in "<OMS_HOME>/lib/" directory path.
libclntsh.so.12.1: Package file is missing in "<OMS_HOME>/lib/" directory path.
This happens when there are missing packages from the package requirements "Package Requirements for Oracle Management Service". For more details on the package requirements, please follow the document provided.
"Package Requirements for Oracle Management Service"
This issue occurs when the below recommended packages are not installed on the host before Install/Upgrade activities of OMS.
gcc-4.8.2-16
glibc-devel-2.17-55-i686
SOLUTION
Install below missing recommended packages on the OMS host before Install/Upgrade activities of OMS.
gcc-4.8.2-16
glibc-devel-2.17-55-i686
After sucessfull installation of above two packages, please follow below action plan based on the activity.
Scenario 1 - Fresh Install: If the issue is observed during a fresh installation of 13c OMS
1. Cleanup the Failed OMS installation
OMS_HOME/oui/bin> ./detachHome.sh
2. Delete the OMS_HOME from the filesystem.
3. Drop the Repository Database Objects by following the MOS note ==> 13c Cloud Control Repository: How to Manually Drop Repository Database Objects in 13c Cloud Control Note 2107485.1 参见前面一个帖子
4. Retry the OMS installation from scratch.
Scenario 2 - Upgrade: If the issue is observed during the upgrade activity to 13.4 OMS:
1.Cleanup the Failed 13.4 binaries
13.4_OMS_HOME/oui/bin> ./detachHome.sh
2. Delete the 13.4_OMS_HOME from the filesystem.
3. Restore the repository Database from backup taken prior to the upgrade activity.
4. Start the existing OMS from the old OMS_HOME and ensure that OMS is working as expected.
5. Retry the OMS Upgrade from scratch.