Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

SAP GUI - Transaction Code - DBACOCKPIT (Load History)

Laszlo_Thoma
Product and Topic Expert
Product and Topic Expert
2 weeks ago

banner - new.png

last updated: 2024-05-05

Introduction
The article explains the SAP GUI – TCODE (Transaction Code): DBACOCKPIT (Load History) usage in details.

SAP GUI

Description
The load history is a collection of key performance indicators (KPIs) related to the SAP HANA hosts and indexserver processes. It allows to understand the SAP HANA activities over time and is one of the key information for SAP HANA performance analysis

Transaction Code:
DBACOCKPIT 

DBA Cockpit menu structure (Navigation Panel):
Performance > Load History

Screen: Load History
Based on the actual problem there is option to choose the KPIs which needs to be investigated. This is a good technique to visualize the issue and as a first step to be familiar with the actual situation.

Inputs:

  1. Time Frame - The exact date and time (period), which needs to be investigated.
  2. KPI - Key performance indicators, such as CPU, memory, etc.

As a next step deeper investigation can be done by using the proper SQL Statement Collection report.
🔖 3311408 - Bookmark of SQL Statement Collection reports for SAP HANA

Examples:

Constantly high memory usage with an OOM (out-of-memory) event. Conclusion: memory issue, memory area needs to be investigated.LoadHistory____constantly_high_memory.png

Normal memory usage with a sudden memory increase and an OOM (out-of-memory) event. Conclusion: memory usage in general was normal, however rapid rise happened. Probably invalid parameter setup.LoadHistory____suddenly_high_memory.png

Constantly high memory usage (while high CPU) with an OOM (out-of-memory) event and after the OOM both CPU and memory decreased. Conclusion: memory issue, memory area needs to be investigated, probably continuous load/unload happens.LoadHistory____SUP____Last7Days___CPU_memory.png

CPU increase and decrease. Conclusion: the exact date and time can be identified which needs to be investigated.LoadHistory___CPU__increased.png

Repeatedly quick CPU spike (on same time in every hour). Conclusion: exact repetition is observed.LoadHistory___CPU_spike_repeatedly.png

Constantly high CPU pattern on work days (Monday-Friday). Conclusion: Probably invalid parameter setup.
LoadHistory____PS4___2024_04_08-2024_04_14___CPU_pattern.png

Other examples
The following examples show a complete investigation process, where the first step was to examine the Load History graphical interface, which proved to be very useful.

  • 3315703 - CPU spikes happens every hour in SAP HANA which freezes the system
  • 3439888 - SAP HANA system freeze/hung/unresponsive on daily basis in same time

Other articles in this series
🔖 3428763 - Bookmark of frequently used SAP GUI transaction codes for SAP HANA related investigations

Do you have further questions?
Please do not hesitate to contact me if you have question or observation regarding the article.
SAP Community for SAP GUI: https://community.sap.com/topics/gui

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 DateDescription
2024.05.05First/initial Release of the SAP Blog Post documentation (Product Information).
Labels in this area
Popular Blog Posts