How to avoid short dump in ECC 5.0

Hi
Can anyone tell me how to avoid short dump in ECC 5.0
I'm told we can avoid program going to short dump, instead IT WILL GRACEFULLY EXIT..

Hi
By implementing the code as for every unsuccess/failure conditions control has come out of the program. then only u can avoid dumps even though u code the not perfect functionality.
Regards,
kumar

Similar Messages

How to avoid ABAP dump

Hi,
How to avoid ABAP dump
With Warm Regards
Khaja

Hi,
One of the most common short dumps is while entering the values in selection-screen.
So Before processing the selection-screen, the values entered by user need to be
examined and make sure program handle any kind of input through test cases.
And also Its good practice to catch exceptions raised in between the process of the
program.
Regards and Best wishes.

How to keep short dumps for a longer time

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 todays 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.

Aruna,
Following may be the action points for your requirements.
1. Create Custom table with all fields you required.
2. Create ABAP program to extract the data from SAP standard table where runtime error information is stored.
Like: select * from snap_beg into wa_snap_beg
          where seqno = '000'
          and   datum in s_datum
          and   uzeit in s_uzeit
          and   ahost in s_ahost
          and   uname in s_uname
          and   mandt in s_mandt.......
So SNAP_BEG is a table where you can find dump information.
After extracting the data from this table insert it into a Custom table which you have created in Step 1.
Use INSERT statement for this.
3. Create transaction for this report.
4. Schedule this program every day so that you will get all data into custom table.
I hope this will help you.
Regards,
Amey

Short dump in ECC 6.0 during delta load

Hi,
We are currently working in BI upgrade project
from BW 2.1c to BI 7.0
At the same time R/3 is being upgraded from 4.0B to ECC 6.0
During delta load we are getting short dump in R/3 system.
Below is the short dump detalis
The current ABAP prgm "SAPMSSY1" had to be terminated because it has come across a statement that unfortunately cannot be executed.
The following syntax error occured in program "/BI0/SAPLQI2LIS_11_VAITM" in include "/BI0/SAPLQI2LIS_11_VAITM" is not Unicode-compatible, according to its attributes.
If any help can be provided on this issue it would be great.
Regards,
Nikhil
Edited by: Nikhil Sakhardanday on Sep 11, 2008 1:58 PM

Hi,
did you made UCCHECK ?
/manfred

Classic scenario-SC not transferred to backend,short dump in ecc

hi Guru's,
Classic scenario, sc not transferred to backend, executed FM bbp_pd_sc_resubmit, short dump occurred in the backend stating call function not found
please help
short dump file attached
regards,
kiran

Hi Kiran,
Could you please send the DUMP for analysis.
Please try to use this -
This is the new report BBP_SC_AUTO_RETRANSFER to change the status from
I1111 Item in Transfer Process
I1112 Error in transfer/ transmission
Thanks,
From RBEI,
Snehal

Short dump-internal table size issue

Hi,
I get the following message in the short dump analysis for a report.
No storage space available for extending table "IT_920".
You attempted to extend an internal table, but the required space was not available.
Error Analysis:
The internal table "IT_920" could not be enlarged further.
To extend the internal table, 9696 bytes of storage space was
needed, but none was available. At this point, the table "IT_920" has
1008240 entries.
Its an old report and I saw the internal table declaration using the "OCCURS" clause in the internal table declaration.
begin of itab occurs 100.
end of itab.
I tried the option of changing to "OCCURS 0", still issue persists.
Any help would be highly appretiated
CM

Hello CMV,
This is basic problem with SAP internal tables. For every internal table memory is alocated ( Max..256K)...once you cross the memory size/limit of the internal table it resuls in short dump.
Only way to overcome this problem is handle limited number of records at a time..
Please refer following sample code which will help you to avoid short dump while processing large number of records....
SORT TAB_RESULT.
DESCRIBE TABLE TAB_RESULT LINES W_RECORDS.
W_LOW      = 1.
W_UP       = 1000.
*Spliting the records from tab_result1 by pakage of 1000 at a time
*to avoid short dump in case of more records
WHILE W_LOW <= W_RECORDS.
    R_PKUNWE-SIGN = 'I'.
    R_PKUNWE-OPTION = 'EQ'.
    R_WERKS-SIGN = 'I'.
    R_WERKS-OPTION = 'EQ'.
    LOOP AT TAB_RESULT FROM W_LOW TO W_UP.
      MOVE TAB_RESULT-PKUNWE TO R_PKUNWE-LOW.
      MOVE TAB_RESULT-WERKS TO R_WERKS-LOW.
      APPEND R_PKUNWE.
      APPEND R_WERKS.
    ENDLOOP.
