Skip to main content

ABAP Dumps Analysis

Ever now and then have you heard about ABAP Dumps, We also have a joke everything in temporary in life except ABAP dumps for SAP Consultants.




Lets try to understand ABAP dumps from perspective of a SAP BASIS Consultant.


Dumps happen when an ABAP program runs and something goes wrong that cannot be handled by the program


We have two broad categories of Dumps , In custom program Dumps and SAP provided program Dumps.


Dumps that happen in the customer namespace ranges (i.e. own-developed code) or known as Custom Program , can usually be fixed by the ABAP programmer of your team. Dumps that happen in SAP standard code probably need a fix from SAP.


You do not have to be an "ABAPer" in order to resolve ABAP dump issues. The common way to deal with them is to look up in ST22


How to correct the error ?


Hints are given for the keywords that may be used to search on the note system.


Gather Information about the issue 


Go to System > Status and Check the Basis SP level as well as information about hardware and operating system, this helps in further analysis as few Support pack have issues running some programs and for those already SAP NOTE is present


Information about where the error occurred : The client, user id, language, transaction. The program, screen and screen line number of the failure, where the program exactly stopped [the function module, for example, the main program, and the exact place in the code that the failure happened.]


Extract the source code , you can see a portion of the code around the area where the failure happened. If no code can be seen, then usually that indicates an issue at the Basis level. If you click on the code, you are navigated to the editor.



Few dumps issues we should be aware of and the cause :-



Error State

What does that Error means

CALL_FUNCTION_SIGNON_INCOMPL

Typical of an RFC-Call with incorrect or missing logon-data. So, we have to find out where the call is coming from.


Check SAP Note 171805 684788 901256 

CALL_FUNCTION_NOT_FOUND

The program called the function which doesn't exist in the library. Means the requested function module is not found in table TFDIR.(TFDIR is a standard Syntax, Compiler, Runtime Transparent Table in SAP Basis application, which stores Function Module data. )


Also you may get this error if the buffered version of the TFDIR contains errors


SAP Note : 98458 

SYSTEM_NO_TASK_STORAGE

For this error, please go to service market to download the latest patch for your SAP Application release and apply patch.


The SYSTEM_NO_TASK_STORAGE is a known problem and related to limitation of 32bit OS


SAP Note : 110172, 552209, 546361


The cause for the dump SYSTEM_NO_TASK_STORAGE could also be an old sap collector.


SYSTEM_CORE_DUMPED

Related to R/3 system kernel. Upgrade the kernel patch to the latest may solve the issue.


SAP Note : 19466 

STORAGE_PARAMETERS_WRONG_SET

The problems with the dump STORAGE_PARAMETERS_WRONG_SET are mainly related to the general restrictions of the 32bit OS.


The parameters which are related to ‘heap memory' ie abap/heap_area_dia, abap/heap_area_nondia, abap/heap_area_total are should be set to 2 GB. 


Three ways to overcome this :-


  1. Migrate to 64-bit OS 

  2. To decrease the value of the parameters: rdisp/ROLL_SHM [Roll Area], rdisp/PG_SHM [Paging Area]

  3. Please use in the 'boot.ini' file the switch '/3GB' and restart your whole computer as described in the below SAP Notes: 552209,  313347 

  4. Add more criteria to your report/program/transaction so that there will be fewer entries that need to be retrieved from your database or buffers. This way, the system would not need to use up much resource to complete the transaction.

RAISE_EXCEPTION

A function module raise an exception that was not intercepted by a program higher up in the stack. If this occurs in a customer program, then the developer needs to handle the exception in the calling program. . Ask your ABAP team to look at the values of sy-msgid and sy-msgno in transaction SE91

RFC_ATTACH_GUI_FAILED

This commonly happens when an RFC enabled function module is run, that then goes on to do something connected with screen handling. 


As it does not have a screen, it fails. It can also happen if SAPGui (or components of it, such a BEX) have a problem, or are incorrectly installed.

LOAD_PROGRAM_LOST

The LOAD_PROGRAM_LOST error can occur when there are two or more versions of a given program loaded into the buffer at any given time. 


