All Forums Extensibility
MiBer 2 posts Joined 03/10
31 Mar 2010

Hello all,
I'm looking for an UDF like the existing UDF "replaces", but for CHARACTER SET UNICODE (nor for CHARACTER SET LATIN). Is there anybody who can give me a correct working C-Code ?? I want to use it on an Teradata V12.


MadMac 14 posts Joined 10/04
01 Apr 2010

We have a UDF which replaces out of range Unicode characters with the Unicode "Replacement Character". I just want to caution anyone who does something similar that you cannot export and then import the Unicode Replacement Character, because the client transformation rejects the replacement character as invalid. Please remember to select an appropriate actual character if you ever plan on trying to move data.

I would post the code we have for this, but it is not a Unicode based app - it is a binary masking app. That said, I think Teradata wrote an example for us some time ago - and they should have something similar which does this work - ask your support team to dig this up...

Best - Michael

MiBer 2 posts Joined 03/10
12 Apr 2010

I've got an answer from TD-technical-support. It works fine :-) Thanks !!

sameties 3 posts Joined 08/11
11 Sep 2011

i have got the same problem. What should i do?

JimmyLee 13 posts Joined 06/10
07 Dec 2011

I am running into a similar problem and would like to get more info on this UDF.

In my case, we get data that at times included unprintable/invalid characters, mostly as a result of users pasting data from other documents (we get smart qoutes and things like that).  Those characters cause problems when we query the data (primarily when a column is used in a Where clause).


I need an efficient way to replace these invalid characters.

"To not give your best is to sacrifice the gift" -- Steve Prefontaine

TDThrottle 51 posts Joined 11/11
23 Jan 2012

I have problem in handling UNICODE colums with Fexp/MLoad. We use Named pipe access module to export and import data in parallel. Please share if any one has got the workaround for it. We use Teradata 12.




You must sign in to leave a comment.