Conversion from the UTF-8 character set to UTF-16LE warning

[asorrell]

We have tried with all options...

Could you please list what you've tried?

[ray.wurlod]

Have you tried setting NLS mapping to "UTF-16 Little Endian" in DataStage?

[chulett]

Ah... was wondering what the "LE" part of "UTF-16LE" stood for.

[ray.wurlod]

At my current engagement we run UTF-16BE - so I guess the OP is on an Intel-chipped box.

[anandsivan]

Have you tried setting NLS mapping to "UTF-16 Little Endian" in DataStage? ...

Yes ... i did this ..but in the job we have date fields if i change UTF8 to UTF-16LE job is aborting because of data fields not converting to UTF-16.
2) when i change to UTF-16LE job is aborted with below warning:

Output Schema does not match data from SELECT statement SQL statement: SELECT TOP 10 ITEM_NBR ,BASE_DIV_NBR ,MDS_FAM_ID , COUNTRY_CODE FROM WW_CORE_DIM_VM.ITEM_DIM WHERE BASE_DIV_NBR IN (1,18) ORDER BY BASE_DIV_NBR (CC_TeraParallelTransporter::initiate, file CC_TeraParallelTransporter.cpp, line 1,295)

In the teradata table :
COUNTRY_CODE CHAR(2) CHARACTER SET LATIN NOT CASESPECIFIC COMPRESS ('AR','BR','CA','CN','GB','IN','JP','K1','MX','US'),

Because of the country_code only i am getting this warning if i remove country_code job is completing successfully with out warning.

[anandsivan]

Andy,
I have tried below activity's
1) In the datastage i have changed NLS UTF-8 to UTF-16LE
2) Project default map : ISO-8859-1
Transaction mode: ANSI
Client character set : ASCII
Automap characterset encoding: No
NLS map name: ISO-8859-1
3)CC_TERA_USE_ISO88591_ASCII_MAP= 1 at the Project level settings in the Administrator

[asorrell]

Is the Country Code the ONLY field that is marked character set Latin?

[anandsivan]

Yes Andy. only the Country Code field that is marked character set Latin.