After Failed Plugin Deployment, Unable to Start EM OMS
(Doc ID 2391609.1)
Last updated on NOVEMBER 16, 2022
Applies to:
Enterprise Manager Base Platform - Version 13.1.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
Recently attempted an Enterprise Manager 13c plugin deployment, which failed.
Now, attempts to start the EM13c OMS fail and point to errors in the nodemanager log file:
emctl start oms
Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
Starting Oracle Management Server...
WebTier Successfully Started
Node Manager Could Not Be Started
Check Node Manager log file for details: /<middleware_home>/gc_inst/user_projects/domains/GCDomain/nodemanager/nodemanager.log
Oracle Management Server is Down
JVMD Engine is Down
The nodemanager.log shows entries like:
<Apr 24, 2018 8:38:45 PM GMT+00:00> <INFO> <Loading domains file: /<middleware_home>/gc_inst/user_projects/domains/GCDomain/nodemanager/nodemanager.domains>
<Apr 24, 2018 8:38:46 PM GMT+00:00> <INFO> <Loading identity key store: FileName=/<middleware_home>/gc_inst/em/EMGC_OMS1/sysman/config/keystore/jksfromwallet.jks, Type=jks, PassPhraseUsed=true>
<Apr 24, 2018 8:38:46 PM GMT+00:00> <SEVERE> <Fatal error in NodeManager server: null>
Changes
Failed plugin deployment.
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 |