Table of Contents

Search

  1. Abstract
  2. Installation and Upgrade
  3. 10.1.1 HotFix 1 Fixed Limitations and Closed Enhancements
  4. 10.1.1 HotFix 1 Known Limitations
  5. 10.1.1 Update 2 Fixed Limitations and Closed Enhancements
  6. 10.1.1 Update 2 Known Limitations
  7. 10.1.1 Update 1 Fixed Limitations and Closed Enhancements
  8. 10.1.1 Update 1 Known Limitations
  9. 10.1.1 Fixed Limitations and Closed Enhancements
  10. 10.1.1 Known Limitations
  11. Informatica Global Customer Support

Mappings and Workflows Known Limitations (10.1.1)

Mappings and Workflows Known Limitations (10.1.1)

The following table describes known limitations:
Bug
Description
PLAT-1531
No validation error occurs if you create a workflow parameter name with a leading dollar sign ($). (429231)
PLAT-14168
When you perform a search and replace operation on a date-time value in an exception task, the Analyst tool does not update the date-time value with the value that you entered. The issue arises when the Analyst tool browser uses an English (United Kingdom) locale.
Workaround: Set the browser locale to English (United States). (461315)
PLAT-1359
When the target for a Write transformation includes two database tables with a parent-child relationship, the mapping fails if you enable the option to
Create or replace table at run time
. The Data Integration Service drops and recreates the tables in a specified order that prevents recreation of the correct primary key - foreign key relationship between the parent and child tables. (439220)
PLAT-12052
A mapping that reads from a flat file source might not be fully optimized at run time when the following conditions are true:
  • The flat file data object uses the SourceDir system parameter for the source file directory.
  • The mapping runs on a Data Integration Service grid configured to run jobs in separate remote processes.
Workaround: Configure the flat file data object to use a string value or a user-defined parameter for the source file directory. (426806)
OCON-794
When you use an ODBC connection and write data to a Netezza target, the Data Integration Service rejects data of the Boolean and Timestamp data types. (439979)
OCON-7025
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 mapping fails.
OCON-328
If a Teradata or Netezza mapping contains an SQL query that reads decimal columns with precision less than 15, the mapping fails to run after you import the mapping from PowerCenter to the Developer tool. (459488)
MWF-599
If a Data Integration Service fails during a workflow run on a Virtual Machine, the workflow can experience problems when it restarts. For example, you might be unable to start the workflow, abort the workflow, or start another workflow. The Model Repository Service might not return any status information for the workflow objects.
MWF-588
The Data Integration Service can run a maximum of ten Mapping tasks in parallel in a workflow. If you configure more than ten Mapping tasks between Inclusive gateways in a workflow, the Data Integration Service runs the tasks in batches of ten.
MWF-587
A Mapping task in a workflow returns a status value of 1 or 0 (zero) on completion in place of true or false.
MWF-525
You cannot import a workflow to the Model repository when the following conditions are true:
  • A task in the workflow has a name that contains more than 128 characters.
  • The Model repository is an IBM DB2 database.
The issue can also arise when you try to save the workflow to an IBM DB2 Model repository.
MWF-484
The Developer tool does not invalidate the following workflow configuration:
  • You configure a Human task to distribute task instances to users based on the values in a column that you select.
  • You configure the Human task so that the task distribution column is editable by all users.
MWF-247
When the Data Integration Service stops during a workflow run, the workflow monitor might incorrectly report the status of one or more tasks. For example, the monitor might report that one or more tasks remain in a running state. Or, the workflow monitor might not refer to tasks that completed.
The issue arises when the following conditions are true:
  • The Data Integration Service stops during the task distribution stage of a Human task.
  • The workflow includes the Human tasks and other tasks on sequence flows between two Inclusive gateways.
  • You configured the workflow for automatic recovery.
MWF-243
When a workflow recovers after the Data Integration Service stops unexpectedly, the Data Integration Service might run one or more Mapping tasks a second time.
The issue arises when the following conditions are true:
  • The workflow includes a Mapping task and a downstream Human task on multiple sequence flows between two Inclusive gateways.
  • You set the maximum number of restart attempts on the domain to 1.
  • You configured the workflow for automatic recovery or manual recovery.
MWF-237
When you manually recover a workflow on a grid, the Data Integration Service on the master node might run one or more Mapping tasks a second time.
The issue arises when the following conditions are true:
  • The workflow includes the Mapping tasks on sequence flows between two Inclusive gateways.
  • The Data Integration Service on the previous master node stopped during the Inclusive gateway phase after it ran one or more Mapping tasks.
  • You configured the workflow for manual recovery.
MWF-220
When the Data Integration Service on the master node in a grid stops during a workflow run, the workflow monitor might incorrectly report the status of one or more workflow tasks. The monitor might report that one or more Mapping tasks are in a canceled state. Additionally, the workflow monitor might not refer to tasks that completed after the Mapping tasks completed.
The issue arises when the following conditions are true:
  • The Data Integration Service on the master node fails over to a Data Integration Service on a worker node while the Mapping tasks are running.
  • The workflow includes the Mapping tasks on sequence flows between two Inclusive gateways.
  • You configured the workflow for automatic recovery.
MWF-218
If the Data Integration Service restarts during a Mapping task in a workflow, the service might not run the Mapping task and one or more subsequent tasks when the workflow recovers. For example, if a Human task follows the Mapping task, the Data Integration Service skips the Mapping task and the Human task when the workflow recovers.
The issue arises when the following conditions are true:
  • The Data Integration Service stops immediately after it begins to run the mapping from the Mapping task.
  • You configured a skip recovery strategy on the Mapping task.
