Fact and Dimention

Dear All ,
Can any one help me what is this '#' symbol represenatation for the table in the OBIEE admin tool .How the OBIEE admin tool will understand the table as fact and Dimenstion tables in RPD .
Please share the above detiails
Thanks

Hi,
# symbol means its a aggregated measure.
The tables with foreign keys denotes as fact table and table with primary keys means dimension table.
Mark If helpful/correct.
thanks.

Similar Messages

Ratio between Fact table and Dimention table for a Infocube

Hi All,
How can we reduce the Ratio between Fact table and Dimention table for a Infocube below 20%.??
please give suggestions

Hi
Reduce Ratio??
The Ratios are dependent on the Fact Table, and the Dimension table that is modeled for your Cube.
You cannot change ratio individually, but can set the Line Item Dimension , provided you have only one char object is taking much space and bulky with much percentage, based on your requirement. You can always use fine tuning objects.
Please be more specific while posting, to get right help from sdn.
Hope it helps

In Answers am seeing "Folder is Empty" for Logical Fact and Dimension Table

Hi All,
Am working on OBIEE Answers, on of sudden when i clicked on Logical Fact table it showed me as "folder is empty". I restarted all the services and then tried still showing same for Logical Fact and Dimension tables but am able to see all my reports in Shared Folders. I restarted the machine too but no change. Please help me out to resolve this issue.
Thanks in Advance.
Regards,
Rajkumar.

First of all, follow the forum etiquette :
http://forums.oracle.com/forums/ann.jspa?annID=939
React or mark as anwser the post that the user gave.
And for your question, you must check the log for a possible corrupt catalog :
OracleBIData_Home\web\log\sawlog0.log

Best practice when FACT and DIMENSION table are the same

Hi,
In my physical model I have some tables that are both fact and dimension table, i.e. in the BMM they are of course separated into Fact and Dim source (2 different units) and it works fine. But I can see that there will be trouble when having more fact tables and I e.g. have a Period dimension pointing to all the different fact tables (different sources).
Seems like the best solution to this is to have an alias of the fact/transaction table and have 2 "copies" of the transaction table (one for fact and one for dimension table) in the physical layer. Only bad thing is that there will then allways be 2 lookups in the same table when fetching data from the dimension and the fact table.
This is not built on a datawarehouse - so the architecture is thereby more complex. Hope this was understandable (trying to make a short story of it).
Any best practice on this? Or other suggestions.

Id recommend creation of a view in the database. if its an oracle DB, materialised views would be a huge performance benefit. you just need to make sure that the MVs are updated when the source is updated.
-Domnic

How to design fact and dimension tables

Hi Team,
Please provide me some useful links!!
I have a Parent & Child table each has around 8 Million records (1 to many relation). These two tables need relation with many other master tables to generate any report.
I want to desing a fact and dimension(s) for this parent & Child tables.
Please help me what are the things I have to keep in mind when desingning datawarehouse fact and dimension tables?
Thanks,
Ali

Hi, any update on this?

Delete Fact and Dimension Tables

Hai All,
Small question! When deleting data from info cube, it asks whether to delete just Dimension table or both fact and Dimension tables.
What is the difference between these two?
Thank you.

Hi Visu,
The dimension table will contain the references to char value by way of SID and DIM ids, whereas the fact table will contain the number (of key figures). If you delete just the Fact table, the numbers go away, yet the DIM ids remain intact, so reload is faster. But if you are convinced that this data is not correct either, or you want a clean slate to strat reload again, then delete both Fact and Dim tables. Then when you reload, the DIM ids will be created again.
Hope this helps...

Best Practice - Outer Join between Fact and Dim table

Hi Gurus,
Need some advice on the below scenario
I have an OOTB subject area and we have around 50-60 reports based on it. The related subject area Fact and Dim1 table are having inner join.
Now I have a scenario for one report where outer join has to be implemented between Fact and Dim1. Here I am against changing the OOTB subject area join as the outer join will impact the performance of other 50-60 reports.
Can anyone provide any inputs on what is the best way to handle this scenario?
Thanks

Ok. I tried this:
Driving table : Fact, Left outer join -- didnt work.
Driving table: Dimension D left outer join -- didnt work either
In either the case, I see physical query as D left outer Join on Fact F. and omitting the rows.
And then I tried this -
Driving table: Fact, RIght outer join.
Now, this is giving me error:
Sybase][ODBC Driver]Internal Error. [nQSError: 16001] ODBC error state: 00000 code: 30128 message: [Sybase][ODBC Driver]Data overflow. Increase specified column size or buffer size. [nQSError: 16011] ODBC error occurred while executing SQLExtendedFetch to retrieve the results of a SQL statement. (HY000)
I checked all columns, everything matched with database table type and size.
I am pulling Fact.account number, Dimension.account name, Fact.Measures. I am seeing this error each time I pull Fact.Account number.

Unable to Create Fact and Dimension tables from the Tools menu in EIS conso

Hi All,
In the EIS console, I am unable to create the fact table and the dimension tables to produce my OLAP model from the TOOLS menu whereas I am able to create them by dragging from the left panel where the tables are displayed. I am geeting the below error message:
"An exception occured while retrieving OLAP model metadata. Please verify you are connected to the catalog and try again"
Any help appreciated.
Thanks,
Raja

I have fact and dimension tables in one server and i moved those stuff to another server.If I do that what happen to essbase and about totale EPM System.I want to know how to do this and what I can expect?
Please reply

How to have fact and dimension which are not joined in same report

Hi All,
suppose we have 2 dimensions and 1 of them is joined to fact but we want to pull both these dimensions along with fact and fact column shows null but we dont want that .how can we have 2nd dimension which is not joined to fact in the same report .Actually i have a column called equipment schedueled time and it can be shown only with equipment dimension but I want to pull both equipment,geography and equipment scheduled time in report if I do it now it shows equipment scheduled time as null because its not joined with geography dimension.I want even if the geography dimension exists it should show the value of equipment scheduled time .
Can someone please help me.
Thanks in Advance

Hi ,
Can you please tell me what are fact and dimension tables of your requirement.If you want display the data from 2 dims and a fact table ,you have to establish the joins between facts and dimensions.
mark if helpful/correct...
thanks,
prassu

Need to pull the information from two facts and associated dimensions

HI All, i need to pull all the columns from the two Facts and their associated dimensions, get the results.
here is the example:
Fact1 --> D1, D2, D3
FACT2--> DA, DB, DC, D1
D1 Dimension has a Join with two fact tables, as long as i'm using columns from D1 and FACT2, DA, DB, DC report works.
but my requirement is to get the results when pulling the columns from all the dimensions and two facts like Fact1, FACT2, D1, D2, D3, DA, DB, DC
how to achieve this requirement, can someone pls help me with this.
your responses are much appreciated.
Thanks
rar

Hi RAR,
I assume you have created proper dimensional hierarchies for all the dimensions in your subject area. Also, ensure that all of them have a Total Level created.
Assuming the above, since D1 is a conformed dimension, if you create a report having columns from only D1,Fact1 and Fact2, the report should show you proper results.
For creating a report having columns from all tables, ensure the following:
1. For all measure columns from Fact1 to be included in the report, set them to be calculated at the Total Level of dimensions DA, DB and DC
2. For all measure columns from Fact2 to be included in the report, set them to be calculated at the Total Level of dimensions D2 and D3
The physical sql will fire separate queries for the 2 star schemas and then join them using the conformed dimension.
Hope this helps,
Gaurav

Urgent - How to join multiple facts and dimensions in OBIEE rpd??

Hi,
In my RPD I have 3 facts and 4 dimensions and the joins defined are as below
Physical layer - All joins are FK and inner (1:N)
FACTA-------------- DIM_TIME, DIM_CUST,DIM_CAL
FACTB-------------- DIM_TIME, DIM_CUST,DIM_CAL
FACTC-------------- DIM_TIME, DIM_CUST,DIM_CAL, DIM_XYZ
BM layer - All joins are complex, inner
The logical table F1 pulls columns from FACTA, FACTB and FACTC . Complex join exists between all 4 dimensions DIM_TIME, DIM_CUST,DIM_CAL, DIM_XYZ to logical table F1.
Issue: I need to build a report with $ column from FACTA, FACTB and FACTC and need to add filter conditions using columns from DIM_TIME, DIM_CUST,DIM_CAL, DIM_XYZ.
However when ever I add a filter condition from DIM_XYZ the physical query generated is not generating code to access data from FACTA and FACTB. Instead it is subsituting a NULL and just pulls data frm FACTC.
My Questions: What is the best way to build the physical and BMM layer using FACTA, FACTB,FACTC, DIM_TIME, DIM_CUST,DIM_CAL and DIM_XYZ??
I need to resolve this issue ASAP so any help is appreciated. Thanks
Edited by: user11935561 on Feb 10, 2010 6:27 AM
Edited by: user11935561 on Feb 10, 2010 6:28 AM

