Table of Contents

Search

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

Mappings and Workflows Fixed Limitations (10.1.1 HotFix 1)

Mappings and Workflows Fixed Limitations (10.1.1 HotFix 1)

Review the Release Notes of previous releases for information about previous fixed limitations.
The following table describes fixed limitations:
Bug
Description
MWF-1471
The workflow engine might fail to start because of an internal exception error.
MWF-1469
If you run infacmd dis UpdateParameterSetEntries to update a complex parameter in a parameter set that a Mapping task uses, the task fails when you run the workflow that contains the task. The complex parameters are Expression, Input Link Set, Port, Port List, Resource, and Sort List.
MWF-1458
You might experience problems when you try to import or export a workflow object from one project to another project in the Model repository.
MWF-1267
The Job Status tab in the Administrator tool does not update the status of a mapping job if the domain restarts while the mapping is running. The Job Status tab indicates that the mapping is running although the mapping failed when the domain stopped. The issue also arises for a mapping that runs in a Mapping task in a workflow.
The issue arises when the following conditions are true:
  • You use a dedicated Model Repository Service to monitor workflows.
  • The Model Repository Service that monitors the workflow restarts after the Data Integration Service restarts.
MWF-1251
The workflow monitor in the Administrator tool can indicate that a completed Command task is in an aborted state.
The issue arises when the following conditions are true:
  • You use a dedicated Model Repository Service to monitor workflows.
  • The Model Repository Service that monitors the workflow stops and restarts while the Command task is running.
  • The Data Integration Service stops and restarts after the Command task is complete.
MWF-1223
You can set a mapping-specific system parameter in tasks other than a Mapping task in a workflow. For example, you can use the sys:TargetDir parameter to set the working directory in a Command task. At run time, the workflow uses the default Data Integration Service directory as the working directory for the Command task and ignores the sys:TargetDir parameter.
MWF-1220
When a Mapping task in a workflow runs in an Apache Hive or Blaze environment, the system-defined mapping output values are 0.
MWF-1213
You cannot create the workflow database contents if the STRICT_READ_PERMISSION_OVERWRITE property is set in the domain.
MWF-1211
If you restart a Data Integration Service that runs multiple workflows, the workflow engine that the Data Integration Service uses can take a long time to restart.
CORE-5690
High CPU consumption occurs when you run multiple mappings with the following conditions:
  • Partitioning is enabled.
  • The mappings contain multiple Sorter transformations.


Updated June 23, 2020