Incorrect Sql Generated From RPD Shows Left Outer join for Right Outer Join.
(Doc ID 2191249.1)
Last updated on MARCH 05, 2019
Applies to:
Business Intelligence Suite Enterprise Edition - Version 12.2.1.0.0 and laterInformation in this document applies to any platform.
Symptoms
OBIEE is generating Left Outer join for Right Outer Join in RPD.
Steps
----------
1 Open the SampleAppLite RPD and check the BMM whole diagram
2 Notice that there is an inner join between D2 Offices and F0 Revenue Based
Measures
3 Run an Analysis using "Offices""Office" and "Base Facts""Revenue"
The physical sql in the session log shows:
from
SAMP_OFFICES_D T9 /* D20 Offices */ ,
SAMP_REVENUE_F T8 /* F10 Revenue Facts (Order grain) */
where ( T8Office_Key = T9Office_Key )
4 Change the inner join in Step#2 to a Left Outer Join in BMM
5 Run the same analysis and notice the following physical sql in the session
log:
from
SAMP_OFFICES_D T9 /* D20 Offices */ left outer join
SAMP_REVENUE_F T8 /* F10 Revenue Facts (Order grain) */ On
T8Office_Key = T9Office_Key
6 Change the inner join in Step#2 to a Right Outer Join in BMM
7 Run the same analysis and notice the following physical sql in the session
log:
from
SAMP_REVENUE_F T8 /* F10 Revenue Facts (Order grain) */ left outer
join
SAMP_OFFICES_D T9 /* D20 Offices */ On T8Office_Key =
T9Office_Key
The physical SQL still shows a left Outer join, although the tables are
interchanged This is causing wrong report results for customer
***Setting a value for "Driving Table" did not make any difference It
still shows left outer join***
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 |