Categories
- All Categories
- 15 Oracle Analytics Sharing Center
- 14 Oracle Analytics Lounge
- 208 Oracle Analytics News
- 41 Oracle Analytics Videos
- 15.7K Oracle Analytics Forums
- 6.1K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 76 Oracle Analytics Trainings
- 14 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
values missing when using 2 facts in obiee 12c

Hi,
I am trying to build a basic report with one dimension (lets assume it to be location) and 2 metrics from 2 facts (F1,F2) and location is a confirmed dimension.
I am missing values from either one of the fact for some rows in the report.
I have checked the sql and it gives right results,but i am not seeing the same results in the report.
I have created hierarchy for location dimension and made location_key as primary key and location_name as display key for location level.I have just added location number to this level (it is not primary key nor display key)
when i use location number i dont see values form either one of the fact and when i use display key i see all the values.
is this a bug in obiee 12c or am i missing something? do i need to use display key always to combine results from 2 facts.
This does not happen always ,it will sometimes show numbers.
I have just attached samples :
location dimension:
Location_Key Location_Number Location_Name
10 10 California
20 20 ohio
30 30 virginia
expected result :
location_number F1.metric F2.metric
10 25 50
20 17 19
30 10 48
result i am seeing:
location_number F1.metric F2.metric
10 25 50
20 19
30 10 48
result when i use display_key:
location_number F1.metric F2.metric
california 25 50
ohio 17 19
virginia 10 48
Answers
-
First: it's a conformed dimension and not a confirmed dimension.
Logical level keys doesn't play a role in showing data. It works fine with multiple facts and conformed dimensions in 12c.
875299 wrote:This does not happen always ,it will sometimes show numbers.
Do you maybe have cache enabled?
How good/bad is the model?
Something not happening always means you have an issue somewhere ...
Analyse generated queries and logs when it works and when not, compare them: what's different?
0 -
Few days back I came across an oracle document which explain similar issue. It was for OBIEE 11g. Doc ID 2257126.1
0 -
Good catch
0