Conversion of special character to normal character
Moderators: chulett, rschirm, roy
The issue what am facing is , the special character is read from a oracle table and its being written as it is to oracle target. But in between we do a dynamic hash file lookup. The special character is not being written to the Hash file its throwing error stating, the character is not defined under NLS setting.chulett wrote:Sure, with Convert() for example... but why? They're not really equivalent and a better solution would be to load them as is. What issue are you having? ...
But the oracle source & target stage are able to read to special character with NLS settign UTF-8. But the special character is not being written to the hash file. Also i couldnt see the NLS setting for Hash file as we see for other stages.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Correct. This can only be changed (deliberately) at the TCL command line, and you would only do that if other applications were going to access the hashed file using non-UV-UTF8 character encoding. This was more important prior to version 6.0, when other UniVerse applications might have accessed data in DataStage hashed files.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Ok, But then why the special character is not being written to the Hashed file if its None by default. Actually we have three different datastge environment(Dev,QA & Prod). In two of the environment the special character is being written into hashed file as it is. But in one(prod) environment we are facing this special character not being writtten to the hashed file issue.
All the settings are same as it is in three environments. The job as well is same.
All the settings are same as it is in three environments. The job as well is same.