In general, Data Mover supports copying tables that contain any kind of character data. Therefore, tables with CHARACTER SET UNICODE, CHARACTER SET LATIN, CHARACTER SET KANJISJIS, or CHARACTER SET KANJI1 columns will be copied correctly in most cases. However, the following scenarios could cause Teradata Database errors when copying data:
- Different export width on the source and target systems
- Copying KANJI1 data to or from a Teradata Database system
- Copying a Character PPI table with Teradata PT API or JDBC when the default collation of the target user does not match the PPI collation of the source table
- Copying a table that contains a mixture of CHARACTER SET UNICODE, CHARACTER SET LATIN, CHARACTER SET KANJISJIS, or CHARACTER SET KANJI1 columns
If a Teradata Database "untranslatable character" error occurs when copying data, the source and target session character sets may need different values in the Data Mover job.
Multi-byte object names are only supported when they are specified in UTF-8.