OWB 10.2 Mapping Generates Different Result if the In-group Order is Changed for the JOINER Operator
(Doc ID 821414.1)
Last updated on FEBRUARY 07, 2019
Applies to:
Oracle Warehouse Builder - Version 10.2.0.1 to 10.2.0.2 [Release 10.2]Information in this document applies to any platform.
Symptoms
In an OWB 10.2 mapping, the order in which the in-groups are defined in the JOINER matters as far as generated code goes. When changing the order of the tables in the JOINER, the actual code that gets generated changes, with incorrect query output as a result.
The issue can be reproduced with the following steps:
1. Create two mapping exactly the same with the join condition.
2. In the first mapping the in-groups are defined as table1, table2 and table3.
3. In the second mapping change the in-groups order to table3, table2 and table1.
4. Validate, deploy and execute the mapping.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |