One Dimension Table Deletion issue

Dear Guru's
Query run's very long time to execute in prod system
In our production system, we have a Cube in which one dimension(Eg:- /BIC/PC_17 which show 38% when i run report SAP_INFOCUBE_DESIGNS ). Due to the performance issue of the Query, i am thinking to delete data from SE11 only for this dim table...What will happen with the Factable?
Since Dim table has reference to Factable...Is it correct if i delete the entries for this Dimension table for the perfomance issue?
PLease suggest me i am very much confused, also this is a prod system....so pls give me only good answers..no gess please...
Also ....suppose if this Dim17 is not used in Query Does it make sense to delete entries from this Dim 17 for Query performance, since this exist's in cube...
Thanks in adv,
Dev

Hi,
you should not do that. In no case. There are some ways to speed up a query. Use them: e.g. building aggregates, running rsrv to check the cube and possibly have unused entries of dimensions deleted, compress the cube....
regards
Siggi

Similar Messages

Multiple 'logical joins' between a fact table and one dimension table

It appears that one cannot create multiple ‘logical joins’ between a fact table and one dimension table in OBIEE using the Oracle BI Administration Tool. For example, considering a Business Model with a dimension table TIMES and a fact table FACT containing START_TIME and END_TIME, we would like to create separate logical joins from FACT to TIMES for the START_TIMEs and END_TIMEs? Obviously, the underlying foreign keys can be created, but as far as I can tell the Oracle BI Administration Tool doesn’t support this. The workaround would be to replicate the TIMES table, but that’s ugly.
I seek an alternative approach.

Try this. Create an two aliases for the TIMES dimension (Start & End) in the Physical Layer and then remove foreign key to the "Parent" Times dimension. Create the Foreign Key in the Physical Layer to the new aliases and then create the complex joins in the BMM Layer to the new aliases as well. This will allow you to present both dates within the same table in the Presentation Layer. Not the most elegant solution but it works.

Two fact and one dimension table

Hi folks
i am new to this field ( 3 months ), my TL has given me one task i have to finish it up today itself, Can anyone one give me some idea how to implement
req. The req is
1. there are 2 fact and one dimension table is there, i have to create reports on Quaterly and monthly basis by using one dimension table.
Can any one tell me what all are the steps in need to follow
2.What is standalone and integrated systems?
Regards
Reddy

Hi
If u r having mapping keys for quarter level n monthly level then create a Alias for the dimension table.Use the original dim table for quarter level mapping and the alias dim for monthly level.
Thanks
Don

Issue using one 2 Fact tables with one dimension Table.

Hi,
I have 1 Dimension table X and 2 Fact tables A and B
X is joined to Both A and B for Loan Amount ( with A) and for colleatral amount (with B) when I am selecting the X.Product_Name, A.Loan_Amt, B.Collateral Amount, it is giving an error message
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 15018] Incorrectly defined logical table source (for fact table EIP Collateral FACT) does not contain mapping for [EIP Reporting FACT.PD ID]. (HY000)
Any clues???
Is there a Inner or Outer join which needs to be created or set in the RPD to get the desired results???

Ok..
I have one table which is Porfolio Details which has Portfolio name, Product Category , Product Name, Product ID, Product sources code.- This is my Dimension table.
I have another 2 set of fact tables : EIP Reporting FACT and EIP Collateral FACT..
These two tables are joined to Portfolio Details table.
EIP Reprting FACT gives portfolio wise Loan Amount
and EIP Collateral FACT gives Portfolio wise Collateral Amount details for same set of customer..
Now, I am selecting Portfolio Name, Product Category, Product Name,SUM( EIP Reporting FACT.LOAN_AMOUNT), SUM(EIP Collaetral FACT.Collateral_Amt) in a report
Now, on selecting these columns I am getting that error message which is related to mapping.
If I take any column from Portfolio details table and any column from EIP Reporting FACT- It works.
If I take any column from Portfolio details table and any column from EIP Colletral FACT- It works.
But if I take any column from portfolio table and columns from both FACT tables it gives mapping error...
Hope I am able to explain the issue in a better way now..
Edited by: help-required on Mar 11, 2010 6:53 PM
Edited by: help-required on Mar 11, 2010 6:53 PM

Dimension Tables deleted

