Regarding ST22 short dumps getting automatically deleted

[zsc]

Hello Experts,

We had an issue sometime back in our production system and want to look at the logs/dumps in ST22 to do some Root Cause Analysis.

However, we do not have ST22 dumps of those days so we restored the earlier backup of our system into a different box to see those dumps.

The strange this is as soon as the restored system is back up the short dumps in ST22 starts to get deleted. There is no background job or any process that we see doing it.

But strangely the number of records in the SNAP table starts reducing.

I want to find out what is it that starts cleaning up the short dumps as soon as it is restored. We have restored it twice and doing it third time now.

Just to mention, We know all about RSSNAPDL / SAP_REORG_ABAPDUMPS background job that cleans these short dumps but definitely we dont see them in SM37 since the system is restored.

Any pointer that could be causing it or anyone who has experienced this before would be really helpful.

Thank you...

[zsc · Accepted solution]

This issue is resolved. Everytime our basis team member restored the system and then goes to SM37 and deleted all the jobs. In the third restore attempt, he performed and additional step to suspend all background jobs as well using the program BTCTRNS1. Now we can see ST22 short dumps in the system that were getting deleted earlier. Also, one more piece of information: in ST22, you can keep/release a specific short dump by going to menu Runtime Errors--> Keep/Release.

[AtulKumarJain]

Hi Shetulkumar,

I hope this note will guide you to reach root cause

1995777 - Dump deleted within a short period of time ST22

Best Regards,

Atul

[zsc]

Thank you Yogesh for quick response... We have ensured that the job has not run in any of the clients...Appreciate other thoughts to look for...

[patelyogesh]

Hello Shetulkumar Chothani,

Thank you for mentioning about RSSNAPDL / SAP_REORG_ABAPDUMPS background job.

Since you mentioned about let me ask you that - Did you check this job is NOT running in other than your productive client/s?

-Yogesh