Dump in production

hi floks,
We have created one new DSO and moved to Production system. When we did data load and try activating the request we are getting a short dump. The screen shots are attached here with.
We did not face any problems in D and Q systems. Please let me know if you need any other information on this.

Hi,
may be the data volume is high and also due to non availability of background process. Try reactivating the request in Prod.
Mostly it will occur due to no background process availability.
Let us know the details.
Reg
Pra

Similar Messages

CX_SY_FILE_OPEN_MODE - short dump on production but not in Dev and Test

Hello,
I'm getting the follwoing short dump in production when I run the program which writes the data to application server. I have open data set and close data set. Same program when I in development and test I do not get any short dump. Can any know what could be cause for this.
CX_SY_FILE_OPEN_MODE
Copy paste of error analysis from ST22 short dump -
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_FILE_OPEN_MODE', was not
     caught in
    procedure "DATA_UPLOAD_APP_SERVER" "(FORM)", nor was it propagated by a RAISING
     clause.
    Since the caller of the procedure could not have anticipated that the
    exception would occur, the current program is terminated.
    The reason for the exception is:
    When accessing the file "/bw/FTPOUT/BPR/OTHER/test.csv", the system recognized
     that this file is
    not open. Therefore, the file cannot be accessed.

The file could not be OPENed in your production system for a variety of reasons - no authorization, file doesn't exist etc. You should have check sy-subrc right after OPEN DATASET and if not zero, yous should not TRANSFER or READ the file and instead you should have given a message with sy-msgid and sy-msgno which would give you the reason. The dump here is simply saying that OPEN is unsuccessful, so any subsequent READ or TRANSFER would throw runtime dump, if done after an unsuccessful OPEN.

Dump in Production due to CALL_FUNCTION_OPEN_ERROR???

Hi all,
I am getting lot of dumps in Production with following details
What happened?
Error in ABAP application program.
The current ABAP program "SAPLOLEA" had to be terminated because one of the
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
An error occurred when executing a Remote Function Call.
"Protocol error when communicating with SAPGUI."
Status of connection.... "RFC DRV=GUI INPUT"
Internal error code.... "RFC_IO20"
When communicating with SAPGUI, a protocol error was detected.
Any have Idea for this ?

Dear Vipin
That is a very complicated error, difficult to analyze.
First I would recommend an update of the SAP GUI onto the newest patch
level. Additionally please update the SAP kernel to the latest patchlevel and the RFC libraries!
If that all should not help, deeper analyses are to be made so in your system.
For that you should then create a support message.
Best regards
Sven

How to download run time ABAP dump in production environment

Hello,
I am getting run time ABAP dump in production environment. Please guide me onHow to download run time ABAP dump in production environment?
Also, please tell me how best can analyze that dump. Like there are tools like gdb, purify etc. to analyze problems in other languages.
Regards,
Sameer.

Hi,
Go to ST22, and Double click on the error line, It will show you the detailed analysis.
See the section How to correct the error for details on error correction and the instructions to download the log( you can download in the format you want - HTML would be a nice option).
And there are no tools to analyze errors but ST22 has a large data regarding the location of the error, the reason and the source code which caused. So you need to use the debugger to reproduce the error and check the source code,
Regards
Karthik D

ZReport getting dump in Production but not in Quality and development

Hi,
There isa Zreport which displays daily stock in PP module.
It is getting dump in Production not in quality and development.
Since four days it is getting dump. Before that it is fine.
Please any one guide How to resolve.
Advance Thanks.

Runtime Error SAPSQL_IN_ITAB_ILLEGAL_OPTION
 Occurred on 29.08.2007 at 08:50:13
Invalid value in OPTION field of value table for IN itab operator.
What happened?
Error in ABAP application program.
The current ABAP program "ZPPRDR417" had to be terminated because o
statements could not be executed.
This is probably due to an error in the ABAP program.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and admin
termination messages, especially those beyond their normal deletio
date.
Error analysis
The current ABAP/4 program attempted to execute an ABAP/4 Open SQL
statement in which the WHERE condition contains an IN itab operator
The IN itab operator is used with internal tables which
have the following structure:
 SIGN(1) OPTION(2) LOW LIKE db_field HIGH LIKE db_field
The OPTION column should contain only one of the following values:
 "EQ LE GE CP BT NE LT GT NP NB"
