Page 1 of 1

Invalid character(s) ([xA9]) codpage warning in DS 8.1

Posted: Tue May 19, 2009 1:02 am
by pradeepphulari
Hi,

I am reading a sequential file, performing lookup and wrting into a table. In the process I am calling a shared container to do the otherlookups and get values

I am getting this warnning
main_program: Invalid character(s) ([xA9]) found converting string (code point(s): IBM Confidential, OCO Source Materials, [xA9] Copyright IBM Corp. 2006. All Rights R...) from codepage UTF-8 to Unicode, substituting.

Not able to trace what is the problem

The the job was running fine before including the shared container

Can any one plz help

Rgs,
Pradeep

Posted: Fri Aug 14, 2009 7:50 pm
by mohan
hey pradeep .. did u get fix for your issue ?.. i am also having same

Posted: Fri Aug 14, 2009 8:32 pm
by chulett
Any chance there is a Pivot stage involved?

viewtopic.php?t=127535

Re: Invalid character(s) ([xA9]) codpage warning in DS 8.1

Posted: Sat Aug 15, 2009 10:21 am
by ragasambath
pradeepphulari wrote:Hi,

I am reading a sequential file, performing lookup and wrting into a table. In the process I am calling a shared container to do the otherlookups and get values

I am getting this warnning
main_program: Invalid character(s) ([xA9]) found converting string (code point(s): IBM Confidential, OCO Source Materials, [xA9] Copyright IBM Corp. 2006. All Rights R...) from codepage UTF-8 to Unicode, substituting.

Not able to trace what is the problem

The the job was running fine before including the shared container

Can any one plz help

Rgs,
Pradeep

Hello Pradeep,
Does your input file contains any German/Spanish/French special Characters . if so ,handle while reading data by specifying proper NLS description . This error is due to different encoding representation of characters in the same file . Unix can read these type of data but unable to process .This error message originated from the UNIX Shell

Posted: Sat Aug 15, 2009 10:30 am
by chulett
If you read the linked post or look closely at the ones here, you'll see that the problem character is a hex A9 - the copyright symbol. And the only time it's been reported here is with that "IBM Confidential" string and have been with a Pivot stage. Hence the question.