EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB35875: "Exception of Type System.OutOfMemoryException was thrown" is shown in MicroStrategy trying to save a MDX Cube


Community Admin

• Strategy


This article notes an error that can be seen with MDX cubes containing 1000s of hierarchies

SYMPTOM:
When users are trying to import a MDX cube using Strategy, they are able to select the cube from the “Available Cubes” list and move it to the “Selected Cubes” list without issues.
 

ka04W000000OagHQAS_0EM440000002Dnu.png

 
Once the MDX Cube is shown on the right-hand side of the screen, users can proceed to “Save and Close” the MDX Cube Catalog. A new question will be shown in order to know if the user wants to review the mappings for that cube.

ka04W000000OagHQAS_0EM440000002Dnw.png

 
As soon as the users select “No” in order to proceed with the cube saving process, they get the error shown below:

ka04W000000OagHQAS_0EM440000002Dnq.png

 
CAUSE:
This issue can be faced if the user has too many hierarchies created under a particular element in the cube. This error has been received when users have more than 1,000 hierarchies. In this case Strategy is getting out of memory trying to import and create thousands of hierarchies at the same time.
 
ACTION:
This problem is faced when user's MDX cube source design involves a lot of hierarchies created under a specific dimension. Strategy can handle a very high number of hierarchies, however this kind of design (thousands of hierarchies) is oriented to support transactional systems rather that OLAP structures. Users should be able to compact the structure (maybe by deleting redundant hierarchies or by modifying the underlying design) in order to support OLAP processing.
  
KB35875


Comment

0 comments

Details

Knowledge Article

Published:

May 30, 2017

Last Updated:

December 30, 2018