The CDC connectors do not support data preview. Attempting to preview the data for a CDC connection can cause errors.

Workaround: Do not attempt to preview data for the CDC for mainframe and midrange connectors. (November 2019)

An attempt to create a mapping fails if the PowerExchange Listener does not respond within 30 seconds of the request.

Workaround: Verify that the PowerExchange Listener for the connection is running and attempt the connection again. (October 2019)

If you import a mapping task and change a non-CDC connection to a CDC connection, the CDC runtime properties are missing from the imported information.

Workaround: Edit the imported mapping task to reset the properties on the

CDC Runtime

page. (December 2018)

If you create a mapping that maps a CDC source field to an Oracle target column that has the data type of RAW and select Data Driven as the target operation type, the Datatype Transformation Manager (DTM) process ends with a fatal error. Also any associated mapping tasks will end.

Workaround: Do not map CDC source columns to Oracle target RAW columns. (December 2018)

If you try to test a CDC connection that has no value in the

Connection Retry Period

or

Pacing Size

property, the test fails with an error message that reports an empty input string. If you try to run a mapping task that uses a CDC connection with one of these properties empty, the mapping task also fails.

Workaround: When you define or edit the CDC connection, accept the default value of 0 or enter a positive number in the

Connection Retry Period

and

Pacing Size

properties. (November 2018)

If you add a Lookup transformation to a mapping, you can select a CDC connection for the lookup object even though CDC connections are not valid for lookup objects.

Workaround: Do not select a CDC connection when you define a Lookup transformation in a mapping. (September 2018)

If a mapping includes source tables or columns that have special characters in their names, the associated mapping task will fail because it cannot import the source metadata. Special characters include s #, $, @, %, *, !, and ~.

Workaround: Ensure that none of the source tables and mapped columns have names with any special character. Rename the tables and columns if necessary.

If you use a parameter for a source connection in a mapping and try to edit the metadata field

Native Type

or

Native Scale

on the

Fields

tab of the source properties, the native type value is cleared and you cannot enter another value.

Workaround: Do not try to edit any "native" metadata field if you specified a parameter for the source connection in the mapping. If you accidentally click one of these fields and the native type value disappears, you can reinstate the original type value by clicking another tab under source properties or refreshing the page. (September 2018)