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

KB263615: Unable to use "Common Trace" log under the "Dimensional Storage" component on Unix environments in MicroStrategy 10 Secure Enterprise Platform


Community Admin

• Strategy


Unable to use "Common Trace" log under the "Dimensional Storage" component on Unix environments in MicroStrategy 10 Secure Enterprise Platform

SUMMARY
This technical document covers a known issue with the Dimensional Storage > Common Trace log, which does not work for Unix environments in Strategy 10 Secure Enterprise Platform.
.
 
SYMPTOM
In Strategy 10 Secure Enterprise Platform, when running the Strategy Intelligence Server on a Unix environment, the "Common Trace" log under the "Dimensional Storage" component can be enabled but does not log any information to the log file.
 
When using a Windows box to host the Strategy Intelligence Server, the log works as expected with contents similar to the following:
 


2015-09-28 18:55:41.669 [HOST:HOSTX][PID:8376][THR:4156][Dimensional Storage][Common Trace] --- Show Cube Info ---
--- Show Cube Basic Info ---
Cube ID  : 25BD4F6C4B1772DAEC5D2AA326AF63AD
Cube Name: Cust_Item_Rev.xlsx
AE Cube Size    = 19841514 Bytes, 19376 KB
Attribute Size  = 164891 Bytes, 161 KB
Relation Size  = 0 Bytes, 0 KB
Metric Size     = 2895306 Bytes, 2827 KB
Index Pool Size(containing element block and index space) = 16781313 Bytes, 16388 KB
Element Block Size = 11776000 Bytes, 11500 KB
Index Space Size = 3619349 Bytes, 3534 KB
Index Key Size = 0 Bytes, 0 KB
Search Tree Size = 0 Bytes, 0 KB
Row Map Size = 0 Bytes, 0 KB
OriTable = 4 Bytes, 0 KB
--- Show Cube Attribute Info ---
Attribute Index,Attribute Name,Partition Index,Cardinality,Number of Forms
0,Item,0,95,1,(UTF8Char )
0,Item,1,79,1,(UTF8Char )
0,Item,2,95,1,(UTF8Char )
0,Item,3,95,1,(UTF8Char )
1,CustomerName,-1,2270,1,(UTF8Char )
2,CustomerLast,-1,7081,1,(UTF8Char )
--- Total Attribute Count = 3 ---
--- Show Cube Relation Info ---
Relation Index,Relationship,Parent,Child,Partition Index,Relation Rows,Parent Cardinality,Child Cardinality
--- Total Relation Count = 0 ---
--- Show Cube Metrics Info ---
Metric Index,Metric Name,Partition,Data Rows,Distinct Data Rows,Data Type,Orig Data Type,Converted,Compressed,Potential Saving (bytes)
0,Revenue,0,187346,0,Integer,Integer,No,N/A,--
0,Revenue,1,149371,0,Integer,Integer,No,N/A,--
0,Revenue,2,197568,0,Integer,Integer,No,N/A,--
0,Revenue,3,189420,0,Integer,Integer,No,N/A,--
1,Row Count - Cust_Item_Rev.xlsx,0,187346,1,Integer,Integer,No,Yes,--
1,Row Count - Cust_Item_Rev.xlsx,1,149371,1,Integer,Integer,No,Yes,--
1,Row Count - Cust_Item_Rev.xlsx,2,197568,1,Integer,Integer,No,Yes,--
1,Row Count - Cust_Item_Rev.xlsx,3,189420,1,Integer,Integer,No,Yes,--
--- Total Metric Count = 2 ---
--- Show Cube Index Pools Info ---
Index Pool,Partition,Index,contained Attributes,Attribute ElementBlocks Number,rows,IndexPool Size(KB),ElementBlock Size(KB)
0,0,0,Item|CustomerName|CustomerLast,94|187346|187346,187346,3936,2976
0,1,0,Item|CustomerName|CustomerLast,78|149371|149371,149371,3156,2380
0,2,0,Item|CustomerName|CustomerLast,94|197568|197568,197568,4148,3136
0,3,0,Item|CustomerName|CustomerLast,94|189420|189420,189420,3980,3008
--- IndexRowMaps --
Index Pool,Partition,Base Index,Target Index,Type,Size(KB)
--- Total Index Pools Count = 1 ---

 
 
CAUSE
This is a known issue with Strategy 10 Secure Enterprise Platform that affects only Unix environments.
 
ACTION
This issue has been fixed in Strategy 10.1 Secure Enterprise Platform.  Please upgrade to take advantage of the fix.
 
WORKAROUND
Point a dummy Strategy Intelligence Server hosted on a Windows machine to the required Metadata and generate the Dimensional Storage > Common Trace log for the required objects.


Comment

0 comments

Details

Knowledge Article

Published:

June 12, 2017

Last Updated:

June 12, 2017