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

KB235985: “We could not obtain the data from the database connection or warehouse table is changed” error occurs when editing a freeform SQL cube in MicroStrategy 2021.


Community Admin

• Strategy


The error impacts Freeform SQL cubes in MicroStrategy 2021 after importing them from web. As a result, a developer may need to access the SQL used to create the cube but cannot because the cube can no longer be edited. This document explains a cause of the error message that is yielded and a potential solution on how to resolve it.

SYMPTOM:
When attempting to edit a freeform SQL in Strategy Developer or Web the following error may occur: 

ka0PW0000000zwLYAQ_0EM440000002C7b.jpeg


We could not obtain the data because the database connection or warehouse table is changed. Encountered error: Execute Query failed. Error Type: Odbc error. Odbc operation attempted: SQLExecDirect. [][Strategy][ODBC PostgreSQL Wire Protocol driver][PostgreSQL] ERROR:column "" does not exist

 
CAUSE:
Typically, the "We could not obtain the data because the database connection or warehouse table is changed" error is suppressed when there is an issue with either the database connection or there is an alteration made to the table being sourced. However, when another error occurs, such as a missing column error, the above error will be unsuppressed and thrown in conjunction with the second error describing the actual problem occurring.  In the instance above, the following refers to the actual error: 

Odbc error. Odbc operation attempted: SQLExecDirect. [][Strategy][ODBC PostgreSQL Wire Protocol driver][PostgreSQL] ERROR:column "" does not exist

In one scenario seen by Support, this issue was caused by a modification of one of the columns that was referenced in the initial creation of the cube. Any change made to the column, would yield this error when attempting to publish or modify the cube. Consequently, the change made in the database results in a cube in an inconsistent state that cannot be modified or published.
 
ACTION:
Contact the database administrator to see what changes have been made in the database to the column(s) that have been referenced in the cube. 
 


Comment

0 comments

Details

Knowledge Article

Published:

April 19, 2017

Last Updated:

February 27, 2024