Archives of the TeradataForum
Message Posted: Fri, 06 Jul 2012 @ 15:23:35 GMT
What "client character set" are you using for the session?
The character ? is not standard 7-bit ASCII, so your client character set should not be set to the default ASCII.
If all the characters were included in the Teradata LATIN repertoire, you could consider a special single-byte character set translation such as LATIN1252_0A instead (but ? is not). Try using UTF8 or UTF16 for the client character set, so your SQL statement can be passed to the database without introducing translation errors prior to parsing.
To actually get the statement to run as intended, you will also need to define columns / parameters that contain these values as UNICODE, and you will need to create a version of OREPLACE that can handle double-byte characters properly.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|