Sequential read on Cube fact table

I have couple of queries on a particular cube that run forever , i rebuilt the indexes for that
cubes fact table and regenerated the queries . some of them started executing pretty quick
whereas the others are still very slow .
The result is similar when i use listcube also
when i check sm66 it it sows that the query reads the cube fact table for a very very long time .
Is there anything that can be done ?
All suggestions welcome !!
cube has no aggregates

Hi oops,
Why dont you build aggregates on the cube? it will considerably reduce the query run time.refreshing cube statistics and creating index definitely help in loading the cube and reading the cube but if it has got huge records, then obviously, the query run time will be high and you have to build aggregates for the cube. If you click on business intelligence in SND, then ull find many documents as how to create an aggregate under performance link. This should help you
Regards
Sriram

Similar Messages

Copy Cube, Fact table partitioned automatically.

Hello Guys.
I have a trouble.
I do a copy of one cube to make a backup of data to redisign the original cube.
The problem is that now I see that the fact table of my new cube is partitioned into multiple tables.
I'm on Oracle database, an I can see with program SAP_DROP_EMPTY_FPARTITIONS in se 38, that on Dev environment there is any partitions in both cubes, but in prod system, if I use the same program, I see that the original cube is not parttitioned, but the new cube (that is a copy of the original one) does have a lot of partitions in it.
This partitions are generating that the loads from one cube to other be very extensive (for 300,000 registers) it delays around 4 hours, and it's because of the partition of the cube.
So I want to know what thing cause that my fact table of the copy cube be parttitioned, and how can I solve this problem in order to make the loads of data more quickly.
THANKS in advance.

Did u tried partitioning the cube by fiscper/calmonth?
This will surely help the system with very low number of partition.
Cheers..
(BTW: if you creating a backup copy/archive of cube which doesnt require posting date in reporting, try to change posting date to end of month and hence the aggregation level with change resulting in low volume)...

How to combine multiple fact tables and dimensions in one worksheet?

Hello Forum,
I am encountering a reporting problem when trying to create a worksheet that uses more than one cube/fact table and common dimensions. I have used Oracle Warehouse Builder 10Gr2 to design and deploy a pretty simple ROLAP data mart. We are using Discoverer Plus for OLAP as our reporting tool. We have 5 dimension tables using a star schema and 3 fact tables, when I create the worksheet I bring in our sales measure from our sales item table and then Store_Name from my Stores Dimension and then day from my time dimension, everything looks good at the stage, we're just trying to get a sum of all sales for that store on that day. Then I bring in a measure from our advertising cost table and a join window pops up asking which join to use, if I choose either the Store or the Time dimension I get correct data for the first fact table (sales) and grossly incorrect data for the ad cost measure from the second fact table (advertsing costs)...... any help would be appreciated

You have encountered one of the key limitations of Discoverer... which I complained about to the Discoverer product manager at OpenWorld in 2001....
Anyhow, to get around this, you are going to have to deal with it either in the database, (views, materialized views, tables), or within the admin tool by creating a custom folder.
Discoverer also calls this the "fan trap", but never really had a solution to the problem. [The solution only worked is you joined to one and only one dimension!]
What you want (using Sales_Fact and Inventory_Fact as an example) is to join Sales to Time, Store, and Product, and save that result. Then join Inventory to Time, Store, and Product, save that result, then do a double outer join between the two intermediate temporary tables in order to calculate something useful like inventory turns by store and product line.
This is also known a "multipass SQL", and is supported by some (but not many) other tools.
So, to accomplish this with Discoverer, you'll either need to create a view, or table, or materialized view that has already put Sales and Inventory into a single (virtual?) fact table. Alternatively you can write the SQL for how to do this linkage (don't forget to handle missing data), and use the Discoverer admin tool to create a custom folder that uses your SQL.
Hope this helps!

Join fact tables with different grain without upsetting measures?

Say I am a business analyst at a university, and I have two analytical cubes available to me: an Enrollment Cube and an Admissions Cube. The Enrollment Cube has a grain of Student and Semester, whereas the Admission Cube has a grain of Student, Application and Semester (a potential student can have more than one application in a semester). Is there any way for the OLAP developer that makes these cubes to make it so that I can use both cubes' fact tables without messing up their corresponding measures, such that I can create such analyses as the following:
County
Semester
Acceptance Rate (Admission Fact)
Retention Rate (Enrollment Fact)
County A
1
30%
88%
2
60%
87%
3
42%
84%
County B
1
90%
100%

One suggestion is to create a view that joins the 2 fact tables and then create a cube with measures mapped to the view for analysis purposes. However, this would be using the measures of the new cube for the analysis.

Long time to load data from PSA to DSO -Sequential read RSBKDATA_V

Hi ,
It is taking long time to load data from PSA to DSO. It is doing Sequential read on RSBKDATA_V and table contents no data .
we are at - SAPKW70105. It started since yesterday . There is no changes in system parameters.
Please advice.
Thanks
Nilesh

