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

KB36700: "Unable to retrieve previous migration window" error occurs during a data load with MicroStrategy Enterprise Manager.


Community Admin

• Strategy


"Unable to retrieve previous migration window" error occurs during a data load with MicroStrategy Enterprise Manager.

SYMPTOM:
When running a Strategy Enterprise Manager 9.x and 10.x data load the following error occurs:


Unable to retrieve previous migration window.

 
When looking at the EM_IS_LAST_UPDATE table using the DB Query Tool, or another similar tool, the IS_STATUS column has more than 1 row with a value of zero, 0.
 
CAUSE:
Due to either some failed previous migrations, or some inconsistencies while a data load was occuring, the IS_STATUS column of the EM_IS_LAST_UPDATE table has more than 2 rows with a value of zero, 0. This column indicates a successful or a failed load, one or zero respectively. By design, the first row in the EM_IS_LAST_UPDATE table should have zero value for the IS_STATUS column. If any other row has an IS_STATUS = 0, this issue can occur.
 
For other related issues please refer to the following Strategy Knowledge Base technical notes:

  • KB8192: 'More than one failed migration windows were found. This process cannot continue' error message appears when performing a data load in MicroStrategy Enterprise Manager 9.x

 
ACTION:
To resolve this isuse, the following SQL will need to be run manually in DB Query tool to see how many rows are affected:
 


SELECT * from EM_IS_LAST_UPDATE
WHERE IS_STATUS = 0;

 
Only one row should appear, if more than one row appears, the additional steps will need to be taken to update all rows except the very first row, which by design should have an IS_STATUS value of 0. Before taking any further steps, ensure that a database back up of the tables exist in case a rollback is required. Contact the database administrator to have the IS_STATUS column changed for all returned rows, except the very first row of the table.
 
Enterprise Manager Warehouse and Statistics Modification WARNING:
Manually editing values in the Strategy Enterprise Manager warehouse and statistics tables incorrectly may cause serious, project-wide problems that may make your Enterprise Manager project unusable. Since these are user-initiated changes, they are not covered by any Strategy warranty. Users are strongly encouraged to backup the Strategy Enterprise Manager warehouse and statistics prior to any alteration.
 
Limitation of Liability: Strategy shall have no liability to licensee for any damages of any kind, including, but not limited to, liability for direct, indirect, special, incidental or consequential, damages (which shall include, but not be limited to, loss of data or information, loss of revenue or anticipated profits or lost business).
 
 
 


Comment

0 comments

Details

Knowledge Article

Published:

June 6, 2017

Last Updated:

June 23, 2017