Junk Characters in datastage
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 353
- Joined: Mon Jan 17, 2011 5:03 am
- Location: Mumbai, India
-
- Participant
- Posts: 4
- Joined: Wed May 15, 2013 1:25 am
-- yes we tried writing to a file and were successful, but our ultimate goal is to write in a tablesendmkpk wrote:how r these words appearing when viewed in DB2? -- In DB2 they are appearing normally, without any of these foreign characters
what is the source datatype etc? -- Soure and Target datatype both are varchar .. it is basically a description field.
which country related data is it? did u try that country NLS? -- This US related data
did u try to write to a file and ck?
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
U did not try any of these things, because U is not at the same site as varsh16785.sendmkpk wrote:how r these words appearing when viewed in DB2?
what is the source datatype etc?
which country related data is it? did u try that country NLS?
did u try to write to a file and ck?
The second person personal pronoun in English is spelled "you", not "u". The present tense plural of the verb "to be" is spelled "are", not "r".
DSXchange is not a mobile phone. There is no limit of 140 characters per post, and therefore no need at all to use SMS-style abbreviations. We strive for a professional standard of written English, not least because English is not the first language of everyone who reads these posts.
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.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Don't trust how View Data represents non-ASCII characters.
Experiment with text files and hex editors/viewers to learn exactly what these characters are, and then process them accordingly.
There are NO junk characters.
Experiment with text files and hex editors/viewers to learn exactly what these characters are, and then process them accordingly.
There are NO junk characters.
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.
Re: Junk Charachters in datastage
For 2 nd query.. try this.. apt_string_pad_char(0X20) we had simlar situation seen tiny box symbo, while viewing data from DB2 .. resolved with setting apt_string_pad_char(0X20) .
-
- Premium Member
- Posts: 1735
- Joined: Thu Mar 01, 2007 5:44 am
- Location: Troy, MI
Re: Junk Charachters in datastage
That you get for char data types, if you have 0x0 or some other un-printable character defined as APT_SRTING_PADCHAR, and the char is padded with NULL character or other unprintable character.sreddy666 wrote:For 2 nd query.. try this.. apt_string_pad_char(0X20) we had simlar situation seen tiny box symbo, while viewing data from DB2 .. resolved with setting apt_string_pad_char(0X20) .
Priyadarshi Kunal
Genius may have its limitations, but stupidity is not thus handicapped.
Genius may have its limitations, but stupidity is not thus handicapped.
Re: Junk Characters in datastage
I faced similar issue and using Translate in the db2 extarct sql helped. If you query the DB2 with hex(clm_name) it will actauuly show you the hex that needs to be translated.
Let me know if you need exact syntax for these. They can be easily found on net.
- nsg
Let me know if you need exact syntax for these. They can be easily found on net.
- nsg