Multiple Aggregate Tables in OBIEE

We are experiencing a funky issue with the use of aggregate tables. Unfortunately, I am not seeing any obvious way in the documentation or blogs to remedy this issue.
Leveraging the Aggregate Persistance Wizard we developed 2 aggregates for our data set.
1st is a monthly aggregate with a rollup data set and the 2nd is the daily aggregate with a more limited data set.
For a set of monthly queries and dashboards both aggregates will produce the correct results, but the monthly agg does it 10 times faster <5 sec. However, for some reason the BI Server is choosing the daily aggregate instead.
Any ideas on how we can force / hint for the BI server to use the monthly aggregate first if it can?Thanks,
Michael

The log, unfortunately, is to big to in its entirety, but here is the example of the queries that go against the daily aggregate as oppose to the monthly:
+++Administrator:7a0000:7a0001:----2009/06/10 09:04:48
-------------------- General Query Info:
Repository: Star, Subject Area: EnterpriseBI, Presentation: EVSalesReporting
+++Administrator:7a0000:7a0001:----2009/06/10 09:05:14
-------------------- Sending query to database named BONARDEV (id: <<6974073>>):
select D3.c4 as c1,
D3.c5 as c2,
D3.c2 as c3,
D3.c1 as c4,
D3.c6 as c5,
D3.c7 as c6,
D3.c8 as c7,
D3.c3 as c8
from
(select D1.c1 as c1,
D1.c2 as c2,
D1.c3 as c3,
D1.c4 as c4,
D1.c5 as c5,
D1.c6 as c6,
D1.c7 as c7,
D1.c8 as c8
from
(select sum(T31738.Curr_Day00015AE1) as c1,
D47.c8 as c2,
D47.c4 as c3,
T31723.Trade_Clas0001777C as c4,
D47.c3 as c5,
D47.c7 as c6,
D47.c6 as c7,
D47.c5 as c8,
ROW_NUMBER() OVER (PARTITION BY T31723.Trade_Clas0001777C, D47.c4 ORDER BY T31723.Trade_Clas0001777C ASC, D47.c4 ASC) as c9
from
SA_Trade_C000176D4 T31723,
SA_Organiz00015413 T31635,
ag_Sales_Metrics_2 T31738,
(select distinct D1.c1 + 1 as c1,
D1.c2 as c2,
D1.c3 as c3
from
(select min(D1.c1) over (partition by D1.c4) as c1,
min(D1.c2) over (partition by D1.c4, D1.c3) as c2,
D1.c3 as c3
from
(select Case when case D1.c5 when 1 then D1.c3 else NULL end is not null then Rank() OVER ( ORDER BY case D1.c5 when 1 then D1.c3 else NULL end ASC NULLS LAST ) end as c1,
Case when case D1.c6 when 1 then D1.c3 else NULL end is not null then Rank() OVER ( PARTITION BY D1.c4 ORDER BY case D1.c6 when 1 then D1.c3 else NULL end ASC NULLS LAST ) end as c2,
D1.c3 as c3,
D1.c4 as c4
from
(select T31704.Date_ID00016FBC as c3,
T31704.Calendar_Y00014B57 as c4,
ROW_NUMBER() OVER (PARTITION BY T31704.Calendar_Y00014B57 ORDER BY T31704.Calendar_Y00014B57 DESC) as c5,
ROW_NUMBER() OVER (PARTITION BY T31704.Calendar_Y00014B57, T31704.Date_ID00016FBC ORDER BY T31704.Calendar_Y00014B57 DESC, T31704.Date_ID00016FBC DESC) as c6
from
SA_Day00015E8E T31704
) D1
) D1
) D1
) D48,
(select distinct min(D1.c1) over (partition by D1.c6) as c1,
min(D1.c2) over (partition by D1.c6, D1.c4) as c2,
D1.c3 as c3,
D1.c4 as c4,
D1.c5 as c5,
D1.c6 as c6,
D1.c7 as c7,
D1.c8 as c8
from
(select Case when case D1.c9 when 1 then D1.c4 else NULL end is not null then Rank() OVER ( ORDER BY case D1.c9 when 1 then D1.c4 else NULL end ASC NULLS LAST ) end as c1,
Case when case D1.c10 when 1 then D1.c4 else NULL end is not null then Rank() OVER ( PARTITION BY D1.c6 ORDER BY case D1.c10 when 1 then D1.c4 else NULL end ASC NULLS LAST ) end as c2,
D1.c3 as c3,
D1.c4 as c4,
D1.c5 as c5,
D1.c6 as c6,
D1.c7 as c7,
D1.c8 as c8
from
(select T31704.Calendar_M00014B4D as c3,
T31704.Date_ID00016FBC as c4,
T31704.Calendar_Q00014B51 as c5,
T31704.Calendar_Y00014B57 as c6,
T31704.Month_End_00014B6D as c7,
T31704.Calendar_D00014B5B as c8,
ROW_NUMBER() OVER (PARTITION BY T31704.Calendar_Y00014B57 ORDER BY T31704.Calendar_Y00014B57 DESC) as c9,
ROW_NUMBER() OVER (PARTITION BY T31704.Calendar_Y00014B57, T31704.Date_ID00016FBC ORDER BY T31704.Calendar_Y00014B57 DESC, T31704.Date_ID00016FBC DESC) as c10
from
SA_Day00015E8E T31704
) D1
) D1
) D47
where ( T31635.Organizati00014BB3 = T31738.Organizati00014BB3 and T31723.Trade_Clas0001777D = T31738.Trade_Clas0001777D and T31635.Business_U00014BC5 = 'EVD' and T31738.Date_ID00016FBC = D48.c3 and D47.c1 = D48.c1 and D47.c3 = '2009 / 05' and (T31723.Trade_Clas0001777C in ('Redemption', 'Sale')) and D47.c2 >= D48.c2 )
group by T31723.Trade_Clas0001777C, D47.c3, D47.c4, D47.c5, D47.c6, D47.c7, D47.c8
) D1
where ( D1.c9 = 1 )
) D3
order by c8, c2, c1
+++Administrator:7a0000:7a0001:----2009/06/10 09:05:14
-------------------- Sending query to database named BONARDEV (id: <<6977524>>):
select D4.c4 as c1,
D4.c5 as c2,
D4.c2 as c3,
D4.c1 as c4,
D4.c6 as c5,
D4.c7 as c6,
D4.c8 as c7,
D4.c3 as c8
from
(select D1.c1 as c1,
D1.c2 as c2,
D1.c3 as c3,
D1.c4 as c4,
D1.c5 as c5,
D1.c6 as c6,
D1.c7 as c7,
D1.c8 as c8
from
(select sum(T31738.Curr_Day00015AE1) as c1,
D49.c3 as c2,
D49.c5 as c3,
T31723.Trade_Clas0001777C as c4,
D49.c4 as c5,
D49.c7 as c6,
D49.c8 as c7,
D49.c6 as c8,
ROW_NUMBER() OVER (PARTITION BY T31723.Trade_Clas0001777C, D49.c5 ORDER BY T31723.Trade_Clas0001777C ASC, D49.c5 ASC) as c9
from
SA_Trade_C000176D4 T31723,
SA_Organiz00015413 T31635,
ag_Sales_Metrics_2 T31738,
(select distinct min(D1.c1) over (partition by D1.c4) as c1,
min(D1.c2) over (partition by D1.c4, D1.c3) as c2,
D1.c3 as c3
from
(select Case when case D1.c5 when 1 then D1.c3 else NULL end is not null then Rank() OVER ( ORDER BY case D1.c5 when 1 then D1.c3 else NULL end ASC NULLS LAST ) end as c1,
Case when case D1.c6 when 1 then D1.c3 else NULL end is not null then Rank() OVER ( PARTITION BY D1.c4 ORDER BY case D1.c6 when 1 then D1.c3 else NULL end ASC NULLS LAST ) end as c2,
D1.c3 as c3,
D1.c4 as c4
from
(select T31704.Date_ID00016FBC as c3,
T31704.Calendar_Y00014B57 as c4,
ROW_NUMBER() OVER (PARTITION BY T31704.Calendar_Y00014B57 ORDER BY T31704.Calendar_Y00014B57 DESC) as c5,
ROW_NUMBER() OVER (PARTITION BY T31704.Calendar_Y00014B57, T31704.Date_ID00016FBC ORDER BY T31704.Calendar_Y00014B57 DESC, T31704.Date_ID00016FBC DESC) as c6
from
SA_Day00015E8E T31704
) D1
) D1
) D50,
(select distinct min(D1.c1) over (partition by D1.c8) as c1,
min(D1.c2) over (partition by D1.c8, D1.c5) as c2,
D1.c3 as c3,
D1.c4 as c4,
D1.c5 as c5,
D1.c6 as c6,
D1.c7 as c7,
D1.c8 as c8
from
(select Case when case D1.c9 when 1 then D1.c5 else NULL end is not null then Rank() OVER ( ORDER BY case D1.c9 when 1 then D1.c5 else NULL end ASC NULLS LAST ) end as c1,
Case when case D1.c10 when 1 then D1.c5 else NULL end is not null then Rank() OVER ( PARTITION BY D1.c8 ORDER BY case D1.c10 when 1 then D1.c5 else NULL end ASC NULLS LAST ) end as c2,
D1.c3 as c3,
D1.c4 as c4,
D1.c5 as c5,
D1.c6 as c6,
D1.c7 as c7,
D1.c8 as c8
from
(select T31704.Calendar_D00014B5B as c3,
T31704.Calendar_M00014B4D as c4,
T31704.Date_ID00016FBC as c5,
T31704.Calendar_Q00014B51 as c6,
T31704.Month_End_00014B6D as c7,
T31704.Calendar_Y00014B57 as c8,
ROW_NUMBER() OVER (PARTITION BY T31704.Calendar_Y00014B57 ORDER BY T31704.Calendar_Y00014B57 DESC) as c9,
ROW_NUMBER() OVER (PARTITION BY T31704.Calendar_Y00014B57, T31704.Date_ID00016FBC ORDER BY T31704.Calendar_Y00014B57 DESC, T31704.Date_ID00016FBC DESC) as c10
from
SA_Day00015E8E T31704
) D1
) D1
) D49
where ( T31635.Organizati00014BB3 = T31738.Organizati00014BB3 and T31723.Trade_Clas0001777D = T31738.Trade_Clas0001777D and T31635.Business_U00014BC5 = 'EVD' and T31738.Date_ID00016FBC = D50.c3 and D49.c1 = D50.c1 and D49.c4 = '2009 / 05' and (T31723.Trade_Clas0001777C in ('Redemption', 'Sale')) and D49.c2 >= D50.c2 )
group by T31723.Trade_Clas0001777C, D49.c3, D49.c4, D49.c5, D49.c6, D49.c7, D49.c8
) D1
where ( D1.c9 = 1 )
) D4
order by c8, c2, c1

Similar Messages

Errors when Creating Aggregate Tables in OBIEE 11.1.1.6 within SQL server

Hi All,
I was trying to create an aggregate table in OBIEE 11.1.1.6 within SQL Server. The sql was generated successfully as below. But an error occurred when I use NQCMD to execute the sql and the following error showed:
1. SQL for creating Aggregate Table:
create aggregates
"ag_Measure"
for "ASOBI_DTT_Demo"."Measure"("ValidVIPCnt")
at levels ("ASOBI_DTT_Demo"."日期"."月", "ASOBI_DTT_Demo"."門市品牌"."門市品牌", "ASOBI_DTT_Demo"."門市類別"."門市類別", "ASOBI_DTT_Demo"."內創門市"."內創門市", "ASOBI_DTT_Demo"."門市/倉庫"."門市/倉庫", "ASOBI_DTT_Demo"."門市群組"."門市群組", "ASOBI_DTT_Demo"."門市行政區課"."行政區", "ASOBI_DTT_Demo"."門市地區"."城市")
using connection pool "ASOBI_DTT_Demo"."ASOBI_System10"
in "ASOBI_DTT_Demo"."ASOBI"."dbo";
2. Error Message:
"ag_Measure"
for "ASOBI_DTT_Demo"."Measure"("ValidVIPCnt")
at levels ("ASOBI_DTT_Demo"."日期"."月", "ASOBI_DTT_Demo"."門市品牌"."門市品牌"
, "ASOBI_DTT_Demo"."門市類別"."門市類別", "ASOBI_DTT_Demo"."內創門市"."內創門市"
, "ASOBI_DTT_Demo"."門市/倉庫"."門市/倉庫", "ASOBI_DTT_Demo"."門市群組"."門市群
組", "ASOBI_DTT_Demo"."門市行政區課"."行政區", "ASOBI_DTT_Demo"."門市地區"."城市
using connection pool "ASOBI_DTT_Demo"."ASOBI_System10"
in "ASOBI_DTT_Demo"."ASOBI"."dbo"
[343][State: 37000] [Microsoft][SQL Server Native Client 10.0][SQL Server]CREATE
、DROP or ALTER 陳述式中使用未知的物件類型 'aggregates'。
Statement execute failed
Which means "Using unknown object type 'aggregates' in CREATE. DROP or ALTER statements" in English.
Can anyone give me a suggestion for this error?? Many thanks!!!

Hi Martin,
I guess, I was not clear enough. Let me try again
How Aggregate Persistence works in OBIEE?
Once you are done choosing options in the Aggregate Persistence wizard, it generates an intelligent Query.
What query is it?
If you happen to understand the query, it is not like any ANSI standard SQL (I would say DDL) query. As you might have noticed there are no SQL Server datatypes, lengths, keys, constraints etc. This query can only be understood by the BI Server.
How do I issue this query?
Since the logical query could only be understood by BI Server, it has to be issued only to BI Server Engine using some tool viz NQCMD in this case.
What does issuing this query using NQCMD do?
The execution steps are as follows, the moment the query is issue via NQCMD
Aggregate Persistent Wiz Generate Query ----- Issued to ---> NQCMD ----- Passes the logical query to ---> BI Server ----- Parses the query ---> Builds the corresponding physical DDL statements Issued --->To the Database --- If successful ---> .RPD is automatically updated with the aggregated sources etc.
How do I pass the query to BI Server using NQCMD?
The format of issuing this logical query to BI Server using NQCMD is
nqcmd -d <Data Source Name> -u <Analytics UserId> -p <Password> -s <command> > output.log
where
<Data Source Name> : Is the DSN name which OBIPS uses to talk to Oracle BI Server. Yes, it's the very same DSN that can be found in InstanceConfig.xml
<Analytics UserID> : Any user in obiee with admin privileges.
<Password> : Password of the obiee UserId
<Command> : Logical SQL Command which you already have handy.
Hope I was good this time..
Dhar

Shortcut object in Sunopsis- Adding one column in multiple aggregate tables

Hello,
We have a situation where we have existing aggregate tables. Now i need to add one column in common to all the aggregate tables(more than 10 aggregate tables). Is there some way out to do all at the same e.g. making some shortcut object or something else.

Hi,
have you tried requesting the focus on your newly selected internal frame ?

Aggregate tables in 10G

Hi Experts,
In OBI 10G how to use Aggregated Tables? How does the server knows when it should use Aggregated Table? And when to use ordinary table at the time of fetching the data?
What is the purpose Aggregate persistence wizard in RPD.
Thanks in advance,

Aggregate Table (Aggregate Persistence Wizard)
Aggregate Table: Aggregate tables store precalculated measures that have been aggregate over a set of dimensional attributes.
This is very useful technique for speeding up query response time in decision support systems. This eliminates the need of run time calculations and delivers faster results to users The calculations are done ahead of time and the results are stored in the tables.
The key point is that the aggregate table should have fewer rows than the non aggregate table and therefore processing should be quicker.
Aggregate Persistence Wizard
Go to: OBIEE Admin > tool> Utilities > Aggregate Persistence Wizard
http://obiee101.blogspot.com/2008/11/obiee-aggregate-persistence-wizard.html
http://obieetutorialguide.blogspot.com/2012/03/creating-aggregate-tables-in-obiee.html

Multiple Hierarchies from Single Dimension Table in OBIEE-11g?

Is it possible to have Multiple Hierarchies from Single Dimension Table in OBIEE-11g?
Like 1)Year-Qtr-Month-Weeks 2)Year-Month-Days

