BSO Calculation

I have 12 dimensions in my cube. I know it is not recommended to have these many dimensions but I am helpless against requirements. Now I have member formulas to do currency conversion in the dimension called Currency Type. The default calc takes 4 hours and because of formulas I cannot utilize the parallel calculation.
So what I did is
CALC DIM ("Currency Type");
CALC ALL EXCEPT DIM("Currency Type");
Will the above calc script provide me the same results as
CALC All;
Thanks

From an aggregation standpoint, it will most likely give you the same results, but not necessarily. You do have to consider order of dimension aggregation possibly giving you different results.
In a CALC ALL, dimensions are calculated in the following order:
1) Dimension tagged as Account
2) Dimension tagged as Time
3) Remaining Dense dimensions in outline order
4) Remaining Sparse dimensions in outline order
In your case, you're going to get something slightly different that could result in different numbers (particularly if you've got two-pass members). Here's what your order would be:
1) "Currency Type" dimension
2) Dimension tagged as Account
3) Dimension tagged as Time
4) Remaining Dense dimensions in outline order
5) Remaining Sparse dimensions in outline order
I guess I'm confused on why you're doing this, though. If you're looking for efficiency in your calc, I'm going to assume your dense dimensions are dynamic at all upper levels (and on the formula members), you don't have formulas on sparse dimensions, and all you need to do after converting currencies is to aggregate your sparse dimensions. If all that's true, use the AGG command on your sparse dimensions instead of CALC DIM or CALC ALL EXCEPT DIM.
Hope that helps,
Edward, Oracle ACE Director - Hyperion
http://looksmarter.blogspot.com/

Similar Messages

MDX / BSO calculations with transparent partitions - Recursive reference

Hi Everyone,
I am using Essbase v11.1.2 and have an empty ASO cube that has transparent partitions to several ASO source cubes. However, I would like to use MDX in the target ASO cube to pull data from one cube, but make it available to all queries from other cubes.
Eg. Empty Target ASO cube TrgtASO has VOLUMEmetric and versions Ver1, Ver2 and Ver3. I have 3 ASO source cubes for each version.
SrcASO1 is only cube with volume data
SrcASO2
SrcASO3
I had created a metric called "Vol-All versions" in the TrgtASO cube and tried to use MDX fornula ([Version].[Ver1],[Measures].[VOLUME]) so that no matter what version is selected, the data will always be from SrcASO1.
It works if I have all data in one cube and load data only into Ver1. However, for performance and query reasons, I need to put each version into it's own cube.
My question is do transparent partitions allow recursive retrieval of data?
I.e. If I log into TrgtASO cube and pull metric "Vol-All versions" but have either Ver2 or Ver3 as the version, is there an MDX formula that will pull the volume from Ver1 cube?
Any assistance would be greatly appreciated.

BSO & ASO

Why do we have to maintain one ASO and BSo for Application
all calculation in one (BSO) and ASO just for reporting .. is that only purpose ..i guess this iwll be good for 100 of user .. what if we have 9 users and data is very very less so still we have to use this
pls do advise in what scenarios we have to maintain such BSO and ASO like format

The below are the simple differences of ASO and BSO
BSO Cubes
Useful for systems that involve complex calculations
BSO Engine cannot handle much sparse data
ASO Cubes
Different method for storage and calculations
Different storage kernel
Useful for databases which are read only
Useful for cases where dimensions are large in number
Eg. Customer analysis, procurement analysis
ASO vs BSO
Load time in ASO is 20% faster than BSO
Calculation time is 20 times faster
Storage space is 10 times smaller
ASO Cubes becomes slower than BSO Cubes for Queries
ASO Cubes can have many more dimensions
End Users
No difference for end users during use with Smart View, Add in, FR Reports
When to use ASO
Database is sparse and has many dimensions. Aggregation is much faster
Calculation of the database is frequent
Storage Kernel of ASO
Multidimensional Index
Indexes the index to facilitate faster aggregation
Unlike BSO Storage is not in Blocks but in optimized aggregation nodes
Loads data at only Level 0
Algorithm selects and stores queries and increased speed
These queries will pre calculate data values and store pre calculate data results in aggregations

Dynamic/Stored calculations in BSO

