Hello Experts,
What are typical reasons when calling transaction ST04 / DBACOCKPIT takes a long time?
Kindly share your valuable views here.
Thanks in advance.
When Calling Transaction ST04 / DBACOCKPIT takes a long Time?
Updated May 18, 2018
Comments
Recommended Posts:
- What is SAP HANA
- SAP HANA Training Tutorials for Beginners
- SAP HANA In-Memory Database
- SAP HANA Studio Guide
- SAP HANA Azure Architecture
- SAP HANA Modeling Guide
- SAP HANA Modeling Scenarios
- Create Schema in HANA
- Rename HANA Schema
- SAP HANA Sidecar
- SAP HANA Excel Integration
- SAP HANA Security Overview
- SAP HANA Compression Techniques
- SAP HANA SQL Operators
- SAP HANA Data Provisioning
- SAP HANA License Types
- SAP HANA Data Archiving vs Data Aging
- SAP HANA Interview Questions
- SAP HANA Certification Cost in India
- GST S/4HANA Master Data Configuration
×
When calling transaction ST04 takes a long time, you can check at first if calling transaction DBACOCKPIT is much quicker. Although both transaction codes are quite similar, they have different entrance screens and only with ST04 comprehensive SAP HANA performance data is shown.
If transaction ST04 is slow while DBACOCKPIT is much quicker, it may suffer from a high amount of SAP HANA alerts. If it takes many seconds or even minutes to start ST04, you can check according to SAP Note 2147247 if the number of alerts in table STATISTICS_ALERTS_BASE is too high and perform a cleanup.
In general you can create a SQL trace for starting ST04 / DBACOCKPIT using transaction ST05. This will show you which database requests take longest, so that you can analyze them more in detail.