You can find the same issue in
Logic of queries in OBIEE
or
Connection between 2 fact tables
Follow the link
http://there-n-back-again.blogspot.com/2009/04/oracle-analytics-how-to-report-over-non.html
Put 'All' or 'Total' at levels for dim_xxx for those facts you need in your report from facta and factb
Regards
Nicolae

What is the total weight and dimentions of a Mac Pro with retina 13"? Including any extra delivery packaging (i.e box, bubble rap, etc)? Thx

What is the total weight and dimentions of a Mac Pro with retina 13" including any extra delivery packaging (i.e box, bubble rap, etc)? Thx

What is the total weight and dimentions of a Mac Pro with retina 13" including any extra delivery packaging (i.e box, bubble rap, etc)? Thx

Facts and dimensions joins

Hi,
Can we use three fact tables in rpd and not join them? We have three facts and four dimensions. All the four are common dimensions to the three fact tables. So in the physical joins can we just join the facts to the dimensions? will it be accepatble if we do not have a join between fact tables. Is it necessary that all the tables (fact and dimensions) need to be joined to some tabler? Can we leave the joins between the facts which are not necessary? Please advice.

We do not do joins between fact tables, the joins between facts will be happened through dimensions (conformed dimensions).
In your case the 4 dimension will act as an conformed one.
Is it necessary that all the tables (fact and dimensions) need to be joined to some tabler? You cannot have a table in BMM which is not joined to any other table.
Can we leave the joins between the facts which are not necessary?Yes, Dim1 - fact1 -Dim 2 in this fact 1 is connected with Dim1, Dim2 and there is no relationship for fact1 with Dim3 so we don't join it.
Dim1,Dim2,Dim3 is joined with fact2 in this case Dim 1 and Dim2 will act as conformed dimesion between fact1 and fact2, where as dim3 will be a non conformed dimesion.
Thanks,
Vino

3 facts and 4 dimensions

Hi,
In my RPD I have 3 facts and 4 dimensions and the joins defined are as below
Physical layer - All joins are FK and inner (1:N)
FACTA-------------- Dim1,Dim2,Dim3,Dim4
FACTB-------------- Dim1,Dim5,Dim6
FACTC-------------- Dim1,Dim7,Dim8,Dim9
BM layer - All joins are complex, inner
Question is
When i am fetching the data some records are showing blanck and some with records
i wants table to be filled with records not blanck anywhere
thanks

If you set the content level for Fact B to be TOTAL for Dim 2 the metric will be null since there is no relationship between these tables. If you want the metric to repeat for this dimension you need to set the metric content level to TOTAL for Dim 2. Try that with one of the metrics and verify the behaviour.

Join multiple facts and dimensions for reporting issue

Hi,
I have a report requirements and need to use multiple fact tables and unconformed dimensions as described below
Fact table: F1,F2,F3
Dimensions tables: D1.....D9
F1:(joined to) D1,D2,D3,D4
F2::(joined to)D1,D2,D5,D6
F3::(joined to)D1,D2,D7,D8
D7::(joined to)D9,D8 (dimension D7 joined to two other dimensions D9 and D8
I'm trying to use columns from almost all the fact and dimension tables but getting "Unable to navigate requested expression. Please fix the metadata consistency warnings."
Repository is consistent and no errors and warnings.
How can I configure the repository to develop reports using all fact tables and dimensions?
Appreciate for your help.
Thanks
Jay.

You can find the same issue in
Logic of queries in OBIEE
or
Connection between 2 fact tables
Follow the link
http://there-n-back-again.blogspot.com/2009/04/oracle-analytics-how-to-report-over-non.html
Put 'All' or 'Total' at levels for dim_xxx for those facts you need in your report from facta and factb
Regards
Nicolae

Fact and Dimention

Similar Messages

Maybe you are looking for