sql server to Teradata for Unicode / UTF8 using TPT：Teradata error 6705

Few records are going to error due to the following error 6705 as the source have many special character like (îù a¯z’ÇÅÿ )

由于以下错误6705，很少有记录会出错，因为源有许多特殊字符，如（îùa¯z'ÇÅÿ）

6705 An illegally formed character string was encountered during translation.

6705翻译期间遇到非法形成的字符串。

All basic set up is good:

所有基本设置都很好：

Source and target have the same Unicode data set
源和目标具有相同的Unicode数据集
Both Source and TGT have the UTF encoding
Source和TGT都有UTF编码
odbc.ini for sql server has the required code page (106)
用于sql server的odbc.ini具有所需的代码页（106）

Questions:

问题：

is their any entry for TPT to check in any file?
他们是TPT签入任何文件的任何条目吗？
any way to convert all special character to recognized teradata value
任何方式将所有特殊字符转换为公认的teradata值
any other inputs?
任何其他输入？

1 个解决方案

#1

It looks like internal Teradata problem, not related to either SQL Server nor Informatica, please compare: https://www.info.teradata.com/HTMLPubs/DB_TTU_13_10/index.html#page/General_Reference/B035_1096_109A/Database.05.2268.html.

它看起来像内部Teradata问题，与SQL Server和Informatica无关，请比较：https：//www.info.teradata.com/HTMLPubs/DB_TTU_13_10/index.html#page/General_Reference/B035_1096_109A/Database.05.2268.html 。

It should not be caused just by Unicode characters within your data. I don't think this is the problem. But perhaps one of those:

它不应仅由数据中的Unicode字符引起。我不认为这是问题所在。但也许其中一个：

A SO is followed by MBCs, then the end of the string.
A SO is followed by SBCs, before encountering a shift-in (SI).

Can you try to verify this and provide some more details?

您可以尝试验证这一点并提供更多详细信息吗？

#1