Page 1 of 1
Posted: Tue May 14, 2013 3:43 am
by ray.wurlod
Verify how character storage is encoded into your Teradata table (perhaps via a SHOW TABLE command) and match that in your DataStage NLS map setting. Probably one of ISO8859-1 or UTF-8 will fill the bill.
Posted: Tue May 14, 2013 6:38 am
by kshah9
Ray, Thanks for reply, But in Table is created as Latin and in NLs is already to ISO-8859-1. But still facing the problem.
Posted: Tue May 14, 2013 8:48 am
by kwwilliams
The name field should be set to Unicode in Teradata and not Latin. And the SQL Server NLS is not ISO-8859-1, it is likely windows-1252. Windows 1252 was developed before the Latin-1 and is a superset of Latin-1. Once you have the column set to Unicode and the NLS MAP set to windows-1252, and then client character set to UTF8 your job should run succesfully.