CR | Description |
|---|---|
ICS-8163 | When you use an Oracle source that includes a field with a BLOB data type, the mapping configuration task fails. Workaround: Unmap the field. |
ICS-7988 | When you partition a mapping that uses an ODBC connection to connect to an IBM DB2 database, you cannot use columns of Date data type for key range values. |
ICS-7742 | When you partition a mapping, you cannot include subseconds in date/time key range values. |
ICS-7332 | When you create a task with a flat file, Salesforce, or SAP source and use a parameter file, the task fails to run if you assign a Unicode value to the parameter. This occurs for previously created tasks and if you copy or migrate an existing task. It no longer occurs when you create a new task. Workaround: Re-create the task. |
ICS-7187 | When you use an Oracle source that includes a field with a BLOB data type, the mapping configuration task fails. Workaround: Unmap the field. |
ICS-5172 (formerly INFA 279686) | Data Synchronization tasks configured to run in real time upon arrival of outbound messages run even when Run permission is revoked. |
ICS-5170 (formerly INFA 293502) | In Data Synchronization tasks with database targets, the Update Target property is cleared if you click the Refresh Fields option on the Field Mappings page of the Data Synchronization wizard. |
ICS-5169 (formerly INFA 361543) | You can delete a connection that is used in a mapping. You must not be able to delete connections that are used in Data Synchronization, Data Replication, Mapping Configuration or any other tasks. |
ICS-5166 (formerly INFA 391533) | Mapping Configuration tasks that pass binary data through a Normalizer transformation fail with data type conversion errors. The Normalizer transformation does not support binary data types. |
ICS-5159 (formerly INFA 281843) | Contact Validation tasks that validate postal addresses sometimes fail due to memory allocation, internal server, or transformation errors. Workarounds: If the task fails with the following error, use the Buffer Block Size advanced option to adjust the buffer block size: FATAL ERROR : Failed to allocate memory. Out of virtual memory. For other errors, try running the task again. If the problem persists, contact Informatica Global Customer Support. |
ICS-5158 (formerly INFA 282057) | The Street With Number advanced option is ignored in Contact Validation tasks. The building number is always included with the street name at this time. |
ICS-5145 | The Japanese Secure Agent fails to uninstall on an English operating system. Workaround: Navigate to the <Secure Agent installation directory>/Uninstall_Informatica Cloud Secure Agent directory and rename the following files:
After you rename the files, redo the steps to uninstall the Secure Agent. |
ICS-4819 | When you run a Data Synchronization task and perform a cached lookup on an SAP HANA source that contains a quoted identifier, the task fails with an error. Workaround: Use a command task with uncached lookup. |
ICS-4791 | When you use the Japanese version of Informatica Cloud, errors generated from scheduled tasks appear in English. |
ICS-4790 | When you switch between English and Japanese in your browser, the activity log error messages are not translated. The messages show in the language originally output when the task was completed. |
ICS-4655 | An error occurs when you export PowerCenter workflows with Command tasks from PowerCenter version 9.1 HotFix 5 and above into Informatica Cloud. Workaround: Remove the EXECORDER attributes manually from the XML file or export the workflow from PowerCenter version 9.1 HotFix 4 or below. |
ICS-4429 | When you use the Japanese version of Informatica Cloud, error messages related to expressions in unconnected lookup functions appear in English instead of Japanese. |
ICS-4081 | When you use the Japanese version of Informatica Cloud, Java exception error messages appear in English. |
ICS-3975 | When you run data synchronization tasks, the task hangs indefinitely and does not display an error message in the Activity Monitor. Workaround: Commit the session in the database and the task will complete. |
ICS-3306 | To reconfigure a business service operation for a Web Services transformation, you need to delete it from the business service and select it again. Workaround: When you define a business service for a Web Services transformation, configure all choice elements or derived types before you close the Configure Operation window. |
ICS-1491 | If a mapping uses more than one Web Services transformation, you cannot pass the new endpoint URL returned from the first Web Service transformation to any downstream Web Service transformations. Workaround: Create another WSConsumer connection using the URL returned from the first Web Service transformation and define a business service that uses the connection. Use the new business service for the downstream Web Services transformation. |
ICS-1478 | In a Web Services transformation, you cannot map a source field to more than one request field. |
ICS-1320 | In a Web Services transformation, if you change the data type of an incoming field after you have mapped fields, you have to clear the mapping for the field and map it again. Workaround: Change the data type of an incoming field before you map the field. |
ICS-385 | In the Mapping Designer, you can edit advanced relationships in View mode. |
DMT-76 | In environments with a non-English locale, the names of masking techniques appear in English on the Masking Rules tab of the Data Masking transformation Properties panel. |
DMT-66 | A mapping that includes the SIN masking technique fails when you disable the property Start Digit. Workaround: Enable the property Start Digit and enter a start digit value when you use the SIN masking technique. |
DMT-54 | When you search for and add fields from the Add Fields window of the Data Masking transformation properties, the transformation clears fields that you selected. Workaround: Scroll down if needed and select required fields instead of searching for fields. |
CTDM-319 | You cannot configure expressions for additional master-detail type relationship fields in the target connection. Workaround: Hide or delete the master-detail type relationship fields in the Salesforce target. |
CTDM-255 | The Data Masking task fails if the task contains objects with self-reference relationships and if the task uses the lookup based reconciliation strategy. Workaround: Use the external ID reconciliation strategy, or remove self-reference relationships from the task. |
CTDM-209 | When you run an inplace masking that contains self-reference relationships, the Data Masking task fails. Workaround: Remove the self-reference relationships from the source and run the task again. |
CTDM-208 | The Data Masking task fails when the task contains a single object with self-reference relationships. Workaround: Add more objects in the source, or remove the self-reference relationships from the source. Run the task again. |