cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Error while activating Calculation View

Former Member
0 Likes
2,344

Hi,

I am trying to activate a very simple calculation view (using sql script) but it is failing with column store error - 34053. I tried different tables and schemas but still get the same error.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

MDXRuntime: Internal deployment of object failed: Internal Error:Deploy Calculation View: SQL: column store error: [34053] failed to save calculation scenario : The following errors occured: Could not create repository entry for scenario (34053)nDetails (Warnings):n- CalculationNode (139206) -> attributes: No attributes found.nnnSet Schema DDL statement: set schema "EFashion"nType DDL: create type "_SYS_BIC"."efashion/CV_SCRIPT/proc/tabletype/VAR_OUT" as table ("ARTICLE_ID" INTEGER, "COLOR_CODE" INTEGER)nProcedure DDL: create procedure "_SYS_BIC"."efashion/CV_SCRIPT/proc" ( OUT var_out "_SYS_BIC"."efashion/CV_SCRIPT/proc/tabletype/VAR_OUT" ) language sqlscript sql security definer reads sql data as  n /********* Begin Procedure Script ************/ n BEGIN n t var_out = SELECT article_id, color_code t          FROM shop_facts;nnEND /********* End Procedure Script ************/nVersion: 62n

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

I'll appreciate any inputs on this.

Regards,

Vimal

View Entire Topic
Former Member
0 Likes

Vimal

Have you been able to resolve this issue with activating calculation views?  I have seen similar behavior on our inhouse copy of SAP HANA.  I have also seen a similar issue when creating a simple proc in sap hana.

Harold

Former Member
0 Likes

Harold,

No, after spending couple of days figuring out what is wrong I ended up re-building AWS box and error went away. I still don't know what was the issue same procs and calculation view works fine in new environment.

-Vimal