Purpose

 

The purpose of this document is to instruct SAP customers on how to analyse ABAP dumps.

 

 

Overview

 

How to troubleshoot ABAP Dumps

 

 

Troubleshooting

 

When looking at an ABAP system you can sometimes come across runtime errors in Transaction ST22:

 

Wiki ST22.PNG

 

 

Clicking into the “Today” or “Yesterday” tab will bring up all the ABAP Runtime errors you have encountered in the past 2 days.

 

You can also filter the dates for a particular dump by using the filter feature:

 

wiki ST22 filter.PNG

 

 

Here are some examples of runtime errors you might see in ST22:

 

wiki 2.PNG

wiki5.PNG

wiki 3.PNG

 

 

 

So from looking at these dumps, you can see

1: Category

2: Runtime Errors

3: ABAP Program

4: Application Component

5: Data & Time.

 

 

The ST22 dumps do not really give you much information here so more information will be needed.

 

For more information you will then look into the Dev_W files in the transaction ST11

 

 

 

ST11 allows you to look further into the Dev_w files relating to the dumps in ST22:

 

wiki 4.PNG

 

Go to ST22 > click on the Runtime Errors for “Today”, “Yesterday” or a filter. This will being up the specific dump you wish to analyse.

 

Here you will see 11 columns like so:

 

wiki 5.PNG

 

 

Here you can see the columns I have mentioned. The Work Process Index number you need is in the column named WP Index.

 

 

Once you find the dev_w index number you can then go to ST11 and find further information:

 

In the ST11 Dev_w files you have to match the time of the dump in ST22 with the recorded times in the Dev_w process files.

 

 

 

 

If there no usable information in the Dev_W files, the next step would be to analyse the issue from a Database perspective

 

 

From the HANA DB perspective

 

1: Open HANA Studio in SAP HANA Administration Console View

 

wiki 1.PNG

 

 

 

2: Check the diagnosis trace files in accordance with the time stamp of the dump you saw previously in ST22. To do this we have to go to the Diagnosis tab in HANA Studio:

 

wiki2.PNG

 

 

 

3: Check the time stamp from the ST22 dump (Date and Time), and then match this accordingly with the time in either the Indexserver.trc or nameserver.trc.

 

wiki 3.PNG

 

Search for the corresponding time stamp mentioned above i.e. 18/11/2015 @ 10:55:43.

 

Or instead of searching you could use the below SQL:

 

select top 500 service_name, timestamp, trace_text from m_merged_traces where service_name in (‘indexserver’, ‘nameserver’) and timestamp between ‘2015-11-18 10:40:00’ and ‘2015-11-18 10:59:00’

 

 

Searching the nameserver log files can be a good indication of whether your ST22 is related to network issues, you may see errors such as:

 

 

TrexNet          Channel.cpp(00339) : ERROR: reading from channel 151 <127.0.0.1:<host>> failed with timeout error; timeout=10000 ms elapsed [73973]{-1}[-1/-1] 2015-01-28 01:58:55.208048 e TrexNetBuffer    BufferedIO.cpp(01092) : channel 151 from <127.0.0.1:<host>>: read from channel failed; resetting buffer

 

 

 

 

If you do find some errors similar to the above then check which host the error is pointing to and check whether or not this service was available at the time of the dump.

 

 

If this does not yield any useful information, the next step is to ask someone from your network team to look into this. Checking the var/logs/messages is always a great place to start.

 

 

When searching through the indexserver.trc file, you could notice some irregularities recorded here. The next step is to search this error on the SAP Service Market Place for a known KBA or Note (Learn how to search more effectively 2081285 – How to enter good search terms to an SAP search? )

 

 

Related Notes / KBA’s

 

Troubleshooting ‘10108’ errors

Troubleshooting ‘10709’ errors

Related Documents

 

Did you know? You can find details of common issues, fixes, patches and much more by visiting SAP moderated forums on http://scn.sap.com/docs/DOC-18971

Documentation regarding HANA installation, upgrade, administration & development is available at http://help.sap.com/hana_appliance

SAP HANA Troubleshooting WIKI: http://wiki.scn.sap.com/wiki/display/TechTSG/SAP+HANA+and+In-Memory+Computing SAP Discussion HANA: http://scn.sap.com/community/hana-in-memory/ Learn how to search more effectively 2081285 – How to enter good search terms to an SAP search?
__________________________________________________________________________________________________________

To report this post you need to login first.

5 Comments

You must be Logged on to comment or reply to a post.

  1. Lucas Oliveira

    Nice Michael!

    What I also do is to execute sql queries to bring me the actual traces in an easier way (instead of scrolling through Diagnosis files, which is also alright).

    So on your case you could execute the following sql to get more info about the issues stated in ST22:


    select top 500 service_name, timestamp, trace_text from m_merged_traces where service_name in (‘indexserver’, ‘nameserver’) and timestamp between ‘2015-11-18 10:40:00’ and ‘2015-11-18 10:59:00’

    BRs,

    Lucas de Oliveira

    (0) 

Leave a Reply