Error: 1Error when Creating Analytics View – Measure cannot be identified

When creating an analytic view in HANA, I received the following error, which prevented from
saving the view.

Even with extensive search in SCN, unable to find any hints on the cause of this error, and how
to resolve it.
When creating the analytic view, used a LEFT join in Data Foundation, to retrieve the data ,
which could then be fed to Logical View (as shown in the screen shot below).

However, for the Data foundation, there can only be ONE main driving table. The analytic view
can use only FACTS from this driving table. In this situation, NOT specified this driving
table/central table, which can be used in Analytic view for FACTS/MEASURES.
Solution: To resolve the error, select the central table and assign it to Central Entity. You should
now be able to save the analytic view.

On a closing note, when there is a situation where we need measures from multiple FACT tables,
we will have to create separate Analytic Views – one for each measure – and then combine them
in a Calculation View.
Error: 2Error during Activating HANA Studio Analytic View

Tried to activate a new created analytic view. An error message was pop up as attached screen
shot.

Solution:

Simply run GRANT SELECT on <schema_name>.<table_name> to _sys_repo WITH GRANT

OPTION;

For all your base tables that you want to build models on.
Error 3: SAP HANA: Select * From Analytic View works sometimes and otherwise
throws the error "Cannot execute select * on olap cube" ?
 

Select <column-list> , sum <measure> from AnalyticView

Group by <column-list>
The above statement it works.
But if find that for some cases in Analytic view even SELECT * From Analytic View is
working. And for some other cases it throws the error message "Cannot execute select * on olap
cube"
Want to check with you guys if any of you have faced a similar situation? And if anybody knows
the reasoning for this?

Solution: Usually the reason you can do SELECT * against an Analytic View is because it's
actually a Calculation View. 
Check to see if you have calculated columns. If so, for all intents and purposes it's an Analytic
View - but at a lower level HANA does some trickery where it creates a CalcView "wrapper" to
handle the calculations, gives this the same name as the Analytic View, and then also maintains
the base analytic view with the same name as original plus a suffix of "/olap".
There are more nuances, such as when calculations are handled in OLAP vs CalcEngine, etc...
But that's the basic idea.
Error: 4error while activating analytical view
Creating analytical view on the top of lips,likp and three master data (attribute views) while
activation it is giving following error
Internal deployment of object failed; Repository: Encountered an error in repository runtime
extension; Internal Error: exception 1: no.8104014
(mdx/metadata/deployment/join/JoinManager.cpp:710)n    Logical join points to different
physical tables in cube.nexception throw location:n 1: 0x00007ff05922efd3 in
what could be the error in this case.

Solution: check that there are more than one columns from the attribute view are joined and
these columns from the attribute view come from different physical tables in the attribute view.
Error: 5Error while activating Analytic View
Having a problem with attribute view
after created its activated well but it doesn’t preview data
it gives me this error:

Solution: It seems that your attribute view is not yet activated ( hence the grey diamond in your
attribute view icon).Please activate the view
Error: 6Error in Decision Table using Analytic View

Trying to create a Decision table on an Analytic view. As per the HANA document guidelines,
the Analytic view has one Calc. Attribute, the Action is created from a Parameter and Conditions
are created from Analytic View column.
But no luck while activationg the Decision Table and facing below errors. Message:
XML Parser error:; Decision Table XML Parser Error: attribute 'ce-id-refs' of element 'av' is
missing
XML Parser error:; Decision Table XML Parser Error: actionVal is NULL
XML Parser error: ; Decision Table XML Parser Error: actionNode is NULL
HANA Version is 1.0 SPS8 Rev80
Thanks in advance,

Solution: resolved this issue by performing following steps.

1. Exported Decision Table Data into XL.
2. Removed the action variable.
3. Added again the same parameters as Action
4. Imported XL file of Decision table.
5. Validated and Activated. It worked
Error: 7Analytic view - Error 
Generated Data Preview Query:
SELECT TOP 1000 sum("FORCURAM") AS "FORCURAM", "MANDT", "FORCURKEY",
"AGENCYNUM" FROM "_SYS_BIC"."sflight/AN_AGENCY_ID_REV" GROUP BY
"MANDT", "FORCURKEY", "AGENCYNUM"
Error:
Error Executing Query: SAP DBTech JDBC: [391] (at 97): invalidated view:
sflight/AN_AGENCY_ID_REV: line 1 col 98 (at pos 97)
I activate and validate my view but then get the same error.

Solution: Whenever you are trying to work with any schema, please ensure that that schema
should added in the _sys_repo under authorization with select and execute makers as Yes, you
can choose other option also like insert, update delete as per requirement.
Error: 8Error in report built on top of Analytical view
Trying to build a report in WebI based on an Analytical view created in HANA studio. The
universe (UNX) is developed in  IDT. While trying to run the report or do a data preview in IDT
on the data foundation layer, getting the following error message:
" feature not supported: not allowed over OLAP VIEW : search without aggregation or grouping
by expression other than view column"

