OracleAS OPMN Fails to Start - LPX-00200: could not convert from encoding
(Doc ID 430093.1)
Last updated on MARCH 19, 2020
Applies to:Oracle Fusion Middleware - Version 10.1.2.0.0 to 10.1.2.3.0 [Release AS10gR2]
Information in this document applies to any platform.
This problem can occur on any platform.
Checked for relevance on 21-May-2009
Oracle Process monitoring and Notification services (OPMN) fails to start, giving an error like
LPX-00200: could not convert from encoding UTF-8 to ISO-8859-1
XML parse failed: error 200.
If DCM commands are issued there are also errors
Subscription request timed out after 120000 millseconds. Possible causes: OPMN may not be running, you may have an OPMN running in an alternate ORACLE_HOME using duplicate port values, or OPMN may be misconfigured.
Unable to start the OPMN process within the time-out period.
Try starting the OPMN process using the command line utility "$ORACLE_HOME/OPMN/bin/OPMNctl start". If the OPMN process does not start check the log files in $ORACLE_HOME/OPMN/logs for more information.
The "opmn.xml" configuration file has recently been edited. The edit may have been done by hand or via Application Server Console (ASC). The edit results in a corruption of the file.
Furthermore, there is the potential for any corruption to the "opmn.xml" to be propagated through to the DCM repository (this is done automatically if editing the file via AS Console, or the change can be made if someone issues 'dcmctl updateConfig'). Once this happens, the DCM becomes corrupt and subsequently DCM commands fail as well as OPMN not being able to start.
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