SAP Virtual/Onsite Trainings

Document Categories:

What's New?

Contribute?

Sample Specs

What's Hot?

Web Dynpro for ABAP Tutorials 


Join the Mailing List
Enter name and email address below:
Name:
Email:
Subscribe  Unsubscribe 

Avoiding automatic deletion of Short Dump

By Rahul Manoj Mahajan, John Deere India

Whenever short dump occurs in the system while executing any program, we refer to the transaction ST22 for analyzing the short dump.

This short dump is getting stored into the table SNAP. Unless they are intended for retention and marked accordingly, these long texts are automatically released for deletion one week after they are generated.

The process for deletion occurs systematically. When a program gets terminated with the run time error and short dump is displayed, deletion of older short dump takes place. For this older short dump (100 to be specific for performance reasons) are searched and deleted.

Sometimes we may want to do some analysis on a particular error which was created in past. We cannot do it if the short dump was deleted.

To avoid the automatic deletion of a particular error, we can follow the simple steps as follows.

Go to transaction ST22 as follows.

Click on Today or Yesterday.  

This list will automatically be deleted after 1 week of time. Let’s say you want to do some analysis on some error in future, you can avoid the automatic deletion of it using following simple steps.

Select the error and click on lock button. Or Choose Save/Release from the menu

You will receive the message once you stored the error in database.

This error will be there in database table until you release it. In this way, you can store the errors which you want for further analysis in future.

Please send us your feedback/suggestions at webmaster@SAPTechnical.COM 

HomeContribute About Us Privacy Terms Of Use • Disclaimer • SafeCompanies: Advertise on SAPTechnical.COM | Post JobContact Us  

Graphic Design by Round the Bend Wizards

footer image footer image