Solution: The query generate by your report doesn't have any group by clause.
In this case you cannot run that query on top of Analytical View. The error message actually is
providing you this infoirmation.
So Always when you have an Analytical View you must run queries which are doing
aggregation.
Queries like:
select * from "Analytical view " are not supported.
But you can run queries like:
select column1, column2, column3...column n from "Analytcal View" group by column1,
column2, column3...column n.
In your case the query generate by webi I think it is something like:
select column1, column2, column3...column n from "Analytcal View" without any group by
clause and this represent amn issue.
Error: 9Urgent: hit error when activate the analytic views.
In my project, there are 7 attribute views and 4 analytic views, and all the attribute views can be
activated, but 3/4 analytic views cannot be activated, the reason is “No Visible Attribute Found
in Analytic View”.
steps are as below, 
0, Grant the select permission on “SYSTEM”, “TEST_SHARED”, “TEST_SHOWMORE” to
_SYS_REPO
1, Import the table.       -- OK
2, Import the model.        -- OK
3, Activate the attribute view.      -- OK
4, Activate the analytic view.       -- ERROR
My HANA version is 53, and HANA Studio version is 1.0.56.
It’s strange that there’s just one analytic view can be activated successfully.
 
You can find the table and model that I imported in the attached. 
1. The following image shows 3/4 analytic views can not be activated.
2. The following image shows error when activate,

3, Open one of the analytic view that cannot activate,

4, Open the only one analytic view that can activate,

Solution: Is the server-side validation going through? If yes and you are running out of options,
then try to turn off the client side validation through Window->Preferences->Modeler-
>Validation Rules.
Or you can try activating by By-Passing the Validation (right click on the Analytical View &
activate)
Error: 10Redeploy Analytic view Error on BW DSO
We have a Analytic view on BW DSO. We deleted few fields and new fields to this DSO.
Trying to Redeploy this Analytic view in HANA Studio it throws an error. I can re-import with
overwrite option but that will remove any changes that were previously made in the Data
foundation layer (for e.g.attributes turned in Data foundation layer Customer City etc),
Restricted/Calculated columns defined in Star Join layer.
We are on HANA SP8 Rev.81 what is the best way to get BW Back end changes into Analytic
views
Error message:
Message :
                Activation ID: 2027 (Repository: Activation failed for at least one object;At least one
runtime reported an error during revalidation. Please see CheckResults for details)
Message :
                Internal deployment of object failed;Repository: Encountered an error in repository
runtime extension;Internal Error:Deploy Analytic View:
invalid column name: USERNAME: line 1 col 9816 (at pos 9815) at
ptime/query/checker/check_cube.cc:330(46)
SQL: column store error: <?xml version="1.0" encoding="utf-8"?><createCubeResult
version="1.0"><status><message>Error during executing SQL
statement</message><errorCode>2116</errorCode></status><details><errors><detail><elemen
t>

Solution: You change the DSO itself then re-importing is the only safe way to be in sync with
the structures in BW.
On the other hand, re-import will drop/create in order to recreate the information model on
HANA (Analytic View in your case). Changing the model generated by BW directly could lead
to modeling losses (you change the model directly and later on you recreate it from BW...
changes you applied are now gone).
Better approach would be to leave the Analytic Views the way they are (as much as possible)
and wrap them with Graphical Calculation View, thus leaving the modeling enrichment part
outside the generated Analytic View itself. 
Later on, if for any reason you change the DSO Structure, then you'll have better chances to
activate your models without issues. I say better chances because you might have a field
removed from the DSO and the same filed used in a calculation column on your Graphical Calc
View. In that case, of course, you'll face activaion issues.
Error: 11Analytical view error : name clash among columns
  While creating analytical view, in data foundation I am using certain tables like EKPO, EKKO
and in logical view joining this data foundation to my attribute views.
Here the Problem is require MEINS field from EKPO table which is in my data foundation ,
Also in one my attribute views which using in analytical view has field MEINS as well.
When I try to activate the model it gives error  saying "Unique Constraint Check"  Duplicate
Entities MEINS Detected. Please resolve the name clash among columns.
I thought of renaming the columns but not able to find that option so at the moment I removed
MEINS from data foundation, keeping the MEIN from attribute view only but I am confused if
data will be correct.
Is there some way I can have both the same name fields of data foundation and Attribute view to
see both have same data or not.
Solution: You can rename the column in data foundation of the analytic view. Add the column
to output. Then click on the column in output and edit the Name of the column from its
properties.
Error: 12Error while data previewing analytic view having BLOB data type field
Getting the below error when trying to data preview a analytic view. The field
"VALUE_DIAGRAM_IMAGE" Has BLOB data type.
Error Executing Query: SAP DBTech JDBC: [264] (at 377): invalid data type:
"VALUE_DIAGRAM_IMAGE" LOB type in group by clause: line 1 col 378 (at pos 377)
Can we use BLOB datatype fields in analytical view as I have read that LOB datatypes cannot be
used in a group by statement. 
I am using version 25 and sp03 as SAP Hana version.

Solution: LOB types cannot be used in DISTINCT, group by or order by. So it cannot be used
within an analytic view (at least as of now) as the queries on analytic views will need you to
have the LOB fields in the group by clause as well.
You can add it in an attribute view and it should work except in cases of data preview-ing (only
because the query during a data preview uses SELECT DISTINCT and this isn't supported by
LOB types) and using it with an analytic view because of the reasons mentioned above. However
if you were select statements on the attribute view, it will work.