Database ingestion and replication jobs that have an Oracle source and SQL Server target incorrectly map source CLOB columns to target VARCHAR columns by default. Because SQL Server VARCHAR columns support only ASCII data, any non-ASCII characters from the source are not stored correctly in the target. Change the default mapping to a target data type such as NVARCHAR(MAX) that would avoid the problem and achieve better data consistency.

(October 2025)

Database ingestion and replication jobs that have an Oracle source and SQL Server target incorrectly map source VARCHAR2 columns to target VARCHAR columns by default. Because SQL Server VARCHAR columns support only ASCII data, any non-ASCII characters from the source are not stored correctly in the target. Change the default mapping to a target data type such as NVARCHAR(MAX) that would avoid the problem and achieve better data consistency.

(October 2025)

Database ingestion and replication incremental load and combined load jobs that have a SQL Server source with XML columns and a SQL Server target might fail with the following error:

Conversion of one or more characters from XML to target collation impossible. Error code: 6355

.

The error occurs when the job tries to convert the source XML data to the intermediate varchar(max) data type in staging, before writing the data to the target XML column.

(October 2025)

For database ingestion and replication incremental load or combined load jobs that have a SQL Server source, if an Update operation writes a non-null value of more than 100 characters to a source TEXT column, that data is truncated in the corresponding SQL Server target table. However, the target log tables contain the full, non-truncated data value.

(July 2025)

After database ingestion and replication combined jobs that have a SQL Server source and Oracle target run using Audit apply mode, if you add a source column and then perform a

Resync (refresh)

operation, the job fails. The problem occurs because the Add Column schema drift operation adds the column at the end of the target table. However, the Resync (refresh) operation causes the added column to appear before the audit columns in the source schema. This discrepancy leads to a mismatch in order of target columns and data received.

(July 2025)

Database ingestion and replication incremental load or combined load jobs that have a SQL Server source and use the

Log-based

CDC method might incorrectly process an update not involving the primary key as a pair of delete and insert operations that have the same sequence value. After restarting the job, the insert operation might have a different sequence value. This discrepancy occurs because the restart temporarily switches to

CDC Tables

mode, which doesn’t handle the update in the same manner as

Log-based

mode.

(May 2025)

Database ingestion and replication jobs that have a Microsoft SQL Server source and process an update in a primary key and a non-primary key column in a single transaction might produce an incorrect timestamp in the DATETIME column on the Microsoft SQL Server target.

(May 2025)

Database ingestion and replication jobs that have a Microsoft SQL Server source might fail to read the CDC capture instance tables because of a deadlock error.

(May 2025)

A database ingestion and replication job that has a Microsoft SQL Server source and is configured to pause between reconnection attempts might retry the connection to the database without waiting for the requested delay.

(May 2025)