The value " " is not allowed here.
How to correct the error
Use only one of the permitted values in the OPTION column.
Information on where terminated
The termination occurred in the ABAP program "ZPPRDR417" in "WIP_STOCK_REP
The main program was "ZPPRDR417 ".
The termination occurred in line 330 of the source code of the (Include)
program "ZPPRDR417_FORM"
of the source code of program "ZPPRDR417_FORM" (when calling the editor 33
Source code extract
Caution: Program has changed
Caution: At time of termination, Active source code no longer available
003000 ? r_bwart-low = '106'.
003010 ? append r_bwart.
003020 ?
003030 ? r_bwart-low = '124'.
003040 ? append r_bwart.
003050 ?
003060 ? r_bwart-low = '125'.
003070 ? append r_bwart.
003080 ?
003090 ? select matnr
003100 ? werks
003110 ? into table i_marc
003120 ? from marc
003130 ? where ( matnr LIKE 'BILC%'
003140 ? OR matnr LIKE 'LGN%'
003150 ? OR matnr LIKE 'BRN%'
003160 ? OR matnr LIKE 'EBB%' )
003170 ? AND matnr NE 'BRN_DECLASSE'
003180 ? AND matnr NE 'BRN_SAF'
003190 ? and werks in r_werks.
003200 ?
003210 ? r_material-sign = 'I'.
003220 ? r_material-option = 'EQ'.
003230 ?
003240 ? loop at i_marc into wa_marc.
003250 ? r_material-low = wa_marc-matnr.
003260 ? append r_material.
003270 ? endloop.
003280 ? clear r_material.
003290 ?
 > ? if not i_matdoc is initial.
003310 ? select MBLNR
003320 ? MJAHR
003330 ? ZEILE
003340 ? BWART
003350 ? MATNR
003360 ? WERKS
003370 ? SHKZG
003380 ? MENGE
003390 ? UMWRK
003400 ? into table i_mseg_qty
003410 ? from mseg
003420 ? for all entries in i_matdoc
003430 ? where MBLNR eq i_matdoc-MBLNR
003440 ? and MJAHR eq i_matdoc-MJAHR
003450 ? and BWART in r_bwart
003460 ? and matnr in r_material
003470 ? and werks in r_werks.
003480 ?
003490 ? sort i_mseg_qty by matnr.

Dump in production system

Hi Experts,
I got following error description in ST22.plz can anyone tell m
what will be the probable reason for this dump. How should i correct it?
Where i need to check?
Errore run-time DBIF_REPO_PART_ALREADY_EXISTS
Analysis:
Internal problem: You attempted to insert a program which already
exists partially at least. This is probably due to an inconsistency in the database tables.

hi Sheetal,
What happened is your Basis guy might have not imported this TR properly.
I will tell what would have been your scenario. There is a program in production.
You deleted that program in developement and recreated the same and you moved it to production under one TR. Correct me if I am wrong in any of above.
Just ask your Basis to import this TR with overwrite option checked.
Reward all useful answers.
Regards,
Atish

Dump in production system :Incorrect status in pricing

Hi All,
We have patched out SRM5.5 server system recently with 15 and 16 patch.
After the patch we are getting many dums in production system.
When i check in the ST22 ,the error syaing that
Error analysis
    An exception occurred which is explained in detail below.
    The exception, which is assigned to class 'CX_BBP_PD_ABORT', was not caught and
    therefore caused a runtime error.
    The reason for the exception is:
     *Incorrect status in pricing*
How to correct the error
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "UNCAUGHT_EXCEPTION" "CX_BBP_PD_ABORT"
    "SAPLBBP_PDH" or "LBBP_PDHU08"
    "BBP_PD_ABORT"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
and i have checked the IPC ,it is also active only,.
We have got his issue all of suddenlly,
Can any one tell us what could be the issue.
Regards
cb

Hi All,
thanks a lot for your response ,
I have done the Simulation which shows everything is fine and i have chcked with BBP_CND_CUSTOMIZING_CHECK t-codes even that is also correct only .
we are plannning for rasing the issue with SAP.
Besides that the system might have activated the BADI simple pricing active (or something like that). This would give trouble as well with the IPC (they can't both be active).
@Robin which the badi we can check.
once agina thanks a lot for your replys.
Regards
cb

Short dump in Production system !!!

Hi Experts,
We have getting a short dump for all actions in Production system. Suppose if we use se38 and tried to press display it shows a short dump error. Despite when we tried to use tcodes or using LSMW or try to execute a program or like this all type of actions its throws a short dump error. Dont know what is the reason behind that since the short dump is not the defined the reason for the dumb. Have any of you experts got this type of experience?. Pls give your ideas. Thanks in advance.

Hello Kavi,
Contact your basis team. SNAP is a table which holds all ABAP dump. It looks like SNAP table is full and cannot accomodate new entries.
In any production enviornment, the SNAP entires will be deleted regularly and only dumps for the last 8 days will be available
Check if any job(SM36 or table tbtcp) is running for this program RSSNAPDL in your production system.
Thanks

TSV_TNEW_PAGE_ALLOC_FAILED Dump in Production BW 3.5 system

Hi Basis Gurus,
In our production BW 3.5 system we are getting dump in ST22.
The dump is TSV_TNEW_PAGE_ALLOC_FAILED
Please let me know what could be the reason for this dump and why we are getting it.
I tried searching in service market place and there we can find lot of things related to this dump.But not sure which one is specificaly related to this dump.
Our system details are as follows
BW 3.5
Solaris OS
Oracle Database.
Please help me in resolving this dump.
Regards,
Anil.

Hello Anil,
what is the frequency of these dumps.
If the dump once in a while,you can simply ignore it
If frequency is more....you will need to reasrch a bit before increasing the paging memory as suggested previously
Just check what program is causing the dump,is it SAP standard program or a z program created by your developers.
If it is a SAP standard program just search on market place and look if any new version of the program exists which is tuned better and which consumes less memory
If it is a z program ask your developer to tune the program(this can be a highly cause of this dump as programs created usually consume a lot of memory due to which this dump occurs)
If none of these help,go for increase in the paging memory as previusly suggested
Rohit

SAP Smartform Timeout Dump in Production for the invoice form

Hi Friends,
I am working on Invoice Smartform. It is working fine when it is having avg line items. where as in my case one invoice iss having more than 500 line items in production. For this in production it is giving timeout short dump.
In that invoice i am displaying standard fuctionality of invoice form and at the same tim i am displaying Serial Numbers based on delivery and Open Quantity based on Order. So it will take time for back processing.
Insted of Back ground processing is there any other possibility to solve this. If not Please give me some steps how to implement this form in background based on conditions (if it is having more than 200 line items then only i need to run in background else foreground)
Pls give me your valuble inputs.
Thanks,
Srinivas.

Hi Vipin,
Pls provide more details like SP level , Kernel level etc.
I can see two probable reasons:
Incorrect installtion of GUI , pls try reinstalling the GUI and then try
Kernel upgrade but this solely depends on the current level and defer for further investigation.
Best Regards
Umesh

VERY URGENT.... DUMP IN PRODUCTION STOPPED TRANSACTION .

"FUNCTION GROUP J1I7 CONTAINS ERROR"
THIS DUMP ERROR IS COMING FOR ALL EXCISE AND INVOICE TRANSACTION IN PRODUCTION.
CAN ANY BODY TELL WHY THIS ERROR COMING AFTER TRANSPORTING A REQUST.
PLEASE HELP ITS VERY CRITICAL.

Hi!
Check out the given function group in SE80 transaction and try to activate it in the production system.
It will navigate you to the error.
Regards
Tamá

Short dump in production

Hello Friends,
I have a z table and it is working fine in development and quality system and it is giving short dump error when I try to maintain the same table in production using SM30 tcode. Please suggest me what would be the issue here?
Thanks,
Shreekant

Please delete the existing table maintenance view and regenerate the same.
1. SE11 > Table Name > MODIFY
2. Menu.. UTILITIES > Table Maintenance Generator
Keep a screen shot of this screen for future use.
3. Click on DELETE in Apps tool Bar
Then regenerate the Table Maintenance View, as usual.
Regard
Vishal

Manny Dumps in production Please helps

I am facing a suddenly a problem in Production server
In sm50 work process get stop one by one and if try to restart again it get stop.
Ther are many dumps of 2 types but in different Tx and Table
(DBIF_RSQL_INVALID_REQUEST, TEXTENV_UNICODE_LANGU_INVALID)in the system .
In sm21 there is like to error like these
21:00:43 DIA 023 R19 Initialization DB-Connect Failed, Return Code 000256
21:00:43 DIA 023 Q02 Stop Workproc23, PID 7384
21:00:43 SPO 034 BY2 Database error 12560 at CON
21:00:43 SPO 034 BY0 > ORA-12560: TNS:protocol adapter error
21:00:43 SPO 034 BY2 Database error 12560 at CON
21:00:43 SPO 034 BY0 > ORA-12560: TNS:protocol adapter error
21:00:43 SPO 034 R19 Initialization DB-Connect Failed, Return Code 000256
21:00:43 SPO 034 Q02 Stop Workproc34, PID 1920
21:00:43 DIA 015 BY2 Database error 12560 at CON
21:00:43 DIA 015 BY0 > ORA-12560: TNS:protocol adapter error
21:00:43 DIA 015 BY2 Database error 12560 at CON
21:00:43 DIA 015 BY0 > ORA-12560: TNS:protocol adapter error
21:00:43 DIA 015 R19 Initialization DB-Connect Failed, Return Code 000256
21:00:43 DIA 015 Q02 Stop Workproc15, PID 8820
21:00:43 DIA 013 BY2 Database error 12560 at CON
21:00:43 DIA 013 BY0 > ORA-12560: TNS:protocol adapter error
21:00:43 DIA 013 BY2 Database error 12560 at CON
21:00:43 DIA 013 BY0 > ORA-12560: TNS:protocol adapter error
21:00:43 DIA 013 R19 Initialization DB-Connect Failed, Return Code 000256
21:00:43 DIA 013 Q02 Stop Workproc13, PID 8236
21:05:10 WRK 000 Q0Q Start Workproc 1, Pid 7012
21:05:10 WRK 000 Q0Q Start Workproc 0, Pid 4252
21:05:10 WRK 000 Q0Q Start Workproc 6, Pid 9112
21:05:43 SPO 033 R19 Initialization DB-Connect Failed, Return Code 000256
21:05:43 SPO 033 Q02 Stop Workproc33, PID 7060
21:05:43 BTC 029 BY2 Database error 12560 at CON
21:05:43 BTC 029 BY0 > ORA-12560: TNS:protocol adapter error
21:05:43 BTC 029 BY2 Database error 12560 at CON
21:05:43 BTC 029 BY0 > ORA-12560: TNS:protocol adapter error
21:05:43 BTC 029 R19 Initialization DB-Connect Failed, Return Code 000256
21:05:43 BTC 029 Q02 Stop Workproc29, PID 4288
21:05:43 DIA 014 BY2 Database error 12560 at CON
21:05:43 DIA 014 BY0 > ORA-12560: TNS:protocol adapter error
21:05:43 DIA 014 BY2 Database error 12560 at CON
21:05:43 DIA 014 BY0 > ORA-12560: TNS:protocol adapter error
21:05:43 DIA 014 R19 Initialization DB-Connect Failed, Return Code 000256
21:05:43 DIA 014 Q02 Stop Workproc14, PID 9456
21:05:43 DP Q0I Operating system call gethostbyaddr failed (error no. 0 )
21:05:43 DP Q04 Connection to user 5740 ( ), terminal 66 (HOLT088 ) lost
21:07:10 ENQ 027 Q02 Stop Workproc27, PID 6888
21:07:10 ENQ 027 Q02 Stop Workproc27, PID 6888
21:07:11 RD S30 SAP gateway was closed
21:07:11 RD S30 SAP gateway was closed
21:07:13 DP Q0M Message server disconnected
21:07:13 DP Q05 R/3 System stop, dispatcher PID 83
21:07:13 MS Q02 Stop Msg Server, PID 10236
21:07:13 DP Q0M Message server disconnected
21:07:13 DP Q05 R/3 System stop, dispatcher PID 83
At present listener is up and running and sap is working. It happen suddenely and after restart of R/3 system it ok but same thing happen today also. we are using windows 2003 Enterprise in server.
Please help
Best Regards,
Kumar
Edited by: Kumar on Aug 28, 2008 7:18 AM
Edited by: Kumar on Aug 28, 2008 7:20 AM

Dear All,
Please find the dev_disp log
trc file: "dev_disp", trc level: 1, release: "640"
kernel runs with dp version 130000(ext=102000) (@(#) DPLIB-INT-VERSION-130000-UC)
length of sys_adm_ext is 524 bytes
sysno 00
sid **
systemid 561 (PC with Windows NT)
relno 6400
patchlevel 0
patchno 129
intno 20020600
make: multithreaded, Unicode, 64 bit
pid 6164
***LOG Q00=> DpSapEnvInit, DPStart (00 6164) [dpxxdisp.c 1098]
 shared lib "dw_xml.dll" version 129 successfully loaded
 shared lib "dw_xtc.dll" version 129 successfully loaded
 shared lib "dw_stl.dll" version 129 successfully loaded
 shared lib "dw_gui.dll" version 129 successfully loaded
 shared lib "dw_mdm.dll" version 129 successfully loaded
Wed Aug 27 21:07:24 2008
WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds
***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 3893]
MtxInit: -2 0 0
DpSysAdmExtInit: ABAP is active
DpIPCInit2: start server >rfcl-sap-vir_PRD_00 <
DpShMCreate: sizeof(wp_adm) 51328 (1316)
DpShMCreate: sizeof(tm_adm) 35937968 (17960)
DpShMCreate: sizeof(wp_ca_adm) 80000 (80)
DpShMCreate: sizeof(appc_ca_adm) 160000 (80)
DpShMCreate: sizeof(comm_adm) 1248000 (624)
DpShMCreate: sizeof(vmc_adm) 0 (512)
DpShMCreate: sizeof(wall_adm) (416064/346352/64/192)
DpShMCreate: SHM_DP_ADM_KEY (addr: 000000000D110050, size: 38247047)
DpShMCreate: allocated sys_adm at 000000000D110050
DpShMCreate: allocated wp_adm at 000000000D111C30
DpShMCreate: allocated tm_adm_list at 000000000D11E4B0
DpShMCreate: allocated tm_adm at 000000000D11E4E0
DpShMCreate: allocated wp_ca_adm at 000000000F364390
DpShMCreate: allocated appc_ca_adm at 000000000F377C10
DpShMCreate: allocated comm_adm_list at 000000000F39ED10
DpShMCreate: allocated comm_adm at 000000000F39ED30
DpShMCreate: allocated vmc_adm_list at 000000000F4CF830
DpShMCreate: system runs without vmc_adm
DpShMCreate: allocated ca_info at 000000000F4CF860
DpShMCreate: allocated wall_adm at 000000000F4CF870
MBUF state OFF
EmInit: MmSetImplementation( 2 ).
<ES> client 0 initializing ....
<ES> InitFreeList
<ES> block size is 4096 kByte.
Using implementation flat
<EsNT> Memory Reset disabled as NT default
<ES> 1226 blocks reserved for free list.
ES initialized.
Wed Aug 27 21:07:25 2008
rdisp/http_min_wait_dia_wp : 1 -> 1
***LOG CPS=> DpLoopInit, ICU ( 2.6 2.6 4.0) [dpxxdisp.c 1466]
**LOG Q0K=> DpMsAttach, mscon (**) []
use SAPLOCALHOST***> as internal hostname
DpStartStopMsg: send start message (myname is ***<)
DpStartStopMsg: start msg sent
CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.
Wed Aug 27 21:07:27 2008
CCMS: start to initalize 3.X shared alert area (first segment).
DpMsgAdmin: Set release to 6400, patchlevel 0
MBUF state PREPARED
MBUF component UP
DpMBufHwIdSet: set Hardware-ID
***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1025]
DpMsgAdmin: Set patchno for this platform to 129
Release check o.K.
Wed Aug 27 21:07:50 2008
MBUF state ACTIVE
DpModState: change server state from STARTING to ACTIVE
Wed Aug 27 21:18:22 2008
***LOG Q0I=> NiPRead: recv (10054: WSAECONNRESET: Connection reset by peer) [ninti.c 789]
Network error of client T39, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3
Wed Aug 27 21:18:24 2008
Client address of T39 is >####->###- ###<)< .107(***)
***LOG Q04=> DpRTmPrep, NiBufReceive (54 ***) [dpxxdisp.c 9632]
RM-T39, U54, 600 ***, ***, M0, W0, SESS, 2/0
Wed Aug 27 21:19:34 2008
***LOG Q0I=> NiPRead: recv (10054: WSAECONNRESET: Connection reset by peer) [ninti.c 789]
Network error of client T40, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3
Wed Aug 27 21:19:35 2008
Client address of T40 is >####->###- ###<)< .34(>####->###- ###<)< ->####->###- ###<)< )
***LOG Q04=> DpRTmPrep, NiBufReceive (59 ***) [dpxxdisp.c 9632]
RM-T40, U59, 600 ***, 21:18:41, M0, W0, SESS, 2/0
Wed Aug 27 21:38:45 2008
DpHdlDeadWp: restart wp (pid=2484) automatically
Wed Aug 27 21:39:05 2008
Wed Aug 27 21:41:05 2008
DpHdlDeadWp: restart wp (pid=1900) automatically
Wed Aug 27 21:48:05 2008
DpHdlDeadWp: restart wp (pid=4384) automatically
Wed Aug 27 22:01:05 2008
DpHdlDeadWp: restart wp (pid=4500) automatically
Wed Aug 27 22:01:45 2008
DpHdlDeadWp: restart wp (pid=2028) automatically
Wed Aug 27 22:09:45 2008
DpHdlDeadWp: restart wp (pid=9536) automatically
Wed Aug 27 22:10:05 2008
DpHdlDeadWp: restart wp (pid=1972) automatically
DpHdlDeadWp: restart wp (pid=7596) automatically
DpHdlDeadWp: restart wp (pid=10104) automatically
DpHdlDeadWp: restart wp (pid=6296) automatically
DpHdlDeadWp: restart wp (pid=7720) automatically
Wed Aug 27 22:12:05 2008
DpHdlDeadWp: restart wp (pid=2428) automatically
Wed Aug 27 22:28:05 2008
DpHdlDeadWp: restart wp (pid=9992) automatically
Wed Aug 27 22:34:24 2008
***LOG Q0I=> NiPRead: recv (10054: WSAECONNRESET: Connection reset by peer) [ninti.c 789]
Network error of client T40, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3
Wed Aug 27 22:34:29 2008
***LOG Q0I=> NiPGetHostByAddr: address ***not found: gethostbyaddr [ninti.c 379]
Client address of T40 is *** (***)
***LOG Q04=> DpRTmPrep, NiBufReceive (122 ***) [dpxxdisp.c 9632]
RM-T40, U122, 600 ***, ***M0, W0, ZVN1, 2/2
Wed Aug 27 22:35:49 2008
DpHdlDeadWp: restart wp (pid=7132) automatically
Wed Aug 27 22:40:49 2008
DpHdlDeadWp: restart wp (pid=9272) automatically
DpHdlDeadWp: restart wp (pid=7896) automatically
DpHdlDeadWp: restart wp (pid=8856) automatically
DpHdlDeadWp: restart wp (pid=8272) automatically
Wed Aug 27 22:41:49 2008
DpHdlDeadWp: restart wp (pid=1372) automatically
DpHdlDeadWp: restart wp (pid=8276) automatically
Wed Aug 27 22:56:49 2008
DpHdlDeadWp: restart wp (pid=10128) automatically
Wed Aug 27 23:07:49 2008
DpHdlDeadWp: restart wp (pid=4476) automatically
Wed Aug 27 23:11:49 2008
DpHdlDeadWp: restart wp (pid=8404) automatically
Wed Aug 27 23:13:49 2008
DpHdlDeadWp: restart wp (pid=9268) automatically
Wed Aug 27 23:14:49 2008
DpHdlDeadWp: restart wp (pid=6472) automatically
Wed Aug 27 23:15:03 2008
***LOG Q0I=> NiPRead: recv (10054: WSAECONNRESET: Connection reset by peer) [ninti.c 789]
Network error of client T42, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3
Wed Aug 27 23:15:09 2008
***LOG Q0I=> NiPGetHostByAddr: address ***not found: gethostbyaddr [ninti.c 379]
WARNING => NiAddrToHost took 6 seconds [dpxxdisp.c 16611]
Client address of T42 is *** (***)
***LOG Q04=> DpRTmPrep, NiBufReceive (165 ****** ) [dpxxdisp.c 9632]
RM-T42, U165, 600 RFCL-CFA-AHDHOLT267, HOLT267, 23:10:06, M0, W0, ZVN1, 2/2
Wed Aug 27 23:29:49 2008
DpHdlDeadWp: restart wp (pid=8020) automatically
Wed Aug 27 23:31:09 2008
DpHdlDeadWp: restart wp (pid=9936) automatically
Wed Aug 27 23:41:29 2008
DpHdlDeadWp: restart wp (pid=1972) automatically
Wed Aug 27 23:41:49 2008
DpHdlDeadWp: restart wp (pid=9168) automatically
Wed Aug 27 23:41:50 2008
DpHdlDeadWp: restart wp (pid=5180) automatically
DpHdlDeadWp: restart wp (pid=5568) automatically
DpHdlDeadWp: restart wp (pid=5964) automatically
DpHdlDeadWp: restart wp (pid=7352) automatically
DpHdlDeadWp: restart wp (pid=5464) automatically
DpHdlDeadWp: restart wp (pid=9080) automatically
DpHdlDeadWp: restart wp (pid=9316) automatically
Wed Aug 27 23:42:09 2008
DpHdlDeadWp: restart wp (pid=9284) automatically
Wed Aug 27 23:42:49 2008
DpHdlDeadWp: restart wp (pid=640) automatically
Wed Aug 27 23:45:49 2008
DpHdlDeadWp: restart wp (pid=5712) automatically
Wed Aug 27 23:47:49 2008
DpHdlDeadWp: restart wp (pid=4872) automatically
Thu Aug 28 00:01:49 2008
DpHdlDeadWp: restart wp (pid=6648) automatically
Thu Aug 28 00:02:09 2008
DpHdlDeadWp: restart wp (pid=6380) automatically
Thu Aug 28 00:02:29 2008
DpHdlDeadWp: restart wp (pid=7656) automatically
Thu Aug 28 00:11:49 2008
DpHdlDeadWp: restart wp (pid=1576) automatically
Thu Aug 28 00:16:48 2008
***LOG Q0I=> NiPRead: recv (10054: WSAECONNRESET: Connection reset by peer) [ninti.c 789]
Network error of client T40, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3
Thu Aug 28 00:16:54 2008
***LOG Q0I=> NiPGetHostByAddr: address ******not found: gethostbyaddr [ninti.c 379]
WARNING => NiAddrToHost took 6 seconds [dpxxdisp.c 16611]
Client address of T40 is *(**)
***LOG Q04=> DpRTmPrep, NiBufReceive (201 ******) [dpxxdisp.c 9632]
RM-T40, U201, 600 ****, ***7, 00:11:42, M0, W1, ZVSL, 2/1
Thu Aug 28 03:59:54 2008
DpHdlDeadWp: restart wp (pid=6008) automatically
Thu Aug 28 04:00:54 2008
DpHdlDeadWp: restart wp (pid=1776) automatically
Thu Aug 28 05:01:14 2008
DpHdlDeadWp: restart wp (pid=7496) automatically
Thu Aug 28 05:04:14 2008
DpHdlDeadWp: restart wp (pid=7848) automatically
Thu Aug 28 05:07:14 2008
DpHdlDeadWp: restart wp (pid=9600) automatically
Thu Aug 28 05:14:54 2008
DpHdlDeadWp: restart wp (pid=480) automatically
Thu Aug 28 06:25:54 2008
DpHdlDeadWp: restart wp (pid=7404) automatically
Thu Aug 28 06:26:54 2008
DpHdlDeadWp: restart wp (pid=9508) automatically
***LOG Q0I=> NiPRead: recv (10054: WSAECONNRESET: Connection reset by peer) [ninti.c 789]
Network error of client T44, NiBufReceive (-6: NIECONN_BROKEN), dp_tm_status=3
Thu Aug 28 06:32:07 2008
***LOG Q0I=> NiPGetHostByAddr: address ****** not found: gethostbyaddr [ninti.c 379]
WARNING => NiAddrToHost took 6 seconds [dpxxdisp.c 16611]
Client address of T44 is **(*)
***LOG Q04=> DpRTmPrep, NiBufReceive (255 &&&& ) [dpxxdisp.c 9632]
RM-T44, U255, 600 ****, 06:27:03, M0, W0, SQVI, 2/2
Thu Aug 28 06:39:54 2008
DpHdlDeadWp: restart wp (pid=2080) automatically
Thu Aug 28 06:47:54 2008
DpHdlDeadWp: restart wp (pid=6620) automatically
Thu Aug 28 06:48:34 2008
DpHdlDeadWp: restart wp (pid=6856) automatically
Thu Aug 28 06:50:54 2008
DpHdlDeadWp: restart wp (pid=8780) automatically
Thu Aug 28 06:51:14 2008
ERROR => W28 (pid 2104) died [dpxxdisp.c 12414]
Thu Aug 28 06:53:34 2008
ERROR => W28 (pid 7484) died [dpxxdisp.c 12414]
Thu Aug 28 06:55:54 2008
DpHdlDeadWp: restart wp (pid=4212) automatically
Thu Aug 28 06:56:34 2008
ERROR => W1 (pid 7940) died [dpxxdisp.c 12414]
Thu Aug 28 06:56:54 2008
DpHdlDeadWp: restart wp (pid=9144) automatically
Thu Aug 28 06:57:34 2008
ERROR => W33 (pid 8824) died [dpxxdisp.c 12414]
Thu Aug 28 06:57:54 2008
DpHdlDeadWp: restart wp (pid=3640) automatically
DpHdlDeadWp: restart wp (pid=8420) automatically
Thu Aug 28 06:58:34 2008
ERROR => W1 (pid 9156) died [dpxxdisp.c 12414]
ERROR => W5 (pid 7220) died [dpxxdisp.c 12414]
ERROR => W28 (pid 8444) died [dpxxdisp.c 12414]
ERROR => W33 (pid 5500) died [dpxxdisp.c 12414]
ERROR => W34 (pid 8076) died [dpxxdisp.c 12414]
Thu Aug 28 06:58:54 2008
DpHdlDeadWp: restart wp (pid=6692) automatically
Thu Aug 28 06:59:34 2008
ERROR => W35 (pid 1996) died [dpxxdisp.c 12414]
Thu Aug 28 06:59:54 2008
DpHdlDeadWp: restart wp (pid=8832) automatically
DpHdlDeadWp: restart wp (pid=6644) automatically
Thu Aug 28 07:00:34 2008
ERROR => W29 (pid 8108) died [dpxxdisp.c 12414]
ERROR => W36 (pid 6760) died [dpxxdisp.c 12414]
my types changed after wp death/restart 0xbf --> 0xaf
Thu Aug 28 07:01:34 2008
DpHdlDeadWp: restart wp (pid=8304) automatically
Thu Aug 28 07:02:54 2008
my types changed after wp death/restart 0xa7 --> 0xbf
Thu Aug 28 07:03:34 2008
ERROR => W1 (pid 1716) died [dpxxdisp.c 12414]
ERROR => W2 (pid 9320) died [dpxxdisp.c 12414]
ERROR => W5 (pid 5296) died [dpxxdisp.c 12414]
ERROR => W28 (pid 6256) died [dpxxdisp.c 12414]
ERROR => W29 (pid 8468) died [dpxxdisp.c 12414]
ERROR => W30 (pid 9000) died [dpxxdisp.c 12414]
ERROR => W31 (pid 5612) died [dpxxdisp.c 12414]
ERROR => W32 (pid 3844) died [dpxxdisp.c 12414]
my types changed after wp death/restart 0xbf --> 0xb7
ERROR => W33 (pid 1700) died [dpxxdisp.c 12414]
ERROR => W34 (pid 1268) died [dpxxdisp.c 12414]
ERROR => W35 (pid 9048) died [dpxxdisp.c 12414]
ERROR => W36 (pid 9668) died [dpxxdisp.c 12414]
my types changed after wp death/restart 0xb7 --> 0xa7
Thu Aug 28 07:07:54 2008
my types changed after wp death/restart 0xa7 --> 0xbf
DpHdlDeadWp: restart wp (pid=1172) automatically
Thu Aug 28 07:11:54 2008
DpHdlDeadWp: restart wp (pid=6484) automatically
Thu Aug 28 07:12:34 2008
ERROR => W3 (pid 1700) died [dpxxdisp.c 12414]
Thu Aug 28 07:17:54 2008
my types changed after wp death/restart 0xa7 --> 0xbf
DpHdlDeadWp: restart wp (pid=8212) automatically
DpHdlDeadWp: restart wp (pid=9276) automatically
Thu Aug 28 07:18:34 2008
ERROR => W2 (pid 1936) died [dpxxdisp.c 12414]
DpHdlDeadWp: restart wp (pid=5108) automatically
ERROR => W7 (pid 3644) died [dpxxdisp.c 12414]
Thu Aug 28 07:18:54 2008
DpHdlDeadWp: restart wp (pid=708) automatically
ERROR => W4 (pid 1560) died [dpxxdisp.c 12414]
Thu Aug 28 07:19:14 2008
ERROR => W0 (pid 8636) died [dpxxdisp.c 12414]
Thu Aug 28 07:19:34 2008
DpHdlDeadWp: restart wp (pid=1736) automatically
Thu Aug 28 07:19:54 2008
ERROR => W11 (pid 9428) died [dpxxdisp.c 12414]
DpHdlDeadWp: restart wp (pid=7572) automatically
DpWpRestart: pid 8056 of WP12 also found for WP28 - removed
ERROR => W28 (pid 8056) died [dpxxdisp.c 12414]
DpHdlDeadWp: restart wp (pid=5932) automatically
DpWpRestart: pid 4248 of WP13 also found for WP31 - removed
ERROR => W31 (pid 4248) died [dpxxdisp.c 12414]
DpHdlDeadWp: restart wp (pid=1988) automatically
DpWpRestart: pid 5220 of WP14 also found for WP33 - removed
ERROR => W33 (pid 5220) died [dpxxdisp.c 12414]
Thu Aug 28 07:20:14 2008
ERROR => W12 (pid 8056) died [dpxxdisp.c 12414]
ERROR => W13 (pid 4248) died [dpxxdisp.c 12414]
ERROR => W14 (pid 5220) died [dpxxdisp.c 12414]
Thu Aug 28 07:20:34 2008
DpHdlDeadWp: restart wp (pid=1348) automatically
Thu Aug 28 07:20:54 2008
DpHdlDeadWp: restart wp (pid=6220) automatically
Thu Aug 28 07:21:14 2008
ERROR => W15 (pid 6096) died [dpxxdisp.c 12414]
ERROR => W16 (pid 4264) died [dpxxdisp.c 12414]
Thu Aug 28 07:21:34 2008
DpHdlDeadWp: restart wp (pid=8708) automatically
Thu Aug 28 07:47:54 2008
my types changed after wp death/restart 0xa6 --> 0xbf
Thu Aug 28 07:48:34 2008
ERROR => W0 (pid 6496) died [dpxxdisp.c 12414]
ERROR => W1 (pid 6772) died [dpxxdisp.c 12414]
ERROR => W2 (pid 6264) died [dpxxdisp.c 12414]
ERROR => W3 (pid 6760) died [dpxxdisp.c 12414]
ERROR => W4 (pid 5772) died [dpxxdisp.c 12414]
ERROR => W5 (pid 9164) died [dpxxdisp.c 12414]
ERROR => W6 (pid 5244) died [dpxxdisp.c 12414]
ERROR => W7 (pid 7908) died [dpxxdisp.c 12414]
ERROR => W8 (pid 9604) died [dpxxdisp.c 12414]
ERROR => W9 (pid 4472) died [dpxxdisp.c 12414]
ERROR => W10 (pid 7164) died [dpxxdisp.c 12414]
ERROR => W11 (pid 1996) died [dpxxdisp.c 12414]
ERROR => W12 (pid 9864) died [dpxxdisp.c 12414]
ERROR => W13 (pid 1848) died [dpxxdisp.c 12414]
ERROR => W14 (pid 8348) died [dpxxdisp.c 12414]
ERROR => W15 (pid 4536) died [dpxxdisp.c 12414]
ERROR => W16 (pid 5808) died [dpxxdisp.c 12414]
ERROR => W17 (pid 5444) died [dpxxdisp.c 12414]
ERROR => W18 (pid 7444) died [dpxxdisp.c 12414]
ERROR => W19 (pid 1160) died [dpxxdisp.c 12414]
ERROR => W20 (pid 2028) died [dpxxdisp.c 12414]
ERROR => W21 (pid 4364) died [dpxxdisp.c 12414]
ERROR => W22 (pid 8752) died [dpxxdisp.c 12414]
ERROR => W23 (pid 3944) died [dpxxdisp.c 12414]
my types changed after wp death/restart 0xbf --> 0xbe
ERROR => W28 (pid 8952) died [dpxxdisp.c 12414]
ERROR => W29 (pid 7804) died [dpxxdisp.c 12414]
ERROR => W30 (pid 4940) died [dpxxdisp.c 12414]
ERROR => W31 (pid 8292) died [dpxxdisp.c 12414]
ERROR => W32 (pid 9200) died [dpxxdisp.c 12414]
my types changed after wp death/restart 0xbe --> 0xb6
ERROR => W33 (pid 7888) died [dpxxdisp.c 12414]
ERROR => W34 (pid 4396) died [dpxxdisp.c 12414]
ERROR => W35 (pid 5496) died [dpxxdisp.c 12414]
ERROR => W36 (pid 8252) died [dpxxdisp.c 12414]
my types changed after wp death/restart 0xb6 --> 0xa6
Thu Aug 28 07:50:00 2008
DpSigInt: caught signal 2
DpHalt: shutdown server >####->###- ###<)< (normal)
DpModState: change server state from ACTIVE to SHUTDOWN
Stop work processes...
Thu Aug 28 07:50:01 2008
Stop gateway
Stop icman
Terminate gui connections
waiting for termination of gateway
Thu Aug 28 07:50:02 2008
waiting for termination of icman
Thu Aug 28 07:50:03 2008
DpStartStopMsg: send stop message (myname is >###- ###<)
DpStartStopMsg: stop msg sent
Thu Aug 28 07:50:04 2008
DpHalt: sync with message server o.k.
detach from message server
***LOG Q0M=> DpMsDetach, ms_detach () [dpxxdisp.c 10153]
MBUF state OFF
MBUF component DOWN
***LOG Q05=> DpHalt, DPStop ( 6164) [dpxxdisp.c 8643]
Thanks
Kumar
Edited by: Kumar on Aug 28, 2008 9:30 AM

Too many abap dumps in production system

gurus ,
i have a doubt . there was around 56 abap dumps by a single user .
i just want to know whether having these much of abap dumps in the production will hit performance system in a way or other ?
if so i can make alert them on the criticality of running a report in production .

"the problem is , most of the dumps are SYNTAX_ERROR which are generated by the customized reports created by the users"
Good! I much prefer them to the "there is something wrong with your system" type dumps.
"these people make a direct attempt in production directly resulting in lot of dumps .
we have a quality client with the latest production datas , but they dont do their first .
i am not sure whether this practice will really hit any performance issue .
if so then i can insist them the importance of being alert before making an attempt in production"
Bad, bad, bad practise.
As you have mentioned a QA system, I'm assuming that you have at least a 3 tier landscape ... tell the developers to use it!
p.s - the problem isn't so much that the users are running the reports directly in Prod, it's that the reports haven't been tested properly before they reach the Prod system !

Short dump on production server

ABAP runtime errors    GETWA_NOT_ASSIGNED
       Occurred on     28.12.2007 at 11:16:11
>> Short dump has not been completely stored. It is too big.
Field symbol has not yet been assigned.
What happened?
The current ABAP/4 program "SAPLCEI0 " had to be terminated because
one of the statements could not be executed.
This is probably due to an error in the ABAP/4 program.
What can you do?
Note the actions and input that caused the error.
Inform your SAP system administrator.
You can print out this message by choosing "Print". Transaction ST22
allows you to display and manage termination messages, including keeping
them beyond their normal deletion date.
Error analysis
You attempted to access an unassigned field symbol
(data segment 2941).
This error occurs:
- if you address a typed field symbol before it has been set with
ASSIGN or
- if you address a field symbol that has been reset with UNASSIGN
or pointed to a local field that no longer exists, or
- if you address a field symbol that pointed to a line of an internal
table that has now been deleted, or
- if you address a global function interface partameter, even
though the relevant function module is not active,
i.e. it is not in the list of active calls. You can get the list
of active calls from the this short dump.
How to correct the error
If the error occurred in a non-modified SAP program, you may be
able to find a solution in the SAP note system.
If you have access to the note system yourself, use the following
search criteria:
"GETWA_NOT_ASSIGNED"
"SAPLCEI0 " or "LCEI0U29 "
"CEI0_DDB_HAS_VALUES_INTERNAL"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
   To obtain this, select the "Print" function on the current screen.
2. A suitable hardcopy prinout of the system log.
   To obtain this, call the system log with Transaction SM21
   and select the "Print" function to print out the relevant
   part.
3. If the programs are your own programs or modified SAP programs,
   supply the source code.
   To do this, you can either use the "PRINT" command in the editor or
   print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
   or which actions and input led to the error.
System environment
SAP Release.............. "46C"
Application server....... "SAPCLUN"
Network address.......... "172.18.112.20"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "16x Intel 80158"
Database server.......... "DBCLUN"
Database type............ "MSSQL"
Database name............ "PRD"
Database owner........... "dbo"
Character set............ "English_United State"
SAP kernel............... "46D"
Created on............... "Apr 9 2006 21:37:58"
Created in............... "NT 4.0 1381 Service Pack 6 x86 MS VC++ 12.00"
Database version......... "SQL_Server_7.00 "
Patch level.............. "2225"
Patch text............... " "
Supported environment....
Database................. "MSSQL 6.5.213 or higher, MSSQL 7.0.1 or higher"
SAP database version..... "46D"
Operating system......... "Windows NT 4.0, Windows NT 5.0, Windows NT 5.1,
Windows NT 5.2, , System build information:,
, LCHN : "
User, transaction...
Client.............. 400
User................ "QPBASIC"
Language key........ "E"
Transaction......... "QA02 "
Program............. "SAPLCEI0 "
Screen.............. "SAPLQPL1 0200"
Screen line......... 34
Information on where termination occurred
The termination occurred in the ABAP/4 program "SAPLCEI0 " in
"CEI0_DDB_HAS_VALUES_INTERNAL".
The main program was "SAPLQPL1 ".
The termination occurred in line 49
of the source code of program "LCEI0U29 " (when calling the editor 490).
Source code extract
000190   *" EXCEPTIONS
000200   *"      NOT_FOUND
000210   *"----
000220
000230     DATA:
000240           ls_charac TYPE api_char,
000250           lt_charac TYPE STANDARD TABLE OF api_char,
000260           ls_vali   TYPE api_vali.
000270
000280     DATA: ls_mi        TYPE ts_mi,
000290           ls_wi        TYPE ts_wi,
000300           ls_icv       TYPE ts_value,
000310           ls_defval    TYPE ts_defval,
000320           ls_inco_val TYPE ts_inco_val,
000330           ls_char_list TYPE ts_char_list,
000340           lv_subrc     TYPE sy-subrc,
000350           lv_kntype    TYPE cukntype.
000360
000370   data: ls_vallist   TYPE ddb_c04,                             "676840
000380         lt_vallist   TYPE STANDARD TABLE OF ddb_c04,           "676840
000390         ls_restrict type ddb_c03,                             "699141
000400         lt_restrict type STANDARD TABLE OF ddb_c03,           "699141
000410         lv_rflag       type c.                                 "676840
000420
000430   *----
000440     REFRESH exp_values.
000450
000460     DESCRIBE TABLE imp_characteristics LINES sy-tfill.
000470     IF sy-tfill EQ 0.
000480       LOOP AT
        INTO   ls_char_list.
000500         ls_charac-atinn = ls_char_list-atinn.
000510         APPEND ls_charac TO lt_charac.
000520       ENDLOOP.
000530     ELSE.
000540       lt_charac = imp_characteristics[].
000550     ENDIF.
000560
000570     LOOP AT   lt_charac
000580          INTO ls_charac.
000590       IF ls_charac-atnam NE space.
000600   *     input: name
000610         PERFORM read_mi_with_atnam
000620                 USING
000630                   ls_charac-atnam
000640                 CHANGING
000650                   lv_subrc
000660                   ls_mi.
000670       ELSE.
000680   *     input: atinn
Contents of system fields
SY field contents..................... SY field contents.....................
SY-SUBRC 0                             SY-INDEX 0
SY-TABIX 0                             SY-DBCNT 1
SY-FDPOS 1                             SY-LSIND 0
SY-PAGNO 0                             SY-LINNO 1
SY-COLNO 1
Chosen variables
Name.......................... Contents.1........2........3....+....4
PROP_BITMAP                    310
                               3000
                               6100
ALLOWED_VALUES
                               2
                               0
PROP_WIDTH                     300
                               2000
                               C100
ASSIGNED_VALUES                X
                               5
                               8
TOP_WINDOW                     33
                               2000
                               1000
ASSIGNED_VALUES_API_DI
                               2
                               0
PROP_INDEX                     350
                               5000
                               E100
DEFAULT_VALUES
                               2
                               0
DYNPRO_9                       19
                               1000
                               3000
DEFAULT_VALUES_API_DN
                               2
                               0
DYNPRO_8                       18
                               1000
                               2000
DEFAULT_VALUES_API_ST
                               2
                               0
DYNPRO_7                       17
                               1000
                               1000
DOCUMENT_INFO
                               2
                               0
PROP_SOUND                     340
                               5000
                               4100
FIRST_ASSIGNED_VALUE
                               2
                               0
PROP_TEXT                      330
                               4000
                               A100
INCONSISTENT_VALUES
                               2
                               0
LANGUAGE                       E
                               4
                               5
SY-LANGU                       E
                               4
                               5
PROP_BITMAP_STYLE              320
                               4000
                               0100
VALID_VALUES
                               2
                               0
PROP_FONT_SIZE                 380
                               7000
                               C100
EXP_VALUES[]                   #########################À##°###########
                               0000000000000000000000000C00B00000000000
                               00000000000000000000000040000A0000000000
... + 40                      ################ÿÿÿÿ####################
                               0000000000000000FFFF00000000000000000000
                               1000000000001000FFFF81007000430000000000
... + 80                      ################################
                               00000000000000000000000000008000
                               00000000000000000000000000004100
PROP_ITEM                      370
                               7000
                               2100
IMP_CHARACTERISTICS[]          #########################À##############
                               0000000000000000000000000C00800000000000
                               00000000000000000000000040000A0000000000
... + 40                      ################ÿÿÿÿI###################
                               1000000000000000FFFF40000000000000000000
                               0000000000000000FFFF90002000430000000000
... + 80                      ################################
                               00000000000000000000000000008000
                               00000000000000000000000000005100
SCREEN-ACTIVE                  0
                               3
                               0
SY-XPROG                       SAPCNVE
                               5454454222222222222222222222222222222222
                               3103E65000000000000000000000000000000000
TVS_EDITLABELS                 6
                               0000
                               6000
SY-TFILL                       0
                               0000
                               0000
INCL_PRICE                     0000
                               3333
                               0000
LS_CHAR_LIST                   00000000000000000000
                               3333333333333333333322222222222
                               0000000000000000000000000000000
RSJOBINFO                                                      00000000
                               2222222222222222222222222222222233333333
                               0000000000000000000000000000000000000000
... + 40                      000000
                               3333332222222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 80                      ####
                               0000
                               0000
SYST                           ########################################
                               0000000000000000000000000000000000000000
                               0000000000000000000000000000000000000000
... + 40                      ####################################I###
                               0000000000000000000000000000000000004000
                               1000100010000000100000000000000000009000
... + 80                      ########################################
                               0000000000000000100000000000000000000000
                               0000000000000000E00000000000000000000000
... + 120                      ####################################p###
                               00000000
                               0000000
LT_CHARAC                      Table[initial]
                               0000FFFD
                               0000FFFF
LS_CHARAC                      0000000000
                               3333333333222222222222222222222222222222
                               0000000000000000000000000000000000000000
... + 40
                               222222222222222222222222222222222
                               000000000000000000000000000000000
SPACE
                               2
                               0
Active calls / events
No.... Type........ Name..........................
       Programm
       Include                                  Line
     1 FUNCTION     CEI0_DDB_HAS_VALUES_INTERNAL
       SAPLCEI0
       LCEI0U29                                    49
     2 FUNCTION     QMCF_CONFIGURATION_READ
       SAPLQMCF
       LQMCFU02                                    61
     3 FUNCTION     QMCF_SPECIFICATION_CONFIG_READ
       SAPLQMCF
       LQMCFU01                                    60
     4 FUNCTION     QPAP_PLAN_READ
       SAPLQPAP
       LQPAPU02                                   297
     5 FUNCTION     QEEV_TABLES_GENERATE
       SAPLQEEV
       LQEEVU01                                   118
     6 FORM         MERKMALSSAETZE_ANLEGEN
       SAPLQPL1
       LQPL1F12                                    85
     7 FORM         ST_RECHNE_571
       SAPLQPL1
       LQPL1F1L                                    26
     8 FORM         OK_PROBENBERECHNUNG
       SAPLQPL1
       LQPL1F1W                                    23
     9 FORM         FCODE_BEARBEITEN
       SAPLV00F
       LV00FF0F                                    97
    10 FUNCTION     SCREEN_SEQUENCE_CONTROL
       SAPLV00F
       LV00FU02                                    46
    11 FORM         FCODE
       SAPLQPL1
       LQPL1F2D                                    61
    12 MODULE (PAI) FCODE
       SAPLQPL1
       LQPL1I0P                                    11
Internal notes
The termination occurred in the function "getwa_abswa" of the SAP
Basis System, specifically in line 1003 of the module
"//bas/46D/src/krn/runt/abgetwa.c#20".
The internal operation just processed is "LOOP".
The internal session was started at 20071228111310.
Active calls in SAP kernel
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App       : disp+work.EXE (pid=500)
When      : 12/28/2007 11:16:13.65
Threads   : 2
Computer Name       : ELEPRDCI
User Name           : prdadm
Number of Processors: 16
Processor Type: x86 Family 15 Model 4 Stepping 8
Windows Version     : 5.2 Current Build: 3790
Stack Dump for Thread Id a5c
eax=00000000 ebx=000003a8 ecx=00000e58 edx=00000000 esi=000003a8 edi=00000000
eip=7c82ed54 esp=03138cc4 ebp=03138d34 iopl=0         nv up ei ng nz ac po cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000             efl=00000297
function : KiFastSystemCallRet
         7c82ed54 c3               ret
         7c82ed55 8da42400000000   lea     esp,[esp]              ss:03138cc4=7c822124
         7c82ed5c 8d642400         lea     esp,[esp]              ss:40cd7cc3=????????
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
03138d34 77e6ba12 000003a8 0001d4c0 00000000 03138d6c ntdll!KiFastSystemCallRet
03138d48 00baaa71 000003a8 0001d4c0 77bf1d88 00000002 kernel32!WaitForSingleObject
03138d6c 004d113b 004d10fc 77bf1d88 77bf1d88 77bf1d88 disp+work!
04b5ffb8 77e66063 00215740 00000000 00000000 00215740 MSVCRT!endthreadex
04b5ffec 00000000 77bcb4bc 00215740 00000000 00000000 kernel32!GetModuleFileNameA
List of ABAP programs affected
Type
Program
Gen. date time
LoadSize
Prg
SAPLQPL1
17.09.2006 09:35:11
479232
Prg
SAPMSSYD
14.08.2000 15:39:21
16384
Prg
SAPFSYSCALLS
21.12.1999 19:32:31
7168
Prg
CL_EXITHANDLER================
18.12.2004 13:14:45
13312
Prg
CL_ABAP_TYPEDESCR=============
04.01.2000 19:06:00
17408
Prg
CL_ABAP_ELEMDESCR=============
04.01.2000 19:06:00
13312
Prg
CL_ABAP_DATADESCR=============
04.01.2000 19:06:00
11264
Prg
CL_ABAP_REFDESCR==============
04.01.2000 19:06:00
14336
Prg
CL_ABAP_STRUCTDESCR===========
04.01.2000 19:06:00
16384
Prg
CL_ABAP_COMPLEXDESCR==========
04.01.2000 19:06:00
11264
Prg
CL_ABAP_TABLEDESCR============
04.01.2000 19:06:00
16384
Prg
CL_ABAP_CLASSDESCR============
04.01.2000 19:06:00
23552
Prg
CL_ABAP_OBJECTDESCR===========
04.01.2000 19:06:00
28672
Prg
CL_ABAP_INTFDESCR=============
04.01.2000 19:06:00
21504
Prg
IF_EX_INSPECTIONLOT_UPDATE====
13.07.2002 00:12:42
5120
Typ
SXS_INTER
30.11.1998 15:55:16
1024
Prg
SAPLSEXV
17.09.2006 08:50:01
155648
Prg
SAPLSXCH
18.12.2004 13:22:27
80896
Typ
V_EXT_ACT
14.10.1999 22:16:55
2048
Prg
CL_EX_INSPECTIONLOT_UPDATE====
13.07.2002 00:12:42
26624
Prg
SAPLV00F
08.03.2001 10:01:57
68608
Typ
T185E
15.07.1997 16:57:08
2048
Typ
T185F
14.08.1997 21:32:52
2048
Typ
T185
16.08.2000 11:43:40
3072
Typ
T185V
10.11.1999 17:45:26
4096
Typ
TQ01
14.02.1998 14:07:17
2048
Prg
SAPLSTXD
17.09.2006 08:53:44
406528
Prg
SAPCNVE
04.01.2000 19:06:37
7168
Prg
SAPLLANG
04.01.2000 19:06:49
9216
Prg
SAPLV01Z
17.09.2006 09:34:42
210944
Prg
SAPLCLFM
17.09.2006 09:34:56
688128
Prg
SAPLCUOB
17.09.2006 09:18:21
34816
Prg
SAPLCLSE
13.02.2005 06:50:14
177152
Prg
SAPLCTMS
17.09.2006 09:34:59
942080
Prg
SAPLCTCV
17.09.2006 09:27:23
192512
Prg
SAPLCTCF
12.02.2005 20:42:31
24576
Prg
SAPLV01P
17.09.2006 09:34:42
166912
Prg
SAPLMFAW
18.12.2004 14:02:28
51200
Typ
TFAWY
29.07.1998 19:48:52
2048
Typ
TFAWL
29.07.1998 19:48:49
2048
Typ
TFAWX
29.07.1998 19:48:51
2048
Typ
TFAW
29.07.1998 19:48:45
2048
Prg
RDDFIE00
04.01.2000 19:06:11
19456
Prg
SAPLQAST
13.02.2005 07:23:55
28672
Prg
SAPLBSVA
17.09.2006 09:02:09
270336
Prg
SAPLQSTA
20.01.2000 10:08:08
26624
Typ
TQ01A
29.07.1998 19:56:34
2048
Prg
SAPLOMCV
04.01.2000 19:06:50
14336
Typ
TMCNV
24.02.1999 03:33:25
2048
Prg
SAPLSCNT
15.11.2001 05:19:20
28672
Prg
SAPLSVSM
15.11.2001 05:19:20
25600
Prg
SAPLSGUI
15.11.2001 05:19:20
33792
Prg
SAPLSTTM
17.09.2006 08:49:52
83968
Prg
SAPLSBDC
17.09.2006 08:46:17
66560
Prg
CL_DATAPROVIDER===============
15.11.2001 05:19:18
50176
Typ
OBJ_RECORD
14.02.1998 08:30:43
2048
Prg
SAPLSTUP
17.09.2006 08:46:10
96256
Prg
SAPLCNDP
17.09.2006 08:53:21
201728
Prg
SAPFGUICNTL
18.12.2004 11:31:41
20480
Prg
SAPLOLEA
12.07.2002 21:39:11
81920
Prg
SAPLSFES
17.09.2006 08:53:22
164864
Prg
SAPLGRFC
12.07.2002 21:39:11
16384
Prg
SAPSHDTV
18.12.2004 12:16:52
36864
Typ
SHDSTU
14.12.1998 23:15:34
1024
Typ
SHDSTCIU
14.12.1998 23:15:34
1024
Prg
CL_GUI_PROPS_CONSUMER=========
18.12.2004 11:27:30
26624
Prg
CL_DYNAMIC_GUI_EXTENSIONS=====
11.02.2000 14:36:06
55296
Prg
CL_GUI_DATAMANAGER============
18.12.2004 11:34:01
82944
Prg
/1BCDWBEN/SAPLQEN0000
13.07.2002 02:11:40
51200
Prg
SAPLSENA
04.01.2000 19:06:53
28672
Prg
SAPLQELA
17.09.2006 09:27:48
415744
Typ
QALS
13.07.2002 00:12:42
27648
Prg
SAPLQAUT
13.02.2005 01:25:27
177152
Prg
SAPLSWUG
17.09.2006 08:53:33
264192
Typ
SWOTOBJID
04.05.1995 15:20:52
2048
Typ
SWHACTOR
04.04.1995 16:18:07
1024
Prg
CL_GOS_MANAGER================
17.09.2006 08:53:30
24576
Prg
CL_GOS_VIEW_MANAGER===========
21.12.1999 19:23:29
29696
Typ
SGOS_MVOBJ
01.12.1999 08:16:05
2048
Prg
SAPLSUU1
17.09.2006 08:53:37
183296
Typ
USR02
15.11.2001 05:09:06
5120
Typ
USREFUS
18.12.2004 11:18:28
1024
Prg
SAPLTHFB
17.09.2006 08:53:29
270336
Typ
BORIDENT
28.08.1997 08:38:50
1024
Prg
CL_GOS_TOOLBOX_MODEL==========
17.09.2006 08:53:30
39936
Typ
SGOS_MODL
08.02.2000 16:42:30
3072
Prg
SAPLBDLS
14.08.2000 15:20:53
13312
Typ
T000
11.09.1997 10:17:18
3072
Prg
CL_GOS_PUBLICATION============
17.09.2006 08:53:30
24576
Prg
CL_GUI_OBJECT=================
15.11.2001 05:19:18
187392
Prg
CL_GUI_CFW====================
18.12.2004 13:28:20
195584
Typ
TOLE
29.07.1998 19:56:01
2048
Prg
SAPLSGOSHIST
17.09.2006 08:53:33
56320
Prg
SAPFSGOS
08.11.2003 23:57:36
13312
Typ
SGOSHIST
14.10.1999 22:09:01
2048
Prg
SAPLURFC
04.01.2000 19:08:13
14336
Prg
CL_GOS_STARTER================
09.12.1999 13:49:28
21504
Prg
CL_GUI_CONTROL================
08.11.2003 23:57:31
117760
Prg
CL_GUI_TOOLBAR================
15.11.2001 05:19:18
72704
Prg
CL_GUI_GOS_CONTAINER==========
01.02.2000 10:16:37
38912
Typ
CFW_LINK
01.12.1999 12:16:48
2048
Prg
CL_GUI_CONTAINER==============
15.11.2001 05:19:18
58368
Prg
SAPLCNTH
08.11.2003 23:56:48
26624
Prg
SAPLSCONTROLINFO
04.01.2000 19:06:52
13312
Prg
SAPLSCONTROLSTATUSCHECK
04.01.2000 19:06:52
10240
Typ
USR05
09.07.1997 23:46:52
1024
Typ
CNTLWARN
25.01.1999 13:09:44
2048
Prg
SAPLICON
17.09.2006 08:39:01
25600
Prg
%_CICON
14.08.2000 15:39:36
55296
Typ
JSTO
27.08.1994 20:32:55
2048
Typ
JEST
27.08.1994 20:32:50
2048
Prg
SAPLAIEV
15.11.2001 05:18:17
14336
Prg
CL_OS_TRANSACTION_END_NOTIFIER
18.12.2004 13:21:30
8192
Typ
LFA1
13.07.2002 01:08:16
12288
Prg
SAPLCPDB
17.09.2006 09:17:36
113664
Typ
PLKO
15.01.1999 22:26:42
9216
Prg
SAPLCCPR
17.09.2006 09:09:14
231424
Typ
TCC08
17.03.1999 16:30:21
4096
Typ
AEEF
13.02.2005 06:49:14
3072
Typ
TCC10
23.04.1998 14:45:07
2048
Typ
TCCET
28.08.1997 09:33:24
1024
Typ
TCCEP
20.08.1998 11:28:15
2048
Typ
TCCER
10.11.1998 05:49:03
2048
Typ
TCCETT
14.02.1998 12:45:20
1024
Typ
TCCEPT
14.02.1998 12:45:07
1024
Typ
TCCERT
17.03.1999 16:24:38
2048
Typ
TCCS01
27.08.1999 18:28:00
1024
Prg
SAPLCCHO
17.09.2006 09:18:17
55296
Prg
SAPLCPTA
17.09.2006 09:09:03
122880
Prg
SAPLCQTA
17.09.2006 09:34:41
88064
Typ
TQ33
10.07.1997 00:12:25
2048
Typ
TQ30
15.04.1998 00:38:23
3072
Typ
TQ30T
14.02.1998 14:11:06
2048
Prg
SAPLCV141
17.09.2006 09:18:22
86016
Typ
DRAD
01.12.1999 15:17:34
3072
Prg
SAPLBSVT
16.08.2000 11:43:43
18432
Prg
SAPLSMSG
18.12.2004 13:27:29
108544
Typ
TJ05
30.11.1993 16:45:10
1024
Typ
TJ01
01.03.1999 13:50:12
4096
Typ
TJ07
30.11.1993 16:45:13
1024
Typ
TJ06
30.11.1993 16:45:11
1024
Typ
TJ03
16.08.2000 11:43:42
2048
Prg
SAPFGUICNTL_CFW
15.11.2001 05:19:19
17408
Prg
CL_GUI_DOCKING_CONTAINER======
15.11.2001 05:19:18
50176
Prg
SAPLQBCK
17.09.2006 09:27:37
106496
Typ
QINF
09.12.1999 19:04:48
5120
Typ
MTQSS
23.04.1998 14:51:52
4096
Prg
SAPLMAQM
17.09.2006 09:35:30
61440
Typ
T001W
18.11.1998 16:27:15
1024
Typ
T001K
01.02.2000 14:56:09
3072
Prg
SAPLMG21
17.09.2006 09:34:30
159744
Typ
MARA
17.09.2006 09:17:34
15360
Prg
SAPLMG22
17.09.2006 09:17:36
115712
Typ
MARC
04.01.2000 18:04:45
23552
Typ
RMQEA
13.08.1997 12:52:02
9216
Typ
TJ02
27.03.1996 18:28:28
1024
Typ
TJ02T
14.02.1998 13:40:18
2048
Typ
TJ04
30.11.1993 16:45:08
2048
Prg
SAPLKDIC
04.01.2000 19:06:48
17408
Prg
SAPLSDTO
04.01.2000 19:06:52
25600
Typ
DD07T
12.05.1997 16:45:51
2048
Prg
SAPLCSCE
04.01.2000 19:06:44
8192
Typ
T024E
10.12.1998 18:01:35
2048
Prg
SAPLSCVU
17.09.2006 08:50:02
59392
Typ
T006A
28.08.1997 09:04:18
2048
Typ
OLE_PA
04.04.1995 16:02:19
2048
Typ
ARFCRDATA
12.07.2002 21:39:11
3072
Typ
SWCBCONT
14.02.1998 10:14:45
2048
Typ
OLE_VERBS
04.04.1995 16:02:20
1024
Prg
SAPLSDSD
17.09.2006 08:53:36
437248
Typ
DDSHIFACE
20.08.1998 10:51:59
2048
Typ
DFIES
15.01.1999 16:49:52
6144
Typ
DDSHFPROP
20.08.1998 10:51:57
2048
Typ
DDSHSELOPT
20.08.1998 10:52:01
2048
Prg
SAPLSDNT
18.12.2004 12:05:44
188416
Prg
SAPLSDIF
18.12.2004 13:03:59
256000
Typ
T006
29.07.1998 19:25:31
3072
Prg
SAPLSCV0
17.09.2006 08:50:22
99328
Typ
TCA01
10.03.1999 18:31:19
5120
Typ
TCA02
14.02.1998 12:40:44
2048
Typ
TCA35
06.07.1998 20:51:04
2048
Typ
QMAT
27.08.1999 18:14:19
5120
Typ
TQ32
10.07.1997 00:12:23
2048
Prg
SAPLXQPL
17.09.2006 09:30:13
28672
Typ
TCA44
29.07.1998 19:44:06
2048
Prg
SAPLQPAP
17.09.2006 09:30:13
295936
Prg
SAPMSSY0
17.09.2006 08:53:44
69632
Prg
SAPLSNR3
17.09.2006 08:53:36
48128
Typ
TNRO
18.12.2004 13:02:43
4096
Prg
SAPLQEEV
17.09.2006 09:27:48
216064
Typ
QAPP
15.04.1998 00:12:33
7168
Typ
TQSS
20.01.2000 10:08:08
3072
Prg
SAPLQMCF
17.09.2006 09:34:35
46080
Prg
SAPLCEI0
03.12.2006 09:44:54
1121280
Prg
SAPLCUEV
13.07.2002 02:21:41
11264
Typ
IBINCOM
01.06.1999 11:56:27
2048
Typ
IBINCONF
01.06.1999 11:56:27
2048
Typ
IBSTCONF
01.06.1999 11:56:28
1024
Prg
IF_EX_CEI0_INVLD_POSSIBLE=====
12.02.2005 20:53:18
4096
Prg
CL_EX_CEI0_INVLD_POSSIBLE=====
12.02.2005 20:52:40
10240
Prg
CL_EXIT_MASTER================
01.02.2000 09:29:10
10240
Typ
V_EXT_IMP
14.10.1999 22:16:55
2048
Prg
SAPLCUCB
17.09.2006 09:34:59
199680
Typ
TCUIBSPECIAL
15.11.2001 05:31:05
1024
Prg
CL_CBASE======================
13.02.2005 07:14:09
95232
Typ
T371G
29.04.1998 10:42:48
1024
Prg
SAPLIBCO
13.02.2005 05:49:04
305152
Prg
SAPLIBXX
13.07.2002 02:21:41
12288
Prg
SAPLIBIBF
13.02.2005 06:58:29
177152
Prg
SAPLIBINF
13.02.2005 06:58:30
452608
Prg
CL_IBASE_STRUC================
13.07.2002 02:21:39
141312
Prg
CL_IBASE_STRUC_BUF============
13.02.2005 01:44:37
120832
Prg
CL_IBASE_STRUC_STAT===========
13.07.2002 02:21:39
9216
Prg
CL_IBASE_STRUC_BUF_IBSTREF====
13.02.2005 01:44:37
61440
Typ
IBINVAL
14.05.1998 22:39:25
2048
Prg
SAPLIBCU
13.07.2002 02:21:41
14336
Prg
SAPLIBCUT
13.07.2002 02:21:41
14336
Typ
T371B
14.05.1998 22:58:43
1024
Prg
CL_IBASE_SERVICE==============
13.07.2002 02:21:39
17408
Prg
CL_IBASE_T371D_BUF============
13.07.2002 02:21:39
15360
Typ
T371D
27.08.1999 18:19:44
2048
Prg
CL_IBASE_R3_MATERIAL==========
17.09.2006 09:33:39
99328
Typ
MAKT
28.08.1997 08:52:19
2048
Typ
ICON
03.01.1996 15:34:02
3072
Prg
IF_EX_CM_BADI_VERSION=========
12.07.2002 23:55:25
4096
Prg
CL_EX_CM_BADI_VERSION=========
12.07.2002 23:54:25
11264
Prg
CL_DEF_IM_CM_BADI_VERSION=====
12.07.2002 23:54:24
8192
Prg
SAPLASTAT_TRIG
18.12.2004 12:15:52
12288
Typ
ASTAT_TYP2
10.11.1998 05:35:18
1024
Typ
ASTAT_TYP1
30.11.1998 15:54:16
1024
Prg
IF_CM_BASELINE================
13.02.2005 06:50:14
40960
Prg
IF_IBASE_IBOF_TREE_OBJECT=====
13.02.2005 05:59:51
10240
Prg
IF_IBASE_INSTALL==============
13.07.2002 02:21:40
4096
Prg
IF_IBASE_MATERIAL=============
13.07.2002 02:21:40
4096
Prg
IF_IBASE_OBJECT===============
13.07.2002 02:21:40
5120
Prg
SAPLBOMA
01.02.2000 14:54:24
13312

Hi Sanjay,
This dump generally occurs when there are inconsistencies between the name of the fields in the fieldcatalog and the names of the fields in the internal table. Please post ur code.(Assuming that this dump has occured in a Z* program)
Edited by: Rajesh on Dec 29, 2007 2:40 PM

Dump in production

Similar Messages

Maybe you are looking for