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

KB218955: In MicroStrategy Intelligence Server 9.4.x, Statistics are not written to the statistics table IS_SESSION_STATS


Community Admin

• Strategy


This article documents an issue with Statistics logging in MicroStrategy Intelligence Server 9.4.x where no Statistics are written to the table IS_SESSION_STATS. This issue has been classified as a defect and has been fixed in MicroStrategy 10. 

SUMMARY
This article documents an issue with Statistics logging in Strategy Intelligence Server 9.4.x where no Statistics are written to the table IS_SESSION_STATS. This issue has been classified as a defect and has been fixed in Strategy 10. 
 
SYMPTOM
In Strategy Intelligence Server 9.4.x, it is noticed that Statistics are not written to the Statistics table IS_SESSION_STATS. The statistics configuration is verified to be setup correctly and administrators see that all the project level statistics get written correctly to tables such as IS_PROJ_SESS_STATS, IS_REPORT_STATS etc. There are no errors in the DSSErrors.log from the time of Strategy Intelligence Server startup. 
After restarting the Strategy Intelligence Server, the issue goes away on a few occasions. In some cases, a restart also does not help. 
Note: The statistics configuration setup at the server level under the Strategy Intelligence Server configuration is irrelevant to this issue. This is because, the server level statistics initiation is done by the Intelligence Server at startup by going through the available projects on startup and then dynamically selecting the required statistics database instance(s)
 
CAUSE
This issue has been classified as a defect with Strategy Intelligence Server 9.4.x.  
 
ACTION
This issue has been fixed in Strategy Analytical Enterprise 10. Upgrade to this version to take advantage of the fix.
 
WORKAROUND
This issue is not seen if parallel project loading is disabled during Strategy Intelligence Server 9.4.x startup. 
When Strategy Intelligence Server 9.4.x is next restarted after disabling parallel project loading, verify that parallel project loading has been disabled by looking for the following entry in the DSSErrors.logs. The slots listed should be 1 and parallel should be marked to false as shown below.


2014-11-17 16:59:42.139-05:00 Projects Loading Started: projects = 6, parallel = false, slots = 1

 
Windows
To disable parallel project loading, implement the steps below:

  • Stop Strategy Intelligence Server 9.4.x.
  • On the Strategy Intelligence Server 9.4.x machine, access the windows registry and go to the location: HKEY_LOCAL_MACHINE\SOFTWARE\Strategy\DSS Server\Castor
  • Create a new entry (DWORD) called 'NumParallelProjectLoadingThreads' and set the value to 1. A screenshot  of this entry is as shown below.

ka04W000000OhEyQAK_0EM4400000029JV.jpeg

 
UNIX/Linux
To disable parallel project loading, implement the steps below:

  1. Stop Strategy Intelligence Server 9.4.x.
  2. Find the MSIReg.reg file in the home folder of the Strategy installation.
  3. Create a backup of this file before making any changes.
  4. Edit the original MSIReg.reg file and look for the entry:[HKEY_LOCAL_MACHINE\SOFTWARE\Strategy\DSS Server\Castor]
  5. Add the new entry "NumParallelProjectLoadingThreads"=dword:00000001 in the above section. The full section should look as shown below:

    "HomePath"="/home/Strategy/IntelligenceServer"
    "IgnoreAllExceptions"=dword:00000000

    "ProcessAffinity"=""

    "NumParallelProjectLoadingThreads"=dword:00000001

 


Comment

0 comments

Details

Knowledge Article

Published:

May 30, 2017

Last Updated:

May 30, 2017