Line graph displays the error, 'Query Execution Failed ! :Ambiguous column name 'DATE_KEY'. Why?
This error occurs if the column name is not defined properly. Illustration: --------------- The 'orderByDes' attribute - "DATE_KEY" might not be enclosed within '#' i.e. It should be defined as '#DATE_KEY#' For all the Dimension levels (For e.g. DATE_KEY) where orderByDes is defined, it should be defined either as: a) "#DATE_KEY#" OR b) "DIM_DATE.DATE_KEY"
Related Articles
KPI log shows the error 'java.lang.Exception: Query Execution Failed ! :Ambiguous column name'. Why?
KPI query returns ambiguos column error, when a particular measure is present in both the Aggregate table (Example, AGG_WLY_STR_DEPT_Details) and DIM table (example, DIM_STORE). You have to change the column name in any one of the table, for the KPI ...
When drilled down from 'Quarter' to 'Month', KPI shows the error - 'java.lang.Exception: Query Execution Failed ! :Invalid column name #DATE_KEY#'. Why?
It happens when the 'OrderByDes' column for MONTH and WEEK levels of TIME dimension is specified as 'OrderByDes="#DATE_KEY#", in the dbmodel.xml file. Modify that to 'OrderByDes="DATE_KEY". Note: This is advanced configuration and affect whole ...
The KPI doesnot execute and throws the error - 'java.lang.Exception: Query Execution Failed ! :Ambiguous column name' in the log
If a particular measure is present in both Aggregate table(E.g. AGG_WLY_STR_DEPT_Details) as well as DIM table (E.g. DIM_STORE), then the KPI query returns ambiguous column error. In such cases, change the column name either in DIM table or in the ...
The KPI doesnot execute when drilled-down from 'Quarter' to 'Month'. It throws the error - 'java.lang.Exception: Query Execution Failed! : Invalid column name '#DATE_KEY#' in the log. How can the issue be solved?
If the 'orderByDes' column for MONTH and WEEK level in TIME Dimension in 'dbmodel.xml' file is specified as 'orderByDes="#DATE_KEY#" then, the KPI will fail. In such cases, ensure that the 'orderByDes' column of the individual levels are specified as ...
The KPI does not execute and throws the error - 'java.lang.Exception: Query Execution Failed! : Ambiguous column name' in the log. How can the issue be solved?
If a particular measure is present in Aggregate table (E.g. AGG_WLY_STR_DEPT_Details) as well as DIM table (E.g. DIM_STORE), then the KPI query returns ambiguous column error. In such cases, change the column name either in DIM table or in the ...