Table of Contents


  1. Abstract
  2. Informatica Installation
  3. Informatica Upgrade
  4. 10.1 Fixed Limitations and Closed Enhancements
  5. 10.1 Known Limitations
  6. Informatica Global Customer Support

Informatica Developer Fixed Limitations and Closed Enhancements

Review the Release Notes of previous releases for information about previous fixed limitations.
The following table describes fixed limitations:
When you create and run a column profile for the first time in the Developer tool and choose the Hive option as the run-time environment, the profile run fails.
An error message appears when the following conditions are true:
  1. You create a table on Hive.
  2. You import the table as a relational data object.
  3. You create a column profile on the data object.
When you have multiple profile mappings, the first mapping runs separately and the rest of the mappings run concurrently.
The Informatica services fail to launch when you start informatica 9.6.1 HF4 services from services.msc, after you apply HotFix 4 on Informatica PowerCenter 9.6.1 on a Windows platform.
You cannot preview the results of a mapping when a Lookup transformation uses a custom query that joins more than one table.
When you use a Microsoft SQL Server native connection with the ODBC provider type and create a Stored Procedure transformation to insert binary data into Microsoft SQL Server, the Data Integration Service loads null data.
After you upgrade from 9.5.1, the mapping performance decreases for a mapping that contains several Expression transformations or transformations with many variables.
The Developer tool displays an unhelpful error message if you cannot view the reference data content status in the Preferences dialog box.
If you configure a classifier model with a numeric value as a label, you cannot open the model.
The Developer tool does not invalidate an Association transformation when the precision, scale, and data type of the input ports and the corresponding output ports do not match.
When you create a column profile with a rule on a logical object lookup, the profile run fails with null pointer exception.
The scorecard metadata becomes unusable when the following conditions are true:
  1. Administrator creates a profile on a mapping specification.
  2. Administrator creates a scorecard on the profile and assigns read and write permissions to the scorecard.
  3. A non-administrator opens the scorecard.
  4. Administrator revokes the read and write permissions.
  5. A non-administrator opens the scorecard.
If you import a relational data object and you use a control file to specify a connection for the object, the operation might disregard the connection that you specify.
If you assign a workflow variable to a Human task output, the Data Integration Service does not update the output value when the Human task runs.
When you try to delete a parameter set that is part of an application or workflow, the Developer tool generates a null pointer exception and does not delete the parameter set.
A mapping fails when the following circumstances are true:
  • The mapping is designed for a flat file source and you parameterize the source to be a relational source.
  • The mapping is deployed with a parameter set.
  • The mapping has a resource parameter and either a port list parameter or a sort list parameter.
When you include a Lookup transformation in a mapping, the Developer tool collapses the Lookup ports under the group name Lookup Columns. The editor does not show the links between the lookup ports and the downstream transformation because the lookup ports are not visible.
A mapping that performs single-source identity match analysis completes with errors when the following conditions are true:
  • You configure the Match transformation to generate temporary index data, and you then update the transformation to write index data to database tables.
  • You do not select the identity index key field in the match strategy.
Data preview fails for a Normalizer transformation with multiple occurring columns or records imported from PowerCenter.
Importing a mapping fails when you configure a the domain twice in the Developer tool.
When you change the default parameter value for the resource parameter on the
Data Object
tab, the
Data Object
tab does not show the correct default value. The
Data Object
tab shows the original default parameter value for the resource parameter.
When you run a data preview on a Lookup transformation with a customized data object lookup source, an unexpected error might occur if a table is deleted or replaced from the customized data object.
When you view a historical version of a mapping that is not valid and then select
View optimized mapping
, the Developer tool returns a null pointer exception. Close the error and open the
Validation Log
view to view the problems with the mapping.
When you use parameters for the control file path and name in a flat file data object and you use the resource parameter for the flat file source in the mapping, the mapping fails.
When you switch between the
option and the
option on the
Data Object
tab, the Developer tool opens the transformation
tab after you choose a new data object value. The Developer tool should continue to show the
Data Object
The optimized mapping contains unconnected ports and the data preview fails when a mapping contains an output expression.
You cannot assign a tag to a reference table in the Developer tool.
When you deploy a workflow that has a parameterized source and target, the workflow fails to create a target when the resource parameter is in an associated parameter set, and you run the workflow from the Developer tool.
The Developer tool can become unresponsive if you configure a Standardizer transformation to replace custom strings and you delete the string to replace from the configuration.
When you drag a port from a transformation with multiple port groups to another object in a mapping, the Developer tool does not display the port links. The issue arises in data quality transformations such as the Address Validator transformation and the Match transformation.
When you enter multiple values in sequence to the Filter field in a classifier model, the cursor moves to the Label field after you enter each value.
When you run a midstream profile on the Router and matcher multiple-group transformations, the first group results are displayed for all the group results.
If you create a parameterized lookup source and you change the input column data type in the lookup condition, the Developer tool returns the following unexpected error message:
Unable to validate cell value
When you create a logical data object mapping from a flat file data source, the mapping fails when you include a non-reusable Sequence Generator transformation. You can use a reusable Sequence Generator transformation.
When you create a port selector in a reusable transformation and you choose to select ports by name, the Developer tool does not list available ports.
Scorecard results do not appear when you create and run a new scorecard on a JSON or XML profile, and you receive a null pointer exception when you run the scorecard in the Analyst tool.
If you move an input port up or down in a Match transformation, the corresponding output port does not move in the same way. The transformation might stop unexpectedly at run time.
If you bind a mapping output to the exceptionLoadCount variable in a Mapping task and you delete the mapping output, you cannot validate the workflow that contains the Mapping task.
You can configure a step in a Human task to distribute task instances to users whom you deleted from the domain. The issue arises when you configure the Human task to distribute tasks by data value.
When you parameterize a resource in a dynamic source and you choose to update the data object columns at run time, the Data Integration Service fails to resolve any system parameter that you configure in the source. The Data Integration Service might also fail to resolve a parameter for the flat file control file.
You cannot view the status of the address reference data files in the Preferences view if you created the Content Management Service that manages the files on an AIX machine.
You cannot use the keyboard shortcut
to link ports.
You cannot bind a workflow parameter to a mapping parameter if the mapping parameter is one of the following parameter types: port, port list, sort list, expression, resource, or input linkset.
When a mapping enabled for partitioning contains a Normalizer transformation, the Data Integration Service always uses one thread to run the transformation. The Data Integration Service can use multiple threads to run the remaining mapping pipeline stages.
If you drag dynamic output ports from a Weight Based Analyzer transformation to an Expression transformation, you cannot perform a data preview on the Expression transformation. The Developer tool displays an error.
When you run an address validation mapping in certified mode on Canadian addresses, the certified report might display percentage values below one percent as a series of zeroes.
The Match transformation performs identity analysis on the key field port and ignores the match strategy ports when you do not include the key field port in the match strategy. The transformation does not perform match analysis correctly on the key field data and does not create accurate clusters.
When you run an identity match mapping that performs dual-source analysis on columns with different names, the Match transformation fails and generates an error message.
The Match transformation does not find duplicate identities if you add optional ports to the identity match analysis and the optional port data values do not match.
You cannot create some types of parameters on a mapping
tab if the mapping does not contain a transformation that supports the parameter type. The Developer tool shows a list of parameter types that includes just the parameter types available for the transformations in the mapping. For example, you cannot create a sort list parameter in the
tab unless the mapping contains a Sorter transformation.
Expression validation fails for dynamic expressions with functions that require arguments of a specific data type. For example, a
function fails to validate because it requires an argument of CHAR data type.
The Developer Tool generates columns incorrectly from a control file that contains the Binary and Timestamp with Time Zone data types.
When you copy a transformation that has parameters, the Developer tool does not include the parameters in the copy of the transformation. This issue also occurs when you copy a mapping that contains the transformation with parameters.
The Developer tool displays an error if you try to copy a command that contains more than 384 characters into a Command task in a workflow.
A screen reader application cannot read all of the properties in a Notification task in a workflow.
A screen reader application cannot read all of the properties on an Exclusive gateway in a workflow.
The properties on an Exclusive gateway in a workflow contain code elements that are unhelpful to a screen reader application.
The properties on an Assignment task in a workflow contain code elements that are unhelpful to a screen reader application.
Connection types are not listed in the Developer tool when you import a mapping from an XML file.
When you create a probabilistic model from a data source, the model creation wizard might not display the data source columns in the current order.
You cannot use a non-reusable Sequence Generator transformation in a mapplet or a logical data object mapping. However, the Developer tool does not show any validation or run-time error if you copy a non-reusable Sequence Generator transformation from a mapping and paste it into a mapplet or a logical data object mapping.
Data preview on a customized data object fails to run after upgrading from version 9.5.
If you create a probabilistic model that contains multibyte data values, the values can break across lines in the Data view of the model. The issue arises if you resize the Developer tool views so that a data value moves from one line to another in the Data view. If you assign a label to a data value that breaks over two lines, the label might not attach to the correct value. The value that you label might overwrite another value in the Data view.
When a mapping contains multiple Match transformations, any change to the settings one of the Match transformations might affect the settings in another Match transformation.
After you edit and propagate port names, the Developer tool fails to update the expression conditions with the revised port names.
The following table describes closed enhancement requests:
When you set the provider type to ODBC in a Microsoft SQL Server connection and truncate target tables, the Data Integration Service first runs the truncate target table command. In case the truncate command fails, the Data Integration Service runs the delete command. This results in better mapping performance.
When you use an IBM DB2 connection to import a table, you can specify one or more schema names from which you want to import the table.
When you run a mapping in the Developer tool, you can monitor the job from the
view. To monitor the job, click the link for the mapping run in the
view. Select
Monitor Job
A probabilistic model includes status values that indicates whether the compilation logic for the model is based on the current labels and data values in the model.