SAP GUI – Transaction Code – DBACOCKPIT (SQL Plan Cache)

SAP GUI – Transaction Code – DBACOCKPIT (SQL Plan Cache)
Estimated read time 7 min read

last updated: 2026-03-26

Introduction
The article explains the SAP GUI – TCODE (Transaction Code): DBACOCKPIT (SQL Plan Cache) usage in details.

SAP GUI

SAP Help Portal – SAP GUI for WindowsSAP Community – SAP GUI – SAP GUI Family147519 – Maintenance strategy / deadlines for SAP GUI for Windows / SAP GUI for Java

Description
The SQL plan cache provides an overview of compiled queries.

Transaction Code:
DBACOCKPIT 

DBA Cockpit menu structure (Navigation Panel):
Performance > SQL Plan Cache

SAP Help Portal – DBA Cockpit for SAP HANA – Screen Layout in DBA Cockpit for SAP HANA

Screen: SQL Plan Cache
The following image represents the screen where we can find the statement and all relevant details.

Usage:
Part of the statement needs to be added and result(s) will be shown.

Statement String: select d.host, d.usage_type%

—————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————
|Host | Port| Plan ID|Statement String |User |Schema |IS Valid|IS Interna|IS Distrib|IS Stored|Abap Varch|Plan Memor|References|Parameter|Updated Ta|Accessed T|Accessed T |Accessed Objects |Accessed Object Names |Table Loca|Storage Ty|Plan Shari|Owner Conn|Executions|Total Exec|AVG Execut|MIN Execut|MAX Execut|Stddev Exe|Total Curs|AVG Cursor|MIN Cursor|MAX Cursor|Stddev Cur|Total Exec|AVG Execut|MIN Execut|MAX Execut|Stddev Exe|Total Exec|AVG Execut|MIN Execut|MAX Execut|Stddev Exe|Total Exec|AVG Execut|MIN Execut|MAX Execut|
Stddev Exe|Total Resu|Last Execu |Total Lock|Total Lock|Last Prepa |Preparatio|Total Prep|AVG Prepar|MIN Prepar|MAX Prepar|Stddev Pre|Applicatio|Statement Hash | Total Exec|AVG Execut|MIN Execut|MAX Execut| AVG Service Network|MAX Servic|Total Serv| AVG Called Thread Co|MAX Called|Total Call|Last Conne
—————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————
|vhcalhdbdb|30.203 | 67.650.003 |select d.host, d.usage_type, d.total_size, sum(t.file_size) file_size, d.path, d.device_id from ( sys.m_tracefiles as t right outer join sys.m_disks as d on d.host = t.host ) where d.usage_type like ‘%TRACE%’ and d.host NOT IN ( SELECT distinct(host) FROM|SAPHANADB|SAPHANADB| X | | X | | X | 110.163 | 0 | 0 | 0 |134193(4) |SYS.DUMMY(4)|134193(4), 135176(1), 136968(13), 137704(10), 137813(9), 155872(67), 134716, 134751, 134772|SYS.DUMMY(4), SYS.HAS_NEEDED_SYSTEM_PRIV_INCL_SYS_STAT(1), SYS.M_DISKS(13), SYS.M_SERVICES(10), SYS.M_TRACEFILES(9), SAPHANADB(67), SYS.M_DISKS_, SYS.M_SERVICES_, SYS.M_TRACEFILES_| | |GLOBAL | 1-| 267 |3.192.858 | 11.958 | 7.644 | 28.374 | 0 |3.220.914 | 12.063 | 7.712 | 28.464 | 0 |3.167.225 | 11.862 | 7.581 | 28.235 | 0 | 2.570 | 9 | 5 | 114 | 0 | 17.553 | 65 | 31 | 391 |
0 | 267 |26.03.2026 01:10:51| 0 | 0 |03.07.2025 01:10:51| 1 | 26.749 | 26.749 | 26.749 | 26.749 | 0 | |6b089e73940f358d3a894fa9bb509df5|55.756.752 | 208.826 | 208.640 | 254.480 | 1,2000000000000000E+01| 12 | 3.204 | 1,3000000000000000E+01| 13 | 3.471 | 346.596 |
|vhcalhdbdb|30.203 |1.010.840.003 |select d.host, d.usage_type, d.total_size, sum(t.file_size) file_size, d.path, d.device_id from ( sys.m_tracefiles as t right outer join sys.m_disks as d on d.host = t.host ) where d.usage_type like ‘%TRACE%’ and d.host NOT IN ( SELECT distinct(host) FROM|SAPHANADB|SAPHANADB| X | | X | | X | 110.031 | 0 | 0 | 0 |134193(4) |SYS.DUMMY(4)|134193(4), 135176(1), 136968(13), 137704(10), 137813(9), 155872(67), 134716, 134751, 134772|SYS.DUMMY(4), SYS.HAS_NEEDED_SYSTEM_PRIV_INCL_SYS_STAT(1), SYS.M_DISKS(13), SYS.M_SERVICES(10), SYS.M_TRACEFILES(9), SAPHANADB(67), SYS.M_DISKS_, SYS.M_SERVICES_, SYS.M_TRACEFILES_| | |GLOBAL | 1-| 15 | 212.793 | 14.186 | 9.189 | 19.534 | 0 | 215.211 | 14.347 | 9.272 | 19.677 | 0 | 205.512 | 13.700 | 9.105 | 19.164 | 0 | 248 | 16 | 10 | 34 | 0 | 1.219 | 81 | 55 | 115 |
0 | 15 |24.03.2026 07:04:03| 0 | 0 |04.02.2026 10:35:40| 1 | 34.074 | 34.074 | 34.074 | 34.074 | 0 | |aba939e305fd4cb5d6164cc5698ed46c| 3.175.440 | 211.696 | 208.640 | 254.480 | 1,2000000000000000E+01| 12 | 180 | 1,3000000000000000E+01| 13 | 195 | 330.517 |
—————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————

Related SAP documentations
The following SAP documentations belongs to the topic.

3322936 – How to find the SQL statement hash for a SQL statement string

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 DateDescription2026.03.26First/initial Release of the SAP Blog Post documentation (Product Information). 

​ last updated: 2026-03-26IntroductionThe article explains the SAP GUI – TCODE (Transaction Code): DBACOCKPIT (SQL Plan Cache) usage in details.SAP GUISAP Help Portal – SAP GUI for WindowsSAP Community – SAP GUI – SAP GUI Family147519 – Maintenance strategy / deadlines for SAP GUI for Windows / SAP GUI for JavaDescriptionThe SQL plan cache provides an overview of compiled queries.Transaction Code:DBACOCKPIT DBA Cockpit menu structure (Navigation Panel):Performance > SQL Plan CacheSAP Help Portal – DBA Cockpit for SAP HANA – Screen Layout in DBA Cockpit for SAP HANAScreen: SQL Plan CacheThe following image represents the screen where we can find the statement and all relevant details.Usage:Part of the statement needs to be added and result(s) will be shown.Statement String: select d.host, d.usage_type%—————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————
|Host | Port| Plan ID|Statement String |User |Schema |IS Valid|IS Interna|IS Distrib|IS Stored|Abap Varch|Plan Memor|References|Parameter|Updated Ta|Accessed T|Accessed T |Accessed Objects |Accessed Object Names |Table Loca|Storage Ty|Plan Shari|Owner Conn|Executions|Total Exec|AVG Execut|MIN Execut|MAX Execut|Stddev Exe|Total Curs|AVG Cursor|MIN Cursor|MAX Cursor|Stddev Cur|Total Exec|AVG Execut|MIN Execut|MAX Execut|Stddev Exe|Total Exec|AVG Execut|MIN Execut|MAX Execut|Stddev Exe|Total Exec|AVG Execut|MIN Execut|MAX Execut|
Stddev Exe|Total Resu|Last Execu |Total Lock|Total Lock|Last Prepa |Preparatio|Total Prep|AVG Prepar|MIN Prepar|MAX Prepar|Stddev Pre|Applicatio|Statement Hash | Total Exec|AVG Execut|MIN Execut|MAX Execut| AVG Service Network|MAX Servic|Total Serv| AVG Called Thread Co|MAX Called|Total Call|Last Conne
—————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————
|vhcalhdbdb|30.203 | 67.650.003 |select d.host, d.usage_type, d.total_size, sum(t.file_size) file_size, d.path, d.device_id from ( sys.m_tracefiles as t right outer join sys.m_disks as d on d.host = t.host ) where d.usage_type like ‘%TRACE%’ and d.host NOT IN ( SELECT distinct(host) FROM|SAPHANADB|SAPHANADB| X | | X | | X | 110.163 | 0 | 0 | 0 |134193(4) |SYS.DUMMY(4)|134193(4), 135176(1), 136968(13), 137704(10), 137813(9), 155872(67), 134716, 134751, 134772|SYS.DUMMY(4), SYS.HAS_NEEDED_SYSTEM_PRIV_INCL_SYS_STAT(1), SYS.M_DISKS(13), SYS.M_SERVICES(10), SYS.M_TRACEFILES(9), SAPHANADB(67), SYS.M_DISKS_, SYS.M_SERVICES_, SYS.M_TRACEFILES_| | |GLOBAL | 1-| 267 |3.192.858 | 11.958 | 7.644 | 28.374 | 0 |3.220.914 | 12.063 | 7.712 | 28.464 | 0 |3.167.225 | 11.862 | 7.581 | 28.235 | 0 | 2.570 | 9 | 5 | 114 | 0 | 17.553 | 65 | 31 | 391 |
0 | 267 |26.03.2026 01:10:51| 0 | 0 |03.07.2025 01:10:51| 1 | 26.749 | 26.749 | 26.749 | 26.749 | 0 | |6b089e73940f358d3a894fa9bb509df5|55.756.752 | 208.826 | 208.640 | 254.480 | 1,2000000000000000E+01| 12 | 3.204 | 1,3000000000000000E+01| 13 | 3.471 | 346.596 |
|vhcalhdbdb|30.203 |1.010.840.003 |select d.host, d.usage_type, d.total_size, sum(t.file_size) file_size, d.path, d.device_id from ( sys.m_tracefiles as t right outer join sys.m_disks as d on d.host = t.host ) where d.usage_type like ‘%TRACE%’ and d.host NOT IN ( SELECT distinct(host) FROM|SAPHANADB|SAPHANADB| X | | X | | X | 110.031 | 0 | 0 | 0 |134193(4) |SYS.DUMMY(4)|134193(4), 135176(1), 136968(13), 137704(10), 137813(9), 155872(67), 134716, 134751, 134772|SYS.DUMMY(4), SYS.HAS_NEEDED_SYSTEM_PRIV_INCL_SYS_STAT(1), SYS.M_DISKS(13), SYS.M_SERVICES(10), SYS.M_TRACEFILES(9), SAPHANADB(67), SYS.M_DISKS_, SYS.M_SERVICES_, SYS.M_TRACEFILES_| | |GLOBAL | 1-| 15 | 212.793 | 14.186 | 9.189 | 19.534 | 0 | 215.211 | 14.347 | 9.272 | 19.677 | 0 | 205.512 | 13.700 | 9.105 | 19.164 | 0 | 248 | 16 | 10 | 34 | 0 | 1.219 | 81 | 55 | 115 |
0 | 15 |24.03.2026 07:04:03| 0 | 0 |04.02.2026 10:35:40| 1 | 34.074 | 34.074 | 34.074 | 34.074 | 0 | |aba939e305fd4cb5d6164cc5698ed46c| 3.175.440 | 211.696 | 208.640 | 254.480 | 1,2000000000000000E+01| 12 | 180 | 1,3000000000000000E+01| 13 | 195 | 330.517 |
—————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————————Related SAP documentationsThe following SAP documentations belongs to the topic.3322936 – How to find the SQL statement hash for a SQL statement stringOther articles in this series🔖 3428763 – Bookmark of frequently used SAP GUI transaction codes for SAP HANA related investigationsDo 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/guiContributionIf 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 InformationRelease DateDescription2026.03.26First/initial Release of the SAP Blog Post documentation (Product Information).   Read More Technology Blog Posts by SAP articles 

#SAP

#SAPTechnologyblog

Avatar for

You May Also Like

More From Author