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

KB424009: The "Dimension xxx unknown at com.microstrategy.Database.JCO.JCOStatement3" error occurs when executing a report based on SAP BW that contains an attribute element prompt in MicroStrategy 10.4 Hotfix 2


Franklin Silva

Senior Cloud Support Engineer II • MicroStrategy


This Knowledge Base article describes a non-MicroStrategy issue that occurs when executing a report based on SAP BW that contains an attribute element prompt in MicroStrategy Web or Developer. Also, it is included the steps to avoid - resolve this issue.

Description:

In Strategy Web or Developer 10.4 Hotfix 2, the following error occurs when running a report based on SAP BW that contains an attribute element prompt:
 

Strategy Web


 

ka04W000001IqRJQA0_0EM440000002Ntw.jpeg

(Message not found in user history list. It may have been deleted fromother session already. Please refresh your history list.
QueryEngine encountered error: ExecQuery failed. 
MDX Execution failed. Error type: JCO layer error. JCOStatement.executeQuery failed.java.lang.Exception: [JCO] Error during MDX Query Execution [JCO] Error during Bapi Execution: Dimension xxxxx unknown at com.Strategy.Database.JCO.JCOStatement3.executeQuery (Unknown Source).
Connection String: N/A:..Error in Process method of Component: QueryEngineServer, Project xxxxx, Job xxxxx, Error Code=-2147212544.
 

Strategy Developer 

 
Report: xxxxx
Job: xxxxx
Status: Execution failed
Error: Unable to resolve prompt
Starting Time: xx:xx:xx
QueryEngine encountered error: ExecQuery failed. MDX Execution failed.
Error type: JCO layer error. JCOStatement.executeQuery failed.java.lang.Exception: [JCO] Error during MDX Query Execution [JCO] Error during Bapi Execution: Dimension xxxxx unknown at com.Strategy.Database.JCO.JCOStatement3.executeQuery
(Unknown Source). Connection String: N/A:..Error in Process method of Component: QueryEngineServer, Project xxxxx, Job xxxxx, Error Code=-2147212544.
After enabling the Strategy Diagnostics and Performance tools > Database Classes SQL Trace option to collect the MDX statement submitted against SAP BW as described in the Knowledge Base article KB14038: Diagnostic logs to enable when troubleshooting issues with access to MDX data sources such as SAP BW, Microsoft Analysis Services or Hyperion Essbase in MicroStrategy 9.x-10.x , the following MDX statement was collected:
Error type: JCO layer error. JCOStatement.executeQuery failed. java.lang.Exception: [JCO] Error during MDX Query Execution [JCO] Error during Bapi Execution: Dimension XXXXX unknown at com.Strategy.Database.JCO.JCOStatement3.executeQuery(Unknown Source). Connection String: N/A;.
Connection String: N/A;. SQL Statement:
with set [Count_set] as '{[xxxxx].[LEVEL01].members}'
member [Measures].[Element_Browse_Count] as 'Count({[Count_set]}, INCLUDEEMPTY)'
select {[Measures].[Element_Browse_Count]} on columns
from [xxxxx/xxxxx]
 

Why is this happening?As described in the Knowledge Base article KB18724: Reports based on SAP BW query cubes with variables produce errors when loading prompts in Strategy 8.1.2 since Strategy 8.1.2, a MDX Statement is submitted against Hyperion to obtain a count of the attribute elements, what can be observed in the MDX statement above. It occurs due to large element sets are fetched incrementally and it requires a count of attribute elements to obtain this information. Therefore, the object referenced in the query, in this case, it is a Query Characteristics must be part of the Query template; otherwise, the execution to count attribute elements will fail. Solution:All characteristics that are used in SAP variables should be present in the rows, columns or "Free Characteristics" sections of the cube definition. For further information, refer to the cited Knowledge Base article.KB424009


Comment

0 comments

Details

Knowledge Article

Published:

May 29, 2017

Last Updated:

September 13, 2019