My Oracle Support Banner

LPX-00217: invalid character During IMPDP: How To Find The Corrupted XML Data On SOURCE Table (Doc ID 1531866.1)

Last updated on AUGUST 01, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 and later
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.

Goal

How to identify the corrupted XML rows on the SOURCE table when IMPDP fails with LPX-00217: invalid character

IMPDP fails with an error like this:

ORA-31693: Table data object "USER"."TABLE_NAME" failed to load/unload and is being skipped due to error:
ORA-29913: error in executing ODCIEXTTABLEFETCH callout
ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00217: invalid character 0 (U+0000)

 

The error is correctly raised because the XML document contains a not supported character. For more info take a look at <Note 248344.1>

 

Solution

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
Goal
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.