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

KB19643: Are report statistics logged for a report/document job that is executing when the MicroStrategy Intelligence Server shuts down?


Community Admin

• Strategy


Job statistics are not logged for those jobs that are executing at the time of the Strategy Intelligence Server shutdown. This behavior is the same for a manual shutdown or for an unexpected shutdown (crash).
 
Report/Document job statistics are logged into the IS_REPORT_STATS after the completion of the job. A job completion does not necessarily indicate a successful completion; it just means that a job should complete execution - either successful execution, manual cancellation of job, or job erroring out.
 
Consider that a report, Report A, is executing on the Strategy Intelligence Server. If the server is shutdown by the Administrator before the report completes execution, then there is no record in the IS_REPORT_STATS table corresponding to Report A's execution at that time. The result is the same even if the server shuts down unexpectedly.
 
If the report completes successfully or if it errors out because of some reason or if the user cancels the job, there is a record of that execution in the IS_REPORT_STATS table.
 
As seen in the example data below, the report starts execution at 9:42:19, and finishes execution at 9:53:31 (execution finish timestamp = 'requestrectime' + execfinishtime). However, this record for execution is written into the Statistics table only at 9:53:33 i.e. after completion of the execution, as indicated by the timestamp value in the RECORDTIME column.
 

ka04W000000OgYCQA0_0EM440000002BEg.jpeg

Comment

0 comments

Details

Knowledge Article

Published:

June 14, 2017

Last Updated:

June 14, 2017