Table of Contents


  1. Abstract
  2. Installation and Upgrade
  3. 10.2 HF1 Fixed Limitations and Closed Enhancements
  4. 10.2 HF1 Known Limitations
  5. 10.2 Fixed Limitations and Closed Enhancements
  6. 10.2 Known Limitations
  7. Emergency Bug Fixes Merged into 10.2
  8. Informatica Global Customer Support

PowerCenter Known Limitations (10.2)

PowerCenter Known Limitations (10.2)

The following table describes known limitations:
You cannot specify an error action when you use the ODBC provider type in the Microsoft SQL Server connection. (442622)
If you update the
Provider Type
options for a Microsoft SQL Server ODBC connection by using the pmrep UpdateConnection command, the command fails. (425055)
On a Windows platform, if you execute a query that uses a Sybase IQ External Loader connection to load to a Sybase IQ target, and if the Server Datafile Directory is not accessible, the session hangs.
Workaround: When you run the mapping, ensure that the Windows machine that hosts the PowerCenter Integration Service has access to the Sybase IQ server. (423523)
On AIX 7.1, if you use the Oracle 12c client to connect to an Oracle database, and enable TLS 1.2 encryption for the Oracle 12c client, the session fails.
WSDL import fails if the request and response elements have different namespaces.
The PowerCenter Intgration Service generates an unhelpful error message when a dual-source identity match mapping fails to run and the mapping originates in a non-current Model repository. (450540)
Failed to check appropriate privileges for the metadata web services. (392671)
When you import a mapping or mapplet and a shortcut to the mapping or mapplet in PowerCenter or Repository Manager, labels might be applied to the wrong version of the imported mapping or mapplet.
Workaround: Import the mapping or mapplet before you import the shortcut.

Updated June 29, 2020