Hi BW Experts,
Recently we loaded SD data. There are 6 data sources and we got 6 requests in Manage screen and got transferred/added records. There are about 8 lakh records. (INITIALIZATION)
When i check the contents, iam not able to see the data in Infocube.
We found the problem that Dimension Tables data deleted and we are able to see the fact table data.
So please can anyone tell me the solution??
Regards
Anjali

Hi,
right click on the cube and select delete data. It will ask you options that you want to delete data from only fact table or fact table and dimension table.
select the second option i.e. "fact table and dimension table", it will delete all data from fact table and dimension table drops them and recreate them.
then you can do the data load again.
Regards,
Purvang

Multiple Joins from one Dimension Table to single Fact table

Hi all,
I have a single fact table with attributes as such:
Action_ID
Action_Type
Date_Started
Date_Completed
and a Time Dimension to connect to the fact table. Currently the 2 Date columns in my fact table are in the format of 20090101 (which is the same as my key in the time dimension), if it means anything. I've tried to create multiple joins but have been getting error messages. What is the easiest way to link the time dimension with the two date columns in my fact table? Thanks.

hi..
it seems to be, you need to use between operator to join time dimension with fact (i.e. Non-equi join)
If it's then you should create complex join in physical layer by connecting dimension with your fact.
select columns and operators in such a way that it resembles something like the below.
timeDimension.timeKey BETWEEN FactTable.Date_Started AND FactTable.Date_Completed

Using different logical tables in one dimension

Hello.
I have two fact tables and two dimension tables Country and Region. One fact table depend on one dimension table like it shown in this link - http://file.qip.ru/file/121151603/3b4ebdba/2_online.html. Table Country is received from table Region by DISTINCT.
At the presentation I have to realize one column in Presentation Catalog for both columns Country Name (or Country Id) from Country and Region, the user won't know that one fact table depends on COUNTRY and other on REGION.
Also I have to realize the dimention "Geography" (Country->District->Region) for fact table SALE_REGION.
Could Oracle BI automatically choose from which table get data and if it can, how I should make the logical model?
Thanks.
PS.
The best variant I realized it this - http://file.qip.ru/file/121154314/8d242b81/3_online.html where District is the shared child for second Country level, but it doesn't work properly.

Y don't u use union request in first request details of fact1 and its related dimensions and in 2nd request fact 2 and its related dimensions.
I guess this should work
Thanks
Subhash

Show name field for two columns Fact Table joing by one Dimension

Hi all,
My question is about physical joins in Oracle BI EE.
Task is:
In a relational fact table "star" there is two columns Entity 1, Entity 2 and a table dimension Entity witch have two filds: ID and NAME. By loadind data fact table is filled with id for Entity 1 and Entity 2.
In a report made in Answers i need to show ID_Entity_1 NAME_Entity_1 ID_Entity_2 NAME_Entity_2
Question is: how to do physical join between two columns fact table and one dimension table entity so, that i can show name field in a report for both columns Entity 1, Entity 2.

You must Create an alias in the physical layer of your table dimEnsion and use it as a second dimension table.

How to Create a Dimension Table in OBIEE11g

Hello,
Chapter 9, page 221(if pdf) of the Build Repository manual of OBIEE 11g explains following.
Creating Dimensions in Level-Based Hierarchies
After creating a dimension, each dimension can be associated with attributes
(columns) from one or more logical dimension tables and level-based measures from
logical fact tables. After you associate logical columns with a dimension level, the
tables in which these columns exist appear in the Tables tab of the Dimension dialog.
To create a dimension with a level-based hierarchy:
1. In the Business Model and Mapping layer of the Administration Tool, right-click a
business model and select New Object > Logical Dimension > Dimension with
Level-Based Hierarchy.
Note that this option is only available when there is at least one dimension table
that has no dimension associated with it.I am still learning OBIEE, and I can not see the dimension menu item as per point 1 becuse i do not have dimension table associated with it. All I have done at this point is to create logical tables based on few physical tables in physical layer.
How do I create Dimension Tables? using BI Admin tool?
Thanks,R

Hi Rich,
If you are new to Oracle BI, you would better start with the Oracle Learning Library; http://apex.oracle.com/pls/apex/f?p=9830:41:0::NO:RIR:IR_PRODUCT,IR_PRODUCT_SUITE,IR_PRODUCT_COMPONENT,IR_RELEASE,IR_TYPE,IRC_ROWFILTER,IR_FUNCTIONAL_CATEGORY:,BI,,,,,
You create dimensions based on your logical tables. In a plain star-schema you would have one logical fact table and at least one or more logical dimension tabes attached (joined) to the fact table. Just follow the documentation and you would be good to go.
Good Luck,
Daan Bakboord
http://obibb.wordpress.com

