OBIEE: Setting Fact to Total Level Of Hierarchy No Longer Forces Outer Join
(Doc ID 1601703.1)
Last updated on APRIL 01, 2019
Applies to:Business Intelligence Server Enterprise Edition - Version 126.96.36.199.1 and later
Information in this document applies to any platform.
Environment was upgraded from 188.8.131.52.5 to 184.108.40.206.1.
Inner joins are used throughout the repository for performance purposes; however, occasionally there is a need to force an outer join between multi-factual analyses. Since the 10g environment, this was done by setting a fact to the total level of an unconformed dimensional hierarchy.
OBIEE is writing the two different queries for 220.127.116.11.5 and 18.104.22.168.1.
- In 22.214.171.124.5, it uses a full outer join between the two datasets.
- In 126.96.36.199.1, it uses a left outer.
A reasonable solution would be to either maintain the full outer join, or be able to force which select statement is used as the anchor. Regardless of syntax selected (SQL Server 2000, 2005, or 2008), OBIEE writes the same query logically.
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