Troubleshooting > ThirdPartyIssues > Resolving Rejected UTF-8 Records When Using Teradata TPump

Resolving Rejected UTF-8 Records When Using Teradata TPump

Article #: Product: Version:

Summary

When loading UTF-8 data into a Teradata target table using TPump in a DMExpress task, records containing 3-byte characters may be rejected.

This is caused by a known Teradata issue. An update is available from Teradata to address this issue.

Symptom

The problem occurs when loading data into a Teradata target table using the TPump utility from the affected version of the Teradata Tools and Utilities (TTU).

Affected versions include:

Records containing 3-byte UTF-8 characters will be rejected and will appear in the error table. If the number of rejected records exceeds the error limit specified in the Teradata Utility Settings for the task, or if you have not specified an error limit, the task will abort.

An affected DMExpress task will produce the following message at runtime:

(TDREJONE) records were rejected while writing to Teradata database "<DATABASE>" table "<TABLE>"; error information is logged in the "tpump" error table "<ERROR_TABLE>"

For each rejected record, an instance of the following error record will be recorded in the error table:

ErrorCode ErrorMsg

----------- ---------------------------------------------------

6706 The string contains an untranslatable character.

These error records can be viewed using the following SQL query, where <ERROR_TABLE> is the error table name referenced in the (TDREJONE) message issued by DMExpress:

SELECT ErrorCode, ErrorMsg FROM <ERROR_TABLE>;

Resolution

To resolve the problem, upgrade to a newer version of Teradata Tools and Utilities:

Last updated: