Data Integration Release Notes > Known issues

Known issues

The tables in this section describe known issues for Data Integration. Not all monthly releases include known issues.

October 2025 known issues

Issue	Description
CLDDI-46863	A mapping fails to run when all of the following conditions are true: - The mapping is configured to preserve special characters in native field names. - A Target transformation uses manual field mapping to write to an existing Oracle target. - A field name in the Target transformation contains an at sign (@). Workaround: Use an Expression transformation before the Target transformation to rename the field that has the at sign.
CLDDI-46768	A mapping fails to run when all of the following conditions are true: - The mapping is configured to preserve special characters in native field names. - A Target transformation uses manual field mapping to write to an existing Oracle target. - A field name in the Target transformation contains a right parenthesis character ( ')' ).
CLDDI-46080	When you configure a mapping with a Union transformation to preserve special characters in native field names, the following issues occur: - In the mapping task, the Input Parameters page isn’t available when the Union transformation uses parameterized field mappings. - The mapping fails if you manually map the fields in the Union transformation. Workaround: Add an Expression transformation to the end of each incoming source pipeline before the Union transformation. In the Expression transformations, configure the fields that you want to map to use the same names in each transformation.
CLDDI-45485	When you create expression fields in a mapping task, you can’t include special characters in the field name. Workaround: Create expression fields with special characters in the field name in the mapping.

May 2025 known issues

Issue	Description
INTAI-134	When you import or export a mapping that contains a Vector Embedding transformation with a Large Language Model connection, the connection doesn’t appear in the asset list and isn’t imported or exported, respectively. Workaround: After you import the mapping, recreate or reconfigure the Large Language Model connection in the Vector Embedding transformation.