Skip to Content
0
Former Member
Apr 10, 2007 at 04:54 PM

How to keep short dumps for a longer time

362 Views

Hi All,

I need to write a program to fetch all the below mentioned fields from the system dump tables and insert into a user defind table. Please help me with the code. Thanks in advance....

PROBLEM DESCRIPTION

-


ABAP runtime errors (also known as short-dumps) are kept in the system only for two days, mainly because every short-dump can use a lot of disk space depending on short-dump type. Problem is that this reduced time frame (two days) is not allowing us to focus in solve the more frequent ones and we do not have any statistic about:

how many are we getting

how often

repetitive ones

PROPOSED SOLUTION

-


We need a program to be executed in a daily job right after midnight which will take the basic information of all today’s short-dumps and store it in a custom table.

Information to be kept:

DATE

TIME

HOST

USER

SYSTEM

CLIENT

ERROR ID

TRANSACTION

PROGRAM NAME

PROGRAM NAME VERSION (TRANSPORT REQUEST NUMBER)

PROGRAM NAME VERSION TIMESTAMP (transported to PPx)

SCREEN

SCREEN LINE

MAIN PROGRAM NAME

MAIN PROGRAM NAME VERSION (TRANSPORT REQUEST NUMBER)

MAIN PROGRAM NAME VERSION TIMESTAMP (transported to PPx)

PROGRAM LINE NUMBER AT TERMINATION

SAP RELEASE

SAP KERNEL

PATCH LEVEL

DATABASE VERSION

The program must have archiving capabilities implemented. In the month end run it will also perform the table house-keeping accordingly with a parameter like this:

ERROR-ID

MONTHS TO KEEP

We need to have the possibility of defining different retention periods for different kind of errors, for example our friend GETWA_TOO_MANY_SEGMENT could be stored for a year and a simple CONVT_NO_NUMBER only for a month. One of the parameters should be the default one, something like

ERROR-ID **************

MONTHS TO KEEP 01.