Queries Sporadically Fail with ORA-31011, ORA-19202, LPX-00210 After Using csalter.sql to Migrate Database Character Set From Single-Byte to AL32UTF8/UTF8
(Doc ID 1313386.1)
Last updated on JANUARY 30, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 11.2.0.2 to 11.2.0.3 [Release 11.2]Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
After using csalter.sql to migrate the database character set from single-byte to AL32UTF8/UTF8, queries sporadically fail with the following errors:
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00210: expected '<' instead of '¯'
Error at line 1
ORA-06512: at "USER.PACKAGE", line 726
ORA-06512: at line 4
XDB can but doesn't have to be installed for this problem to occur.
An errorstack trace for the ORA-19202 error is generated by executing the statement below before running the failing query:
SQL> alter session set events '19202 trace name ERRORSTACK level 3';
The trace file shows the following function calls in the stack trace:
----- Call Stack Trace -----
. . . . . . . . . .
<- qmxErrHandler <- XmlErrOut <- LpxErrMsg <- LpxFSMParseProlog
<- LpxFSMParseDocument <- LpxParse <- LpxBufferParse <- $cold_qmxuParseXobDoc_int
<- qmxManifest <- qmxIterInit <- qmxGetNodeByNameCS <- qolTextXmlStringToHintList
<- $cold_qsmoGetSqlMgmtObjHintsByType <- qsmoGetSqlProfHints
. . . . . . . . . .
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 |