Archives of the TeradataForum

Message Posted: Tue, 24 Mar 2015 @ 20:46:35 GMT

	<Prev	Next>		<<First	<Prev	Next>	Last>>

<-- Anonymously Posted: Tuesday, March 24, 2015 14:31 -->

I am developing a TPT load (Unix environment) for a data file (with UTF-8 encoding) to populate a Teradata (14.10)?table with columns defined as VARCHAR(nnn) CHARACTER SET UNICODE.

One character in the data file is causing my load to fail. If I remove this character the load completes successfully.

When the data file is viewed via Winscp the problem character appears as a square box, when I copy and paste the character into a Word document it appears as a "smiley face" emoji/emoticon type thing. This makes sense as the data being loaded is a "free text" field which is populated?from a website.

Winscp details the following attributes for the character: character '5535' (oxD83 encoding utf-8), whilst a bit of a googling suggests the following character 55357, unicode code point U+D83D, UTF-8 (Hex) ed a0 bd?

I'm afraid this means nothing to me, what do I need to do to ensure that the TPT load job doesn't fail for these spurious UTF-8 characters which appear not to be supported by Teradata UTF-8 Unicode character set ?

I don't really want to pre process the file to remove this specific character as tomorrow I could easily receive a file with a different problem character.

Thanks for any assistance

	<Prev	Next>		<<First	<Prev	Next>	Last>>