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

KB20400: "The object is not found in metadata, it may have been deleted" error message appears when performing a data load in MicroStrategy Enterprise Manager


Community Admin

• Strategy


This Knowledge Base article explains why a data load in MicroStrategy Enterprise Manager may fail with an error "The object is not found in metadata, it may have been deleted" and suggests steps to resolve this problem.

Symptom

Strategy Enterprise Manager dataload fails with the following error message:


Object with ID `XXX` and type Y (description of object type) is not found in the metadata. It may have been deleted.

In the above error message, XXX corresponds to the GUID of an object in the metadata and Y corresponds to the OBJECT_TYPE of that metadata object, example object type 3 corresponds to a report definition.
 

Cause

This error can be seen in case of a metadata inconsistency after the deletion of an object from the metadata. In most cases, the above error is encountered during dataload if one of the following additional dataload options is enabled.
 

ka04W000000OcWOQA0_0EM440000002BB0.jpeg

 

  • Update Object Deletions.
  • Repopulate Relate Tables.

NOTE: This error is independent of the actual dataload and is related to the dataload options mentioned above. Hence this error can also be encountered if the above dataload options are run individually (from Tools > Dataload Options) i.e. independent of the dataload process.
 
For more information about the above dataload options, refer to the following Knowledge Base articles:
KB7230: How to update the Object Exist Status indicator in MicroStrategy Enterprise Manager
KB11307: What does the "Repopulate relate tables" option achieve in MicroStrategy Enterprise Manager
The failure point is indicated in the Enterprise Manager Dataload log, mstrmigration.log. Additional information regarding where the enterprise manager dataload is failing can be obtained by tracing the SQL during dataload.
 
KB30594: How to enable the SQL executed during the MicroStrategy Enterprise Manager 9.x data load (ETL) to be logged to the MSTRMigration.log
 

Action

To avoid the failure of dataload, users can run the Enterprise Manager Dataload without enabling the above mentioned additional dataload options.
 
In cases where it is essential to run the additional dataload options, it is necessary to identify and fix the inconsistency in the metadata that is causing the problem. Users can run Scan MD to try to identify and fix the inconsistency. For more information about ScanMD, refer to the following knowledge base document:
 
KB35809: Using ScanMD to fix known logical metadata inconsistencies in the MicroStrategy Product Suite
In cases, where the inconsistency is not resolved by running ScanMD, the metadata causing the error should be provided to Strategy Technical Support for further analysis.
 


Comment

0 comments

Details

Knowledge Article

Published:

April 7, 2017

Last Updated:

December 22, 2022