Table of Contents


  1. Abstract
  2. Informatica Installation
  3. Informatica Upgrade
  4. Informatica Closed Enhancements
  5. Informatica Fixed Limitations
  6. Informatica Known Limitations
  7. Informatica Third-Party Limitations
  8. Informatica Global Customer Support

PowerCenter Fixed Limitations

PowerCenter Fixed Limitations

Review the Release Notes of previous releases for information about previous fixed limitations.
The following table describes fixed limitations:
The Integration Service skips generating some rows for an XML source or an XML Midstream Parser transformation under the following circumstances:
  • The XML definition contains a base type view and a derived type view.
  • The XML definition also contains a view for a multiple-occurring element from a complex type.
  • The derived type has an inheritance relationship with the base type and a type relationship with the multiple-occurring element.
The PowerCenter Repository Service shuts down unexpectedly when a session and the repository contains inconsistencies.
The PowerCenter Repository Service rolls back a deployment successfully, but does not complete after upgrading to 9.6.1 HotFix 3.
A mapping configured for dynamic partitioning hangs when it reads from a MapR source.
After you upgrade from 961 HotFix 1 to 961 HotFix 3, the session fails to substitute some of the variables correctly in the parameter file.
The session performance is slow when you write data to an Oracle target that contains multiple Varchar2 columns with precision greater than 4000.
A mapping that writes to an HDFS target on a Hadoop cluster on Cloudera CDH fails with the following error:
<DATE>: ERROR : (31186 | WRITER_1_*_1) : (IS | <ISNAME>) : <nodename> : HDFS_66007 : Unable to establish a connection with the specified HDFS host because of the following error: [java.lang.NoClassDefFoundError: org/apache/log4j/Level
When you use a relational connection to connect to a Sybase ASE 15.5 database and use a long identifier in the table name, an error occurs stating that the table name is too long.
The session performance is slow when all of the following conditions are true:
  • On a Linux operating system, you use an ODBC connection to connect to a Microsoft SQL Server database.
  • The database contains a column of the char data type.
  • You update many rows in the database.
When you purge an object version, the entry for the purged version no longer remains in the repository.
If the source contains a large volume of data, the PowerCenter Integration Service randomly reads the value of the port as NULL instead of 1.
When you enable Metadata Exchange option in the PowerCenter Client, the port-to-port data lineage links between the input and output ports in the Expression transformation are incorrect.
The pmcmd stoptask command fails to stop a task in the workflow.
Data corruption occurs when all of the following conditions are true:
  • You read BLOB data from an Oracle source and write it to an Oracle target.
  • The BLOB column is placed before a CHAR column in the target database.
You can use the pmrep purgeVersion option -c with or without the -p option.
When you use the -c option without the -p option, the command does not purge versions that are contained in deployment groups. When you use -c with -p, the results display which versions would be purged, and then list which versions are contained in deployment groups.
When you purge objects that are part of deployment groups, you cannot deploy groups that contained the purged objects.
When you set the StoreHAPersistenceInDB property to Yes and the PowerCenter Integration Service runs on a grid, the PowerCenter Integration Service shuts down unexpectedly.
When you use the pmrep DeployDeploymentGroup command, the PowerCenter Integration Service specified in the control file is not assigned to the target repository.
The welcome page links in the Designer and Workflow Manager do not work in the Simplified Chinese locale.
A session that runs an identity match mapping might fail when the following conditions are true:
  • The mapping reads a Japanese population file.
  • Multiple sessions run identity match mappings concurrently.
When you use Design API to export the repository metadata, the Design API fails to create a workflow object.
When you run the script containing multiple pmrep commands where one of the pmrep commands contains the hash (#) symbol in the middle of the command, the PowerCenter Repository Service fails to run the pmrep Run command using the -f option for all the commands.
When you specify special characters for the DBPassword option, the infacmd UpdateRepositoryService command fails.
The REP_TARG_MAPPING, REP_TBL_MAPPING, and REP_FLD_MAPPING repository metadata exchange views are empty because they reference deprecated OPB repository tables.
When data type entries are missing in the REP_FLD_DATATYPE, the views joining the tables fail to return the entries for the fields that use the data type.
When the workflow contains a worklet, the REP_SESS_CONFIG_PARM view displays multiple session configuration parameters.
When you use the REP_SESS_CONFIG_PARM view in PowerCenter 9.5.1 HotFix 2 or later, performance might be slow.
When you copy a workflow across different repositories in different domains, the owner of the connection in the target repository is not set correctly.
When you import a workflow with a node resource from the exported domain, the import process fails to validate the node resource in the imported domain.
The REP_SESS_LOG view and the OPB_SESS_TASK_LOG repository table do not reflect the latest entries for workflow run instances.

Updated October 25, 2018