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

KB489530: "The object shown in the following hierarchy no longer exists in schema: -Table (). -DBMSObject is not found in DFCSchema during DFC conversion" error occurs when updating a project schema


Vanessa Munoz

Cloud Support Expert I • MicroStrategy


This article describes an issue that occurs during schema update for a project, due to a metadata inconsistency.

Symptom:

When performing a project schema update, the following error appears:

ka0PW0000007IGLYA2_0EMPW00000VwAzd.jpeg

 

Error(s) occurred while loading schema: [DFCSCHEMA] Population Exception: The object shown in the hierarchy no longer exists in schema: -Table (). -DBMSObject is not found in DFCSchema during DFC conversion <DB Instance name> <DB Instance ID>

The Database Instance the error message refers to can be edited successfully and schema can be updated in other projects where that Database Instance is used. 

Cause:

This is a metadata inconsistency that occurs because the Database Instance mentioned in the screenshot is not selected as an available database instance for the project, under Project Configuration.

Action: 

Follow the below steps in order to resolve this issue:

  1. Connect to the project in Strategy Developer.
  2. Right mouse click on the project name and select Project Configuration. 
  3. Go under Database instances > SQL Data warehouse and check the checkbox corresponding to the database instance name from the error message.

Contact Strategy Cloud Support for further assistance. In order to track down the cause of the inconsistency, customers encountering this issue should make note of Schema-related changes, Object Migrations, or error messages prior to experiencing the problem. Change Journaling, if it has been enabled, can help in preserving this information.


Comment

0 comments

Details

Knowledge Article

Published:

October 31, 2025

Last Updated:

October 31, 2025