GoldenGate Incorrect Encoding While Writing To JMS, character set issue (Doc ID 1641257.1)

Last updated on JULY 17, 2017

Applies to:

Oracle GoldenGate Application Adapters - Version 11.2.1.0.0 and later
Information in this document applies to any platform.

Symptoms

OGG Adapter writes data to JMS queue if source database was created in CL8MSWIN1251 character set.  The sourcedefs contains correct character set ID and trail-file also contains correctly encoded WIN1251 characters.
However JMS-adapter writes garbage to JMS queue.

The characters "Àëåêñàíäð Ðûíäèí" in cp1252 has same hex code as "Александр Рындин" in cp1251.

So it looks like GoldenGate JMS Adapter reads byte array from trail file. Then JMS Adapter should understand from def-file that trail file is encoded in cp1251. However it ignores def-file and treats byte array as default character set cp1252.



Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms