Getting Warning

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
shobhitj
Participant
Posts: 47
Joined: Sat Jun 14, 2008 8:55 am
Location: Pune, India

Getting Warning

Post by shobhitj »

Hi,

I have getting the following warning i am getting:-

SOURCE_TABLES,0: Invalid character(s) ([xFFFD]) found converting Unicode string (code point(s): ST PIERRE DE B[xFFFD]UF) to codepage ISO-8859-1, substituting.

SOURCE_TABLES,0: Invalid character(s) ([x2019]) found converting Unicode string (code point(s): CENTRE D[x2019]ETUDE DE LA KABBALE) to codepage ISO-8859-1, substituting.

Please provide some solution for the above warning to be removed.
Thanks & Regards,
Shobhit Jauhari
Minhajuddin
Participant
Posts: 467
Joined: Tue Mar 20, 2007 6:36 am
Location: Chennai
Contact:

Post by Minhajuddin »

This warning says that Datastage encountered a hex code which has no definition in the code page being used (ISO - 8859-1 in your case). If I were you, I would find out the hex codes not defined in this code page (Search wikipedia for ISO-8859-1) and search for them in my source and then find the source of these literals and stop them at the source.
Minhajuddin

<a href="http://feeds.feedburner.com/~r/MyExperi ... ~6/2"><img src="http://feeds.feedburner.com/MyExperienc ... lrow.3.gif" alt="My experiences with this DLROW" border="0"></a>
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

That is an odd error - I'Ve just checked and x2019 is the back apostrophe see here and it does not seem to have a ISO8859-1 counterpart! The error is valid and you will need to handle it by either removing the character, or defining a replacement.

The xFFFD is a "replacement mark" for a character which is unknown in UniCode, so translating that to any other character set is going to be impossible in any case.
shobhitj
Participant
Posts: 47
Joined: Sat Jun 14, 2008 8:55 am
Location: Pune, India

Post by shobhitj »

Hi,

Plase provide the complete solution

ArndW wrote:That is an odd error - I'Ve just checked and x2019 is the back apostrophe see here and it does not seem to have a ISO8859-1 count ...
Thanks & Regards,
Shobhit Jauhari
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

shobhitj - please get Premium membership.
Post Reply