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

KB485394: "Cube and Cache Monitoring" Dossier from Platform Analytics project shows incorrect cube number and size in MicroStrategy 2021


Danfeng Zhan

Principal Product Specialist • Strategy


This article outlines PA dossier shows incorrect cube number due to cube telemetry missing USERID in topic Mstr.PlatformAnalytics.IsCubeRepStats get ignored by PA. A solution/code fix for this issue is not available in current releases but is being reviewed for a future MicroStrategy release. Two workarounds are available in current release.

Starting with the release of Strategy ONE (March 2024), dossiers are also known as dashboards.

Symptom


Starting with Strategy 2021 Update 2 "Cube and Cache Monitoring" Dossier from Platform Analytics project shows incorrect cube number and size. 
The dossier shows 4 cubes instances while in workstation there are 6 cubes instance for an intelligent cube as shown below:

ka0PW0000001JhKYAU_0EM4W000004YYBI.jpeg

The missing cube instance GUID could be found in Mstr.PlatformAnalytics.IsCubeRepStats, but not in PA warehouse tables LU_CACHE or fact_latest_cube_cache .

Cause


This is a known issue with Strategy 2021. 
USERID field and value missing at Kafka topic Mstr.PlatformAnalytics.IsCubeRepStats when load cube at the Intelligence Server restarts, topic data is missing USERID field will be ignored by Platform Analytics as USER is the mandatory field, thus not flow into Platform Analytics warehouse. 

Action


Strategy will continue to investigate and post updates as soon as they are available.

Workarounds

Workaround 1:

  1. Disable "Load Intelligent Cubes on startup" from developer -> Intelligent Cubes -> General -> "Load Intelligent Cubes on startup", then cubes won't be loaded when startup, thus no corresponding logs sent to Kafka.
  2. After startup, the cube can be loaded by user manually, or automatically triggered when running subset report/document/dossier based on the corresponding cube.

Workaround 2:

  1. For those cubes missing USERID in topics, manually unload then reload the cube.
  2. USERID will be filled with real user ID, and evenly been consumed by PA consumer, and flow to lu_cache.

Comment

0 comments

Details

Knowledge Article

Published:

March 11, 2022

Last Updated:

March 21, 2024