After the migration, when you run a mapping to read data that contains double quotes ("), the double quotes is treated as a qualifier resulting in data mismatch in the target.

After the migration, when you run a mapping to read data where a column name contains a single quote ('), the agent replaces the single quote in the metadata with an underscore (_) character resulting in failure.

When you read data that contains special characters and create a target at runtime, data corruption occurs and the mapping fails. After the migration, data corruption does not occur and the same mapping runs successfully.

When you read a compressed file either in the source object or in the overridden object, ensure that the file name has a .gz extension.

The

Header in the first row of Blob

option in the source in a Microsoft Azure Blob Storage V1 mapping after the migration is mapped to the

Header Line

and

First Data Row

options in the Microsoft Azure Blob Storage V3 mapping.

After the migration, when you configure a Target transformation, the Success File Directory and Error File Directory target properties are not available in Microsoft Azure Blob Storage V3.

The

Header in the first row of Blob

option in the target in a Microsoft Azure Blob Storage V1 mapping after the migration is mapped to the

Target Header

option in the Microsoft Azure Blob Storage V3 mapping.

If the override value for the blob container name in the Microsoft Azure Blob Storage V2 mapping ends with a forward slash (/), the mapping fails after the migration.

The

Header in the first row of Blob

option in the source in a Microsoft Azure Blob Storage V2 mapping after the migration is mapped to the

Header Line

and

First Data Row

options in the Microsoft Azure Blob Storage V3 mapping.

If the override value for the blob container name in the Microsoft Azure Blob Storage V2 mapping ends with a forward slash (/), the mapping replaces the blob container with an unnamed folder in the target.

The

Header in the first row of Blob

option in the target in a Microsoft Azure Blob Storage V2 mapping after the migration is mapped to the

Target Header

option in the Microsoft Azure Blob Storage V3 mapping.

If you create a completely parameterized mapping, do not specify the connection type in the connection parameterization. If you specify the connection type in the connection parameterization and then migrate the mapping, the mapping fails at runtime.

When you parameterize both the connection and the objects in a Microsoft Azure Blob Storage V1 and V2 mapping, the data preview in the mapping task might fail after the migration with the following error:

Internal error while processing request. Please contact Informatica Global Customer Support.