My Oracle Support Banner

UTF8 Conversions when Using MGW/DBMS_AQ.DEQUEUE (é to é ) (Doc ID 2056218.1)

Last updated on MARCH 26, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.3 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 Backup Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

DBMS_AQ.DEQUEUE is being used to process messages which are taken by Oracle Message Gateway (MGW) from IBM's MQ series.  When handling some UTF8 characters conversions are incorrectly happening.   The source and target of the data are UTF8/AL16UTF16.  The issue is not observable from MQ side.  The source and target of the data is an Oracle database.

Site 1
~~~~~

Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production

NLS_CHARACTERSET                     UTF8
NLS_NCHAR_CHARACTERSET     AL16UTF16


Site 2
~~~~~~

Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production

NLS_CHARACTERSET                AL32UTF8
NLS_NCHAR_CHARACTERSET AL16UTF16



For example we get have this string (hex dumps):

sent       -- smé      -- c3a93c2
received  -- smé -- c383c2a93c2

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
References


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