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

KB439512: "We could not obtain the data because the database connection or warehouse table has changed. Encountered error: JdbcResultWrapper...Disconnected." error occurs when publishing a Data Import FFSQL Cube


Chris Robinson

Principal Product Specialist • Strategy


When attempting to publish a Data Import FFSQL Cube, the cube fails to publish displaying error message, "We could not obtain the data because the database connection or warehouse table has changed. Encountered error: JdbcResultWrapper...Disconnected."

SUMMARY:
This technical article explains an issue when attempting to publish a Data Import FFSQLCube using a DSN-less connection, the cube fails to publish displaying error message:


We could not obtain the data because the database connection or warehouse table has changed. Encountered error: JdbcResultWrapper::Fetch failed. Disconnected. Error type: Unknown exception

Currently this issue is tied specifically to using Amazon Athena with a DSN-less connection in Strategy Web 10.8.
SYMPTOM:
This issue only presents itself using FFSQL and is tied to number rows returned by the query. Executing the SQL in the 'Type a Query' window will work successfully. Executing the SQL outside of Strategy will work successfully. Lastly, limiting the amount of rows returned will allow the actual cube to publish successfully. A null pointer exception is thrown in the DSSErrors.log file,and the error is suspected to be tied to number of rows trying to be returned or a specific row being returned. Strategy has not been able to reproduce this issue internally. 
CAUSE:
This is an identified issue when attempting to publish a FFSQL Cube connected to Amazon Athena with a DSN-less connection.
ACTION:
Create a DSN connection instead of DSN-less and the cube will publish with no issues. The 'Find and Replace' tool in Developer can be used to replace cubes where necessary.
Please contact Strategy Technical Support for more information on this issue.
KB439512


Comment

0 comments

Details

Knowledge Article

Published:

January 22, 2018

Last Updated:

January 4, 2019