*fetch sold to party
     SELECT KUNNR NAME1
       FROM KNA1
       APPENDING CORRESPONDING FIELDS OF TABLE TAB_KNA1
       WHERE KUNNR IN R_PKUNWE.
*fetch plant
SELECT WERKS NAME1
         FROM T001W
         APPENDING CORRESPONDING FIELDS OF TABLE TAB_T001W
         WHERE WERKS IN R_WERKS.
   REFRESH: R_PKUNWE,
            R_WERKS.
    W_LOW = W_LOW + 1000.
    W_UP = W_UP + 1000.
ENDWHILE.
Hope this will help you to solve problem.
Cheers,
Nilesh

21st Interactive list goes to short dump?

Hi,
Why does the 21 st Interactive list goes to short dump?
I know this is due to memory is it correct?
If it is mentioned in the kernal, then where can i find this info?
aRs

Hi,
Please see this test program
report.
uline.
set user-command'PF08'.
at pf8.uline.
set user-command'PF08'
It is giving short dump of "No further selection list possible"
I need to avoid short dump in this scenario. For avoid this i am writing a C call
if sy-lsind > 21 then resetting to 0.
aRs
(Due to this same kind of logic applied to lot of programs i don't want to change all)

Short Dump with Fetch in ECC 6.0

Hello Friends,
I have a query sth like this.
<b>fetch next cursor wc_cursor
into table it_bdi_entry
package size s_pkg.</b>
it_bdi_entry is a internal table of type bdi_entry.
When i use this fetch statement in ECC 6.0 and the fetching row is not all char (like bdi_entry) then i see a short dump saying sth like the source and target are not of same types. How do i overcome this error. please suggest. Thanks in advance.

HI Ramu
I doubt the dump is due to UNICODE compliancy.
In UNICODE systems, we can transfer data between structures only when the structure are similar or having only character fields.
To avoid the dump, we might need to handle field by field.
Hope this helps.
Kind Regards
Eswar

How to delete the short dump list in st22

Hi all,
i want to clear the runtime error list in ST22.
How to clear the list of short dump in ST22.
is there any T.code kindly suggest
thanks in advance
Sundar.c

Dear Sundar,
By default, short dumps are stored in the system for 14 days. The transaction for managing short dumps is ST22. You can delete short dumps in accordance with a time specification using the Reorganize function, which you can call by choosing
Goto u2192 Reorganize in ST22. You can save a short dump without a time limit using the Keep function, which you can choose under Short Dump u2192 Keep/Release in ST22.
The short dumps are stored in table SNAP. If there are too many entries in table SNAP, problems can occur during the reorganization (see SAP Note 11838). There are different options for deleting short dumps from table SNAP:
1. Call transaction ST22. Choose Goto u2192 Reorganize. You can now specify that all short dumps older than n days old (default 7) are to be deleted. If a very large number of records are deleted at once during the reorganization,
ORACLE error ora1562, failed to extend rollback segment ..., can occur. In this case, see SAP Note 6328.
2. Dropping and recreating table SNAP with the database utility (transaction SE14): you can use this transaction to drop and recreate the table SNAP. This means that all short dumps are deleted.
3. The reorganization program RSSNAPDL deletes old short dumps in pieces (to avoid database problems) from table SNAP. It deletes short dumps that are not flagged for retention and are older than seven days old. Schedule this program at a time of low workload, as large changes in the database are to be expected. The program RSNAPJOB performs a standard scheduling: it starts the program RSSNAPDL every day at 1:00 a.m.
4. TableSNAP is also automatically reorganized. At every short dump that occurs in dialog (the dump is displayed immediately after it is created), a maximum of 20 short dumps that are older than 7 days old are deleted from SNAP. This reorganization should be sufficient in normal production operation.
Hope this information resolves your error and also more useful in the feature.
Thanks
Kishore

ECC 6.0 bar chart short dump

We are starting an upgrade from 4.7(non-Unicode) to ECC 6.0(Unicode), using SAPgui for Windows (version 7.10). In our 4.7 systems, the graphical bar chart on the Project Planning Board (txn CJ2C) works as expected. However, in the 6.0 development system, before displaying the gantt chart, the system short dumps with CREATE_ERROR.
I have searched the forums and looked through OSS notes and was unable to find anything that described the problem or was pertinent to our release. I have debugged through the transaction and am finding that the short dump occurs in method cl_gui_barchart=>constructor around the following code:
at line 83 if the system is unicode (which it is), the code calls method cl_gui_frontend_services=>check_gui_support, exporting 'ganttcontrol'/'usedataasstream' and expecting a result in variable l_guisupp_data_as_string. When it returns from the check_gui_support method, l_guisupp_data_as_string is blank, so the next "if" statement raises an error that is not handled:
     if l_guisupp_data_as_string = abap_true.
     .....code not executed because the variable = abap_false.
     else.
     .....raise create_error.    <<<<< this is where the dump occurs.
     endif.
Note that in the debugger, if I force l_guisupp_data_as_string to be = abap_true, the gantt chart/barchart displays as expected. (gotta love the debugger) But since it is standard SAP code I would prefer to resolve the problem without a modification and am hoping someone out there can point me in the right direction.
This short dump occurs with gui versions 710 and lower. (I personally am using sapgui version 710, patch level 7.) Has anyone had problems like this with the graphical elements in SAP or does anyone have a suggestion as to why the gui is not displaying the barchart correctly in our unicode system?
Sorry for the very long message, but thanks in advance for the help!
Amanda Salt
Edited by: Amanda Salt on Jun 17, 2008 11:14 PM

We are starting an upgrade from 4.7(non-Unicode) to ECC 6.0(Unicode), using SAPgui for Windows (version 7.10). In our 4.7 systems, the graphical bar chart on the Project Planning Board (txn CJ2C) works as expected. However, in the 6.0 development system, before displaying the gantt chart, the system short dumps with CREATE_ERROR.
I have searched the forums and looked through OSS notes and was unable to find anything that described the problem or was pertinent to our release. I have debugged through the transaction and am finding that the short dump occurs in method cl_gui_barchart=>constructor around the following code:
at line 83 if the system is unicode (which it is), the code calls method cl_gui_frontend_services=>check_gui_support, exporting 'ganttcontrol'/'usedataasstream' and expecting a result in variable l_guisupp_data_as_string. When it returns from the check_gui_support method, l_guisupp_data_as_string is blank, so the next "if" statement raises an error that is not handled:
     if l_guisupp_data_as_string = abap_true.
     .....code not executed because the variable = abap_false.
     else.
     .....raise create_error.    <<<<< this is where the dump occurs.
     endif.
Note that in the debugger, if I force l_guisupp_data_as_string to be = abap_true, the gantt chart/barchart displays as expected. (gotta love the debugger) But since it is standard SAP code I would prefer to resolve the problem without a modification and am hoping someone out there can point me in the right direction.
This short dump occurs with gui versions 710 and lower. (I personally am using sapgui version 710, patch level 7.) Has anyone had problems like this with the graphical elements in SAP or does anyone have a suggestion as to why the gui is not displaying the barchart correctly in our unicode system?
Sorry for the very long message, but thanks in advance for the help!
Amanda Salt
Edited by: Amanda Salt on Jun 17, 2008 11:14 PM
I just installed the latest patch on the SAPgui, so I am now running:
Release: 710 Final Release
File Version: 7100.2.8.1039
Build: 983952
Patch Level: 8
But I am still getting the short dump. I have done extensive searches of SAP Help, OSS notes, and this and other forums (even just looking up the problem on "google") but can't seem to find anything that applies to this scenario. I'm not very familiar with the methods in cl_gui_frontend_services, so if anyone can give me a pointer of where else I can look, I would greatly appreciate it!
I also have edited the Subject line to be more informative about the problem

How to deal with Short dump that restarts the index server?

Hi ,
I have been experiencing this problem whenever any exception occurs in my SQL SCRIPT procedure. For instance when there is a situation when I try to insert a value of 50 characters in length to a column with max size of 40 it throws a short dump and restarts the index server. I tried to insert the exception handling code as well but still the problem persists. Is there a way to solve this issue?

Hi Sudarshan
crashes are rather generic reactions of the system to virtually any kind of problem that may occur.
Memory shortage is one of the more common issues in current SAP HANA setups and SAP HANA development is heavily working on handling memory shortage situations more gracefully.
Massive over allocation of memory, for example by very large intermediate result sets or join result sets typically can be addressed by correcting the query or model that leads to the issue.
Anyhow, the initial post was not about a memory shortage but about a crash that seemed to have occurred with wrong data type handling.
These are two very different kinds of problems, so I am not really sure how your comment relates here.
- Lars

Short Dump with VA22 transaction in ECC 6

Hi All,
We are on ECC 6 and facing a short dump whenever we are trying to save some quotation. We are getting the following error.
There is probably an error in the program "SAPLSYDB". The program is triggered in the update task. There, the following ABAP/4 statements are not allowed:
CALL SCREEN
CALL DIALOG
CALL TRANSACTION
SUBMIT
"POSTING_ILLEGAL_STATEMENT" " "
"SAPLSYDB" or "LSYDBU27"
"DB_COMMIT".
Is there a sap note for this. Any link or pointer to this will be highly appreciated.
Regards,
Jayant

Hello,
This looks like a problem for SAP. I assume that you have not modified the
program SAPLSYDB. I also assume that you have searched the Service Marketplasce
for any OSS notes. My next step would be to create a message to SAP to get them to
have a look.
Regards
Greg Kern

ODS activation, short dump COMPUTE_INT_PLUS_OVERFLOW. How to solve?

Hello Gurus,
We are on BW 3.1.
We have an issue - ODS activation failed due to a short dump.
Runtime Error          COMPUTE_INT_PLUS_OVERFLOW
Exception              CX_SY_ARITHMETIC_OVERFLOW
Since the caller of the procedure could not have expected this exception
to occur, the running program was terminated.
The reason for the exception is:
In the current program "SAPLRSSM_PROCESS",
using + or 'ADD' to add the values 2137304138 and 12410267 resulted in a
value greater than 2147483647 or samller than -2147483648. This
leads to a whole number overflow.
Could you please guide me to solve this?
Please let me know if you need more details.
Thanks,
raj

This dump is happening because of the overflow of the size assigned for the variable.
This dump can be avoided by changing the declaration of the variable definition.
DATA: variable_name type p decimals 0.
                          OR
DATA: varibale_name(25) type n decimals 0
Try this. This will resolve your dump.
regards,
brijesh

Hi! At connection to iTunes the section "other" constantly increases. What's the matter? How to avoid it? On phone music isn't necessary, video too isn't present. But another grows. How to correct it? I know only one method, it to dump all settings and a

Hi! At connection to iTunes the section "other" constantly increases. What's the matter? How to avoid it? On phone music isn't necessary, video too isn't present. But another grows. How to correct it? I know only one method, it to dump all settings and a content.

http://discussions.apple.com/docs/DOC-5142

Short dump in BP after upgrade to ECC 6.0

Hi,
We have upgraded system to ECC 6.0 from ECC 5.0
After upgrade system is giving short dump in transaction BP, event tried to navigate on BP screen.
Short dump description:
A RAISE statement in the program "CL_OS_TRANSACTION=============CP" raised the exception condition "OS_COMMIT_TOP_FAILED".
Since the exception was not intercepted by a superior program, processing was terminated.
Please advise to resolve this issue.
Regards,
Dipak

When exactly does this error appear? On save? clicking on a specific entry?
I suggest opening an OSS call for this problem, this doesn't seem to known (at least I didn't find any notes)
Markus

How to avoid short dump in ECC 5.0

Similar Messages

Maybe you are looking for