This blog will track the changes for SAP HANA dump analyzer.
You can get the latest SAP HANA dump analyzer here. The latest HANA dump analyzer is on version 1.0.201910151100, You can query your SAP HANA dump analyzer version via the following comma...
This is the third post from the Autonomous Self-Analysis System blog series. Read "Autonomous Self-Analysis System II" to set up the autonomous self-analysis system this post builds upon. This blog aims to enhance the autonomous self-analysis solutio...
This is the second post from the Autonomous Self-Analysis System blog series.
"Autonomous Self-Analysis System I" is the first one from the blog series which explains an autonomous self-analysis solution to automate email notification with issu...
Working in an SAP HANA mission critical data center, the DBA colleagues are usually monitoring multiple SAP HANA systems. It has been quite challenging for them to react quickly and properly when the productive HANA system encounters critical issues....
When we troubleshoot SAP HANA issues based on its runtime dumps, we are often faced with this question: was the HANA system completely stuck, or was it still processing queries, requests, etc.? Answering this question based on a single HANA runtime d...
Hi Nandam,
Just let you know, the latest version HANADumpAnalyzer 1.0.202004281800 fixed the bug that the HANA composite OOM dump is not analyzed with error popup message “For input string:”XXgb(XXXXXXb)”.
Kind regards,
Nina
Hi Nandam,
The SAP HANA dump analyzer can analyze HANA runtime dump , it is not able to analyze other traces, e.g. indexserver trace etc.
Kind regards,
Nina
Hi Prabhat,
Sorry for replying you late. the latest version HANADumpAnalyzer 1.0.202004281800 fixed the bug that the HANA composite OOM dump is not analyzed with error popup message “For input string:”XXgb(XXXXXXb)”
Kind regards,
Nina
Hi Nandam,
Thanks for providing feedback. I would assume you've provided a composite OOM dump. This is a known issue that will be fixed in the next release of SAP HANA dump analyzer. As a temporarily workaround, please modify the following line on t...
Hi Aamrin,
In terms of OOM analysis. if a top consumer is the cause, the Top Memory Consumer part will provides details e.g. connection id, SQL user name. If you find the query on the Concurrency Memory Flame, tooltip on the corresponding sql execu...
