BI Blog,  Essbase,  Hyperion EPM

Clear Data in Essbase ASO with MaxL

In 11.1 release Essbase allows 2 kinds of data clearance from an ASO cube:

  • Logical Delete: Essbase automatically creates another slice of data with an exact negative of the actual data in the region. So, when end users query from the region, they would in effect be getting zeroes for all intersecting cells in the region. This is the recommended delete option as it is much faster than Physical Delete.
aso logical delete
Logical Delete: Essbase create a slice with negative values
  • Physical Delete: Essbase deletes the physical cells from the region defined. It is generally slower than logical delete as it has to do I/O to remove the cells physically.
aso physical delete
Physical Delete: Essbase physically delete data

For example, in the ASOSamp->Sample ASO cube for logical delete the January data, open the MaxL editor in Administration console and type:

alter database ASOSamp.Sample clear data in region '{[Jan]}';

To do a physical delete type:

alter database ASOSamp.Sample clear data in region '{[Jan]}' physical;

You can use a MDX member selection to clear data in a specified region, like:

alter database 'ASOsamp'.'Sample' clear data in region '{CrossJoin(CrossJoin([Jan].children,[Age].children),[Stores].children),[Geography]}';

Source: Oraclebizint

 

 

Leave a Reply