Essbase ASO Calculation Issue

Question

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

Answer 1

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