Hello Guys,
(Rephrasing the question)
I've below queries in respect to Storage for a BSO member calculations,
first consider 3 two dimensions,
Measures
-Source
---A(~)
---B(~)
-Cals
---D(~)
---E(~)
Product
--P1(+)
----P11(+)
----P12(+)
----P13(+)
Customer
--C1
---C11(+)
---C12(+)
Here
1) For Measure 'D', I want data for Measure A to be aggregated only for P11 and P12 products,
Calculation based on Single Dimension members.
2) Measure 'E', I want data to refer to only particular Combinations sum like D = (B -> P13 --> C12) + (B -> P11 -> C11)
Calculation based on combinations of Dimensions
I have several KPIs and different rules needs to be implement across dimensions, so using Fix is not so easy.
For now I'm using member formulas with dynamic cacls.
As data is increasing then I'm facing the following challenge
dynamic calc processor cannot allocate more than [100] blocks from the heap. Please increase CalcLockBlock setting and then retry
I've increased the CalcLockBlock to 500, restarted Essbase service and tried but still facing the same problem. Hence I made calc members to Stored Type
What I want to know is
1) Any suggestion for calcs, as the levels and dimensions are different for several measures
2) What is the difference for Calculation process and result for Dynamic Calc over Stored across dimensions.
Thank You
Edited by: NareshV on Mar 28, 2011 8:19 PM

Thank you for your responses.
Srinivas Bobbala wrote:
D = (B -> P13 --> C12) + (B -> P11 -> C11) - This requires to calculate onlt two blocks. I think calculations are more complex than this with if conditions.
I was just giving an example, to increase the complexity here, I've some 5 other dimensions as well and hence you can understand it is not just 2 blocks.
I've few Dynamic Cal members with outline formulae which refer to different block combinations.
When I pull data from Add-in, I get Essbase Error
Dynamic calc processor cannot allocate more than [100] blocks from the heap. Please increase CalcLockBlock setting and then retry
From the Application log, I get to see the following error
*[Wed Mar 30 01:43:44 2011]Local/APP/DB1/admin/Error(1020004)*
An error [1012700] occurred in Spreadsheet Extractor.
*[Wed Mar 30 01:43:44 2011]Local/APP/DB1/admin/Info(1020055)*
Spreadsheet Extractor Elapsed Time : [0] seconds
*[Wed Mar 30 01:43:44 2011]Local/APP/DB1/admin/Info(1020082)*
Spreadsheet Extractor Big Block Allocs -- Dyn.Calc.Cache : [100] non-Dyn.Calc.Cache : [0]
*[Wed Mar 30 01:43:44 2011]Local/APP/DB1/admin/Warning(1080014)*
*Transaction [ 0x400c3( 0x4d928ad0.0x58610 ) ] aborted due to status [1012700].*
I've tried to resolve this by
1) Adding 'CALCLOCKBLOCK HIGH 500' in essbase.cfg ( as I did not see CALCLOCKBLOCK in the config file)
2) Increased my Datafile cache to 505416KB as per existing Blocks & Block size
Block Size is 1792 B, Existing Blocks 577619
3) Restarted Essbase service and application
Guys, Am I following the correct steps ? How can I make this to work.

Running calculations BSO versus ASO

which architecture is better to use if you have to run large calculations? (Essbase Version 11)

Allocations were introduced in ASO in 11.1.2. They are done in memory and create data slices. In theory, this could be quicker than an allocation done in BSO especially if you have to agg the cube to get what is being allocated. Plus you are not bringing in whole blocks just cells. I cant give you an honost answer because I've not tried large allocations in ASO yet. I will say if they are complicated, it will take a lot more work to set them up in ASO than in BSO. Also, if you actually use the allocation function in BSO it can be quite slow. You also get the block creation issue at time.
I guess the onl;y thing I can advise is to set up tests in both ASO and BSO and see which performs better.

Date Difference Calculation in BSO Cube

Hello,
need help with Date Calc
I have a Dim. Called Inv Date and another Dim. Check Date( which is Time Dim.)
I will like to do this calculation Inv Date - Check date and store the difference in a Measure member called days outstanding
This should return how many days difference between both dates.
will really appriciate if some one could help.
thkx
mits
Edited by: user12527998 on Jan 28, 2010 1:43 PM

Hi,
I always find a post by John Booth's a useful guidance when you are wanting to run calculations with dates, have a read at :- Calculations with dates
If you are using Version 11 you also have a look at the new date functions e.g. @DATEDIFF - http://download.oracle.com/docs/cd/E12825_01/epm.111/esb_techref/calc_datediff.htm
Cheers
John
http://john-goodwin.blogspot.com/

