Short Dumps in System Monitoring
Hi!
I set up the system monitoring in SAP Solution Manager.
The most alerts I get from short Dumps.
In order to avoid this issue I would like to optimize the settings of short dumps.
Here my questions:
- Is it possible to set the threshold values behind short dumps
- If I switch off the short dumps is there some possibilities to be inform about frequency?
- Is there some other possibilities to optimize this issue?
Thank you very much!
regards
Thom
Hi Thom.
I think what you need is to setup in System Monitoring the threshold values for the following MTEs of the Satellite System:
Transaction RZ20 --> <Instance> --> R3Abap
This MTE has two attributes:
Shortdumps (MTE Class:R3AbapShortdumps)
Shortdumps Frequency (MTE Class:R3AbapShortdumpsFreq)
By clicking on the properties of one of each attribute you can setup the threshold for how many alerts you want to maintain (General Tab). In Performance tab you will be able to customize the threshold for the alerts.
Hope this helps
Antonio
Similar Messages
-
Short Dump in system while deleting the SC item
Hi Experts,
We are receiving the short dump while trying to delete the shopping cart item.
The dump Says... "Buffer table not up to date"
When we debugged the same , found that becuase of the error message "No address found for partner function type 0008u201D.(bbp_pd-051) the BBP_PD_ABORT is called and thus the termination
Please let me know the reason for the same.
We are using SRM Version 5.00
Regards,
RanjithaHello,
Kindly check the SAP Notes 1574131 & 1484165.
Best regards,
Rahul -
Trcing down to JOB or program level from Short dump or system log in APO.
Hi Guru's
Can anyone please guide me how to trace down to JOB or program level from ST22 and SM21 logs.
I have SQL errors and lock entries in APO system, I want to find which program or job writing them.
Thanks in advance,
Sreerama.Hi,
Thanks for the replay,
I have checked same way as you suggested >>>> in ST22 dump, but it is taking me to Include "LARFCF06" which is trying to delete ARFCSTATE table.
and I have error message :
Database error text........: "[1205] Transaction (Process ID 291
deadlocked on lock resources with another process and has been
deadlock victim. Rerun the transaction."
Internal call code.........: "[RSQL/DELE/ARFCRSTATE ]"
Please check the entries in the system log (Transaction SM21).
User and Transaction
Client.............. 100
User................ "APORFC"
Language Key........ "E"
Transaction......... " "
Transactions ID..... "002FE8DE2A71F1B182E80019BB345F90"
Program............. "SAPLARFC"
Screen.............. "SAPMSSY1 3004"
Screen Line......... 2
Information on caller of Remote Function Call (RFC):
System.............. "P48"
Database Release.... 700
Kernel Release...... 700
Connection Type..... 3 (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)
Call Type........... "synchron and non-transactional (emode 0, imode 0)"
Inbound TID.........." "
Inbound Queue Name..." "
Outbound TID........." "
Outbound Queue Name.." "
Client.............. 100
User................ "APORFC"
Transaction......... " "
Call Program........."SAPLERFC"
Function Module..... "ARFC_DEST_CONFIRM"
Call Destination.... "NONE"
Source Server....... "debosap172_P48_21"
Source IP Address... "10.132.184.172"
Additional information on RFC logon:
Trusted Relationship " "
Logon Return Code... 0
Trusted Return Code. 0
Note: For releases < 4.0, information on the RFC caller are often
only partially available.
Information on where terminated
Termination occurred in the ABAP program "SAPLARFC" - in
"DELETE_ARFC_ORPHANS_WO_COMMIT".
The main program was "SAPMSSY1 ".
In the source code you have the termination point in line 508
of the (Include) program "LARFCF06".
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
procedure "DELETE_ARFC_ORPHANS_WO_COMMIT" "(FORM)", but it was neither handled
locally nor declared
in the RAISING clause of its signature.
The procedure is in program "SAPLARFC "; its source code begins in line
489 of the (Include program "LARFCF06 ".
Now I want to find how this dead lock is created and which two (programs or JOB's) causing this dead lock.
And program "APLARFC" is not a exicutable program and even I try to where used list I am not able to find exicutable program.
now I need to find which are the two programs or jobs causing this loack.
Thanks in Advance,
Sreerama. -
Short Dump on BAPI_TRANSACTION_COMMIT with destination NONE
Hi All
I am using SAP-PM with Compatible Unit(CU) functionality in ECC6 environment.
After we release the CU design to Generate order we get SHORT DUMP.
Any help will be of great help.
I am pasting the details from the dump file here.
Please let me know.
Appretaite your help.
Thanks
Meghana
Runtime Errors CALL_FUNCTION_REMOTE_ERROR
Date and Time 27.08.2007 18:01:10
Short text
"The current application triggered a termination with a short dump."
What happened?
Error in the ABAP Application Program
The current ABAP program "/***/SAPLCUORDER_N" had to be terminated because it
has
come across a statement that unfortunately cannot be executed.
The error occurred during an RFC call to another system.
In the target system, a short dump has been written as well.
More detailed information on the error cause can be found there.
What can you do?
Note down which actions and inputs caused the error.
To process the problem further, contact you SAP system
administrator.
Using Transaction ST22 for ABAP Dump Analysis, you can look
at and manage termination messages, and you can also
keep them for a long time.
Error analysis
An error occurred when executing a REMOTE FUNCTION CALL.
It was logged under the name "MESSAGE_TYPE_X"
on the called page.
How to correct the error
Please refer to the notes described in the
short dump.
System environment
SAP-Release 700
Application server... "MB1ES1005"
Network address...... "10.191.97.206"
Operating system..... "Windows NT"
Release.............. "5.2"
Hardware type........ "2x Intel 801586"
Character length.... 16 Bits
Pointer length....... 32 Bits
Work process number.. 3
Shortdump setting.... "full"
Database server... "MB1ES1005"
Database type..... "ORACLE"
Database name..... "EC6"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Jul 25 2007 00:57:05"
create on........ "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version. "OCI_10201_SHARE (10.2.0.1.0) "
Patch level. 121
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows
NT 6.0"
Memory consumption
Roll.... 8176
EM...... 14633136
Heap.... 0
Page.... 131072
MM Used. 5005432
MM Free. 1263944
User and Transaction
Client.............. 200
User................ 10086330
Language key........ "E"
Transaction......... "/***/DESIGN "
Transactions ID..... "409954DC5D77F1C58E2D0013725D3B3B"
Program............. "/***/SAPLCUORDER_N"
Screen.............. "/***/SAPLCUORDER_N 2000"
Screen line......... 34
Information on where terminated
Termination occurred in the ABAP program "/***/SAPLCUORDER_N" - in
"SAVE_DESIGN".
The main program was "/***/SAPLCUORDER_N ".
In the source code you have the termination point in line 594
of the (Include) program "/***/LCUORDER_NF07".
Source Code Extract
Line
SourceCde
564
ENDIF .
565
ENDLOOP .
566
IF l_ret-type = 'E' OR
567
l_ret-type = 'A' .
568
CLEAR: save_okcode .
569
570
Show Messages
571
CALL FUNCTION '/***/N_LOG_ADD_MSG'
572
EXPORTING
573
i_log_type = 'G'
574
TABLES
575
t_ret = t_ret.
576
PERFORM log_order_create_show .
577
Show first Message
578
MESSAGE ID l_ret-id TYPE l_ret-type NUMBER l_ret-number
579
WITH
580
l_ret-message_v1 l_ret-message_v2
581
l_ret-message_v3 l_ret-message_v4.
582
CALL FUNCTION '/***/N_DESIGN_INIT' .
583
ELSE .
584
IF g_design_mode = con_mode_crea.
585
Need to update DMS documents with real design number
586
PERFORM document_prepare_002 USING con_desnum_tmp_1
587
lv_desnum.
588
ENDIF.
589
Commit design BAPI's
590
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' .
591
592
IF save_okcode = con_order.
593
Commit order BAPI's
>>>>>
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
595
DESTINATION 'NONE'.
596
597
call of fct. RFC_CONNECTION_CLOSE is important to get a new
598
initial roll area with initial internal tables next time
599
CALL FUNCTION 'RFC_CONNECTION_CLOSE'
600
EXPORTING
601
destination = 'NONE'
602
EXCEPTIONS
603
destination_not_open = 1
604
OTHERS = 2.
605
ENDIF.
606
607
IF lv_desnum IS INITIAL .
608
lv_desnum = /***/cudesign-desnum .
609
ENDIF .
610
SET PARAMETER ID '/***/DESNUM' FIELD lv_desnum .
611
Changes saved
612
MESSAGE ID '/***/MSG' TYPE 'S' NUMBER '529' WITH lv_desnum .
613
ENDIF .
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
1
SY-DBCNT
1
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
2000
SY-UCOMM
CU01
SY-TITLE
Change Design: 50000109
SY-MSGTY
X
SY-MSGID
00
SY-MSGNO
341
SY-MSGV1
MESSAGE_TYPE_X
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20070827
SY-UZEIT
180110
SY-XPROG
SAPMSSY1
SY-XFORM
XAB_READ
Active Calls/Events
No. Ty. Program Include Line
Name
4 FORM /***/SAPLCUORDER_N /***/LCUORDER_NF07 594
SAVE_DESIGN
3 FORM /***/SAPLCUORDER_N /***/LCUORDER_NF07 2616
CHECK_AND_SAVE_F07
2 FORM /***/SAPLCUORDER_N /***/LCUORDER_NF04 311
USER_COMMAND_D2000
1 MODULE (PAI) /***/SAPLCUORDER_N /***/LCUORDER_NI05 28
USER_COMMAND_2000
Chosen variables
Name
Val.
No. 4 Ty. FORM
Name SAVE_DESIGN
%_DUMMY$$
2222
0000
0000
0000
CL_GUI_RESOURCES=>COL_TEXTAREA
31
1000
F000
G_DESIGN_MODE
R
5
2
0
0
CON_MODE_CREA
I
4
9
0
0
GT_NODE_CUI
Table[initial]
SY-REPID
/***/SAPLCUORDER_N
2454254544545445542222222222222222222222
F35DF310C35F2452FE0000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CON_DESNUM_TMP_1
TM00000001CY
543333333345
4D0000000139
000000000000
000000000000
LV_DESNUM
222222222222
000000000000
000000000000
000000000000
SAVE_OKCODE
CU01
4533222222222222222222222222222222222222222222222222222222222222222222
3501000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
CON_ORDER
CU01
4533222222222222222222222222222222222222222222222222222222222222222222
3501000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
SY-XPROG
SAPMSSY1
5454555322222222222222222222222222222222
310D339100000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CON_DELETE
LVMS
4545222222222222222222222222222222222222222222222222222222222222222222
C6D3000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
No. 3 Ty. FORM
Name CHECK_AND_SAVE_F07
CL_GUI_ALV_GRID=>MC_MB_VIEW
&MB_VIEW
2445544522222222222222222222222222222222222222222222222222222222222222
6D2F695700000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000
GT_OP
Table IT_303[2x1320]
PROGRAM=/***/SAPLCUORDER_NDATA=GT_OP
Table reference: 118
TABH+ 0(20) = 7039FC3C5824DB3C00000000760000002F010000
TABH+ 20(20) = 0200000028050000FFFFFFFF0400000030140000
TABH+ 40( 8) = 08000000C1308001
store = 0x7039FC3C
ext1 = 0x5824DB3C
shmId = 0 (0x00000000)
id = 118 (0x76000000)
label = 303 (0x2F010000)
fill = 2 (0x02000000)
leng = 1320 (0x28050000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000093
occu = 8 (0x08000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
groupCntl = 0
rfc = 0
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x2010FC3C
pgHook = 0x00000000
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 234 (0xEA000000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 8 (0x08000000)
lineAlloc = 8 (0x08000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = 0x60B7153D
collHook = 0x00000000
ext2 = 0x1024DB3C
>>>>> 2nd level extension part <<<<<
tabhBack = 0xE00FFC3C
delta_head = 0000000000000000000000000000000000000000000000000000000000000000000000000000000
pb_func = 0x00000000
pb_handle = 0x00000000
G_BADI_PROGRAM
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
LOG_ERROR
2
0
0
0
CON_BUTT_DELETED
@11QDelete@
43355466676422222222222222222222222222222222
011C145C545000000000000000000000000000000000
00000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000
G_CU_EXIT_CU_EXPLODE
F0000000
F0000000
/***/CUDESIGN-OBJNR
CY00000000000000008835
4533333333333333333333
3900000000000000008835
0000000000000000000000
0000000000000000000000
CL_GUI_RESOURCES=>COL_TEXTAREA
31
1000
F000
G_SEC_COUNT
0
0000
0000
LV_UPD
X
5
8
0
0
%_SPACE
2
0
0
0
GS_ROW_NO
0.0.0.1.
0000
1000
0000
0000
SCREEN
/***/CUDESIGN-GLTRP
2454245445444244555222222222222222222222222222222222222222222222222222222222222222222222222222
F35DF3545397ED7C420000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SY-MSGID
00
33222222222222222222
00000000000000000000
00000000000000000000
00000000000000000000
SWO_%CONTAINER
000000000
2222222222222222222222222222222233333333322222222222222222222222222222222222222222222222222222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SPACE
2
0
0
0
SY-MSGNO
341
333
341
000
000
/***/CVCUI-CUTYP
2
0
0
0
SY-MSGV1
MESSAGE_TYPE_X
44554445555455222222222222222222222222222222222222
D533175F4905F8000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV2
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV3
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
SY-MSGV4
22222222222222222222222222222222222222222222222222
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000
No. 2 Ty. FORM
Name USER_COMMAND_D2000
/***/CVCUI
0.0.0.0.0.0.0.1. 000000
2220000000022222222222222222222222222222222222222222222222222222222222222222222222223333332222
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
SYST-REPID
/***/SAPLCUORDER_N
2454254544545445542222222222222222222222
F35DF310C35F2452FE0000000000000000000000
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
CON_MODE_COPY
C
4
3
0
0
LT_BAPI_RETURN
Table IT_1778[2x1088]
PROGRAM=/***/SAPLCUORDER_NFORM=USER_COMMAND_D2000DATA=LT_BAPI_RETURN
Table reference: 310
TABH+ 0(20) = 8837083D407E1C3D0000000036010000F2060000
TABH+ 20(20) = 0200000040040000FFFFFFFF04000000F0170000
TABH+ 40( 8) = 08000000C1308101
store = 0x8837083D
ext1 = 0x407E1C3D
shmId = 0 (0x00000000)
id = 310 (0x36010000)
label = 1778 (0xF2060000)
fill = 2 (0x02000000)
leng = 1088 (0x40040000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000113
occu = 8 (0x08000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 8 (cmpManyEq)
occu0 = 1
groupCntl = 0
rfc = 1
unShareable = 0
mightBeShared = 0
sharedWithShmTab = 0
isShmLockId = 0
gcKind = 0
isUsed = 1
isCtfyAble = 1
>>>>> Shareable Table Header Data <<<<<
tabi = 0x50C6073D
pgHook = 0x00000000
idxPtr = 0x00000000
shmTabhSet = 0x00000000
id = 1534 (0xFE050000)
refCount = 0 (0x00000000)
tstRefCount = 0 (0x00000000)
lineAdmin = 8 (0x08000000)
lineAlloc = 8 (0x08000000)
shmVersId = 0 (0x00000000)
shmRefCount = 1 (0x01000000)
>>>>> 1st level extension part <<<<<
regHook = 0x00000000
collHook = 0x00000000
ext2 = 0x6067033D
>>>>> 2nd level extension part <<<<<
tabhBack = 0xE82F063D
delta_head = 0000000000000000CF000000000000000400000020180000000000004D00430055004F000000000
pb_func = 0x00000000
pb_handle = 0x00000000
CON_MODE_ORDE
O
4
F
0
0
TGSBT
22222222222222222222222222222222222222
00000000000000000000000000000000000000
00000000000000000000000000000000000000
00000000000000000000000000000000000000
CL_GUI_RESOURCES=>COL_TEXTAREA
31
1000
F000
LS_NUMBERS-AUFNR_NEW
000001000677
333333333333
000001000677
000000000000
000000000000
T024I
200UT10100PG for Term & Comp
33355333335426672567622246672222222222222222
20054101000706F20452D0603FD00000000000000000
00000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000
LS_T399X
200UT10UM01 X INST 30UT01UT01
3335533543322222222222222222252222445522335533553322222222222222222222222222222222222222222222
20054105D01000000000000000000800009E3400305401540100000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
CON_VBKZ_U
U
5
5
0
0
/***/CU_ORDER_IO-DISP_FACTOR
2097152
0
0
LS_DESIGN
200########000050000109DDCY00000000000000008835PROFILE1 0001UT10UM0100220100MWH001
333D5FC807333333333333344453333333333333333333355444443223333553354333333333345433322222222222
200CDB1E02B00005000010944390000000000000000883502F69C5100000154105D0100220100D7800100000000000
000599F215300000000000000000000000000000000000000000000000000000000000000000000000000000000000
0004C91D3DB00000000000000000000000000000000000000000000000000000000000000000000000000000000000
/***/CUDESIGN
200########000050000109DDCY00000000000000008835PROFILE1 0001UT10UM0100220100MWH001
333D5FC807333333333333344453333333333333333333355444443223333553354333333333345433322222222222
200CDB1E02B00005000010944390000000000000000883502F69C5100000154105D0100220100D7800100000000000
000599F215300000000000000000000000000000000000000000000000000000000000000000000000000000000000
0004C91D3DB00000000000000000000000000000000000000000000000000000000000000000000000000000000000
G_DROP_COUNT
0
0000
0000
LS_DESIGN-DESNUM
000050000109
333333333333
000050000109
000000000000
000000000000
No. 1 Ty. MODULE (PAI)
Name USER_COMMAND_2000
GT_SELTAB_INIT
Table[initial]
Internal notes
The termination was triggered in function "RfcExtendedReceive"
of the SAP kernel, in line 422 of the module
"//bas/700_REL/src/krn/rfc/abrfcrcv.c#4".
The internal operation just processed is "FUNC".
Internal mode was started at 20070827180011.
Status of connection:
RFC state: " "
RFC error text: "RFC_ERROR_SYSTEM_FAILURE"
CPI-C error text: "The current application triggered a termination with a short
dump."
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
SAP (R) - R/3(TM) Callstack, Version 1.0
Copyright (C) SAP AG. All rights reserved.
Callstack without Exception:
App : disp+work.EXE (pid=26488)
When : 8/27/2007 18:1:10.942
Threads : 2
Computer Name : MB1ES1005
User Name : ec6adm
Number of Processors: 2
Processor Type: x86 Family 15 Model 4 Stepping 10
Windows Version : 5.2 Current Build: 3790
State Dump for Thread Id 5e10
eax=000f93c0 ebx=0000042c ecx=00003118 edx=00000000 esi=0000042c edi=00000000
eip=7c82ed54 esp=056d71f0 ebp=056d7260 iopl=0 nv up ei ng nz ac po cy
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00200297
function : KiFastSystemCallRet
7c82ed54 c3 ret
7c82ed55 8da42400000000 lea esp,[esp] ss:056d71f0=7c822124
7c82ed5c 8d642400 lea esp,[esp] ss:62bd5803=00000000
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
056d7260 77e6ba42 0000042c 0001d4c0 00000000 056d7298 ntdll!KiFastSystemCallRet
056d7274 0109504d 0000042c 0001d4c0 00000001 7c38b5c8 kernel32!WaitForSingleObject
056d7298 00582118 00582151 7c38b5c8 7c38b5c8 7c38b5c8 disp+work!NTDebugProcess (ntstcdbg.c (501))
056d729c 00582151 7c38b5c8 7c38b5c8 7c38b5c8 01e9b1b8 disp+work!NTStack (dptstack.c (1367))
056d72b8 00582185 7c38b5c8 00000000 008b7ec8 7c38b5c8 disp+work!CTrcStack2 (dptstack.c (352))
056d72c4 008b7ec8 7c38b5c8 00000000 005f0059 00330030 disp+work!CTrcStack (dptstack.c (182))
056d72e8 008bb39f 00711076 056d8018 056d7be8 00200020 disp+work!rabax_CStackSave [abrabax.c (7063)
056d7b90 009eca8b 020b9e4c 020b9e14 000001a6 5d88acf0 disp+work!ab_rabax (abrabax.c (1243))
056d7bcc 009ed19e 00000003 00711076 00000020 00000000 disp+work!rcv_message (abrfcrcv.c (422))
056d8068 009ed29d 00000003 00000000 00710c47 056d80c0 disp+work!RfcExtendedReceive [abrfcrcv.c (14
056d808c 00714873 00000003 00710c47 056d80c0 00711076 disp+work!ab_rfcreceive (abrfcrcv.c (59))
056d80e4 0071886b 2694a7c8 2694a7cc 2694a7cc 2694a7cc disp+work!jfunc_get (abfunc.c (5103))
056d89f4 007191d0 00000003 000000b4 00000000 05e8b7c0 disp+work!jfunc_nonstandard [abfunc.c (1655)
056dcfb0 006e3e2d 00000003 3ced8f90 00000000 056dd018 disp+work!ab_jfunc (abfunc.c (554))
056dd018 0081cb5e 00000000 3ced8f90 056dd164 3cedb514 disp+work!ab_extri (abextri.c (552))
056dd02c 00897dbd 00000000 3cedae46 005bf4cd 3ceda13c disp+work!ab_xevent (abrunt1.c (281))
056dd038 005bf4cd 3ceda13c 000000ea 3cedae46 00000000 disp+work!ab_dstep (abdynpro.c (492))
056dd164 005c25be 3ced8f90 3ced8f90 056dfc78 00000000 disp+work!dynpmcal (dymainstp.c (2398))
056dd178 005c1def 00000001 3ced8f90 00000003 056dfc78 disp+work!dynppai0 (dymainstp.c (1004))
056dd194 00595e69 3ced8f90 00000001 00000001 00000001 disp+work!dynprctl (dymainstp.c (360))
056dfcec 00490e06 00000004 0049d15f 00000004 01dadd00 disp+work!dynpen00 (dymain.c (1628))
056dfcf4 0049d15f 00000004 01dadd00 00000003 00000002 disp+work!Thdynpen00 (thxxhead.c (4773))
056dfee0 0049d6d6 00000001 00000000 00000000 00430000 disp+work!TskhLoop (thxxhead.c (4455))
056dff00 00421c36 00000000 00000000 7ffde000 056dff60 disp+work!ThStart (thxxhead.c (1173))
056dff14 00401080 00000003 05876980 00000001 00000000 disp+work!DpMain (dpxxdisp.c (1121))
056dff60 01242970 00000003 05876980 05877a10 01cce000 disp+work!nlsui_main (thxxanf.c (82))
056dffc0 77e523e5 00000000 00000000 7ffde000 8967f020 disp+work!wmainCRTStartup (crtexe.c (395))
056dfff0 00000000 0124282d 00000000 00905a4d 00000003 kernel32!IsProcessorFeaturePresent
State Dump for Thread Id 61fc
eax=00000000 ebx=00000103 ecx=0587a700 edx=02714360 esi=00000000 edi=00000000
eip=7c82ed54 esp=0799fec0 ebp=0799ff04 iopl=0 nv up ei pl zr na po nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000246
function : KiFastSystemCallRet
7c82ed54 c3 ret
7c82ed55 8da42400000000 lea esp,[esp] ss:0799fec0=7c821514
7c82ed5c 8d642400 lea esp,[esp] ss:64e9e4d3=00000000
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0799ff04 0119030a 000006e0 00000000 00000000 0587a798 ntdll!KiFastSystemCallRet
0799ff84 7c349565 00000000 00000000 00000000 0587a700 disp+work!SigIMsgFunc (signt.c (610))
0799ffb8 77e6608b 0587a700 00000000 00000000 0587a700 MSVCR71!endthreadex
0799ffec 00000000 7c3494f6 0587a700 00000000 00000000 kernel32!GetModuleFileNameA
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
/***/SAPLCUORDER_N
0
10.08.2007
10:12:44
541696
E
1
Typ
/***/CUDESIGN
0
10.08.2007
10:05:19
7168
2
Typ
/***/CU_ORDER_IO
0
10.08.2007
09:53:38
4096
3
Typ
/***/DESTYPE
0
10.08.2007
10:05:21
2048
4
Typ
/***/PRF_ORD
0
10.08.2007
10:05:21
4096
5
Prg
SAPMSSYD
0
04.04.2007
10:28:36
21504
E
6
Prg
SAPFSYSCALLS
0
09.09.2004
14:18:32
8192
E
7
Typ
/***/G_CUST
0
10.08.2007
09:53:39
3072
8
Prg
/***/SAPLTABLES
8
10.08.2007
10:13:00
19456
E
9
Typ
/***/G_CHAR
0
10.08.2007
10:05:21
3072
10
Prg
SAPLCTCE
10
09.09.2004
14:18:34
9216
E
11
Typ
CABN
0
18.09.2001
10:02:26
12288
12
Prg
SAPLICON
12
04.04.2007
10:10:28
27648
E
13
Prg
%_CICON
12
07.02.2006
10:40:00
104448
E
14
Typ
ICONT
0
04.04.2007
10:10:08
2048
15
Typ
NRIV
0
02.04.1998
08:14:54
3072
16
Prg
SAPLBSVA
16
04.04.2007
14:47:00
296960
E
17
Typ
/***/CU_ORDER_S_OP_N
0
10.08.2007
09:53:39
14336
18
Prg
CL_GUI_CONTROL================CP
18
28.02.2005
21:03:09
112640
E
19
Prg
%_CCNTL
18
18.02.2005
14:15:08
15360
E
20
Typ
OBJ_RECORD
0
14.02.1998
08:30:43
2048
21
Prg
CL_GUI_OBJECT=================CP
21
05.07.2005
13:10:15
375808
E
22
Prg
CL_GUI_CFW====================CP
22
28.02.2005
21:03:09
172032
E
23
Prg
CL_GUI_PROPS_CONSUMER=========CP
23
18.02.2005
14:15:08
30720
E
24
Prg
SAPLTHFB
24
04.04.2007
13:24:38
390144
E
25
Typ
EUDB
0
06.11.2003
20:28:08
8192
26
Prg
SAPLSFES
26
08.08.2007
16:46:17
259072
E
27
Prg
SAPLSPLUGIN
27
09.09.2004
14:18:36
8192
E
28
Prg
SAPLSTTMYes even i find it strange. But there is no syntax error and the fact is that it was working 2 days back. Suddenly it has started giving us this dump.
The code is as follows.
Commit design BAPI's
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT' .
IF save_okcode = con_order.
Commit order BAPI's
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
DESTINATION 'NONE'.
Here con_order is CU01.
Please let me know if anybody has faced this problem earlier.
Thanks in Advance
Meghana -
Short dump 'DBIF_RSQL_SQL_ERROR' in R/3 system
Hi,
In the daily extraction process in BW a load process(infopackage) fails due to short dump "DBIF_RSQL_SQL_ERROR" in the source system(R/3) side.
The load getting the 20000 records but the process failed due to above error. i have made the request red and delete the request from the respective data target and repeate the load, it isthrowing same error "DBIF_RSQL_SQL_ERROR" with 0 records.
my question is if i solve the error and repeate the load can i get previous delta records with the latest delta.
Can any one give a solution.
ThanksHi,
If you are marking the dataload as "RED" in monitor before deleting the request, you will get the same delta with next load.
You can verify this in next load @ monitor. It will show you the request type as 'Repeat of last delta' and normal requests will be shown as 'Delta'.
In case you are manually running the infopackage, system will prompt the message something like' last detla request was incorrect, repeat the last delta'.
Regards,
Pratap Sone -
Empty System Fields after error creates a short dump
Hello!
Could someone please help me?
After calling a function, I catch errors with sy-subrc NE 0.
Handling this error the "normal" way throws a short dump (I marked the row bold), because all the system fields are empty!
Could someone please give me a hint, how to handle this situation?
Many thanx in advance!
Perhaps some code:
CALL FUNCTION 'Z_CONFIRM'
EXPORTING
is_bdnum = is_bed-bdnum
TABLES
et_return = lt_return
EXCEPTIONS
error_occured = 1
lock_error = 2
OTHERS = 3.
IF sy-subrc NE 0.
MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
I get a short dump with this:
Content of the system fields
Name
Wert
SY-SUBRC
1
SY-INDEX
1
SY-TABIX
1
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
HTTP-Steuerung
SY-MSGTY
SY-MSGID
SY-MSGNO
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080117
SY-UZEIT
080907
SY-XPROG
SY-XFORMHi,
You need to capture the message like this way
IF sy-subrc eq 1.
message e999(your mesage class) with 'Error Occured'.
endif.
IF sy-subrc eq 2.
message e999(your mesage class) with 'Lock error'.
endif.
IF sy-subrc eq 3.
message e999(your mesage class) with 'Other Errors'.
endif.
a® -
Short dump while running Alert Monitor
Hi,
I am getting a short dump while determining alert in Alert Monitor through T. Code /SAPAPO/AMON1. The error says as below:
Runtime Errors BCD_NO_SIGN
Short text : A packed number contains no sign.
What happened? : Error in the ABAP Application Program, The current ABAP program "SAPLKKBL" had to be terminated because it has come across a statement that unfortunately cannot be executed.
Information on where terminated : Termination occurred in the ABAP program "SAPLKKBL" - in "FB_OUTTAB_SORT2".Hi Axon Generic,
Please checkon the following
1) In the overall profile of alert monitor, check the relative
time interval whether specified correctly
2) Under the alert profile in Overall profile, check the
threshold values are defined correctly
3) Check the SAP Note 151709 , 189061
Please confirm your findings.
Regards
R. Senthil Mareeswaran. -
System Throws short dump while executing data source 2LIS_11_VASCL in RSA3.
Hello Experts,
I got short dump while executing data source 2LIS_11_VASCL in RSA3.
The details are as follow.
When importing object "MC11VA0SCL_TAB", the structure did not match the
structure of the target object. The error occurred in component
no. 567.
This may be due to one of the following reasons:
- the structure is actually different (the next field has, for
example, a different data type) or
- the same sequence of components were exported and imported,
but the fields were from other include units.
I have checked source and target fields and those are of same length and data type.
Could you please give some points why this short dump occurs.
Thanks
Konda ReddyHi,
This error is not between BI and R/3. It is within R/3. You may have setup data and then modified the datasource.
Delete setup data, generate your datasource again. Setup data and try again.
If you are on a live system with data setup after a downtime and you do not want to delete it, then bring your datasource to the original state when you setup data and pull data.
Cheers.... -
Short dump when '1 BOX PACK' clicked on VL02N, in ECC 6 system
Hi
I am getting a short dump "'DYNPRO_MSG_IN_HELP' "when i click '1 box pack' button in VL02N transaction during our upgrade system from 4.6C to ECC 6.0. When i go through the old SAP note - 401823, it says to add entries in VFBS transaction for all T185 entries for this kind of dumps. But i am missing entries for SAPMV50A, I0 and ZVPK combination at support pack level '14'(SAP_APPL) in our system.
Could anyone let me know the entries to be maintained for all the T185* tables mentioned in VFBS transaction.
(or) is there any OSS note already created for this issue? please let me know all the details.
Thank you,
AnilHi Laxmi,
We are already in Support pack. (SAPKH60014), and note which you given was SP - SAPKH60007, so this correction was already implemented in our system.
Is there a note/solution specific to '1 BOX PACK' dump and T185* table entry missing?
Let me know,
thank you,
Anil -
Short Dumps in BW Production System
Hi BW Experts,
When iam loading the PCA data (0PCA_C01), i am getting the following Short Dumps in my Systems.
DBIF_RSQL_SQL_ERROR
RAISE_EXCEPTION
TSV_TNEW_PAGE_ALLOC_FAILED
TSV_TABH_POOL_NO_ROLL_MEMORY
TSV_TNEW_OCCURS_NO_ROLL_MEMORY
SYSTEM_NO_ROLL
Today i got 131 Short Dumps in my System.
Please can anyone tell me the solution for this Short Dumps.
Thanks in advance
Regards,
AnjaliI am receiving the following Run time error in a Process Chain
Name of the runtime: System_NO_ROLL
*Information on where terminated*
The termination occurred in the ABAP program "GP45O123XOQKIU82AMIR5C27RCN" in
"ROUTINE_9998".
The main program was "SAPMSSY1 ".
The termination occurred in line 3255 of the source code of the (Include)
program "GP45O123XOQKIU82AMIR5C27RCN"
of the source code of program "GP45O123XOQKIU82AMIR5C27RCN" (when calling the
editor 32550).
Source Code Extract
Line SourceCde
3225 *delete DATA_PACKAGE where CRM_SRVORG <> '50000053'.
3226 *** Move data package to internal table******************************
3227 *it_package[] = DATA_PACKAGE[].
3228 *SORT it_package ASCENDING BY CRM_ACGUID.
3229 *DELETE ADJACENT DUPLICATES FROM it_package
3230 * COMPARING CRM_ACGUID.
3231 *ilookup[] = it_package[].
3232 *SORT ilookup ASCENDING BY CRM_ACGUID.
3233 ** if abort is not equal zero, the update process will be canceled
3234 * ABORT = 0.
3235
3236 * New code to get the Interaction id for Quick Close
3237 DATA : it_package like STANDARD TABLE OF DATA_PACKAGE.
3238
3239 delete DATA_PACKAGE where CRM_SRVORG <> '50000053'.
3240
3241 it_package[] = DATA_PACKAGE[].
3242
3243 DELETE it_package where crm_prctyp <> 'Z260'
3244 AND crm_preotp <> 'BUS2000126'
3245 AND crm_predoc is INITIAL.
3246 SORT it_package ASCENDING BY crm_predoc.
3247
3248 DELETE ADJACENT DUPLICATES FROM it_package
3249 COMPARING crm_predoc.
3250
3251 SELECT CRM_ACGUID CRM_OBJ_ID FROM /BIC/AZ0SAL_D100 INTO TABLE ilookup
3252 FOR ALL ENTRIES IN it_package
3253 WHERE CRM_ACGUID = it_package-crm_predoc.
3254
>>>>> SORT ilookup ASCENDING BY CRM_ACGUID.
3256
3257
3258 -
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 -
Reporting Agent : Alert Monitor Preview - Short Dump
Hi All,
I have some questions related to Reporting Agent :
1.) When I am executing the Alert Monitor Preview, it ends with short dump.
2.) Where to do the settings for Email, Printing and Alert settings so as to send the notifications to the user using the different output options as mentioned above.
Please provide solutions.Hi Richa,
Chech in txn ST22 for your short dump to analyse the root cause of the error.
See this link for integration of BW Reporting with Alert Monitor.
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/031faa90-0201-0010-23b3-a5b88e812d15
Cheers!
Amit -
In 4.5b system, program temporarily buffered; short dump when changing
Hi,
I have a program needs to be activated in 4.5B system.. when I clicked on Change button it is displaying options: -
a) get temporary version
b) get from database and keep temporary
c) get from database and delete temporary
I tried all the 3 options... and try to change the program and activate it.. It is going to short dump.
Could someone tell what needs to be done..to activate the program and delete the temporary version.
Regards,
HKHi,
Thats the real problem . Try this way which i used previously. dont know how effective in 4.5B
1) In the SE38 screen, give the program name. in the menu list,
Utilities ->Versions->Versions Management
2) Try compare the latest with last version. Note down if there are any changes. If not much, you can select the previous version and press Retrieve button ( or CTRL + F5 )
Then try enter the program again. It will be in previous version. then you can activate it
If still this is not working, the practical way is to copy the program, save in local system. Delete the program and create a new one
//Kothand -
What is the purpose of short dump error report generated by the system? What r the major parts/section of this report?
hi please look through this:
Whenever any transaction or any process is executed it hits an ABAP code.
If there is any issue in executing the code the situation is called "ABAP DUMP" or 'Short Dump'
Transaction ST22 is used to check any ABAP Dump within a given duration.
U can also fix the issue with the help of ABAP editor (Transaction Code SE38) if u r good with ABAP.
you can select back to the last 14 days if you are
running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
old ABAP dumps every day, possibly further if you run it weekly or
monthly.
sap-basis sap-basisAll Groups Ignore this text box. It is used to detect spammers.If you enter anything into this text box, no search results will be displayed.
SAP Groups > Technical-functional > sap-basis > Message
About This Group | Invite peers to join this group
<< Prev thread < Prev msg Next msg > Next thread >>
short dump----urgent
Reply from Keith Lewis on 5/2/2003 3:22:00 AM
Good explanation Joy, but it is not only limited to the current day and
yesterday. If you click on the Selection button you can select previous
days as well. In fact you can select back to the last 14 days if you are
running the SAP_REORG_ABAPDUMPS job (program RSSNAPDL) which deletes te
old ABAP dumps every day, possibly further if you run it weekly or
monthly.
Cheers
Keith
SAP R/3 Support Specialist
Information Services International
Tel +44 1664 41 6178 Mobile +44 7887 627818
E-mail email@removed
Archive Page - http://www.ittoolbox.com//I/sap-r3-basis.asp
Dear sreenivas
If you receive an error message in the R/3 System log (SM21), or if you
see
a terminated update in the update service analysis transaction (SM13), or
DB
realated error ,check for dumps using the dump analysis transaction
(transaction ST22), or choose Tools -> Administration -> Monitoring ->
Dump
analysis.
Transaction ST22 enables you to analyze short dumps from the current and
previous day.
The dump analysis function shows you:
What happened
What you can do
How to correct the error
The dump analysis function also provides an error ID and keywords that you
can use to search in SAPNet, as well as information about:
The system environment
Users and transactions
Transaction ST22 enables you to analyze the following data:
Date, time, user, client
Contents of system and data fields
Contents of internal tables and application tables
ST22 is a very nice feature in SAP. This is where all the system errors
and users mistakes showed up. If there is a problem that you cannot
solve and you contact SAP support, they look at this area to analyze it.
This gives us lead where to handle the problems.
Error analysis
How to correct the error
System environment
User, transaction...
Information on where termination occurred
Contents of system fields
Chosen variables
Active calls / events
Internal notes
Active calls in SAP kernel
List of ABAP programs affected
List of internal tables
Directory of application tables (contents)
Directory of data areas (administration information)
Directory of data areas (contents)
ABAP control blocks CONT
End of runtime analysis
i think this would be helpful
regards
sravani -
Short Dump, Exception condition "NOT_EXIST" raised
Dear Colleagues!
I am having a problem with short dump, I am getting the message Exception condition "NOT_EXIST" raised.
I am trying to load data to ODS with full load and filtering via a DTP.
In the monitoring the load doesn't even get started.
I have already loaded data succesfully in this ODS... But now it doesn't work anymore..
I also tried to replicate and active all the rules and objects again.
And in the source system if I test the extractor it works fine.
I saw an earlier thread on this issue, and it recommended programs ZDMDELTAREPAIR or RSBDELTAREPAIR, but this thread was especially for BW 3.5. We are using 7.0 and have SP10. Are these programs still valid or is there another note for 7.0?
Hope you can help!
Regards Silje
Does anyone have any ideas?
regards, UrosHi again,
I tried RSBDELTAREPAIR and it worked!
Thanks to the forum again!
Silje
Maybe you are looking for
-
Shortage qty - sub-contract process
hi, In sub-contract process: Vendor suppose to return - 10 qty but, we received only 8 qty. Vendor has accepted to pay For shortage 2 qty. 1. How to address the above scenario?. (exciseable material) reg mrs
-
Hi All, I have a requirement to enhance the vendor payment process by using BTE.I am using the P/S BTE 1030 for the same. Can anyone guide me as to what is the field AUZZ3-AGZEI have any relationship with the other tables of the sample FM. regards, P
-
Concept Question about EDI and Error Processing
Hello All, This is a concept question, I was wondering how others would approach this scenario. Let's take this scenario. In EDI often the transmission for a purchase order comes in with an invalid material number. Normal error processing is for the
-
My steam keeps on asking for universal access
My steam keeps on asking for universal access but i gave it access and it keeps on asking for it!!!!!! help me please!!!!
-
My system drives locked up -- "custom" access can't be reset
My system crashed and it took be a day and a half to get it working again: Lion wouldn't reinstall from the DVD, from the internet or from the Lion USB stick I made. Finally I pulled out all the drives and put in only a Lion drive I had set aside as