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

KB13836: "The definition of object with ID 'XXX' is inconsiste." error message returned when trying to update schema in a project in MicroStrategy Developer


Community Admin

• Strategy


This technical note outlines an issue where users may encounter "The definition of object with ID 'XXX' is inconsiste." when trying to update schema.

SUMMARY
This technical note outlines an issue where users may encounter "The definition of object with ID 'XXX' is inconsiste." when trying to update schema.
 
SYMPTOM
When trying to update the schema, the following error is thrown:


"The definition of object with ID 'XXX' is inconsiste."

The misspelling of the word inconsistent is intentional for purposes of this Knowledge Base article as that is how the error message displays.
Neither MD Doctor nor ScanMD will resolve this issue.
 

CAUSE

This error message is indicative that there are duplicate records in the metadata for one or more of the tables in the metadata repository. Duplicate entries can occur in a database table if the primary key constraints are removed.
There are only two scenarios where Strategy will ever remove primary key constraints from a SQL Server metadata, and that is upon first creating the metadata shell and upgrading the metadata. In both instances, the primary key constraints are immediately recreated.
 

ACTION

To troubleshoot this issue, speak to your DBA to gather more information about when these objects were removed and how, and possibly restore an earlier backup of your metadata when the primary key constraints still existed. At that point, run Project Merge to move over the projects from the metadata exhibiting the error to the working metadata.
If you are unable to obtain a copy of the metadata that has these primary key constraints, contact Strategy Technical Support with a copy of your metadata BEFORE the upgrade was attempted and reference this technical note.
 

DISCLAIMER

Note: Removing the primary key constraints from a Strategy metadata is unsupported and Strategy Technical Support cannot guarantee a proper fix for this issue, even if a backup of the metadata is provided.
KB13836


Comment

0 comments

Details

Knowledge Article

Published:

June 8, 2017

Last Updated:

December 3, 2018