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

KB441370: Execution behavior when enterprise manager dataload time window overlap


Community Admin

• Strategy


This article has been classified as a work by design behavior by MicroStrategy. The impact is limited to MicroStrategy Enterprise manager 10.x product only with data load time window overlap. No specific action need to be taken.

SYMPTOM:
 
 
What happen when previous data load is still running, and next data load custom time window is reached?
 
The next data load will be pending. It will not trigger until the previous data load finish.
 
Take “Daily Data Load at 11 pm” for example. It will be added to the queue until previous data load finish.
 
<log4j:event logger="MAEntMgr" timestamp="1483016400200" level="INFO" thread="Timer-20">
<log4j:message type ="DEFAULT"><![CDATA[Dataload added to the queue Daily Data Load at 11 pm]]></log4j:message>
</log4j:event>
 
<log4j:event logger="MAEntMgr" timestamp="1483016400850" level="INFO" thread="Timer-20">
<log4j:message type ="DEFAULT"><![CDATA[Dataload queue: {5370D946154847A23681163304775635=Daily Data Load at 11 pm}]]></log4j:message>
</log4j:event>
 
 
 
 
Article Reference Number: KB441370


Comment

0 comments

Details

Knowledge Article

Published:

July 10, 2018

Last Updated:

November 9, 2018