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

KB47473: A custom time window dataload does not migrate data from the statistics tables to the Enterprise Manager warehouse tables in MicroStrategy Enterprise Manager


Community Admin

• Strategy


A custom time window dataload does not migrate data from the statistics tables to the Enterprise Manager warehouse tables in MicroStrategy Enterprise Manager 9.x.

SYMPTOM:
 
A custom time window dataload does not migrate data from the statistics tables to the Enterprise Manager warehouse tables in Strategy Enterprise Manager 9.x. Additionally, the time period covered by the custom time window is when statistics failed to insert into the database, but were instead written to the StatisticsFailedSQL.log files. After manually executing the the SQL statements from the StatisticsFailedSQL.log files (through DB Query Tool or other SQL tools), a dataload for that same period will not migrate the data into the Enterprise Manager warehouse tables.
 
CAUSE:
 
The time period specified in the custom time window dataload is based on the "RECORDTIME" column of the statistics tables. This column keeps track of the time when the data was inserted into the statistics tables. In other words, this is the time when data was inserted, either by the Intelligence Server at the time of job execution or at a later time when inserted manually by the user, is when the dataload will cover for the migration period.
 
ACTION:
 
The custom time window period should cover the time period when the statistics data was manually inserted into the tables by the user, instead of the period when the statistics logging by the Intelligence Server failed (resulting in the StatisticsFailedSQL.log files).
 


Comment

0 comments

Details

Knowledge Article

Published:

April 1, 2017

Last Updated:

April 1, 2017