Hi,
or if your lowest level is the same like
Day->month->year->Total
Day->businessMonth->businessyear->Total
Then yes, it is.
Create the first, then you start to create the second by adding your top(business year) level on the same level as the one you have (year) both under your total.
Then when you would add your second base level, there is a special option for it, something like use other hierarchy level/shared level (sorry can't recall and does not have a connection right now) then you select your existing day level under your businessmonth level.
Hope this helps,
Regards,
D

OBIEE bypasses smaller aggregate table and queries largest aggregate table

Hello,
Currently we are experiencing something strange regarding queries that are generated.
Scenario:
We have 1 detail table and 3 aggregate tables in the RPD. For this scenario I will only refer to 2 of the Aggregates.
Aggregate 1 (1 million rows):
Contains data - Division, Sales Rep, Month, Sales
Aggregate 2 (13 milliion rows):
Contains data - Division, Product, Month, Sales
Both tables are set at the appropriate dimension levels in the Business Model. Row counts have been updated in the physical layer in the RPD.
When we create an answers query that contains Division, Month and Sales, one would think that OBIEE would query the smaller and faster of the two tables. However, obiee wants to query the table with 13 million records completely bypassing the smaller table. If we make the larger aggregate inactive, then OBIEE queries the smaller table. We can't figure out why OBIEE wants to immediately go to the larger table.
Has anyone experienced something such as this? Any help would be greatly appreciated.
Edited by: gwb on Aug 19, 2009 7:45 AM

Have you try to change the sort order of the logical table source in your logical table ?
!http://gerardnico.com/wiki/_media/temp/obiee_logical_table_sources_sort.jpg!
Set the Aggregate 1 first.
Cheers
Nico

How to model in RPD aggregate tables with different years of data

Can someone let me know how to accomplish the following in OBIEE?
I want to create a logical fact table with multiple logical table sources. I have an aggregate table that only stores current year data. In OBIEE, if a user builds a report using data from the current year, I want the query to hit this aggregate table. My base fact table however stores all years of data. If a user builds a report using data from prior time periods, I want the query to hit the base fact table.
And if you're curious, the aggregate only contains current year data because the ETL needs to do a full load each night due to the complexity. The high volume of data and the amount of time it takes to populate this aggregate means we only have time to populate the current year data.
Thanks in advance.

Yes this situation is both an aggregate table and fragmented data. I already modeled the aggregate table correctly specifying the content logical levels.
I'm not familiar with how to set the fragmentation logic. I see the fragmentation content section. What do I enter in this section to specify that my AGG table is for current year data? Do I need to enter something for both logica table sources?
Please let me know if there is a link with examples or an explanation. Appreciate the responses.

Error when creating aggregate table

Hello,
I am creating an aggregate table using the Aggregate Persistence Wizard. When trying to run the batch file, I am receiving an error: "Could not connect to the Oracle BI Server instance".
But then, the Oracle BI Server is running and I am able to do queries in answers with no connection issues. (Pls see below)
Please help.
Thanks,
Felicity
D:\OracleBI\server\Repository>create_agg.bat
D:\OracleBI\server\Repository>nqcmd -d AnalyticsWeb -u Administrator -p Administ
rator -s D:\OracleBI\server\Repository\CREATE_AGG.sql
Oracle BI Server
Copyright (c) 1997-2009 Oracle Corporation, All rights reserved
create aggregates
"ag_SalesFacts"
for "SupplierSales"."SalesFacts"("Net Weight Shipped","Units Ordered","Units Sh
ipped","Dollars")
at levels ("SupplierSales"."ProductsDim"."Type", "SupplierSales"."CustomersDim"
."SalesRep", "SupplierSales"."PeriodsDim"."Month")
using connection pool "ORCL"."SUPPLIER CP"
in "ORCL".."SUPPLIER2"
create aggregates
"ag_SalesFacts"
for "SupplierSales"."SalesFacts"("Net Weight Shipped","Units Ordered","Units Sh
ipped","Dollars")
at levels ("SupplierSales"."ProductsDim"."Type", "SupplierSales"."CustomersDim"
."SalesRep", "SupplierSales"."PeriodsDim"."Month")
using connection pool "ORCL"."SUPPLIER CP"
in "ORCL".."SUPPLIER2"
[10058][State: S1000] [NQODBC] [SQL_STATE: S1000] [nQSError: 10058] A general er
ror has occurred.
[nQSError: 37001] Could not connect to the Oracle BI Server instance.
Statement preparation failed
Processed: 1 queries
Encountered 1 errors

Will this help you solve issue http://forums.oracle.com/forums/thread.jspa?messageID=3661598
Check the comments in this blog http://obiee101.blogspot.com/2008/11/obiee-aggregate-persistence-wizard.html
It deals with use permissions for the database.
hope answers your question..
Cheers,
kk

Filter not applied in answers because of aggregate tables

Hi Gurus:
I am having an issue with filters and aggregate tables.
I have a report which I am filtering on a dimension.
Now, if I dont expose that column on report, it is not filtering properly. It is hitting aggregate tables and hence result is not correct.
I checked physical SQL issued, and it doesn't even have that filter in WHERE clause. However, logical SQL has it.
However, if I expose that column on report table, then it is filtering properly, since it is hitting base tables.
I cannot include this column in aggregated dimension , since it is not part of hierarchy ( Snow flaked ).
Any idea why is this happening?
Please help me.
- Vinay

Hi Vinay,
The hints I gave you are not work-arounds or band-aids to OBIEE. They are the features in OBIEE meant for a specific purpose.
As far as the Best Practice OBIEE is meant strictly to source a Fully Qualified Data Marts. You cannot expect a high level summarized data within a few seconds from OBIEE, if you dont have data rolled-up and summarized to different levels.
When we first started using this tool replacing Actuate a couple of years ago, we thought our users will be happy seeing the reports on a click. But it was horrible than Actuate because we dont have our data rolled-up or aggregated.
Now our users love the reports because we have highly aggreagated data sources such as Essbase, Materialized Views, Query Re-Writes, Indexes, Partitioning etc.... etc... and these are all out side OBIEE.
Thanks
Sai

Has anyone managed to configure aggregate tables correctly?

Hi all,
Although OBIEE supports the use of aggregate tables in fact tables as an additional source (for performance improvements), has anyone actually correctly configured them for metrics that use AVGs?
We are seeing that if you create an aggregate table which already calculates averages, when these values are used in further aggregations at the higher levels, they are actually incorrect, as they are based on the pre-calculated averages of the aggregate table, and not on the average of the lowest grain of detail of the fact. This is not a problem for SUM, MIN or MAX metrics, but is a problem for AVG metrics.
This is partly logical, but is a serious limitation for the use of aggregate tables. These tables are correct for all the dimensions included in that aggregated table, but not when you remove one of those dimension in an OBIEE request.
The only workaround we see is to redefine the metric as a metric with a logical definition:
SUM(column that contains value which we want an average for) / SUM (no. of columns in question)
At the lowest detail this has no impact, but on the aggregated levels above, this would assure a correctly calculated average.
Any advice? Opinions? Prior experiences? anything?

Thanks Wildnight.
Yes, it seems logical that with sum all would work correctly, however i think this is only one type of common metrics in use in any datawarehouse. If anyone has any other ideas let me know.
There is also the possibility to play around with the aggregate configuration based on dimensiones (maybe introducing some clever formula in the 'Others' dimension option), or maybe defining AVG in the actual metric definition in the column mappings, and setting the aggregate rule to None.

How can build BMM with multiple fact tables

HI Gurus,
I have 4 fact tables and 18 Dimension table. Dimension tables have links with multiple fact tables. i have created physical joins in Physical layer. Now my questions is how can i create Business Model with multiple fact tables.
i mean should i create 4 fact tables as logical tables and logical keys ? Then i have to move all dimension tables in to Business model?
i am new to OBIEE. i gone through tutorial it is showing with one fact and multi dimension table. Should i do follow same style with multi fact tables.
Please help me. Thanks in advance for your support.

Thanks for your response.
I had drag all tables from the phisical layer to Business Model. then i have deleted all links and recreated complex joins with default values.
now i have some revenue amont columns in fact tables.
my question is should i should i create aggregation ( like Sum..) for those columns? is it must ?
please let me know thank you very much

Unable to join 3 fact tables in obiee data model.

Hi,
I am unable to join the 3 fact tables in obiee rpd. If I join with 2 fact tables I got the data in repors, Once I add the one more fact table and join with related dimensions, I am getting nodata error. I am following all joins keys as per datamodel, I am able to see the data in database. anyone pls give me the solution. Thanks in advance.
Edited by: 1007582 on May 23, 2013 2:17 AM

Can you please give some more detail as in what you have model in RPD;
For example, if There are 3 Fact table F1, F2, F3 and two Dimesion Confirmed_D1, Non_Conf_D2. Confirmed_D1 is joined to all three fact tables and Non_Conf_D2 is joined to F2.
Now to implement this model we have to set the logical content level in BMM layer for Non_Conf_D2 in F1 & F2 to Total*. After this only we can report on Confirmed_D1, Non_Conf_D2, F1, F2, F3 whithout any error.
Sometime join with multiple table can also result in No Data, since the join conditions filters out the result data.
Please mark helpful or correct.
Regards,
Kashinath

Hierarchy with multiple Physical tables

Some time ago there was a post with this subject and I am in need, if you pls, with the same situation:
I am looking for Dim (1) - (1:N)-> Dim (3). And Dim (3) - (1:N)-> Fact.
Suggestion by Mr. Bharath was to, just reduce your snowflake to star in your BMM with Dim (3) as your single LTS. Within the LTS map Dim (1). to Dim (3).
Could someone pls. help me clarifying the suggestion .../
a) Should I use the Dim(3) LTS and how to map Dim(1) ? - I believe we should use a column ? right ? Or just Add the Dim(3) in the LTS tables
Txs. for any hints
Antonio

Hi Antonio,
First of all - try to avoid SNF in BMM.
http://www.oraclebidwh.com/2010/10/obiee-bmm-layer-design-principalsbest-practices/
Comments:
1) You can keep the SNF model in BMM, but if you keep them, then you cannot create an hiearchy with combination of Dim(1) and Dim(3) together as those are two seperate LT.
2) OBIEE will take the shortest path in forming the query. But, if there are multiple shortest path, then OBIEE will use the latest relationship ID in creating the execution plan. For example: Dim (1) is joined with Dim(3) and Dim(4) and your report pulls - Dim(1) and Fact(1), then the shortest path can be either through DIM(3) or Dim(4), and for such scenario's OBIEE will use the ID (latest ID). Say Dim(4) was the latest join - then OBIEE will use Dim(4) in the query to join with Dim(1).
3) I actually do not undertstand your issue here - if you are creating an Hiearchy using Dim(1) and Dim(3) together, then why don;t you pull all the fields from Dim(1) into this LT. And in your presentation create folders if you want both the dimensions to be displayed seperately.
If you are trying to understand and explore OBIEE - then go ahead play with all possible ways you could think off.
Regards,
Bharath