This happens when the program is changed by one user while it is still in use by another user.


When a user gets to the program that is having this problem and R/3 attempts to load the generated version from the buffer, it sees that the version is not the most current and tries to swap it out for the most current, but the load was lost from the PXA buffer, hence it throws the dump.


Ask the user to restart the transaction


SAP Note : 5451 24824 10367 

DBIF_RSQL_SQL_ERROR

Indicates a problem occurred in the database. You may find more information in the system log via SM21


The exact nature of the failure is usually seen in the “How to correct the error” section.


 If this occurs in standard SAP code, then there may be a corrective note

ASSIGN_TYPE_CONFLICT

Most likely a programming error. This message indicates that an ASSIGN is occurring that is going to an incorrectly typed field-symbol. Check the Source Code Extract to see exactly where the problem occurs, and carefully check that the typing of the object matches.

OBJECTS_OBJREF_NOT_ASSIGNED_NO

An attempt was made to access an object (the class type is given), that had not been instantiated. 


Programming error

TSV_TNEW_PAGE_ALLOC_FAILED and MEMORY_NO_MORE_PAGING

The error TSV_NEW_PAGE_ALLOC_FAILED means that more memory was requested by the system because the program needed to expand an internal table, but it is not available. 


When Extended Memory is completely used up, the process will go into PRIV mode and it will starts using Heap Memory in case of Windows or vice versa in case of Unix.


Once this enters into PRIV mode, no other user will be able to use the corresponding work process. If there is enough memory for it to finish, you will not see the error.


SAP Notes : 649327 20527 185185 369726   

TSV_TNEW_OCCURS_NO_ROLL_MEMORY

The dump TSV_TNEW_BLOCKS_NO_ROLL_MEMORY usually means that the roll buffer has been exhausted. Please check the usage of your roll buffer with ST02->History->Page. Near the bottom of the screen you can see ROLL BUFFER history. If the roll buffer has been exhausted, you can increase the size with parameter rdisp/ROLL_MAXFS, but make sure you have sufficient disk space to handle the additional size of this buffer if it writes to disk.

UNCAUGHT_EXCEPTION

This error mostly appears with the user SAPSYS. The user SAPSYS is an internal user, it is not a personally used ID in the R/3 system. However, all system errors and ABAP programs are run via this user id


since release 4.0 the parameter auth/rfc_authority_check is set on 1 per default. This means, as long as you did not set it explicitly to value ‘0', any incoming RFC call is checked


Resolve this issue by, 


  1. Deactivate RFC authority Check: set auth/rfc_authority_check to value '0' (zero) in profile and restart


OR


  1. Assign full RFC authorities to the users who need to connect to your system via RFC



SAP Note : 171805 93254 91980  

COMPUTE_INT_ZERODIVIDE

Exactly what it says – an attempt has been made to divide by zero. This is either a data or programming error.

RFC_NO_AUTHORITY

The user that tried to execute an RFC enabled function module, via RFC, was not authorised via authorisation object S_RFC to run the function module.

MESSAGE_TYPE_X

The program met a situation that it just did not know what to do with.


Sometimes the error indicates inconsistent data


 It can be used deliberately during the development process.


If, during development you simply want to know if a certain piece of code gets executed at all (usually background stuff, like workflow ), you just code a type X message with some values such as sy-uname, or other variable you are interested in. This is a very good way to exactly find out the value of a parameter when differences can occur in debugging.


TIME_OUT

There is a Basis setting that sets a limit for the run time of a transaction or report- typically fifteen minutes. If a dialogue process exceeds this limit, the kernel spots it and stops the program with a TIME_OUT dump. Common causes are:


1.User selecting too much data – like all companies, or all controlling areas.

2.A programming error resulting in a endless loop

3.Inefficient programming. For example, using STANDARD tables instead of HASHED or SORTED, loops within loops, selecting the same data again and again etc.


Resolution :-


In SAP, there is a parameter rdisp/max_wprun_time which limits the maximum permitted runtime without interruption. By default this value is set to 600 seconds. However, if you are frequently encountering more dumps in SAP system due  to this, you can consider increasing this value to 3600 seconds to avoid this issue


