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

KB39379: "DB Instance object cannot be deleted because Catalog object in project depends on it." error message appears when deleting a Database Instance object after unchecking it from the project in MicroStrategy Developer


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This knowledge base article describes an issue where "DB Instance object cannot be deleted because Catalog object in project depends on it." error message appears when deleting a Database Instance object after unchecking it from the project in in MicroStrategy Developer.

SYMPTOM:
After un-checking a Database Instance object from Project Configuration and trying to delete it from the database instance monitor, users receive the below error in Strategy Developer: 

ka02R000000kVEBQA2_0EM440000002DK6.jpeg


Sample Code/Error:

DB Instance object cannot be deleted because Catalog object in project depends on it.

 

 
CAUSE:
Although the database instance was unchecked from the project it has still some dependency to the Warehouse catalog.
This can be verified by running the following SQL in DB Query tool directly against the metadata to see which object depends on this database instance: 
 

SELECT  a11.object_id,   
 a11.object_name,   
 a11.object_type,   
 a11.project_id,   
 a11.parent_id     
FROM  DSSMDOBJINFO a11,   
DSSMDOBJDEPN a12   
WHERE a11.object_id = a12.object_id   
AND a12.DEPN_OBJID = `<ID>`

 
This SQL has been written to be applicable to Microsoft SQL Server use, and should work for most relational databases.  Contact your DBA if you need this SQL to be modified for other Database Platforms. 
 
ACTION:
Users can use the option "delete unused managed objects" to clean up the dependency and delete the database instance or in some cases, check the database instance in project configuration, and then un-check the database instance to resolve the issue.
 
 
 

This issue has been logged as Scopus ID: 550914 and KB39379


Comment

0 comments

Details

Knowledge Article

Published:

June 9, 2017

Last Updated:

September 13, 2018