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 Aggregate table. Then the KPI should work fine.
Related Articles
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 ...
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 ...
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 ...
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 ...
Why is the KPI not displaying results and throws an exception - 'java.lang.Exception: Query Execution Failed! : A column has been specified more than once in the order by list. Columns in the order by list must be unique'?
In case of a crosstab KPI, the KPI fails to execute when the crosstab ORDER BY clause contains two columns. Therefore the columns in the ORDER BY must be unique. Also, please note that the measure ORDER BY should be specified as None as it will not ...