Dimension table is associated with N number of fact tables

Hi Expert's,
In case of star schema one fact table is associated with N dimension tables , is it possible to join one dimension table with N number of fact tables...please let my know the your suggestion...
Thank's
Harish

is it possible to join one dimension table with N number of fact tablesYes you can join one dimension table to many fact tables.
Thanks,
Vino

Dimension table design Data modeling question

Hi Experts,
Sorry if I am putting my question in a wrong forum and please suggest an appropriate forum.
need your opinion on the existing design of our 10 years old datawarehouse.
There is one dimension table with structure like following
Dimension Table
Dimension Key Number (THIS IS NOT A PRIMARY KEY)
Natural key (from source) Number
source name character
current record indicator char(1)
form_date date
to_date date
many other columns, which if change a new current record is created and previous is marked as H-historical
Data is stored in the dimension table like this
Dimension_key Natural key Source Name current record ind from_date to_date
1 10001 Source1 H 1-jan-2005 31-may-2005
1 10001 Source1 H 1-jun-20005 12-dec-2011
1 10001 Source1 C 13-dec-2011 NULL
2 20002 Source1 H 1-jun-20001 12-dec-2011
2 20002 Source1 C 13-dec-2011 NULL
The problem I see in this design is that there is no surrogate key, if any attribute is changed the new record is inserted by first taking the dimension key based on the (natural_key,source_name,current_record_ind).
Shouldn't it be stored like following based on the data-warehousing principals.
Dimension_key Natural key Source Name current record ind from_date to_date
1 10001 Source1 H 1-jan-2005 31-may-2005
2 10001 Source1 H 1-jun-20005 12-dec-2011
3 10001 Source1 C 13-dec-2011 NULL
4 20002 Source1 H 1-jun-20001 12-dec-2011
5 20002 Source1 C 13-dec-2011 NULL
Please let me know the pros and cons of the current design.

And what if you have both the features something like this :
Lineno Dimension_key Natural key Source Name current record ind    from_date         to_date
     1              1       10001     Source1                  H   1-jan-2005     31-may-2005
     2              1       10001     Source1                  H 1-jun-20005     12-dec-2011
     3              1       10001     Source1                  C 13-dec-2011            NULLI mean just add a new column and populate it with required order by clause. Because what i guess, that in the second example you just added a new column which is something like a line number.
Regards
Girish Sharma

One Dimension with Facts at different levels

I currently have a single dimension with 5 levels. I have two fact tables that both connect to the dimension table but at different levels.
For example. If we have a Dimension Country -> Region -> City and then two fact tables. One that has facts at the Region level and one that has facts at the City level.
Is there a way to be able to have an answer that contains facts from both fact tables. So if there was a fact from City and the Region level? Everything I seem to try does not work. Would I have to create an additional aggregate table that aggregates the City level data up to the Region? Or is there a way to show the data at the lowest level and show either nulls or duplicate values for the additional records.
Any help is greatly appreciated

This has helped a little. I am now getting values from both levels. However, because i am summing the two values. The value from the upper level is now summing duplicate values. For example.
Value 1 on its own
Level1 Level 2 Level 3 Value 1
1234 10 10 13.05
1234 20 10 70.00
1234 20 20 70.00
1234 30 10 105.00
1234 30 20 105.00
Value 2 on its own
Level1 Level 2 Level 3 Value 2
1234 10 10 0.50
1234 20 10 2.00
1234 20 20 2.00
1234 30 10 3.00
1234 30 20 3.00
What I am getting
Level1 Level 2 Level 3 Value 1 Value 2
1234 10 10 13.05 0.50
1234 20 10 140.00 2.00
1234 20 20 140.00 2.00
1234 30 10 210.00 3.00
1234 30 20 210.00 3.00
Desired Outcome
Level1 Level 2 Level 3 Value 1 Value 2
1234 10 10 13.05 0.50
1234 20 10 70.00 2.00
1234 20 20 70.00 2.00
1234 30 10 105.00 3.00
1234 30 20 105.00 3.00
Now, the problem with this is that Value 1 is a fact at Level 2 and Value 2 is a fact at Level 3. I have one dimension table and two fact tables. The join between the fact table for Value two and the dimension table is the same as the join between the dimension table and Value 1 only it is missing the last level of detail.
I have then set the logical table source content tabs for each fact table to the corresponding levels.
I thought this would be enough but i still don't get the desired result. I am not sure if this is possible with one dimension table.
Any ideas would be greatly appreciated.
Edited by: user10800227 on Jan 11, 2010 12:43 PM