Single date dimension while creating Aggregate tables

hi Guys ,
I have single date dimension(D1-D) with key as date_id and granularity is day-level. I have fact table(F1-D) which gives daily transactions . Now i created three aggregate tables with F2-M(aggregated to monthly),F3-Q(Aggregated to quarterly),F4-Y(Aggregated to yearly). As I said.I have a single date dimension table with date-id as a key.I have other columns month,quarter,year in Date dimension.
My question is : Is this single dimension table is enough to create the joins and maintain the BMM layer .I have joined the date_id to all the facts in physical layer. In BMM Layer i have one fact and 4 logical table sources .Ii have created dimension hierarchy on Date dimension and created the logical levels as year ,quarter,month and daily level and also set their respective level keys . Now after doing these i have also set the logical levels to the 4 logical table sources in the fact table.
Here i am getting an error saying :
WARNINGS:
BUSINESS MODEL Financial Model:
[39059] Logical dimension table D04_DIM_DATE has a source D04_DIM_DATE at level D04_DIM_DATE Detail that joins to a higher level fact source F02_FACT_GL_DLY_TRAN_BAL.F03_FACT_GL_PERIOD_TRAN_BAL
Can anyone tell me why am i getting this error .

1) as you suggest, creating mini dimension tables for each level
3) using views with select distinct x,y,z to model 1) but without the need for phsical tables
I have thought of these scenarios .But it's just creating a multiple Date Dimension tables with there respective grains if we follow 1 and 3 steps you mentioned.
But i don't want to create aliases or views either on Datawarehouse or physical layer (Admin tool).Just with using a single Date Dimension table I need to comeup with a solution as mentioned by my Colleagues.
2) pushing all the calendar attributes into the aggreate table (eg your year aggregate has all the year fields, your month aggregate has all the year fields and all the month fields etc.). Then in BM&M use the aggregate table as a logical table source for the date logical table.
What do you mean by "pushing all the calendar attributes into the aggreate table".If possible can you eloborate a bit so i can try in this way to get this done .
One morething .Here What they were saying is .Join the Single Date Dimension to all the 4 fact tables in Physical layer . Then drag all the tables into the BMM layer and create a Dimensional hierarchies for the Date dimension with levels as Year -->Quarter--> Month--> day level. With the Fact tables: Single fact tables with multiple logical table sources .Then we need to set the levels on the respective logical table sources with the desired levels .Say monthly aggregate table--> Month, Quarter Aggregate table--> quarter level in the Contents TAB.
When i do this I am getting the Warning:
WARNINGS:
BUSINESS MODEL Financial Model:
[39059] Logical dimension table D04_DIM_DATE has a source D04_DIM_DATE at level D04_DIM_DATE Detail that joins to a higher level fact source F02_FACT_GL_DLY_TRAN_BAL.F03_FACT_GL_PERIOD_TRAN_BAL

Model Aggregate tables to speed up query processing

Hi,
Can anyone help me in the topics
"Model Aggregate Tables to Speed up Query Processing"
"Model Partitions and Fragments to improve application performance and usability"
Am new to this concept, haven't worked on this before.
Regards,
Arun

Arun wrote:
Thanks. This would definitely help me out. But, i face issue in opening the repository in Online mode. Could you please tell me how to solve this issue?
Here OBIEE server is lying on Unix Environment.
I've created a repository in Windows Client.(Have installed OBIEE 11g developers client, BI Admin tool in my local machine).
I would like to know the way to open a repository file in online mode in Client side.
Regards,
ArunCreate a 'BI Server' type ODBC connection in your windows environment pointing to your Unix box, then when you go open -> Online in admin tool you will see the entry as an option.
Better to start a new thread when your original question is answered.

Multiple Aggregate Tables in OBIEE

Similar Messages

Maybe you are looking for