German Special Characters Incorrectly Translated from UEL
(Doc ID 2110097.1)
Last updated on AUGUST 13, 2018
Applies to:Oracle Communications Billing and Revenue Management - Version 18.104.22.168.0 to 22.214.171.124.0 [Release 7.5.0]
Information in this document applies to any platform.
On all versions of Oracle Communications Billing and Revenue Management (BRM) when storing German characters in the database through the Universal Event Loader (UEK), special characters are being incorrectly stored.
For example, the string:
after being processed by UEL has been stored as:
The character set used on the server and the database is UTF-8 and the Java version installed is 1.7.
Steps to reproduce this issue:
1. Set up the UEL so that it calls an opcode which writes to the database (one of the fields to write is a STRING)
2. Create an input text file for UEL where one of the parameters is a string with German special characters inside
3. Process the file with UEL so that it writes the German string on the STRING field.
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