Skip to main content

Essbase for Beginners: Data Block concepts Part A


An Essbase outline has a number of dimensions.  The number of dimensions can range in quantity and size, but each dimension is identified as a dense or sparse dimension. 

As we understood the concept of Dense and Sparse in our last discussion, let’s begin with the cocept of data blocks now.

To understand this, let’s carry forward our hierarchy of 5 dimensions in a test application in my previous post..

We have 3 dense and 2 sparse dimensions each with 3 stored members.

So let’s begin:


Number of Existing Blocks = (potential number of blocks) * estimated density= 9
Block Size = Dense Stored * Dense Stored * Dense Stored * 8 bytes = 3*3*3 *8 = 216
Potential number of blocks = Sparse Stored * Sparse Stored = 9

If all dimensions are assigned as Dense,

Number of Existing Blocks = (potential number of blocks) * estimated density= 1
Block Size = Dense Stored * Dense Stored * Dense Stored * 8 bytes = 3*3*3*3*3 *8 = 1944
Potential number of blocks = Sparse Stored * Sparse Stored = 1

So if all members are marked as Dense, we just have one data block but the block size is still a multiple of dense member combinations i.e.

So to conclude:

“The potential, expanded (uncompressed) size of each data block that is based on the number of cells in a block and the number of bytes used for each cell.

The number of cells is based on the number of stored members in the dense dimensions. Essbase uses eight bytes to store each intersecting value in a block.”


If all dimensions are assigned as Sparse,

Number of Existing Blocks = potential blks * estimated density= 18
Block Size = Dense Stored * Dense Stored * Dense Stored * 8 bytes = 8 bytes
Potential number of blocks = Sparse Stored * Sparse Stored = 3*3*3*3*3 = 243

Number of Existing Blocks is basically only those sparse dimensions to which we have loaded data, which in our case is “A” “C” “E” each having 2 members so a total of 18 combinations are there which have data at upper level blocks.

So to conclude:

"Essbase creates a data block for each unique combination of sparse standard dimension members (providing that at least one data value exists for the sparse dimension member combination). The data block represents all the dense dimension members for its combination of sparse dimension members. "

So here we understand the difference of Number of Existing Blocks, Block Size and Potential number of Blocks and how a data block is created.

Conclusions:

  1. -          A Data block constitutes of all dense dimensions members for sparse combinations
  2. -          Number of existing data blocks clearly depends on the number of upper level blocks created by sparse entries.
  3. -          Potential number of blocks is the combination of all the sparse dimension stored members.
Hope this post enlightens the newbies on the concepts of Data Blocks a little...

Cheers!
Anvi




Popular posts from this blog

Planning Admin Extension

Planning 11.1.2.3 – Smart View metadata management One of the new features in planning 11.1.2.3 is the ability to manage dimensional metadata through Smart View  • The new Hyperion Planning Admin Extension for Smart View allows Oracle Hyperion Planning administrator users to import and work with metadata in Smart View. • With this extension, Planning administrators can use Oracle Hyperion Smart View for Office applications to perform these tasks: 1. Add, edit and import existing Oracle Hyperion Planning dimensions and members, including moving members and designating members as shared in Smart View 2. Create and refresh cubes • The extension can be downloaded from the Tools menu in workspace. • This will download a file called “ PlanningSVExtension.msi ” which is 1.4mb in size and can be easily installed by running the msi . Once you Install Planning Admin Extension A Smart View Set up Wizard opens up for the extension installation. Click on Next :
Home

Shared Connection and Private Connection

You connect to data sources through shared or private connections. Shared Connections •Shared connections are stored in a central location and are available to multiple users through the Smart View Panel. You cannot add, edit, or rename shared connections, but you can save them as private connections, which you can edit and rename. Private Connections •Private connections are those that you create by saving a shared connection to your local computer or by entering a URL to a provider that is not configured for shared connections. When you create a private connection, it becomes the active connection. Shared Connections : 1. From the Smart View ribbon, click  Panel . 2. From Smart View Home or from the menu displayed when you click the arrow next to Home button, do one of the following: • Click a connection name under  Recently U sed . You can click    to pin items to this list. • Select  Shared Connections  to open the Shared Connections panel, where you s
Home

Import Security : Planning

There will be a huge number of requests to grant or remove security access for users. For one or two changes, it is simple task, click on member and then assign access and grant permission. It becomes tiresome when we need to make changes for large number of members. It involves considerable amount of time. Automating the security changes saves considerable amount of time. The ImportSecurity utility in planning loads access permissions for users or groups from a text file into Planning. Importing access permissions using Import security utility overwrites existing access assignments only for imported members, users, or groups. All other existing access permissions remain intact. The SL_CLEARALL parameter clears all existing access permissions. ImportSecurity utility is located at /Hyperion/Oracle/Middleware/user_projects/epmsystem1/Planning/planning1 on Planning server as shown in the following picture: Steps for importing access permissions: STEP1 :Create a text
Home