Archives of the TeradataForum

Message Posted: Sat, 09 Jul 2005 @ 21:50:11 GMT

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

I have noticed a problem with selecting columns with untranslateable characters :-

When you select many columns from a table and one contains an untranslateable character then there are no problems, i.e. a column contains 1 or many '1A'XC characters.

Now if you do the same select but one of the columns uses a case statement then it falls over with the untranslateable character error, can't remember the error 6***.

Does anyone know if this is a problem with v2r5? I've managed to get round it for this situation as its a simple case statement i.e. I've been able to use coalesce. So coalesce works, but case doesn't.

We're getting these untranslateable errors as there coming from a mainframe. We can identify them with translate_chk but can't change them. If we knew it was only going to occur once then it would be easy to get rid of, I think, with index and substring. I suppose we could write a UDF....

Anyone any experience?

Thanks

Rob C

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