Calculation Function BSO

Hi All,
I was trying to achieve something similar to crossjoin in BSO. Can anyone please suggest , if there is any function similar to Crossjoin in BSO ?
Please advice.
Thanks
Andy

I am confused about what you are asking. a crossjoin is what is done in BSO cubes. Do you mean what is the equivelent to a crossjoin in an ASO cube?

Calculation in Secondary Hierarchies

Hi
Can anyone help me to apply a different calculation for a secondary hierarchy ? I have designed a BSO cube and the one of the Dimensions has a an Secondary Hierarchy . The requirement is that when a user look at the data for the Sec Hierarchy I want to apply a different calculation using cross dimension (than the Primary One) .
Thanks in advance
Unnimon

A different calculation for a member or a different aggregation to a parent?
A different calculation would have to have a different member name (could not be shared member) that could reference the original member in the calculation if you wish. And, really, if "one member" has two different calculations, the two instances really shouldn't have the same name anyway as they obviously mean (at least) two different things.
A different aggregation, you just put different aggregation on the shared member.
Have Fun!

Data issues in Migrating Essbase(BSO and ASO apps)from Server 7 to Server 9

I was able to copy application one is BSO another one is Aso
Both APPS ARE CLEARED IN BATCH FILE.
Budget data excel and flat files is loaded to BSO, calcualation for current year data is done the some for budget files loaded and then calcs are executed.
Then the data for curent year is extracted from bso
then this data all such previus yr and prev exports are loaded to ASO
Then agg is enabled in ASo
All this is done using a batch which call s 10 maxl and which in turn load data and run staggered calcs.
But the issues is Data is not matching after perform these steps in Server 9 at many intersections
Every artifact/var are copied, batch logs are success but still data does not match vs Server 7.
I believe some extra data is generated by Creteblockoneq, createnonmissblock and other calc functions.
I tried copy/Migrate/Manual copy but nothing worked.
Data analysis shows atleast some extra recored are generated after calc in export file
Help needed?

Hi
Thanks for the reply.
There are no rejects.
I am exporting level 0 data and loaading it to ASO.
And, the issue includes both points-
1)Extra data points coming in
2)Some intersections data is missing
It is like 80% data is matching
It seems some essbase Calcs calculation way is modified although not sure.

Essbase not calculating number after 10 digits

This is on version 11.1.2.1, Essbase BSO cube.
In Essbase after data being loaded whatever the number larger than 99,999,999.99, the system starts dropping digits and rounding. In other words, it seems like Essbase wants to store a maximum of 10 digits, so we start having problems with numbers that have 11 or more digits. see below for example.
Data Loaded Data in Essbase
Account 1 83,613,9500.13 83,613,9500.1
Account 2 634,269,675.79 634,269,675.7
And obviously total is wrong, for above 2 number total should be 1,470,409,175.92 but it is showing 1,470,409,175.80 as it is not considering last 3 & 9 and its stopping at 10 digits.
Please let me know if I have to make any changes or I am missing anything.

Give this a try. Make a copy of your outline. Then, lock & load the 2 values in question. Don't run any calculations. Export the entire database to a file. Finally, open the exported file in a text editor and find your values. This should ease your mind concerning what Essbase can store.
BTW, I entered your values into sample/basic without issue.
Dave

Execute Calculation for ASO

Hi,
I am trying to convert BSO calc script to ASO calc script using "Execute Calculation" function in maxl. But getting some errors.
here is one of the example of calc script.
FIX (Actual, "Curr Assig", "Any Product")
Sales=0;
ENDFIX
execute calculation on database 'App'.'Db' with
local script_file "\Oracle\Middleware\user_projects\epmsystem1\EssbaseServer\essbaseserver1\app\App\Db\ASOFILE1.txt"
POV "Crossjoin({[Actual],[Curr Assig]},Crossjoin({[Any Product]}))"
SOURCEREGION "{[Sales]}" ;
here ASOFILE.txt has equation [Sales] := 0;
BUt when I ran it. It give me an following error.
"Statement executed with warnings.
Syntax error in input MDX query on line 1 at token ')'
Custom Calculation terminated with Essbase error 1260052 in POV"
Can anyone suggest me something?
Thanks,

