when we run calc scripts again only dirty blocks are calculated it is known as Intelligent Calculation.īy default Intelligent calculation is ON. Subsequently, when we change value in any block the block is marked as Dirty block. When we run Calc all/Calc dim Essbase would calculate and mark all blocks as Clean blocks. Whenever the Block is created for the 1st time Essbase would treat it as Dirty Block. We need to restart the server to make the changes in calculator cache after setting it in config file.

We set cache value for calculator cache in Essbase.cfg file. The optimum size of the calculator cache depends on the amount of memory the system has available.Set cache High |Low |Off -–à command used in calc scripts to set the cache. This cache setting not used if Essbase is set to use buffered I/O.ĭata Cache: Min – 3072 KB (3145728 bytes) Default – 3072 KB (3145728 bytes) Opt -0.125 * the value of data file cache size.Ĭalculator Cache: Min – 4 bytes Max: 200,000,000 bytes Default – 200,000 bytes Opt -The best size for the calculator cache depends on the number and density of the sparse dimensions in your outline. Min – Direct I/O: 10240 KB(10485760 bytes) Default -Direct I/O: 32768 KB(33554432 bytes) Opt -Combined size of all essn.pag files, if possible otherwise as large as possible. Do not set this cache size higher than the total index size, as no performance improvement results. Index Cache: Min -1024 KB (1048576 bytes) Default – Buffered I/O : 1024 KB (1048576 bytes) Direct I/O : 10240 KB (10485760 bytes) Opt -Combined size of all essn.ind files, if possible as large as possible otherwise. When we moved, deleted, or added a member to a sparse dimension then sparse restructure would happen. If we want to moved, delete and add a member to a dense dimension then dense Restructure would happen. When we rename any member or add Alias to any member or member formula changes then outline Restructure would happen. Guide to Oracle Cloud: 5 Steps to Ensure a Successful Move to the CloudĮxplore key considerations, integrating the cloud with legacy applications and challenges of current cloud implementations.

DB name Force Restructure Ģ)Add and Delete One Dummy Member in the Dense Dimension to force a full restructure. There are Three ways of doing Defragmentation.Įxport Data of the application in to text file, then clear data and reload the data using text file without using Rules file.Īlter Database App name. If the average clustering ratio is less than 1, then the cube is fragmented which degrades the performance of the cube. We can check whether the cube is fragmented or not by seeing its Average Clustering Ratio in the properties. Using hourglass model improves the calculation Performance of the cube.įragmentation is caused by any of the following activities: We have to build the Outline should be in a way that dimensions are placed in the following orderġ) Dimension tagged as an Account Dimension TypeĢ)Dimension tagged as a Time Dimension Type Good application design and proper system administration include some of following items.ĭesign the Outline using Hour Glass Model: Essbasse system and application performance tuning are very important tasks for a successful implementation of Essbase or Hyperion Planning.

Time space compression as an hourglass