My Oracle Support Banner

Chr(0) added to the end of a Message Payload on Inbound Propagation when using the Message Gateway Agent (Doc ID 603415.1)

Last updated on NOVEMBER 15, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 10.2.0.1 to 10.2.0.4 [Release 10.2]
Oracle Database - Enterprise Edition - Version 11.1.0.6 to 11.1.0.7 [Release 11.1]
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
Information in this document applies to any platform.
Checked fro currency on 23-Aug-2010

Symptoms

When messages are sent via inbound propagation to Oracle using the Messaging Gateway Agent, the following errors are reported

ORA-31011: XML parsing failed
ORA-19202: Error occurred in XML processing
LPX-00216: invalid character 0 (0x0)

The Websphere MQ CCSID is 1208.

A transformation is in use on the inbound propagation schedule. If a transformation is not in use the problem
will still exist but is less likely to be detected unless careful payload checking is in place.

If the payload contains two (or more) byte characters, the XML parsing fails.

A null character is added to the end of the message for each two (or more) byte character in the message payload, e.g. if the message contains 6 two-byte characters 6 null characters will be added to the end of the message.

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
Cause
Solution

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