LIST_TOO_MANY_PROs

This usually happens when any transaction has fifty or more nested “CALL SCREEN”. The solution is to redesign your transaction to prevent that many nested calls. Note that there ia a distinction between CALL SCREEN and SET SCREEN. While CALL SCREEN creates a new stack and puts the entry in it,  SET SCREEN only navigates between screens. 

CONTROL_NOT_FOUND

All we can say is that this either happened because the release of the kernel is not the same as the release of the database, or that the text was deleted for some reason. You can look for further information in the note system. 





Read more on:-

Comments

You might find these interesting

How to properly Start/Stop SAP system through command line ?

Starting/stopping an SAP system is not a critical task, but the method that most of us follow to achieve this is sometimes wrong. A common mistake that most of the SAP admins do is, making use of the 'startsap' and 'stopsap' commands for starting/stopping the system.  These commands got deprecated in 2015 because the scripts were not being maintained anymore and SAP recommends not to use them as many people have faced errors while executing those scripts. For more info and the bugs in scripts, you can check the sap note 809477.  These scripts are not available in kernel version 7.73 and later. So if these are not the correct commands, then how to start/stop the sap system?  In this post, we will see how to do it in the correct way. SAP SYSTEM VS INSTANCE In SAP, an instance is a group of resources such as memory, work processes and so on, usually in support of a single application server or database server with

sapstartsrv is not started or sapcontrol is not working

 What is sapstartsrv ? The SAP start service runs on every computer where an instance of an SAP system is started. It is implemented as a service on Windows, and as a daemon on UNIX. The process is called  sapstartsrv.exe   on Windows, and   sapstartsrv   on UNIX platforms. The SAP start service provides the following functions for monitoring SAP systems, instances, and processes. Starting and stopping Monitoring the runtime state Reading logs, traces, and configuration files Technical information, such as network ports, active sessions, thread lists, etc. These services are provided on SAPControl SOAP Web Service, and used by SAP monitoring tools (SAP Management Console,  SAP NetWeaver  Administrator, etc.). For more understanding use this link : https://help.sap.com/doc/saphelp_nw73ehp1/7.31.19/enUS/b3/903925c34a45e28a2861b59c3c5623/content.htm?no_cache=true How to check if it is working or not ? In case of linux , you can simply ps -ef | grep sapstartsrv In case of windows, you need

HANA System Replication - Prerequisites & Setup

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out operation & replication modes in hana system replication. If you haven't gone though that blog, you can checkout  this link In this blog we will be talking about the prerequisites of hana replication and it's setup. So let's get started. When we plan to setup hana system replication, we need to make sure that all prerequisite steps have been followed. Let's have a look at these prerequisites. HANA System Replication Prerequisites: Primary & secondary systems should be up & running HDB version of secondary should be greater than or equal to Primary database sever But, for Active/Active(read enabled config), HDB version should be same on both sites. System configuration/ini files should be identical on both sides Replication happe

ST03N : The chapter for all BASIS Admins

This blog is targeted to BASIS ADMINS Transaction for workload analysis statistical data changed over time are monitored using transaction code ST03 , now ST03N (from SAP R/3 4.6C) . With SAP Web AS 6.4 the transaction ST03 is available again. From time to time ST03 and ST03N has seen many changes but later in SAP NW7.0 ST03N has reworked in detail specially processing time is now shown in separate column. Main Use of ST03N  is to get detailed information on performance of any ABAP based SAP system. Workload monitor analyzes the statistical data originally collected by kernel. You can compare or analyze the performance of a single application server or multiple application server. Using this you start checking from the entire system and finding your way to that one application server and narrowing down to exact issue. By Default :- You see data of current day as default view , you can change the default view. Source of the image : sap-perf.ca Let's discuss the WORKLOAD MONITOR By D

How to resolve Common Error : Standard Template "sap_sm.xls" missing

Hey everyone, putting forward a common error we usually face when we have “ Excel inplace” functionality enabled in our SAP system. This error occurs when validity of the signature of SAP standard templates expired or were incorrectly delivered via support packages. We can reproduce the error by doing as below.. Click on “spreadsheet” icon after any SAP ALV grid view of data is on screen to make this data to export into excel directly from SAP.

