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

KB18668: In MicroStrategy Enterprise Manager 9.x, the 'RP Exec Duration hh:mm:ss' metric reports values greater than the maximum 'Report execution time' governing limit


Community Admin

• Strategy


SYMPTOM:
When executing a Strategy Enterprise Manager 9.x report to determine report execution times, using the 'Report' attribute and the 'RP Exec Duration hh:mm:ss' metric, the values reported appear to exceed the "Maximum Report Execution" governing limit.
 
The example below shows that the governing limit has been set to 26600 seconds, which is 7 hours, 23 minutes and 20 seconds.
 

ka04W000000OeV3QAK_0EM440000002BJA.jpeg

 
The sample report below shows that the 'SQL Execution' step for the report 'REPORT 1' took 13 hours, 17 minutes and 36 seconds; far longer than the expected governer set above.
 

ka04W000000OeV3QAK_0EM440000002BJ4.jpeg

 
CAUSE:
In Strategy Enterprise Manager 9.x, report level statistics are stored per report execution (read job). In fact, the misleading numbers above are an aggregation of all of the executions, jobs, of the report.
 
ACTION:
To see the correct report statistics, the 'Report Job' attribute needs to be included on the report template. Including the "Report Job" level will ensure that the metrics do not aggregate the data.
 

ka04W000000OeV3QAK_0EM440000002BJN.jpeg

 
**As displayed in the screenshot above, none of the executions of the report exceed the governor. The screenshot just displays two of the executions as an example.
 


Comment

0 comments

Details

Knowledge Article

Published:

June 9, 2017

Last Updated:

June 9, 2017