MWF-210
When a workflow that includes a Command task and a Human task recovers from a Data Integration Service interruption, the workflow monitor might not show the correct state of the Command task. The workflow monitor might show that the Command task is running, although the task restarted and completed on recovery.
The issue arises when the following conditions are true:
  • The workflow runs the Command task and the Human task in parallel between two Inclusive gateways.
  • The Human task generates a large number of task instances, for example 600 task instances.
(456589)
MWF-209
A workflow that contains multiple Mapping tasks on sequence flows between two Inclusive gateways might re-run the tasks when the following conditions are true:
  • The Data Integration Service stops while the Mapping tasks are running.
  • The Data Integration Service fails over on a grid or fails over from a primary node to a backup node in a domain.
  • You configured the workflow for automatic recovery.
MWF-1285
If a primary node on which a workflow runs fails over to a worker node, the Model Repository Service that monitors the workflow can report an incorrect status for tasks that started before the node failed. The Model Repository Service reports that the tasks are running when the services start on the worker node.
The issue arises when the following conditions are true:
  • The domain fails over to another gateway node or to a Data Integration Service in a single-node domain.
  • The domain uses different Model Repository Services to store the workflow metadata and to monitor the workflow.
  • The Model Repository Service that monitors workflows stops after the primary node fails and restarts after the other services start on the worker node.
  • The workflow is configured for automatic recovery.
MWF-1283
If the Model Repository Service that monitors workflows stops during an aborted workflow, the monitor might not reflect the status of an aborted task when the service restarts. For example, if a Command task was running when you aborted the workflow, the monitor indicates that the Command task status is unknown.
MWF-1282
If the Model Repository Service that monitors workflows stops during an aborted workflow, the monitor might not reflect the status of a completed task when the service restarts. For example, if a Mapping task completed before you aborted the workflow, the monitor indicates that the Mapping task status is unknown.
MWF-1281
If the Model Repository Service that monitors workflows stops during a workflow run and restarts after the workflow completes, the monitor statistics do not indicate the completed state of the workflow. Instead, the monitor indicates that the task that ran when the Model Repository Service stopped is still running.
MWF-1280
If a domain fails over from one node to another node while a workflow is running, the workflow engine can take several minutes to start on the latter node.
The issue can arise when one of the following conditions is true:
  • The primary node fails over to a backup node in a domain.
  • The nodes are on a grid.
The Data Integration Service starts on the node without issues.
MWF-1279
If a domain fails over from a primary node to a backup node while a Command task is running, the task does not restart when you recover the workflow on the backup node. The Monitoring tool might identify a Command task in a running state on the backup node, but the Command task is not running.
The issue arises in the following scenario:
  • The domain uses different Model Repository Services to store the workflow metadata and to monitor the workflow.
  • The Data Integration Service that runs the workflow is configured to run on the primary node and the backup node.
  • The domain restarts while the workflow is running, and the Model Repository Service that monitors the workflow also restarts.
MWF-1276
If a domain fails over from a node to another node in a grid while a workflow is running, the workflow engine does not start on the failover node. Additionally, the grid Data Integration Service might start and subsequently become unavailable on the failover node.
The issues arise when the grid Data Integration Service runs the workflow.
MWF-1275
If you complete a task in a workflow that is interrupted when the domain restarts, the Monitoring tool displays duplicate statistics for the task. The statistics indicate that the task is running and that an additional task is complete. The workflow instance does not contain the additional task.
The issue arises in the following scenario:
  • The domain uses different Model Repository Services to store the workflow metadata and to monitor the workflow.
  • After the domain restarts, the Data Integration Service restarts before the Model Repository Service that monitors the workflows restarts.
MWF-1273
If a Notification task in a workflow specifies a large number of email recipients, the workflow can take a long time to send the notifications to the set of recipients. The issue is observed when you select a group with 5,000 users as the recipients in the Notification task.
MWF-1259
If you configure a parameter in a Command task to return a value in multibyte characters, the workflow might return the value in Latin characters. The issue is observed when you run the workflow on an AIX operating system.
MWF-1209
If a Data Integration Service stops and restarts while it is running multiple workflows, the workflow engine can take a long time to restart. For example, if the Data Integration Service stops and restarts while 600 workflows are running, the workflow engine might take 20 minutes to restart.
BDM-4701
When you run multiple concurrent instances of the same workflow, the Mapping tasks might fail to update a persisted mapping output.
Workaround: Start the workflows with a ten second delay between them. (443810)
BDM-4489
When an SQL data service query generates a long WHERE clause, pushdown to the source fails. For example, if an SQL query generates a WHERE clause of 61 KB or higher, pushdown to source fails.
Workaround: You can reduce the optimizer level for the query or increase memory for the JVM that runs the Data Integration Service. (375473)
BDM-2611
A partitioned mapping fails if you use the default merge file name to sequentially merge the target output for all partitions.
Workaround: Change the default name of the merge file. (393416)
BDM-2558
The Data Integration Service does not apply the cost-based optimization method to a mapping that contains an unspecified row limit or a LIMIT clause in the SQL transformation even if the mapping is configured to use the cost-based optimization method. (440275)
BDM-2553
When the Data Integration Service applies the cost-based optimization method to a mapping with an Aggregator transformation, it might add an extra Sorter transformation even if the data is sorted before the Joiner transformation and the Aggregator transformation appears after the Joiner transformation. (440849)
BDM-2436
A validated mapping fails to run with an expression parsing error because an expression contains Unicode punctuation characters in field names. (431685)


Updated January 17, 2019