Hi Patrick,
Analytical views make use of olap engine and olap engine is specifically designed to execute star schemas. basic master data and fact table join is nothing but a star schema, and olap engine processes them faster than calculation engine. I conducted a poc and analytical view was faster than calculation view. This is not applicable when your view has complex calculations. In that regard prefer calculation view.
Regards,
Safiyu
Seems this file does not exist any more. Please access to the ide and check if this file exists or not.
You can also via query: select * from "_SYS_REPO"."ACTIVE_OBJECT" where object_name = 'adminData';
Hello Raj,
If this is the case, then open a incident to SAP AGS. Let SAP Support to analyze the case.
Regards,
Ning Tong
Dear SAP HANA experts, and HANA Gurues!
SQL Plan Cache
2040002 - Size recommendation for the HANA SQL Plan Cache
Current default plan cache size is 2GB. However, it should be adjusted based on system's characteristic or workload.
plan cache size is 2GB!!!
I didn't find any detailed information or SAP Notes or blogs about:
What does it mean SQL Plan in HANA? What is it at low level and how it works?
What's information stores in sql plan cache? Is it only metadata, or mixed (metadata and data).
Maybe you know?
The SQL plan cache is used to keep already parsed query statements (the statements, not the data that the statements work on!) in memory and available for quick re-use.
That's a technique that every major and most nice DB products employ and the way this works is pretty similar to all of them.
For SAP HANA you can find information e.g. here
The SAP notes recommendation basically is about optimizing the size of the memory area available for SQL statement re-use.
As different application types have different degrees of re-use for single statements (e.g. transaction oriented applications often repeat the same queries over and over while analytical applications tend to have a higher share of unique queries) different recommendations can be made to get more overall performance from a SAP HANA system.
- Lars
2GB of memory for storing only already parsed query statements?
Statements or execution plans?
Technically, the plan cache stores compiled execution plans of SQL statements for reuse, which gives a performance advantage over recompilation at each invocation. For monitoring reasons, the plan cache keeps statistics about each plan, for instance number of executions, min/max/total/average runtime, and lock/wait statistics.
The SQL plan cache contains load key figures, information about the parsed statement and some details about the actual execution plan. Unfortunately the execution plan details aren't exposed in the related view M_SQL_PLAN_CACHE, so they are only available internally.
In order to judge if the SQL cache should be resized or if some other problem exists, I would recommend you to have a look at SAP Note 2124112.
Dear Experts,
While checking the system health check with the commend "saphana-support-ibm.sh -s" on my HANA box system.
How can we enable and disable JDBC trace globally .
Please be more specific.
What do you want to trace? What means "globally" here?
Generally, JDBC is a client API, so tracing usually depends on the application/the process, the user account and the machine where the tracing should be set up.
- Lars
What seems to be the issue?
What is the question you are asking?
One of the user is complaining that whenever he logs into SAP HANA studio there is a message that JDBC trace is active globally.
I want to disable the same.
Please check the documentation on JDBC tracing Trace a JDBC Connection on the Command Line - SAP HANA Developer Guide for SAP HANA Studio - SAP Library
Basically, you need to logon with the user account for which the message occurs, and disable the trace by calling the JDBC driver jar with the TRACE OFF option.
- Lars
Dear All,
I have created the DB view using sql statement on HANA system.
I would like to give the access to it to external system i.e. ECC.
So when I am trying to call this view using ECC tcode, It is trying to access via secondary db connection.
Then it is giving an issue, saying you have no access privileges.
How to provide an access to view from external system.
Regards,
Jo
Please let me know the difference among these 2 certifications and which one is more beneficial to gain. As per the course content both seems to be following HA200.
Please suggest
Hello Lars,
Thank you for posting such an answer.
However I feel a question is a question, doesnt matter if its a general question or a specific question.
To some who are highly experienced, it may seem a general question, but for guys like me, its another question.
I did my own research and am still doing so (with replying to your post 
) , but I would be really grateful if I could get some help.
Atleast thats what we all come here for
Regards,
Vinay
Hi Razal,
Here is the explanation for the option INITIALIZE LOG AREA during the PITR as per SAP Documentation:
1. It is used for specific cases if normal recovery procedure to the most recent point in time fails
2. With this option no log entries from the log area are initialized
3. It is a MUST to specify this option
a. when the log area is unusable
b. if you recover the Database to a different system
In my case we have always done a refresh using the Data backup and we do not use this option to IINITIALIZE LOG AREA
We have done PITR by using the Data and Log backups for the same HANA Database without using this option and it had worked for us. If it had failed we could have used this option
I think it is absolutely right that you need to use this option in your case due to a PITR being used for a refresh from one SID to another(point 3.b. above)
Hope this answers your question
Dear BR, Bojan,
Thanks a lot!
Best
Shu
You're right that everyone around here has different levels of experience and that the forums are there in the first place to ask questions and discuss ideas.
To make this more doable for everybody participating in it - and that includes the people that try to answer questions - the The SCN Rules of Engagement set the expectation that everybody does her or his part of research and shows that.
General questions as the one you posted often don't actually address general topics but actually have very specific questions carried within that should be answered.
Just as you did not want to know whether or not there is an option to find the data access time, but instead you really want get an explanation how to do that.
Searching SCN for "HANA" + "Performance analysis" would probably be a good start to find information on that topic. Such a search will also bring up the performance analysis and tuning guide for SAP HANA which is part of the official documentation.
And that's what I proposed that you may do: search SCN, read the documentation.
There's already a lot of information available.
I am pretty sure that after digesting this information first your question will not be answered - but you maybe will come back with different (more specific) questions.
And that's the kind of question that I'd say can be really interesting.
That's where I am likely to engage and look into it.
That's what I come here for.
The interesting questions.
- Lars
Hi,
I need your help, I created calculation view based on three tables, Region, Product, and Sales. when I try to run Data preview, I am getting error: SAP DBTech JDBC: [258]: insufficient privilege: Not authorized. Although I used all necessary steps successfully executed: GRANT SELECT ON SCHEMA "NEO_NEO_xxxxxxxxxSLXI8UGAURxxx" TO _SYS_REPO WITH GRANT OPTION; and
GRANT SELECT ON SCHEMA "NEO_xxxxxxxxxSLXI8UGAURxxx" TO P99329992;
I am very grateful if you solved this.
