Table of Contents

Search

  1. Abstract
  2. 2020 - August
  3. 2020 - July
  4. 2020 - April
  5. 2020 - February
  6. 2020 - January
  7. 2019 - November
  8. 2019 - September
  9. 2019 - August
  10. 2019 - July
  11. 2019 - June
  12. 2019 - May
  13. 2019 - April
  14. 2019 - March
  15. Informatica Global Customer Support

Connector Release Notes

Connector Release Notes

MySQL CDC Connector Known Limitations

MySQL CDC Connector Known Limitations

The following table describes known limitations:
CR
Description
PWXCLD-359
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.
PWXCLD-355
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.
PWXCLD-352
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.
PWXCLD-327
MySQL CDC Connector captures values in unsigned int, mediumint, and bigint fields as nulls when the values are larger than the maximums allowed for signed fields.
Workaround: In Data Integration, select the Source transformation on the mapping canvas. On the
Fields
tab under
Source Properties
, select
Edit Metadata
from the
Options
menu. For the mediumint and int fields, change the
Native Type
value to
num64u
. For unsigned bigint fields, make sure that the captured values are no greater than the maximum of
2
63
- 1
.
PWXCLD-307
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.
PWXCLD-295
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.
PWXCLD-294
If a mapping includes source tables or columns that have one or more spaces in their names, the spaces are converted to underscores (_). The associated mapping task will fail with the following error:
PWX-02140 SQL error at position
nn
. Column "t_bit" does not exist in table "d10uxqa000.allspace_all_space".
Workaround: Ensure that none of the source tables and mapped columns have names that include spaces. Rename the tables and columns if necessary.
PWXCLD-285
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.
PWXCLD-251
If you create a mapping that contains multiple sources and that specifies a parameter for a source connection, you must enter a specific source connection for the mapping task. For this connection, you can enter
Filter Overrides
and
SQL Query Override
advanced properties. However, these advanced properties will be used only for the first source in the mapping.
Workaround: In the mapping, define a connection parameter for each source. On the
Sources
page of the mapping task wizard, select the same specific connection for each source. Then click
Advanced
next to each connection to define the
Filter Overrides
and
SQL Query Override
attributes. The advanced attributes will then be used for the corresponding source.
PWXCLD-239
If you create a mapping that defines parameters for the source connection and source object and then select a specific connection for the associated mapping task, the
Sources
page in mapping task wizard displays the following error message:
Not able to find the adapter runtime impl for adapter id [com.infa.adapter.pwx.mysqlcdc] and nmoType [table]
Workaround: You can ignore this error and continue.
PWXCLD-118
In the
Filter Overrides
advanced property for a source, if you define a filter condition that uses a CHAR or VARCHAR2 column with the equals (=) operator, the comparison fails when the columns are wider than 255 characters.
Workaround: Do not filter on CHAR or VARCHAR2 columns wider than 255 characters or use another type of operator in the filter condition.
PWXCLD-116
If you enter a SQL statement that includes a line feed in the
SQL Query Override
source property in a mapping and run the associated mapping task, data is not written to the target. The error message indicates that the error is related to the SQL statement but does not describe the problem.
Workaround: Ensure that the SQL statement that you enter in the
SQL Query Override
property does not include a line feed. You can use a space instead.


Updated August 02, 2020