Hi Nilesh,
I guess the following SAP Note will help you in this situation.
[1476842 - Performance: read RSBKDATA only when needed|https://websmp107.sap-ag.de/sap/support/notes/1476842]
Just note that the reference to Support Packages is wrong. It is also included in SAP_BW 701 06.

Most economical fact table?

Hi,
When I read about implicit fact tables, there's always the mention of 'most economical fact table'. I have not yet understood the exact meaning of this. Does it mean the table with least number of joins? That's not the case because when I don't mention any implicit fact tables, it does not choose the fact table with least number of joins.
Then what does 'most economical fact table' mean?
regards.

Hi User,
This generally means that Obiee will take the fact table from the business model with the least amount of dimensions.
that was my understanding.
mark if helps, or correct me if m wrong.
fiaz

Fact table with datetime measure showing #value error while browsing the cube

Hi All,
I have a cube with a fact table having datetime measure.
when I browse the cube, I am able to see the data for all measures except for the measure with the datetime as datatype.
Thanks in advance.

Hi jarugulalaks,
Actually this forum is to discuss:
Visual Studio WPF/SL Designer, Visual Studio Guidance Automation Toolkit, Developer Documentation and Help System, and Visual Studio Editor.
To make this issue clearly, would you mind letting us know more information about this issue? Whether it is the VS IDE issue? Which language are you using? Which kind of app are you developing? Maybe you could share us a screen shot about it.
But like this case posted by you here:
https://social.msdn.microsoft.com/Forums/vstudio/en-US/bc2d30b8-a60d-4f0f-a273-b7cf0f5aaed5/value-error-for-datetime-measure-in-ssas?forum=visualstudiogeneral#bc2d30b8-a60d-4f0f-a273-b7cf0f5aaed5
If it is the SSAS issue, please post this issue to the SSAS forum for dedicated support.
Best Regards,
Jack
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Error for the fact table while processing the cube - attribute key cannot be found when processing

Please help as I am new to SSAS and this is urgent requirement. This is a MOLAP cube and below is the error that I am receiving when processing the cube. The cube is set to Prrocess Full. Several similar errors are popped up for various dimensions.
"Errors in the OLAP storage engine: The attribute key cannot be found when processing: Table: 'Fact_Table', Column: 'ID', Value: '1'. The attribute is 'Id'. Errors in the OLAP storage engine: The attribute key was converted to an unknown member because
the attribute key was not found. Attribute Id of Dimension: 17 - Ves - PoC Cont from Database: DB, Cube: IPNCube, Measure Group: iSrvy, Partition: Partition1, Record: 1."
Thanks in advance.

Thanks for the recommendations David.
It will be really great if you can clear some of my doubts:
To my information, all the dimensions need to be processed first and then the fact table will be processed.
So if the ID's are not present in the dimension tables, then it should not be present in the Fact table either.
Here we found null values in the dimension table and the ID's were present in the Fact table. What might be the reasons causing such situation?
Also how frequently the cube needs to be processed? Currently the ETL which processes the cube, is scheduled in a SQL Job Agent on hourly basis everyday.
Is there any possibilty that the cube might be under processing state and the SQL job for the next run getting executed trying to access and process the cube while it was still processing?

How to create a ROLAP Cube that has two fact tables.

I want to know if it is possible to create a ROLAP Cube with two fact tables.
Suppose that I have these two star schemas:
The first star schema has only a measure and a time dimension. The time dimension has three levels (Year -> Month -> Day)
The second star schema has the same measure of the first schema and a time dimension. In this schema the time dimension has only two levels (Year -> Month). The values of the measure of this schema come from the first schema, this is, the value of the measure for a defined year and month results of the sum of all fact values of the first schema, that have the same year and month.
I want to know if is possible to create a ROLAP cube that can get the information of the two star schemas, according to the level that the user are consulting.
For example, if the user consults the cube with "OracleBI Spreadsheet Add-In", and if the user is consulting the first two levels (Year and Month), then the ROLAP cube would get the information of the second star schema.
But if the user does a drill down in a month to get information of the days, then the ROLAP cube would get the information of the first star schema.
Is it possible to do this?
Regards,
Rui Torres

I'm not exactly sure what you want to do. Sorry if I get this wrong.
You have two fact tables, one with data values at the day, month and year levels and a second fact table with data values at just the month and year levels. If this is the case, in the CWM2 APIs or OWB Paris, you would create a view that joins the two tables together and then map this view to the ROLAP cube.
For CWM2 details, please refer to the Oracle OLAP Reference.

SSAS 2008 Using multiple (three) fact tables in the same cube

Hi, I have three fact tables in my cube,
Actions
Events
Visits
Events captures anything that happens, any transaction. It contains parent actions and parent visits, plus other things that business deems as "actions" that change all the time.
Actions captures a subset of Events and has its own transactional structure. Each action has an event, but not every event has an action.
Visits is a completely different subset of Events with a very different transactional structure from both events and actions. Each condition can have an event, but not every event has a condition.
These facts don't have many overlapping dimensions, perhaps a couple of outrigger look-up dimensions, like Codes and Dates.
I am struggling to reorganize the cube in such a way that I don't have to process with errors and unknown dimension members. Is there any specific guidance re: what to do in these situations?

@Victor Rocca
Some dimensions are common, like Dates and Codes, but mostly they are their own dimensions. Visits
and Actions facts have foreign keys from Events in them, so I would prefer to join directly, anyway.

Are fact tables and cubes same in OWB?

Dear all
A simple question. How can I create a star schema (that is, with a fact table and dimensions) using OWB?
OWB has options to create cubes, but as per my understanding a cube is not a fact table.
Cube contains pre-computed data where as fact table contains normal data with references to dimensions.
Please correct me if I am wrong.
thanks in advance

These are just different levels of abstraction.
"Cube" is the highest level of abstraction referring to the overall package of data.
"Star schema" is how cubes are modelled showing the relationships from a fact entity to the dimension entities.
Relational and OLAP are different methods of physical implementation.
In OWB, to promote sharing of dimensions across cubes to avoid inconsistency the idea is you define and build the dimensions independently. Then you define the "cubes" as measures and references to the dimensions. When you build the "cube" you pass in business identifiers from the source data which OWB will use to link the measures to the applicable dimension data. Due to the wonders of inner joins anyone reading the "cube" will only see dimension data related to the data in that cube!
Using OWB you do not need to be concerned with the physical implementation when you use the dimension and cube operators as those operators know what to do.

Record count is double in the Fact tables when compared to Cube data!

Hello BW Gurus,
I have 2 question to be answered!
1. I have a cube which consist of 3 years of data. Due to some bad data in it, I have dropped the cube data completely from fact and dim tables and did an init. from ODS. the load failed due to "No SID found for value '2000000000000000000000010' of characteristic 0MAT_PLANT". I have run a RSRV test to find if there is any inconsistency in SID's for 0MAT_PLANT but everything looks great. Considering the time span in mind to finish the load I have removed that record from PSA and re-pushed the data from PSA which was successful, however I wanted to know if anyone has come across such kind of error.
2. The load finished successfully in the cube but the performance of the cube was very bad coz my cube request shows only 3.5 million records but when I checked in the fact table it was showing double i.e. 7 million records, which is because I deleted the failed init. request and re-pushed the data from PSA. can anyone suggest me how to overcome this I mean how to bring back my fact table records to 3.5 million?
please advise me and thanks so much!
Swathi.

hi Swathi,
1. for 0mat_plant no sid, beside rsrv, you can try rsd1, infoobject maintenance, there is menu (about 3rd from left) 'fill sid ...'.
for infocube update, please make sure you 'delete data',
'fact and dim...'. check again if fact table counts 0 records then you can update from ods with 'initialize'. or if you go by psa then delete data both infocube and ods (from ods to cube should sufficient).
2. for performance, check in infocube -> manage -> performance, make sure index and statistic is green. you can create index there, also refresh the statistic.
hope this helps.

AWM adding very less rows in cube as compared to source fact table

AWM is adding just 4 lack rows in the cube. While there are above 10 billion rows in fact table. Even I have applied no aggregation rule at any dimension in cube. And number of rejected records is zero.I am confused what could be the possible reason

Take a look at the SQL query generated by OLAP during cube load.
You can look at it in AWM cube mapping, OR in the CUBE_BUILD_LOG table.
Maybe a SUM..GROUP BY ... is happening during cube load and that is why 1 billion rows are becoming 400,000 rows.
Are the numbers correct when you look at the data at top nodes?

Fact table size of the cube

BW Gods!
I need to selectively delete data from a cube which holds data from 2001-2006.....say I want to delete data only for 2001. It was suggested to me by pizzaman in one of our earlier threads that BW would decide if the data to be deleted is more than 10% of the cube size and if it is, it would just copy the cube without the data which has to deleted and it would rename the cube. So he suggested that I should find out the fact table size and make sure that there is enough space in my fact tablespace for this operation to go on.
My question is, how do I find out the fact table size of the cube?
How do I find out if there is enough space on fact tablespace for the above said deletion operation to be executed.
I am not too sure whether I have put across the question correctly. Let me know.
Thank you all in adavance
Ashwin

You want to make sure you include space for the F fact table and the E fact table, assuming you compress the infocube. If you use DB02 and use wild cards you migh be able to get all teh size info in one shot.
Gnerally, he indices for an InfoCube don't occupy a lot of space, but they do take space.
The default InfoCube table space is PSAFACTD and indics are in PSAPFACTI - not 100% sure that is universal acorss all the different DBs. Your shop could also have put them in differnt tablespaces altogether. Probably worth a quick check with your DBAs - they might know that they have lot of space availalbe, and you don't need to take the time to run down the space usage info.
The table copy process will NOT delete the original fact tables unless/until it has successfully loaded to new copy.

Identify the Cubes where dimension table size exactly 100% of the fact tabl

Hello,
We want to Identify the Cubes where dimension table size exactly 100% of the fact table.
Is there any table or standard query which can give me this data?
Regards,
Shital

use report (se38) SAP_INFOCUBE_DESIGNS
M.

Sequential read on Cube fact table

Similar Messages

Maybe you are looking for