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

KB442168: Incorrect Processing Time totals displayed in Cube Quick View Job Execution Statistics


Heather Brewster

Senior Manager, Technical Support • MicroStrategy


The issue described in this document has been classified as a defect by MicroStrategy. When viewing the Cube Quick View Job Execution Statistics, it can be seen that the processing totals are incorrect and display an extremely high value. This issue has been addressed in MicroStrategy 11.0 and newer. 

SUMMARY
The issue described in this document has been classified as a defect by Strategy. When viewing the Cube Quick View Job Execution Statistics, it can be seen that the processing totals are incorrect and display an extremely high value. This issue has been addressed in Strategy 11.0 and newer. 
SYMPTOM
After a cube has been published, the Job Execution Statistics found in the Cube Quick View shows incorrect values for the total processing time statistics. 

ka02R000000kYpYQAU_0EM44000000R9Pj.png


Total Data Fetching and Processing Time: 728:59:41.32
Total Other Processing Time: 165:33:23.11
Total Cube Publish Time: 0:00:00.86

It can be seen that the 'Total Data Fetching and Processing Time' and the 'Total Other Processing Time' display very high values while the cube completed publishing in less than 1 minute (See Total Cube Publish Time). 
CAUSE
This display issue is caused by a incorrect calculation of the total processing time statistics for cube publication. 
ACTION
This issue has been addressed in Strategy 11.0 and newer. Upgrade to an applicable version to take advantage of this fix. 
KB442168


Comment

0 comments

Details

Knowledge Article

Published:

October 26, 2018

Last Updated:

October 26, 2018