My Oracle Support Banner

SAS Data Is Getting Loaded With Incorrect Special Characters. Non-English Characters Are Not recognized. (Doc ID 2302052.1)

Last updated on JULY 13, 2023

Applies to:

Oracle Life Sciences Data Management Workbench - Version 2.4.6 and later
Oracle Life Sciences Data Hub - Version 2.4.6 and later
Information in this document applies to any platform.

Symptoms

Data is getting loaded with special characters into LSH application. But actual data doesn't have the Special Characters.

EXPECTED BEHAVIOR
---------------------------------
If data does not have special characters, expect it is getting loaded WITHOUT unexpected special characters into LSH application.


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Load SAS Data using a .SAS7BDAT File.



ADDITIONAL DETAILS
---------------------------

1. Below are the DP server settings before calling cdr_apps_dpserver.sh

export NLS_LANG=AMERICAN_AMERICA.UTF8
sleep 1
...


Checked the owb process via <NOTE:2211668.1> "How To Get The Environment Variables In Use By A Running Process". It displays, among other details:
 java -Dfile.encoding=UTF8 -Duser.language=en -Duser.country=US

2. Below profile options have value as UTF8 only and then, are correct:

a) FND: Native Client Encoding
b) ICX: Client IANA Encoding


3. The generated SQL Loader control file to load data is missing "CHARACTERSET" parameter and it may cause the non-English characters not getting recognized. It was corrected and after that, some special characters are displayed correctly now, but others not.

Changes

 Testing by first time the UTF8 characters in the SAS Data Load.

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