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

KB228389: "Fail to join to ancestor or descendent" error occurs when running a report in MicroStrategy Analytics Enterprise 9.4.1


Community Admin

• Strategy


This issue has been classified as a defect by MicroStrategy. The impact is limited to MicroStrategy 9.x reports using a specific schema design. No workaround is available at this time. A solution/code fix for this issue is not available in the current releases but is being reviewed for a future MicroStrategy release.

SUMMARY
This issue has been classified as a defect by Strategy. The impact is limited to Strategy 9.x reports using a specific schema design. No workaround is available at this time. A solution/code fix for this issue is not available in the current releases but is being reviewed for a future Strategy release.
SYMPTOM
When running a report in Strategy Analytics Enterprise 9.4.1, the following error is seen:

ka04W000000OhFZQA0_0EM440000002C83.jpeg

 


Status: Initialization Failed
Error: SQLEngine got an Exception from DFC: [DFCENGINE] Engine Logic: Fail to join to ancestor or descendent.

CAUSE
This is a known issue in Strategy 9.x.
This issue occurs only with a specific schema design; W shape schema design is one of the specific designs that may expose the issue.
 
For example, the attribute relationship is as follows:
 

ka04W000000OhFZQA0_0EM440000002C87.jpeg

A,B,C,D,E are all attributes, A is parent of B, C is parent of B, C is parent if D, E is parent of D.
 
Attribute group (B, C, E) can join together because C can join with B and E separately. After C and B are joined, the key for the joined table is B, which has no relationship with E. And an exception is thrown out.
ACTION
Strategy will continue to investigate and post updates as soon as they are available. A solution/code fix for this issue is not available in the current releases but is being reviewed for a future Strategy release.
The Strategy Internal Reference Number for the issue discussed in this knowledge base article is 632206.


Comment

0 comments

Details

Knowledge Article

Published:

May 30, 2017

Last Updated:

May 30, 2017