Try changing your POV to:
POV "CROSSJOIN(CROSSJOIN({[Actual]},{[Curr Assig]}),{[Any Product]})"

Conditions Need to decided for ASO or BSO cube?

Hi
Could you please tell me on what conditions or business needs we need to decided whether we need to build an ASO or BSO cube?,
which dimension needs to be Label only or Stored or Accounts or Multiple Hierarchy Enabled property?
Which needs to be Dense & which needs to be Sparse if it is BSO cube?
Could you please let me with an example with above question that would be helpfull.
Thanks,
Raj

For dense data sets and Analytic databases ( databases with complex calculations ) and read/write databases we will go for BSO.
In BSO we can load high and apply the pushdown calculations.
For large dimensionality and sparse data sets and for read only database we will go for ASO.
In ASO we can load at leaf level only.

Essbase ASO Calculation Issue

Hi All
I am writing a calculation for a client to copy one version to another version for an Essbase ASO application.
It seems to work correctly when my POV is set on a smaller datapoints. Hower it seem to have issues when fixed on larger datapoints.
The calculations is pretty simple
[ActualFinal] := [ActualWorking];
I tried creating and running the calculation both using MaxL and Calculation Manager. However the same issue seem to occur.
I first thought it might have been an implied share issue, but further investigation, it doesn't seem to be the issue as I can get the data copied using a smaller POV.
The client is on version 11.1.2.3 of Essbase.
Any one have any thoughts of what may be causing this?
Thanks
Jimmy

I had this issue in 11.1.2.1. Never tried on the later versions
FYI - Have a look at this post (http://www.network54.com/Forum/58296/thread/1359579119/MDX+Query+-+Error+127001)
Below is an excert from the post by Joe Watkins
Joe Watkins
167.107.191.217
ASO Performance
No score for this post
February 11 2013, 1:18 PM
Here are the current limitations as I see them when trying to go ASO only:
- These scripts are not as fast as calc scripts
- performance is worse when users are on the system
- Cannot run these types of calcs when loads are taking place
- need to watch for incremental slices
- Users cannot natively execute these types of scripts
- These scripts can be very fussy to get working
- When I ran the exact same scripts (per my examples) as 'Calculation' versus 'Allocation' the 'Calculation' would skip random cells which was really weird and impossible to fix which is why I switched to using 'Allocation'
In my mind the technology is not mature enough at the moment to get rid of BSO but its getting better..
Amarnath
ORACLE | Essbase

Maximum number of members in a dimension (BSO)

we are designing a new planning application and the requirement for one of the dimensions may force us to have a large number of members. I needed a ballpark figrue on what the maximum number of members should be in planning for it to work in an acceptable manner (aggregate times, run time calculations etc) ... the number we are looking at is over 30,000 members and another 15,000 shared members 10-11 levels deep. If any one has experience with such large dimension, can you shed some light on how long the aggregation times would take and if we use it in form, how best to agg the RTPs for that dimension? thank you in advance.

Check out below posts:
For facts:
Members in Essbase
Maximum members in a Dimension
For limits:
Maximum members for a Dimension in a BSO cube
Cheers..!!

Export - import between ASO and BSO cubes of different structure

Hi everybody!
I have a 'large' ASO cube with information for a period of several years.
I need to be able to load a smaller slice (e.g. one quarter) from the 'large' cube into a BSO cube with a different (simpler) structure , perform calculations and then load the updated data back to the 'large' ASO cube.
What's the best way to approach this (import - export)?
Thanks in advance,
Alex

Hi GlennS,
Hello and thank you again for the help.
I'm running version 9.3.1
The ASO cube has 12 dimensions plus 8 attribute dimensions.
The BSO cube - 8 dimensions plus 2 attribute dimensions.
Data size:
The ASO cube is about 1 GB, about 16 M input level cells. Only about 10 % of it will be extracted and loaded into the BSO cube.
The BSO cube is ~ 300 MB fully calculated. 300,000 existing blocks
I prefer not to load the BSO cube from the same source as because ASO cube contains not only the source data, but also modifications - for example - allocations etc. I would like to keep these modifications and to be able to load (modified) data to BSO, make additional modifications and then 'save' the modified data back to the ASO.
How should I approach loading data back to the ASO? I will need to 'replace' a slice of ASO cube - delete the 'old version' cells and load new version from the BSO cube.
Thanks,
Alex

BSO Calculation

Similar Messages

Maybe you are looking for