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

KB429013: "The object shown in the following hierarchy no longer exists in schema: -Relation-TableObject is not found in DFCSchema during DFC conversion" error message seen when updating schema in 3 tier in MicroStrategy 2021


Stefan Zepeda

Salesforce Solutions Architect • Strategy


SUMMARY
This issue has been classified as a default behavior by Strategy. The impact is limited to cases when logical tables are inadvertently deleted from the schema collection. A solution for this issue is present and provided in this document.
  
SYMPTOM
In Strategy 2021, after migrating objects to a higher environment using Object Manager packages the following error is seen when attempting to update the schema with a 3-tier connection.
 
2015-06-02 00:05:19.007-06:00 [HOST:XX.XX.XX.XX][PID:7930][THR:2725673280][Engine][Error][0x80042202] Error(s) occurred while loading schema: DSSSQLEngine: Schema loading error: [DFCSCHEMA] Population Exception: The object shown in the following hierarchy no longer exists in schema: -Relation-TableObject is not found in DFCSchema during DFC conversion.( MTRL_COLR_FCT )
 
Updating the schema via 2-tier connection is successful without issue
 
 
STEPS TO REPRODUCE
The following steps are general steps based on the Strategy Tutorial project in which the error has been seen: 
 

  1. Create a package in Object Manager with Category attribute and Revenue metric.
  2. Migrate attribute to a separate 3-tier environment.
  3. Attempt to update schema in 3-tier and notice error
  4. Connect to the same MD in 2-tier, update schema and notice schema updates without issue.

CAUSE
This error is caused by a missing logical table in the schema table collection (MTRL_COLR_FCT). The reason for this table deletion is unknown but without it all 3-tier schema updates will fail.
ACTION
To restore the missing logical table run the schema verifications tests with the latest version of ScanMD as seen below:

ka0PW0000000hTBYAY_0EM440000002X0D.jpeg

When running the test the user should see entries similar to the following:
[2015/06/03 23:09:30.27][Error Found][Strategy Tutorial][Schema Collection Verification] [Missing References: Schema collection does not contain all needed objects in its Table collection][2015/06/03 23:09:45.48][Process Started] [Strategy Tutorial][Rebuild Schema Collection.] [Fix started] [Fixing] [Missing References: Schema collection does not contain all needed objects in its Table collection]
[2015/06/03 23:09:58.01][Process Finished][Strategy Tutorial][Rebuild Schema Collection.] [Fix finished][Success][Missing References: Schema collection does not contain all needed objects in its Table collection]


Comment

0 comments

Details

Knowledge Article

Published:

December 26, 2018

Last Updated:

February 13, 2024