If
you are running incremental subscriptions that rely on unique fields to
track changes, data type differences can produce Row
Count Errors if change data cannot be reconciled between the source
and target databases.A subscription that attempts to replicate a Db2 TIMESTAMP column may fail with the following message:
"[SQL Server]The conversion of char to datetime resulted in a value out of range."
This problem occurs because Db2 and SQL Server have different ranges for their respective TIMESTAMP and DATETIME fields. You cannot replicate a Db2 TIMESTAMP column to a SQL Server DATETIME column if the source column contains year values earlier than 1753, or if it contains any time value of 24:00:00.000, which is equivalent to the allowable 00:00:00.000. If your Db2 source table contains values that SQL Server does not accept in a DATETIME column, you can set the subscription to replicate to a SQL Server column of type CHAR instead of DATETIME, as described in the topic Mapping Data Types. You also can add a derived column to overcome the data type differences, as described in Defining Derived Columns.
If
you are running incremental subscriptions that rely on unique fields to
track changes, data type differences can produce Row
Count Errors if change data cannot be reconciled between the source
and target databases.