last updated: 2026-09-22
The following article focuses on a general system health check for an SAP HANA database using an SAP GUI connection.
Why was this blog post created?
There are generally applicable steps that can be used when examining a system or addressing a potential performance issue. These general steps and examinations provide a good starting point and a comprehensive overview of the system’s status.
- 2222220 – FAQ: SAP HANA DBACOCKPIT
What are these steps (in order)?
Investigation steps:
- ST04 > Current Status > Overview, reference: SAP GUI – Transaction Code – ST04
- ST04 > Current Status > Alerts
- ST04 > Performance > Load History , reference: SAP GUI – Transaction Code – DBACOCKPIT (Load History)
- ST04 > Diagnostics > SQL Editor, report: 2903141 – Best practice configuration checks for SAP HANA
- ST04 > Diagnostics > SQL Editor, report: 3284834 – SQL Statement Collection: “HANA_Configuration_Minichecks” report for SAP HANA
- ST04 > Diagnostics > SQL Editor, report: 3330262 – SQL Statement Collection: “HANA_Memory_Overview” report for SAP HANA
- ST04 > Diagnostics > SQL Editor, report: 3293572 – SQL Statement Collection: “HANA_Disks_Overview” report for SAP HANA
Other articles
📚 List of My Articles (Laszlo_Thoma) – SAP HANA
Do you have further questions?
Please do not hesitate to contact me if you have question or observation regarding the article.
Q&A link for SAP HANA: https://answers.sap.com/tags/73554900100700000996
Contribution
If you find any missing information belongs to the topic, please let me know. I am happy to add the new content. My intention is to maintain the content continuously to keep the info up-to-date.
Release Information
| Release Date | Description |
| 2026.09.22 | First/initial Release of the SAP Blog Post documentation (Technical Article). |
#SAPCHANNEL