Data Engineering Integration
- Data Engineering Integration 10.2
- All Products
Bug
| Description
|
|---|---|
PLAT-18498
| When you run a mapping that contains a logical data object and a Lookup transformation, the mapping terminates unexpectedly on AIX.
|
PLAT-18386
| A mapping that contains a Match transformation fails in a workflow if a Match transformation strategy specifies a mapplet that contains a Lookup transformation.
|
PLAT-16529
| If the Data Integration Service is enabled to use operating system profiles, the mapping name does not appear in the name of mapping log files.
|
MWF-1443
| The Data Integration Service cannot reopen a network connection to the workflow database when the network connections are closed.
|
MWF-1271
| The workflow engine might fail to start because of an internal exception error.
|
MWF-1261
| The default name of a link between an Exclusive gateway and a Command task in a workflow contains a period in a Japanese locale.
|
MWF-1091
| 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-857
| If the Data Integration Service restarts while multiple workflows are running, the workflow engine can take many minutes to start.
|
MWF-763
| 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-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-585
| You cannot create the workflow database contents if the STRICT_READ_PERMISSION_OVERWRITE custom property is set in the domain.
|
BDM-2747
| When an expression uses TO_CHAR with a port selector that is configured to a date/time data type, the Data Integration Service incorrectly validates the mapping.
|