You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

CLEARDATA increased .pag files after lame block creation

edited Aug 2, 2018 2:36AM in Essbase 10 comments

Summary

CLEARDATA increased .pag files after lame block creation

Content

Hello,

Assuming it was a lame move to create as many blocks as possible for a single month of FY17, we have experienced something I wasn't expecting.

This is a hugely sparse application. Each block has some 250000 cells and there are as many as 815 million potential blocks —, considering 7 years, it's about 117 million blocks a year

The app typically had a index of about 150 MB and the .pag file was about 450 MB. The creation of blocks did not increase the size of  the .pag or the .ind files.

Valid data is on Jan; the block creation was performed against Dec.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!