My Oracle Support Banner

EM 13c: Enterprise Manager 13c Cloud Control OMS Fails to Start with Errors: oracle.ods.virtualization.engine.config.parsers.ConfigErrorHandler.fatalError; XML-20193: (Fatal Error) Unexpected EOF (Doc ID 2815784.1)

Last updated on FEBRUARY 26, 2022

Applies to:

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

Symptoms

Enterprise Manager (EM) 13.2 Cloud Control Oracle Management Service (OMS) fails to start with the following command session error:

<OMS_HOME>/BIN> ./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
Oracle Management Server Could Not Be Started
Check EM Server log file for details: <EM_INSTANCE_BASE>/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.out
AdminServer Could Not Be Started
Check Admin Server log file for details: <EM_INSTANCE_BASE>/gc_inst/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/logs/EMGC_ADMINSERVER.out
Oracle Management Server is Down
JVMD Engine is Down
Starting BI Publisher Server ...
BI Publisher Server Could Not Be Started. Check BIP Server log file for details.
BI Publisher Server Logs: <EM_INSTANCE_BASE>/gc_inst/user_projects/domains/GCDomain/servers/BIP/logs/
AdminServer Could Not Be Started
Check Admin Server log file for details: <EM_INSTANCE_BASE>/gc_inst/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/logs/EMGC_ADMINSERVER.out
BI Publisher Server is Down

<EM_INSTANCE_BASE>/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS1/logs/EMGC_OMS1.out shows this corresponding error:

Oct 13, 2021 9:13:36 AM oracle.ods.virtualization.engine.util.VDELogger error
SEVERE: Error writing XML file.
org.xml.sax.SAXException: Error Parsing at line #249: 4,199.
org.xml.sax.SAXParseException; lineNumber: 249; columnNumber: 4199; <Line 249, Column 4199>: XML-20193: (Fatal Error) Unexpected EOF.
at oracle.ods.virtualization.engine.config.parsers.ConfigErrorHandler.fatalError(ConfigErrorHandler.java:103)
at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:435)
at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:290)
at oracle.xml.parser.v2.NonValidatingParser.parseAttrValue(NonValidatingParser.java:1990)
at oracle.xml.parser.v2.NonValidatingParser.parseAttr(NonValidatingParser.java:1865)
at oracle.xml.parser.v2.NonValidatingParser.parseAttributes(NonValidatingParser.java:1797)
at oracle.xml.parser.v2.NonValidatingParser.parseElement(NonValidatingParser.java:1634)
at oracle.xml.parser.v2.NonValidatingParser.parseRootElement(NonValidatingParser.java:458)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)
Caused by: org.xml.sax.SAXParseException; lineNumber: 249; columnNumber: 4199; <Line 249, Column 4199>: XML-20193: (Fatal Error) Unexpected EOF.
at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:425)



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
References


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