KB221518: How to activate the Cube Subsetting Instruction (CSI) Log in MicroStrategy 10

• Strategy

This document shows how to enable the CSI (Cube Subsetting Instruction) logging for troubleshooting purposes in MicroStrategy 10.

SUMMARY
This document shows how to enable the CSI (Cube Subsetting Instruction) logging for troubleshooting purposes in Strategy 10.

Steps to activate CSI Log in Windows:

Open the Strategy Diagnostics and Performance Logging Tool
Navigate to the Engine Component with CSI Dispatcher.

Create a new File Log and name it “CSI” (or any other name). Then click "Save".

After saving the log destination, the File Log column should now read as "CSI" for the Engine Component in the CSI Dispatcher, as seen below:

After running a report, document, or dashboard based on an OLAP or PRIME cube, the CSI log file can be found (depending on the selected installation path) at: "C:\Program Files (x86)\Common Files\Strategy\Log"

Steps to activate the CSI Log in Unix/Linux:
Whenever a GUI is available, the same steps used for a Windows environment can be performed. The Strategy Diagnostics utility can be found within the bin folder of the Strategy home folder. However, in case there is no GUI available, the CSI log could also be activated from command line. Additional information on how to activate traces by command line can be found in the following Strategy Knowledge base Document:

KB15868: How to modify diagnostics logging for MicroStrategy components from the command line in Windows and Unix/Linux environments
In order to activate the CSI Log from the command line, the following steps should be followed:
1) Run the mstrctl command to generate the logging destination:


./mstrctl -s IntelligenceServer ssc
<configuration>
<log_destinations>
<log_destination n="CSILog" tp="3" max_size="2048" callstack_message_ids=""/>
</log_destinations>
</configuration>

Note: To terminate the input for the mstrctl command, pressing "Control + D" is required.

2) Confirm the changes made in step 1 were saved successfully by running the following:


mstrctl -s IntelligenceServer gsc

3) Run the mstrctl command to activate the log:


./mstrctl -s IntelligenceServer ssic
<configuration n="CastorServer">
<diagnostics pru="0">
<logger n="Engine">
<dispatcher n="CSI">
<log_destination n="CSILog"/>
</dispatcher>
</logger>
</diagnostics>
</configuration>

Note: To terminate the input for the mstrctl command, pressing "Control + D" is required.

4) Confirm the changes made in step 3 were saved successfully by running the following command:


mstrctl -s IntelligenceServer gsc

Example of the CSI Log:
If a subset report or document based on an Intelligent Cube is run, an example of the CSI generated for that report or document would be as follows:


Tables Accessed:
Table4:Call Center, LOOKUP_TABLE
Table9: Subcategory,Quarter,Year,Region,Call Center,Category,M01, FACT_TABLE


select [Call Center]@[CALL_CTR_ID],
 [Call Center]@[CENTER_NAME],
 [Year]@[YEAR_ID],
 sum([Table9.M01])@{[Call Center],[Year]} as [M01]
from Cube02- Prime Cube by AE
with Table Join Tree:  Table9<[Year]@[YEAR_ID] in (2008.000000)>

Comment

0 comments

Details

Knowledge Article

Published:

April 3, 2017

Last Updated:

April 3, 2017

./mstrctl -s IntelligenceServer ssic <configuration n="CastorServer"> <diagnostics pru="0"> <logger n="Engine"> <dispatcher n="CSI"> <log_destination n="CSILog"/> </dispatcher> </logger> </diagnostics> </configuration>

Tables Accessed: Table4:Call Center, LOOKUP_TABLE Table9: Subcategory,Quarter,Year,Region,Call Center,Category,M01, FACT_TABLE select [Call Center]@[CALL_CTR_ID], [Call Center]@[CENTER_NAME], [Year]@[YEAR_ID], sum([Table9.M01])@{[Call Center],[Year]} as [M01] from Cube02- Prime Cube by AE with Table Join Tree: Table9<[Year]@[YEAR_ID] in (2008.000000)>