My Oracle Support Banner

Use of dimension hierarchies (Doc ID 732638.1)

Last updated on JANUARY 10, 2020

Applies to:

Business Intelligence Suite Enterprise Edition - Version 7.8.5.2 [AN 7164] and later
Information in this document applies to any platform.
Information in this document applies to any platform.

Goal

Qn1:

If there is no hierarchy with a dimension, is a dimension hierarchy table still needed in the logical model? What can go wrong if the hierarchy is not used?

Qn2:

Is it a rule that once you create a hiearchy on 1 table joining to a fact, you must create it on others? So, for Fact1, we have DayDim and Dim2, we create a hierarchy on DayDim, does Dim2 need it also? I have seen problems when this isn't set. Similar situation where Fact1 joins to Dim1, and Dim2 and Fact2 joins to Dim1 and Dim3 - if we have all hierachies set on Dim1 and Dim2, then we get problems showing Fact1 and Fact2 on one report if Dim1 hiearchy not set for Fact2?

Solution

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
Goal
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.