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

KB15323: Objects exist in the metadata but are not migrated to the lookup tables of the Enterprise Manager warehouse during the data migration of MicroStrategy Enterprise Manager 9.x


Community Admin

• Strategy


SYMPTOM:
Users might notice that certain objects, e.g. metrics, reports, attributes, etc., are missing in the lookup tables of the Enterprise Manager warehouse of Strategy Enterprise Manager 9.x
 
For example, users might have created a report in the Strategy Enterprise Manager project with just the attribute 'Metric' in order to compile a list of all metrics that exist in a certain project. Upon comparing the result with the metrics that exist in the monitored project, they notice that certain metrics are missing in the Strategy Enterprise Manager report.
 
By querying the corresponding Strategy Enterprise Manager lookup table, in this case IS_MET, directly, they confirm that the missing objects don't exist in that lookup table.
 
Re-running the Strategy Enterprise Manager data migration process does not correct the result.
 
CAUSE:
By default, during the lookup migration stage of the data migration process, Strategy Enterprise Manager 9.x only checks for objects that have been created or modified between the previous and the current data load. If newly created or modified objects are found, these objects are then migrated to or updated in the respective Strategy Enterprise Manager warehouse table.
 
However, there is one scenario where objects might exist in the monitored project but do not get transferred to the Strategy Enterprise Manager warehouse lookup tables. This scenario involves using Strategy Object Manager (or Project Merge).
 
The following an example of what might have happened:

  • The customer has a production project and a development project.
  • The Strategy Enterprise Manager data migration for the production project is scheduled to run every day at 5 AM.
  • Developers create new objects, e.g. metrics, in the development project on Tuesday.
  • The migration of these objects from development to production via Project Merge or Strategy Object Manager takes place on the Friday. The objects created on Tuesday have since then not been modified (modification timestamp is set to Tuesday).

The new objects will be missing in the Enterprise Manager lookup tables if the objects retain the original modification timestamp (Tuesday) during the object migration. Since Strategy Enterprise Manager will only migrate objects where the modification timestamp is greater than the timestamp of the last Enterprise Manager data load, these objects that were created will not be picked up by the Strategy Enterprise Manager data load process during the scheduled data load on Saturday at 5 AM (only objects with a modification timestamp between Friday 5 AM and Saturday 5 AM will be migrated over).
 
 
ACTION:
There is an option "Preserve object modification timestamp during migration." in Object Manager 9.x. To avoid the objects being missing in the Enterprise Manager lookup tables, make sure that this option is unchecked.

ka04W000000OeE9QAK_0EM440000002BXK.jpeg

 
 
 


Comment

0 comments

Details

Knowledge Article

Published:

June 12, 2017

Last Updated:

June 12, 2017