2 date columns and one dimension hierarchy

Hi,
I have one question in OBIEE 10g.
I have one dimension table with 2 date columns (insertedOn, updatedOn)
I created insertedOnYear, insertedOnMonth and updatedOnYear, updatedOnMonth columns from my date columns.
I have hierarchy
Year -> Month -> Day for that dimension table
and I would like to dril down both columns insertedOnYear and updatedOnYear
insertedOnYear -> insertedOnMonth -> insertedOn
updatedOnYear-> updatedOnMonth -> updatedOn
I am able to do it only for one of these columns and not for both.
I can place both columns to appropriate levels, but drilling doesn´t work as I want
Can you tell me how to solve my problem?

Oops, I was talking about 11G. Ok no problem. Do this. In the physical layer, cretea 2 alias tables. Both pointing to the table where you have these 2 fields. The put everything in your BMM. There create the 2 hierarchies using the 2 different tables (that will point to the 2 alias tables create in the physical layer). This will make them unique.

How many heirachies can be created using one dimensional table

Hi,
I have one dimension table and one fact table, how many heirachies can be created, is it only one?
Thank you.

Hi,
One dimension can have only one hierrarchy for sure.But create dimension in a such a way(columns should be included in one dimension,example: Year and FYear in Time Dimension) that we can create two branches on Total level.
Refer this blog..Will solve your doubt....http://gerardnico.com/wiki/dat/obiee/hierarchy#defining_multiple_hierarchies_for_the_same_dimension_logical_table
Regards,
Srikanth
http://bintelligencegroup.wordpress.com

Urgent-Issue in the Dimension tables

Hi Experts,
Question1:
I have a flat file load to a cube.this flat file has 1.5 mil records.One of the dimension created has a 2 dates(original date & current date) assigned.
When i look at dimension table for # entries is 30million.And when i look at the table i see the sids as 0,0 ( for 2 dates) and dim id's being creted.
When i did a search on the dimension table with current date & original date as not equal to 0.I see only 76,000 records.
Question 2:
we have an ODS which loads to the cube.In the process chain we have program that deletes the data in ods which does not match some conditions and then loads it tot he cube.
My question is,since we are not deleting contents from the cube and reloading it from the ODS(Full update).Will i not be seeing same records coming in with Full update which get agrregated in the cube.
Ex: i have a record in ODS.
A   X Z 100 1000
After full update to the cube,the cube would have
A   X Z 100 1000
When i run the process chain and data is dleeted from ODS on some condition and i still have hte same record in ODS and when this loads into cube wont this be aggregated with the previous record.
A X   Z 200 2000
Would appreciate,if anyone could explain if i am missing anything.

Hello,
If you can't see the SID means you have not loaded the master data, that why there is no reference to the SID table and the values are 0.
InfoCube by default will have aggregated values, when there are duplicate records on the Keyfigures will be aggregated.
For example I have a Material Dimension and Customer Dimension
In the fact table, it will be like this
DIM1     DIM2    KF1   KF2
Mat001 Cust1 100    10
Mat001 Cust2 200    5
for this there will be 1 entry in Material DIM table for Mat001 and 2 entries for Customer DIM table for Customer Cust1 and Cust2.
Material Dimension
DIM ID    SID
1             Mat001 (Here it will be SID from Material Master)
Customer Dimension
1             Cust1 (Here it will be SID from Customer Master)
2             Cust2 (Here it will be SID from Customer Master)
Note : DIM ID is the combination of one or more SID in the dimension table.
So the exact fact table will look like
MATDIM    CUSDIM       AMT      QTY
1               1                  100        10
1               2                  200        5
If you load the data again with same characteristics values then the key figure will be aggregated
Example if you load
Mat001 Cust2 25 5
then the fact table will not have a new entry instead the it will aggregates and looks like (bolded one)
MATDIM    CUSDIM       AMT      QTY
1               1                  100        10
1               2                  220        10
Hope its clear
thanks
Chandran

One Dimension Table Deletion issue

Similar Messages

Maybe you are looking for