Page 1 of 1
Posted: Mon Jun 17, 2013 5:46 am
by nikhil_bhasin
I am also facing similar issue. Was anyone able to resolve this?
Posted: Mon Jun 17, 2013 6:24 am
by crystal_pup
1) Identify the column on which the error is encountered. Check the character set associated with that column in Teradata. If its LATIN, change it to UNICODE (UNICODE takes much space though).
2) In the Teradata Connector stage, change the character set to UTF8 and then try re-running the job.
Posted: Tue Jun 18, 2013 4:51 am
by nikhil_bhasin
@crystal_pup
Are you saying to change the table definition?
That field is defined as LATIN, if I use UTF-8 in terdata connector, the job simply aborts but when I change it to ASCII, then it replaces those characters with space/some other charcaters
Posted: Tue Jun 18, 2013 5:22 am
by crystal_pup
Hi Nikhil
Yes, change the column character set to UNICODE in the table definition.
Regards