Invalid Character warnig in datastage

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
rumu
Participant
Posts: 286
Joined: Mon Jun 06, 2005 4:07 am

Invalid Character warnig in datastage

Post by rumu »

Dear All,

I am getting the following warning in datastage:

ODBC_Enterprise_3,0: Invalid character(s) ([xFF]) found converting string (code point(s): StateProvinceID[x00][x00][x00][x00][x01][x00][x00][x00][x00][xFF][xFF][xFF][xFF][xFF][xFF]) from codepage ibm-1051_P100-1995 to Unicode, substituting.


My job design is as mentioned here:

Input :One Seq file stage and one ODBC stage .Through ODBC I am accessing sqlserver table.
Join stage:Joining(inner) the seq file and ODBC data based on one key column.

Output:ODBC stage ---another sql server table.

I am getting the above warning in the input odbc stage .
the field 'StateProvinceID' is of nvarchar in source table.

In my project the following NSL mapping is used:

Parallel job default NLS map ISO-8859-1, default locale OFF

Could you please let me why this warning is coming?

regards,
rumu
hemanthakumar
Participant
Posts: 34
Joined: Mon May 05, 2008 1:31 am

Post by hemanthakumar »

try with UTF-8 IN NLS setting in each stage.
rumu
Participant
Posts: 286
Joined: Mon Jun 06, 2005 4:07 am

Post by rumu »

Hi Hemanthkumar,

Thanks for your reply..
I already tried this option but issue remains same.

regards,
rumu
shershahkhan
Participant
Posts: 64
Joined: Fri Jan 25, 2008 4:41 am

Post by shershahkhan »

I don't know how it the characters works in SQL Server but i was facing the same type of issue in Teradata, to solve the issue use the character set ibm-1051_P100-1995, use the one that is used in SQL server and that will solve the issue
toshea
Participant
Posts: 79
Joined: Thu Aug 14, 2008 6:46 pm

Post by toshea »

Perhaps the character set in your job NLS map does not match the character set in your ODBC data source. If you have your NLS map set to ibm-1051_P100-1995, make sure your data source in .odbc.ini is set to an equivalent character set.
Post Reply