HANA hdbuserstore

The hdbuserstore (hana secure user store) is a tool which comes as an executable with the SAP Hana Client package. This secure user store allows you to store SAP HANA connection information, including user passwords, securely on clients. With the help of secure store, the client applications can connect to SAP HANA without the user having to enter host name or logon credentials. You can also use the secure store to configure failover support for application servers in a 3-tier scenario (for example, SAP Business Warehouse) by storing a list of all the hosts that the application server can connect to. To access the system using secure store, there are two connect options: (1)key and (2)virtualHostName. key is the hdbuserstore key that you use to connect to SAP HANA, while virtualHostName specifies the virtual host name. This option allows you to change where the hdbuserstore searches for the data and key files. Note

SUM Tool : An Introduction

Let’s Discuss about the famous tool, that is asked in almost all the Basis and HANA interview and it is very easy to understand but a bit tricky. Tighten your seatbelts and Let’s understand in one go. SAP Technical Upgrade is a periodic project that is implemented across companies to upgrade their SAP system to the latest released version. Most of the upgrade activities are done by the technical team and the role of functional consultants is limited and mostly confined to regression testing What are the maintenance that are performed by help of SUM ? Release upgrade (major release change) System update (EHP installation) applying Support Packages (SPs) / Support Package Stacks applying Java patches correction of installed software information combine update and migration to SAP HANA (DMO: Database Migration Option) System Conversion from SAP ERP to SAP S/4HANA   First thing first , never confuse in these two things : Upgrade and Update. Updating SAP products is for applying support pac

SAP HANA System Replication - Operation Mode & Replication Mode

Hey Folks! Welcome back to Hana high availability blog series. In our last blog we checked out what is hana system replication and how it basically works. If you haven't gone through that blog, you can checkout link In this blog we will be talking about the replication modes and operation modes in hana system replication. So let's get started. When we setup the replication and register the secondary site, we need to decide the operation mode & replication mode we want to choose for replication. For now we won't focus on setting up replication as we'll cover it in our next blogs.  Operation Modes in Hana System Replication: There are three operation modes available in system replication: delta_datashipping, logreplay and logreplay_readaccess. Default operation mode is logreplay. 1. Delta_datashipping: In this operation mode initially one full data shipping is done as part of replication setup and then a delta data shipping takes place occasionally in addition to cont

Work Process and Memory Management in SAP

Let’s talk about the entire concepts that are related to memory when we talk about SAP Application. Starting with few basic terminologies, Local Memory :  Local process memory, the operating system keeps the two allocation steps transparent. The operating system does the other tasks, such as reserving physical memory, loading and unloading virtual memory into and out of the main memory. Shared Memory :  If several processes are to access the same memory area, the two allocation steps are not transparent. One object is created that represents the physical memory and can be used by various processes. The processes can map the object fully or partially into the address space. The way this is done varies from platform to platform. Memory mapped files, unnamed mapped files, and shared memory are used.  Extended Memory : SAP extended memory is the core of the SAP memory management system. Each SAP work process has a part reserved in its virtual address space for extended memory. You can set

Complete Guide : XPI Inspector Tool

Content of this blog :           What is an XPI Inspector Tool ? Why XPI Tool is used ? XPI standard URL How to check XPI Tool version ? How to Install/Update XPI version using TELNET How to Use XPI Tool ? References – SAP Notes What is XPI Inspector tool ?          -    XPI Inspector is a diagnostics web application developed by SAP that collects logs and debug traces from various PI components in a very simple way and is useful for SAP PI consultants, developers, and administrators to get more insights on an issue. Why XPI is used  – 1.  Used to collect traces and logs from Messaging system or XI module. 2. Used to collect the related information to solving the issues or improving the PI or PO systems’ performance. 3. Using XPI Inspector application you will be able to collect a lot of information about your system that will help you to learn about problems in the past, to analyze new and detect such at an early stage. 4. Performs certain number of configuration checks, such as SSL c