last updated: 2024-02-24
Introduction
The article explains the SAP GUI – TCODE (Transaction Code): ST22 usage in details.
SAP GUI
- SAP Help Portal – SAP GUI for Windows
- SAP Community – SAP GUI – SAP GUI Family
- 147519 – Maintenance strategy / deadlines for SAP GUI for Windows / SAP GUI for Java
Description
Transaction Code ST22 developed to overview and analyze the dump files created by the system.
- SAP Help Portal – ABAP Dump Analysis (ST22)
Video explanation by SAP PRESS
See how to analyze ABAP short dumps in your SAP S/4HANA system.
Menu
ST22 – Tools -> Administration -> Monitor -> Dump Analysis
Screen: ABAP Runtime Errors - All Clients
Initial screen where the required filters can be selected based on the actual need. There are dedicated buttons to list the dumps from actual day or yesterday.
- Date – filter the desired date condition
- Time – filter the desired time condition
- Host – filter the desired host
- Work Process Index – filter the desired work process
- User – specific user name or user name with * character (e.g. USER001 or USER*)
- Client – filter the desired client
- Runtime Error – filter the desired runtime error
- etc.
Execution with the 'Start' button.
Screen: List of Selected Runtime Errors
List of Selected Runtime Errors screen shows the result of the filtered criteria.
Open the dump with double click on the requested row.
Screen: Runtime Error Long Text
The Runtime Error Long Text screen contains the detailed dump information.
Informations:
- Header (red) - These are initial informations about the issue. Important to find the proper component of the issue. Based on the information the error can be assign to the proper component where the issue belongs to.
- Short Text - Also initial information.
- What happened? - Further details about the issue.
- ...
- System environment - Detailed information about the actual system (such as Kernel, Database, Operating system, Patch level, ect.).
- ...
- Source Code Extract - Points where the issue occurred inside the code.
To export the content use menu: System -> List -> Save -> Save or Local File.
Based on the dump file and the available ‘Date’ and ‘Time’ information the issue can be checked further with transaction SM21 and ST11.
- 1896868 - How to save a short dump in text format
Which SAP Knowledge Base Article belongs to the topic?
- 2194685 - How to find work process trace for SM21 System Log or ST22 dump
- 2399990 – How-To: Analyzing ABAP Short Dumps in SAP HANA Environments
How does a complete dump looks like?
This is an example ABAP dump from a test system.
Category Installation Errors Runtime Errors DBSQL_SQL_ERROR Except. CX_SY_OPEN_SQL_DB Date and Time 08.06.2023 16:36:41 ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |Short Text | | SQL error "SQL code: -99999" occurred while accessing table "SMODILOG". | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |What happened? | | Database error text: "SQL message: CLI0135E Invalid scale value. | | SQLSTATE=HY094 col=5" | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |What can you do? | | Note which actions and entries caused the error to occur. | | | | Consult your SAP administrator. | | | | Using transaction ST22 for ABAP dump analysis, you can view, manage, | | and retain termination messages for longer periods. | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |Error analysis | | An exception has occurred which is explained in more detail below. The | | exception is assigned to class 'CX_SY_OPEN_SQL_DB' and was not caught in | | procedure | | "SELECT_DELETED_OBJECTS" "(FORM)", nor was it propagated by a RAISING clause. | | Since the caller of the procedure could not have anticipated this | | exception, the current program was terminated. | | The reason for the exception is: | | Database error text: SQL message: CLI0135E Invalid scale value. | | SQLSTATE=HY094 col=5 | | Return value of the database layer: "SQL dbsl rc: 99" | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |How to correct the error | | The exception must either be prevented, caught in procedure | | "SELECT_DELETED_OBJECTS" "(FORM)", or | | the possibility of it occurring must be declared in the RAISING clause | | in the procedure. | | To prevent the exception, note the following: | | | | Analyze the entries in the system log (transaction SM21). | | If the error occurs in a non-modified SAP program, you might be able to | | find a solution in the SAP Notes system. If you have access to the SAP | | Notes system, check there first using the following keywords: | | | | "DBSQL_SQL_ERROR" CX_SY_OPEN_SQL_DB | | "SAPRUPGM" or SAPRUPGM | | "SELECT_DELETED_OBJECTS" | | If you cannot solve the problem yourself, please send the following | | information to SAP: | | | | 1. This description of the problem (short dump) | | To do this, choose System -> List -> Save -> Local File (unconverted) | | on the screen you are in now. | | | | 2. A suitable system log | | To do this, call the system log in transaction SM21. Restrict the time | | interval to ten minutes before the short dump and five minutes after | | it. In the display, choose System -> List -> Save -> Local File | | (unconverted). | | | | 3. If these are programs of your own, or modified SAP programs: Source | | code of these programs | | To do this, choose More Utilities -> Upload/Download -> Download in | | the Editor. | | | | 4. Details regarding the conditions under which the error occurred or | | which actions and input caused the error. | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |System environment | | SAP Release..... 740 | | SAP Basis level 0030 | | | | Application server... | | Network address...... | | Operating system... Linux | | Release.............. 4.12.14-122.159-defa | | Hardware type....... x86_64 | | Character length..... 16 Bits | | Pointer length........ 64 Bits | | Work process number... 27 | | Shortdump setting. full | | | | Database server... | | Database type..... DB6 | | Database name..... Q7Q | | Database user ID SAPXXX | | | | Terminal.......... | | | | Character set C | | | | SAP kernel....... 753 | | Created on....... May 7 2023 17:47:47 | | Created at....... Linux GNU SLES-11 x86_64 cc4.8.5 use-pr230506i | | Database version DB6_81 | | Patch level....... 1200 | | Patch text....... | | | | Database............. DB6 09.07.*, DB6 10.*, DB6 11.* | | SAP database version. 753 | | Operating system... Linux | | | | Memory consumption | | Roll.... 0 | | EM...... 0 | | Heap.... 64851136 | | Page.... 40960 | | MM used. 21168224 | | MM free. 7087288 | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |User and Transaction | | Client................. 000 | | User.................. C5346207 | | Language key.......... E | | Transaction......... | | Transaction ID...... AE03978B8C5701B0E006481BF5F8BBA2 | | | | EPP whole context ID...... 42010AEE27F91EDE81C0D318B5632082 | | EPP connection ID........ 00000000000000000000000000000000 | | EPP call counter......... 1 | | | | Program.............. SAPRUPGM | | Screen.............. SAPMSSY0 1000 | | Screen line.......... 6 | | Active debugger..... "none" | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |Information on where terminated | | The termination occurred in ABAP program "SAPRUPGM", in | | "SELECT_DELETED_OBJECTS". The main program | | was "SAPRUPGM". | | | | In the source code, the termination point is in line 1579 of (Include) | | program "SAPRUPGM". | | Program "SAPRUPGM" was started as a background job. | | | | Job name....... OCS_QUEUE_IMPORT | | Job initiator.. C5346207 | | Job number...... 16360400 | | The termination is due to exception "CX_SY_OPEN_SQL_DB" occurring in procedure | | "SELECT_DELETED_OBJECTS" "(FORM)". | | This exception was not handled locally or declared in the RAISING | | clause in the procedure's signature however. | | The procedure is in program "SAPRUPGM". The source code begins in line 1351 of | | (include) program "SAPRUPGM". | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |Source Code Extract | ---------------------------------------------------------------------------------------------------- |Line |Code | ---------------------------------------------------------------------------------------------------- | 1549| ls_modified_indx-sub_name(10). | | 1550| ls_modified_indx-indexname = | | 1551| ls_modified_indx-sub_name+10(gc_len_indx). | | 1552| | | 1553| ls_modified_indx-obj_name = ls_modified_indx-sub_name. | | 1554| modify lt_modified_indx from ls_modified_indx. | | 1555| endif. | | 1556| | | 1557| endloop. | | 1558| | | 1559| delete lt_modified_indx where indexname is initial. | | 1560| | | 1561| describe table lt_modified_indx. | | 1562| if sy-tfill > 0. | | 1563|* INDX | | 1564| select distinct (lt_select_fields) | | 1565| from smodilog | | 1566| appending corresponding fields of table gt_deleted_objects | | 1567| for all entries in lt_modified_indx | | 1568| where sub_type = obj_indx | | 1569| and sub_name = lt_modified_indx-sub_name | | 1570| and inactive <> smodi_c_inactive_reset | | 1571| and not exists | | 1572| ( select * from dd12l as d | | 1573| where d~sqltab = lt_modified_indx-sqltab | | 1574| and d~indexname = lt_modified_indx-indexname | | 1575| and d~isextind = space ) | | 1576| %_hints HDB '&max_blocking_factor 50&'. "#EC CI_HINTS | | 1577| | | 1578|* XINX | |>>>>>| select distinct (lt_select_fields) | | 1580| from smodilog | | 1581| appending corresponding fields of table gt_deleted_objects | | 1582| for all entries in lt_modified_indx | | 1583| where sub_type = obj_xinx | | 1584| and sub_name = lt_modified_indx-sub_name | | 1585| and inactive <> smodi_c_inactive_reset | | 1586| and not exists | | 1587| ( select * from dd12l as d | | 1588| inner join tadir as t on t~pgmid = pgmid_r3tr and t~object = obj_xinx and t~ob| | 1589| where d~sqltab = lt_modified_indx-sqltab | | 1590| and d~indexname = lt_modified_indx-indexname ) | | 1591| %_hints HDB '&max_blocking_factor 50&'. "#EC CI_HINTS | | 1592| | | 1593| endif. | | 1594| | | 1595| | | 1596|* Views | | 1597|* ===== | | 1598| | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |Contents of system fields | ---------------------------------------------------------------------------------------------------- |Name |Val. | ---------------------------------------------------------------------------------------------------- |SY-SUBRC|4 | |SY-INDEX|0 | |SY-TABIX|6 | |SY-DBCNT|0 | |SY-FDPOS|40 | |SY-LSIND|0 | |SY-PAGNO|1 | |SY-LINNO|1 | |SY-COLNO|1 | |SY-PFKEY| | |SY-UCOMM| | |SY-TITLE|Specify Adjustment Modes and Deleted Objects | |SY-MSGTY|E | |SY-MSGID|SCWN | |SY-MSGNO|400 | |SY-MSGV1|0002698675 | |SY-MSGV2|0002 | |SY-MSGV3| | |SY-MSGV4| | |SY-MODNO|0 | |SY-DATUM|20230608 | |SY-UZEIT|163620 | |SY-XPROG|SAPCNVE | |SY-XFORM|CONVERSION_EXIT | ----------------------------------------------------------------------------------------------------
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 Date | Description |
| 2023.07.06 | First/initial Release of the SAP Blog Post documentation (Product Information). |
| 2024.01.26 | SAP Community 2024 optimized content. |
| 2024.02.06 | Other articles in this series section maintained. |
| 2024.02.24 | Insert SAP PRESS video. - How to Analyze ABAP Short Dumps in an SAP S/4HANA System |
- SAP Managed Tags:
