Partitioned Mappings in the Native Environment
Effective in version 9.6.1, partitioned mappings in the native environment include the following changes:
- Mapping Maximum Parallelism
When the maximum parallelism for a mapping is Auto, the actual parallelism value equals the minimum of the following values:
- - Maximum parallelism value set for the Data Integration Service process.
- - Maximum number of partitions for all flat file, IBM DB2 for LUW, and Oracle sources in the mapping. The Data Integration Service determines the number of partitions based on the source type. The number of partitions for a flat file source equals the maximum parallelism value set for the Data Integration Service process. The number of partitions for a DB2 for LUW or Oracle relational source equals the number of database partitions in the relational source.
Previously, when the maximum parallelism for a mapping was Auto, the actual parallelism value equaled the maximum parallelism value set for the Data Integration Service process.
- IBM DB2 for LUW Relational Targets
The Data Integration Service can create partitions for a mapping when the mapping contains a DB2 for LUW target that has more database partitions than the parallelism value. If the DB2 for LUW target has more database partitions than the parallelism value, the Data Integration Service uses all of the writer threads defined by the parallelism value. The Data Integration Service distributes multiple database partitions to some of the writer threads.
Previously, if the DB2 for LUW target had more database partitions than the parallelism value, the Data Integration Service did not create partitions for the entire mapping. The Data Integration Service used one thread to process each mapping pipeline stage.