The following topics provide information about tasks that you might need to perform before or after an upgrade of Data Integration Connectors. Post-upgrade tasks for previous monthly releases are also included in case you haven't performed these tasks after the previous upgrade.
Post-upgrade tasks for the October 2024 release
Perform the following tasks after your organization is upgraded to the October 2024 release.
Google Analytics Connector
Informatica dropped support for the following Google Analytics APIs:
•Analytics Reporting API v4
•Core Reporting API v3
The default value of the API Version in the connection properties changed from Core Reporting API v3 to Google Analytics 4.
After the upgrade, if an existing mapping is configured with either Analytics Reporting API v4 or Core Reporting API v3 as the API version, the test connection and mapping fail.
To resolve this issue, follow these steps:
1Migrate your Universal Analytics account to Google Analytics 4 in Google Analytics.
2Set the API Version connection property to Google Analytics 4 in the Google Analytics connection.
3Synchronize the mapping metadata and re-run the mapping.
Google BigQuery V2 Connector
Google BigQuery V2 Connector includes the following upgrade impact:
•After the upgrade, an existing mapping fails when all of the following conditions apply:
- The Google BigQuery V2 connection uses the simple connection mode.
- The Use EXPORT DATA statement to stage property is enabled in the source advanced properties.
- The transformation includes fields with the Record or Repeat data type from the source table.
To resolve this issue, remove the fields with the Record or Repeat data type from the transformation, and re-run the mapping.
•After the upgrade, an existing mapping in SQL ELT mode fails if it uses the REGEXP_EXTRACT function in an Expression or Aggregator transformation with the Byte data type in the argument and the String data type in the return type.
To resolve this issue, update the data types in the argument and return type of the REGEXP_EXTRACT function to compatible formats, and re-run the mapping.
IBM MQ Connector
After the upgrade, it is important that you change the directory where you copy the required IBM MQ JAR files to connect to IBM MQ.
When you change the directory for the IBM MQ JAR files, you do not need to copy the JAR files in the Secure Agent installation directory each time a new version of the IBM MQ Connector package is deployed.
Before you run new or existing IBM MQ mappings, perform the following steps:
1Copy the required IBM MQ JAR files from the IBM MQ client.
For more information about the IBM MQ JAR files that you need to copy, see the IBM MQ Connector documentation.
2Create the ibmmq folder, and then paste the copied JAR files to the following directory:
After the upgrade, when you write source data that contains a FileName port or when the FileName in the mapping is not excluded from the input fields of the target, the mapping runs successfully. However, it inserts an empty string in the FileName column in the target. Previously, the source data with the FileName port was written to the Microsoft Fabric Data Warehouse target.
To prevent writing empty strings, perform the following steps:
•Exclude the FileName port when you create a new target at run time.
•Do not use the FileName port column when you use an existing target object.
•Connect FileName port values from the source to a different port.
Microsoft Fabric Lakehouse Connector
After the upgrade, when you write source data that contains a FileName port or when the FileName in the mapping is not excluded from the input fields of the target, the mapping fails. This issue occurs in both existing target objects and new target objects created at run time. Previously, the source data with the FileName port was written to the Microsoft Fabric Lakehouse target.
To resolve this issue in existing or new mappings, perform the following steps:
•Exclude the FileName port when you create a new target at run time.
•Do not use the FileName port column when you use an existing target object.
•Connect FileName port values from the source to a different port if an existing target object does not contain the FileName port column.
MySQL Connector
After the upgrade, an existing mapping fails if MySQL Connector is configured on Windows with an ODBC driver version 8.0.28 or earlier.
To resolve this issue, upgrade the ODBC driver to version 8.0.29 or later and re-run the mapping.