Archives of the TeradataForum

Message Posted: Mon, 29 Aug 2011 @ 19:10:15 GMT

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

<-- Anonymously Posted: Monday, August 29, 2011 14:35 -->

I think you are mistaken. Both Teradata and Oracle reference the number of characters (not the byte width) in the DDL. There is no incompatibility here.

More likely this is a client issue. Are you using latest drivers? On the client side, UTF16 requires 2 bytes per character plus another 2 bytes if you have a byte order mark prefix; UTF8 requires 1 to 3 bytes per character.

See also the dbscontrol Export Width Table ID field for additional information regarding the byte length reported to the client.

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