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

KB441030: How to enable the Kernel > EM Migration trace that is needed to troubleshoot Enterprise Manager data load issues


Kevin Mohammed

Senior Product Specialist • MicroStrategy


This article describes the process to enable the EM Migration trace for use in troubleshooting Enterprise Manager data load issues. The article describes the process for Linux/Unix and Windows depending on the Operating System of the Intelligence Server.

Steps to enable Kernel > EM Migration on the Strategy Diagnostics and Configuration Tool
The following steps can be used if the Intelligence Server is running on a Windows Operating System or if the Unix/Linux Operating System has access to use a GUI interface.
1. Run the Diagnostics Configuration tool
If on Windows, open the Diagnostics Configuration tool either by accessing shortcut on the Start Menu or running the .exe file (MADPCfg_64). By default, the file is located in the C:\Program Files (x86)\Common Files\Strategy
If on Linux, run the Diagnostics Configuration tool named 'mstrdiag' (located by default at /var/opt/MicroStrategy/bin/)
2. Enable the EM Migration Trace
- Under the Component-> Kernel and Dispatcher -> EM Migration Trace. 
- Choose File Log location by clicking on the cell for File Log. For readability purposes, the recommendation is to have a different log location other than DSSErrors.log.
- Choose <New> to bring up the filename dialog box. Enter filename for log file and file log size. Select this newly created log file under the 'File Log' column. 
- Click the Save button and close out of the Dialog box. Click Save icon (disk icon) and close out of the Diagnostics Configuration tool. The below screenshot shows the EM Migration trace correctly enabled.

ka02R000000kV7oQAE_0EM44000000WTtX.png

3. Restart Intelligence Server (optional)
If the logging does not start automatically, in order for the changes to take effect, the Intelligence Server will need to be restarted. After restarting the Intelligence Server, check the default log location to see the file has been created.
Steps to enable the trace via Command Line on UNIX/Linux Operating Systems
In the absence if a GUI on the Intelligence Server machine, this option can be used. The following KB article gives the instructions for using the mstrctl tool to enable new traces: https://community.Strategy.com/s/article/KB15868-How-to-modify-diagnostics-logging-for-Strategy
For Strategy Intelligence Server Universal installations on Unix/Linux the mstrctl script may be found in the <Strategy Home>/bin folder.
To specifically enable the EM Migration trace, the following commands will need to be run:
1. Create the log destination of the EM migration trace
 


mstrctl -s IntelligenceServer ssc

Paste the below information after running the above command. 

<configuration>
<log_destinations>
<log_destination n="EM Migration Trace" tp="3" max_size="2048" callstack_message_ids=""/>
</log_destinations>
</configuration>

Press Ctrl + D to confirm the change. (Note: Ctrl + D may need to be pressed a 2nd time to confirm the change)
2. Enable the EM Migration trace to log to the above destination

mstrctl -s IntelligenceServer ssic

Paste the below information after running the above command. Ensure the log destination exactly matches the log destination from Step 1.
 

<configuration n="CastorServer">
<diagnostics pru="0">
<logger n="Kernel">
<dispatcher n="EM Migration Trace">
<log_destination n="EM Migration Trace"/>
</dispatcher>
</logger>
</diagnostics>
</configuration>

Press Ctrl + D to confirm the change. (Note: Ctrl + D may need to be pressed a 2nd time to confirm the change)
3. Restart Intelligence Server (optional) 
If the logging does not start automatically, in order for the changes to take effect, the Intelligence Server will need to be restarted. After restarting the Intelligence Server, check the default log location to see the file has been created.
 


Comment

0 comments

Details

Knowledge Article

Published:

June 27, 2018

Last Updated:

November 12, 2018