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

KB441282: Data Import 10.11 Max Quota being hit when actual usage is below Quota


Andrew Geyster

Principal Product Specialist • MicroStrategy


In MicroStrategy Secure Enterprise 10.11 a Data Import request may be rejected for exceeding a User's quota even though the actual usage is below the quota.

SYMPTOM
When attempting to load a Data Import Intelligent Cube, the following error may be seen within the User interface:

ka02R000000kUxwQAE_0EM44000000WW9r.png

This can be seen even when the actual total memory consumption of the Intelligent Cubes loaded for this Project is below the configured Governing Setting. For example, the above Data Import fails even though the actual utilization of the Intelligent Cubes are 5388mb out of 12000mb, and the Data Import Manager from Strategy Web lists 11998mb out of 12000mb.

ka02R000000kUxwQAE_0EM44000000WWA6.png

After closing out the entire User Session from the Intelligence Server and logging back in the Data Import Manager from Strategy Web lists the correct value for the amount of memory consumed.

ka02R000000kUxwQAE_0EM44000000WWA1.png

When tracking the governing setting limitations, what is seen is that the governing setting does not get reduced by the full amount when an Intelligent Cube is unloaded from memory, even though all of the consumed memory is freed from the Intelligence Server. This difference is roughly equal to the size of the Intelligent Cube footprint in-memory versus the size of the compressed disk cache.
CAUSE
This is a known issue with Data Import functionality in version 10.11. The underlying cause comes from a miscalculated governing setting which incorrectly prevents new Data Import Intelligent Cubes. The issue does exist specifically for the governing setting tracker, so the memory consumption of the Intelligence Server itself is not impacted by this known issue.
ACTION
This issue will be fixed with Strategy 10.11 Critical Update 1. Please apply the Critical Software Update in order to take advantage of the fix.
WORKAROUND
The governing setting tracker which handles the amount of memory consumed per Project is reset on an Intelligence Server restart. If the issue is being encountered and the Critical Software Update cannot be immediately applied the governing setting can be increased to a higher value, or the Intelligence Server can be restarted for temporary relief
 
KB441282


Comment

0 comments

Details

Knowledge Article

Published:

June 29, 2018

Last Updated:

December 31, 2018