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

KB485542: Dozens of Intelligent Cube caches are invisible in one Intelligence Server among the six nodes cluster in MicroStrategy 2021 GA


Danfeng Zhan

Principal Product Specialist • Strategy


This issue has been classified as a none defect by MicroStrategy. Dozens of Intelligent Cube caches are invisible in one Intelligence Server among the six nodes cluster in MicroStrategy 2021 GA, is due to Intelligence Server starting up before mount of the cube shared location.

SYMPTOM:
In Strategy 2021 GA six nodes cluster Linux environment, dozens of Intelligent Cube caches are missing from one Intelligence Server’s cube monitor.
Following error is noticed in DSSErrors.log for the missing displayed Intelligent Cube:
[COM][Error][0x80064618][UID:D52F7DED11EB918AB9BA0080EFD59824][SID:CA3D92A3A9EB53083E7C6E28B4C6CF42][OID:0E030BD942F21C7A4D22988ABAFC756D][CDSSCubeManager.cpp:2040] Intelligent Cube (xxxxxxx) for locale English (United States) is not published. 
Centralized cube cache sharing is used in this cluster. 
Refer to online help for setup centralized cube cache sharing on Linux:
Configuring Caches in a Cluster
There were yum update installed, and all the Intelligence Server machines were rebooted. It is found the Intelligence Server node has incorrect mounting configuration; thus, a separate restart of Intelligence Server is performed after corrected the mounting.
CAUSE:
 
Some Intelligent Cubes are published locally before correctly mount the share folder in the problematic node, thus some Intelligent Cubes are in local folder and others in shared folder.
ACTION:
 
Restart all the Intelligence Server nodes in sequence.
NOTE: The cube cache folders should be mounted and accessible before starting Intelligence Server. otherwise, there will be inconsistent since the index are loaded at the Intelligence Server startup.
Further Readings:
KB30309: How to use the Cache Parser tool to read cache information from information and lookup files and user inbox messages.
 


Comment

0 comments

Details

Knowledge Article

Published:

June 14, 2022

Last Updated:

August 11, 2022