Compacting ASO Outline – Defragmenting

Why does it grow?

In BSO, defragmenting the cube is actually quite simple. One way is to do a full restructure and the other way is to export, clear all blocks then re-import the data. So you think ASO doesn’t need to defrag since it doesn’t contain any blocks? Too bad, you’re very wrong. ASO fragmentation happens when you add/delete/regroup members or delete/add dimensions. So to make it simple, any meta-data changes will cause fragmentation. In fact, even if you use EPMA or work direct from EAS or Essbase Studio and EVEN OBIEE AGGREGATE PERSISTENCE WIZARD, it will still cause fragmentation.

So how much would it grow?

To be honest, I do not have the algorithms on this. But if you update the cube on a daily basis, I should think it will double the size in a few months time.

What happens if I don’t do anything?

If you don’t do anything to it, and when .otl file grows to over 2gb in size, EAS won’t be able to open the outline. Would users still be able to access it? Yes they would. It’ll still work but it doesn’t really feel safe does it?

What are the solutions?

There are 3 ways to compact the outline which in the end is basically defragmenting the outline, each with pros and cons. They are explained as follows:

Continue reading “Essbase ASO Outline Grows Too Big – Solution to Fragmentation Using Compact”