Polish Character Issue in Datastage

ray.wurlod · Post by **ray.wurlod** » Thu Jan 27, 2011 4:42 am

Use the National Language Support capabilities of DataStage, with an appropriate map that can handle accented European characters.

Kartik Dharia · Post by **Kartik Dharia** » Fri Feb 18, 2011 1:09 am

@ray.wurlod

I had tried numerous NLS packages like ISO-8859-1 ( proj default),8859-2,8859-12,UTF-8,IBM 01147,IBM 918,8859-1:1987 but i could not resolve the issue .
I had done these changes in the NLS tab of the job properties wherin i have changed the Default map for Stages section

Could you please suggest an appropriate pack for the same

Sreenivasulu · Post by **Sreenivasulu** » Fri Feb 18, 2011 1:57 am

1.Are you able to see the polish characters when you open in the unix box ? If no then you need to fix this as well

2.If you are loading this data to DB then check the NLS settings in the DB as well.

Regards
Sreen

Kartik Dharia · Post by **Kartik Dharia** » Fri Feb 18, 2011 2:29 am

@Sreen
1. I did not get your question ?
Are you able to see the polish characters when you open in the unix box ?

I have used a csv and db stage in the existing job having the NLS pack of 8859-1 (proj default).
Then created another job to read the csv using the UTF-8 pack and i was able to see the data correctly. This means datastage pack is converting the data into an intermediate format and while reading it agains converts into the original form. This is within datastage but in DB is still showing incorrect value.

2. The code of db is 1208 which supports the polish character. I manually updated the records in DB and was able to view them correctly. Hence there is no issue in DB.

The problem i am facing is while loading the data from the queue to DB , the translation is done by Datastage and hence the characters are not loaded properly in DB.

Let me know if you require some further inputs

thupallireddy · Post by **thupallireddy** » Sat Aug 09, 2014 7:00 am

HI Kartik,

Im also facing the same issue. Pls let me know how to overcome this?

priyadarshikunal · Post by **priyadarshikunal** » Mon Aug 11, 2014 5:50 am

You should have created your own topic and tell what are your source target types such as oracle, db2, seq files etc. Does your IS installation supports NLS etc.

thupallireddy · Post by **thupallireddy** » Mon Aug 18, 2014 1:02 am

Hi Kunal,

This issue is resolved. I have configured nls_lang value as same as oracle db in dsenv and it worked.

priyadarshikunal · Post by **priyadarshikunal** » Mon Aug 18, 2014 2:57 am

well thats the thing, If you would have mentioned oracle and the database and that datastage was installed with NLS, the first answer you would have got to set NLS_LANG, you do not have to set it in dsenv only, you can have it as environment variable as well. Both will work.