SAP HANA Memory Status (part of BIAnalyst Technical content HANA)
We at BIAnalyst have created some interesting views to enable system administrators to better monitor their HANA databases. They are Calculation Views based on SAP HANA system views and can provide vital insights to activity in your HANA system.
As Calculation Views they can be consumed in SAP Analysis for MS-Office in EXCEL and/or PowerPoint for easy analysis. in regular Excel Display, or alternatively via PowerPoint. For example an overview of your systems memory saturation, can give you insights into the necessity to manually create a LOAD / UNLOAD Concept to save HANA memory and to shift tables from HOT to WARM HANA memory (additional to SAP HANA dynamic tiering).
Display of Memory occupation in HANA (CV_HANA_MEMORY_PROB)
Today we would like to introduce you to the Hot Memory overview (CV_BIA_HANA_MEMORY_PROB).
Using an AfO workbook you will be prompted for your analysis timeframe- Select FROM — TO dates and execute the query.
The example shows a monthly overview, with a peak of memory used that is not normal for daily average memory consumption of HOT HANA memory.
A further drill down to evaluate which table / schema caused that peak. As shown in next figure, reveals that the SAP table RSMONMESS caused the memory peak on January 22nd.
The insights provided by this and other views created by our Team of HANA experts from our project experience and hands on analysis can help you to detect abnormal behavior e.g. after system or DB patches. The information available and leveraged to you through calculation views can unveil unwanted tables, such as PSA based data, not included in dynamic tiering or early unload settings.
You can manually also spot large objects not wanted in HOT memory, or causing memory bottlenecks, using the Non-Active Data Monitor in the SAP HANA Database in the RSA1 – Administrator Workbench:
Administration -> Monitors -> Active/Non-Active
You will find further tips in SAP Service Marketplace Note:
1776749 – Activating the Handling of Non-Active Data During Main Memory Bottlenecks