DSXchange

Kamal,

I use client "Client Access ODBC driver" from IBM and it works fine. Make sure whether you need to check translation box for character set e.g: "Translate CCSID 65535" if you are using Client Access driver.

Srinivas

HI, I have source is unicodedata but lookup table has nonunicodedata while doing lookup it's rejecting. pls tell me how i can do lookup in this case Thanks in advance regards, Bollineni. Bollineni, Couple of ways, 1. Change the lookup field format to unicode (nvarchar, nchar etc. ) if possible, OR,...

Just wanted to ask you that are you sure you will never have any other special cahracters other than what you specified here?? If yes then the above solution is perfect !! Adding to Deepak comments... Usually these characters are from European character set and are called "diacritic" char...

Yes, I tried both a negative end value and a step value of zero. It won't accept either. The step value cannot be zero. The start value must be less than the end value if the step value is positive, or start must be less than end if the step is negative. If I understand your issue correctly.....We ...

I am wondering if anyone has come across this situation and if so any advice is appreciated. Situation: Datastagem: 7.5.1.A Platform: Windows Source: SQL server Job: ODBC ---> Transformer ---> Hash File Recently I converted the Datastage from non-NLS to NLS (ie., reinstalled Datastage as NLS enabled...

Ha, another one brainwashed by Oracle bin Larry! VARCHAR2 only exists in Oracle - the OP made no mention of Oracle. NVarChar (the "Standard" representation) does use two bytes per character. You (srinivas_dsx, and welcome aboard) can try using Long NVarChar for larger data. Or change the ...

I am sure this topic is discussed before or it is very elementary, however, I am trying to understand how would one handle ntext (16) in a unicode database/application in Datastage. I tried nvarchar with NLS enabled (UTF8) and its works fine in datastage wherever the string length is less than 2000,...