EM13c : OMS Fails To Start - Status codes are: Console - 404 and PBS - 200
(Doc ID 2853827.1)
Last updated on JANUARY 26, 2024
Applies to:
Enterprise Manager Base Platform - Version 13.4.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
Enterprise Manager (EM) Cloud Control, Trying to start the EM fails at "Oracle Management Server" step.
Error stack observed from <EM_INSTANCE_HOME>/em/EMGC_OMS*/sysman/log/emctl.log file:
2022-03-02 09:35:06,537 [main] INFO commands.BaseCommand logAndPrint.673 - WebTier Successfully Started
2022-03-02 09:35:06,598 [main] ERROR oms.StatusOMSCmd processStatusOMS.307 - Encountered error while hitting page. Status codes are: Console - 404 and PBS - 200
2022-03-02 09:35:06,599 [main] INFO commands.StartCommand startOMS.462 - startOMS finished with result: 2
2022-03-02 09:35:06,639 [main] ERROR oms.StatusOMSCmd processStatusOMS.307 - Encountered error while hitting page. Status codes are: Console - 404 and PBS - 200
2022-03-02 09:35:06,639 [main] ERROR commands.BaseCommand logAndPrint.671 - Oracle Management Server is Down. Console may not be up.
Check the following log files:
EM log files: <EM_INSTANCE_HOME>/em/EMGC_OMS1/sysman/log/emctl.log, emoms.trc, emoms_pbs.trc
Managed Server log files: <EM_INSTANCE_HOME>/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.out
2022-03-02 09:35:06,598 [main] ERROR oms.StatusOMSCmd processStatusOMS.307 - Encountered error while hitting page. Status codes are: Console - 404 and PBS - 200
2022-03-02 09:35:06,599 [main] INFO commands.StartCommand startOMS.462 - startOMS finished with result: 2
2022-03-02 09:35:06,639 [main] ERROR oms.StatusOMSCmd processStatusOMS.307 - Encountered error while hitting page. Status codes are: Console - 404 and PBS - 200
2022-03-02 09:35:06,639 [main] ERROR commands.BaseCommand logAndPrint.671 - Oracle Management Server is Down. Console may not be up.
Check the following log files:
EM log files: <EM_INSTANCE_HOME>/em/EMGC_OMS1/sysman/log/emctl.log, emoms.trc, emoms_pbs.trc
Managed Server log files: <EM_INSTANCE_HOME>/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.out
Error stack observed from <EM_INSTANCE_HOME>/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.log file:
<Jan 23, 2022 10:18:49,244 PM EST> <Error> <Deployer> <HostName> <EMGC_OMS1> <[STANDBY] ExecuteThread: '57' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <99281a39-d7e6-4c1f-85a4-08dbffb38fe0-0000000a> <1642994329244> <[severity-value: 8] [rid: 0:58] [partition-id: 0] [partition-name: DOMAIN] > <BEA-149205> <Failed to initialize the application "emdb [LibSpecVersion=13.5.1.0.0,LibImplVersion=13.5.1.0.0]" due to error weblogic.management.DeploymentException: java.io.FileNotFoundException: <Middleware_Home>/plugins/oracle.sysman.db.oms.plugin_13.5.1.0.0/archives/emdb.war (No such file or directory)
weblogic.management.DeploymentException: java.io.FileNotFoundException: <Middleware_Home>/plugins/oracle.sysman.db.oms.plugin_13.5.1.0.0/archives/emdb.war (No such file or directory)
weblogic.management.DeploymentException: java.io.FileNotFoundException: <Middleware_Home>/plugins/oracle.sysman.db.oms.plugin_13.5.1.0.0/archives/emdb.war (No such file or directory)
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 |