When replicating LOB data to Teradata targets, the Applier and InitialSync truncate the LOB data to the size that is specified in the

global.lob_truncation_size

runtime parameter.

To load data to Teradata tables, ensure that the row size does not exceed the TPT loader buffer of 64 KB. If you have source tables that include multiple LOB columns and expect the TPT loader buffer limit to be exceeded, set the

global.lob_truncation_size

runtime parameter to a smaller value. Also, edit the datatype conversion rules in the

DataReplication_installation

/uiconf/DataTypes.xml file to map the LOB columns to Teradata VARCHAR and VARBYTE columns of the appropriate length.

The Applier might incorrectly apply Updates and Deletes to Teradata MULTISET tables that include multiple rows that contain the same primary key values from the source.

When performing an initial synchronization of a source table with a Teradata target, if the source table contains duplicate rows and does not have a primary key or unique index, the corresponding Teradata target table must be defined as a NoPI (No Primary Index) table. NoPI tables are inherently multiset. If the target table is not defined as a NoPI table, InitialSync processing will fail with exit code 46.

On a Teradata target, the maximum number of concurrent sessions for a TPT operator that an Applier thread can use for loading data to the target is determined by the value of the

apply.teradata.td_max_sessions

runtime parameter. This parameter value must be less than or equal to the number of Access Module Processors (AMPs) on the Teradata target database. The default value is 8.

On a Teradata target, the maximum number of concurrent sessions for a TPT operator that an InitialSync thread can use for loading data to the target is determined by the value of the

initialsync.teradata.td_max_sessions

runtime parameter. This parameter value must be less than or equal to the number of AMPs on the Teradata target database. The default value is 8.

If you use a version of the Teradata ODBC driver earlier than 15.00.00.04 and include special characters in the user name or password for connecting to the target, you must specify a custom connection string in the connection on the

Target Database

tab. In the custom connection string, enclose the user ID or password that contains the special characters in double quotation marks. Alternatively, use version 15.00.00.04 or a later version of the ODBC driver. These drivers can accept user IDs and passwords that include special characters, and you can connect to the Teradata target without specifying a custom connection string.