ST22 Dumps in ECC pushed to Slution Manager

Hi,
We have a ECC6.0 and Solution Manager in our system.
I wanted to configure that if a ST22 Dump occurs in ECC 6.0, the ST22 dump should be pused to the Solution Manager and i should be able to view it through the Solution Manager.
Please let me know whether it is possible or anyone has done it

Dear andreas,
You will not be able to see ST22 dumps in solution Manager. You can see dumps in Solution Manager Diagonstics.. for that you need to configure SMD agents on satelite system and SMD on solution Manager...
also if you just want to get alerts .. you can configure.. CCMS RZ20 and use solution manager as central system..
search in help.sap.com for more info..
Let me know if you require any furher info..
Regards,
akhilesh

Similar Messages

How to avoid short dump in ECC 5.0

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

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

COMPUTE_BCD_OVERFLOW ST22 dump

Dear All,
When I run the ECC_PRD_BITX_D_FDM_INVOICE, which is a standard SAP(program FDM_INVOICE_MEMORY).
I get COMPUTE_BCD_OVERFLOW ST22 dump.
This short dump occured due to CX_SY_ARITHMETIC_OVERFLOW i.e. Target field size was not able to store the value of source field at the folowing code location while assigning value to l_days_of_delay.
 90 ENDIF.
 91
 92 * set actual discount and delay in payment
>>>>> l_days_of_delay = sy-datlo
 94 - <open_item>-zfbdt
 95 - <open_item>-zbd1t.
Are there SAP Notes that can solve this problem?
My system details
S/w Component : SAP_APPL
Release : 604
Highest Support : SAPKH60405
sapnote_0000620532, sapnote_0001239612 , sapnote_0001323002 do not work in my system
Regards,
Jack Silverz

hi jack,
just check these avalilabe notes for your dump.
620532
1323002
1239612
hope this will help u.
thanks

How can I read st22 dump in ABAP

hello,
i would like to know if st22 dump info could be read via FMs or Classes. I found a class CL_DUMP_INFO_MANAGER, btu well could not find documentation on it usage. Will be glad if someone can tell me how to retrieve St22 info.
- Harish

Hi,
Try the fun module
RS_ST22_GET_DUMPS
to get the dump results.
other related fun modules are:
RS_ST22_GET_DUMPS_CATEGORIES
RS_ST22_GET_DUMP_CATEGORY
RS_ST22_GET_DUMP_CATEGORY_TEXT
reward if useful
regards,
Anji

UNCAUGHT_EXCEPTION in SOAP TO PROXY scenario dump in ECC system.

Hi Experts,
My scenario is saop to proxy .while performing testing the scenario using saopui. iam getting client_send_failed error in sxmb_moni.
but data processed to ecc system and updated the data in database level and giving dump in ecc system.
i am getting dump like below.
UNCAUGHT_EXCEPTION.
we increased the size of instance profile parameters also upto 500 mb .in rz10.
still getting dump.
Please give the solution for above.
Regards
Ravinder.s

Hi All,
We resolved the issue using below notes and my system is newly upgraded its not accepting asynchronous scenarios with quality of service as BE in sender communication channel.
1966422 - XI runtime: Dump: synchronous proxy calls asynchronous interface
Thanks for all.

ST22 Dump - Need to find associated proxy XML

Hi,
I need to find the inbound proxy call (xml message), which has caused the ST22 dump. Can any of you tell me whether the transaction id or any other values from ST22 can be used to track the message unique?
Thanks,

HI Joe,
for any proxy call either inbound or outbound, you will find all the processed the messages in the SXMB_MONI transaction.
the messages which are processed successfully has the status and processed successfully but if there is any problem during the processing of message because of program dump then this message remains in the green flagged status. hence try to find out the green flagged status and check the error log for the same. you will find out the exact error message which is appearing in ST22.
you can also try to check the queue using smq2 transaction , if there is any dump while processing the message the followeing messages are got stuck as long as you are not deleting the first messages. from there also you can see the erroneous XML data.

St22 Dump in Mail

Dear All,
I want to configure the St22 dump in mail , With criteria if Mail is more than 150 in a day it should send a mail.Please Let me know the steps need to be done.
RK

Hello Rableen,
in RZ20 there are several MTEs, where dumps are catched, for example, ABAP dumps are displayed under:
RZ20 --> SAP CCMS Monitor Templates
 --> Entire System
 --> <SID> --> Application Server
 --> <instance> --> R3Abap
and here you have these MTEs
You can configure threshold values in the properties of MTE "Shortdumps Frequency" and assign an autoreaction method.
But this MTE is only for ABAP dumps. Other type of dumps you can find as described in KBA:
1942651 - RZ20 does not display shortdumps
but there is no such monitor in RZ20, which cathes all dumps from ST22 in one MTE.
Regards,
Alwina

Trigger ST22 Dumps as EMAIL

Hi Everyone,
I want all my ST22 Dumps to be automatically triggered to a particular User mail id (Busines Workplace). so that, if any new Dump comes in a Production system i will come to know that while checking mail and provide solution immediately.How this can be done from Basis side
Thanks& Regards,
Siva

Hai,
Check the below link.....
http://help.sap.com/saphelp_nw70/helpdata/en/2c/abb2e7ff6311d194c000a0c93033f7/frameset.htm
Regards,
Yoganand.V

Background job failing - ECC 6.0, Solution Manager 7.0

Dear All,
Four days back, I have installed the Solution Manager 7.0 and ECC 6.0 on
HPUX IA64 hardware with database as Oracle 10.2.0.2.0 (Unicode).
In both server, latest kernel patch has been applied.
The Support package versions are (both server):
KERNEL (Release 700)      146
SAP_BASIS           0014
SAP_ABA           0014
PI_BASIS(2005_1_700)      0014
ST-PI                0005
SAP_BW                0016
While checking the the jobs from SM37, in both the server,
I am observing that following jobs are always failing with
same reason:
SAP_COLLECTOR_FOR_PERFMONITOR
=============================
Date       Time     Message text                                                           Message class Message no. Message type
========== ======== ====================================================================== ============= =========== ============
15.05.2008 06:25:12 Job started                                                                 00           516          S
15.05.2008 06:25:12 Step 001 started (program RSCOLL00, variant , user ID BGDUSER)              00           550          S
15.05.2008 06:25:18 Clean_Plan:Cleanup of DB13 Plannings                                       DB6PM         000          S
15.05.2008 06:25:18 Clean_Plan:started by RSDBPREV                       on server gcbeccd     DB6PM         000          S
15.05.2008 06:25:18 Clean_Plan:Cleaning up jobs of system RD3                                  DB6PM         000          S
15.05.2008 06:25:18 Clean_Plan:finished                                                        DB6PM         000          S
15.05.2008 06:25:18 Database system not supported                                               S1           101          S
15.05.2008 06:25:36 ABAP/4 processor: DBIF_DSQL2_SQL_ERROR                                      00           671          A
15.05.2008 06:25:36 Job cancelled                                                               00           518          A
SAP_REORG_UPDATERECORDS
=======================
Date       Time     Message text                                                          Message class Message no. Message type
========== ======== ===================================================================== ============= =========== ============
14.05.2008 00:31:01 Job started                                                                00           516          S
14.05.2008 00:31:01 Step 001 started (program RSM13002, variant SAP&001, user ID BGDUSER)      00           550          S
14.05.2008 00:31:01 Reorganization of update date not allowed in batch                         15           100          A
14.05.2008 00:31:02 Job cancelled                                                              00           518          A
SAP_WP_CACHE_RELOAD_FULL
========================
Date       Time     Message text                                                                                Message class Message no. Message type
========== ======== ============================================================================================ ============= =========== ============
15.05.2008 00:30:11 Job started                                                                                00           516          S
15.05.2008 00:30:11 Step 001 started (program RWP_RUNTIME_CACHE_RELOAD, variant SAP&RELOAD_ALL, user ID BGDUSER)      00           550          S
15.05.2008 00:30:11 No component system chosen                                                                   URL_GEN_MSGS      031          E
15.05.2008 00:30:11 Job cancelled after system exception ERROR_MESSAGE                                                00           564          A
Please help to resolve this issue.
Thanks in advance.
Regards
Sudip Ghosh

Hi Markus,
Thanks for the reply.
Below is the dump:
======
======
Runtime Errors         DBIF_DSQL2_SQL_ERROR
Date and Time          15.05.2008 06:25:36
Short text
An SQL error occurred when executing Native SQL.
What happened?
The error 3113 occurred in the current database connection "DEFAULT".
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.
How to correct the error
Database error text........: "ORA-03113: end-of-file on communication channel"
Database error code........: 3113
Triggering SQL statement...: "FETCH NEXT "
Internal call code.........: "[DBDS/NEW DSQL]"
Please check the entries in the system log (Transaction SM21).
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:
"DBIF_DSQL2_SQL_ERROR" " "
"RSORAVSH" or "RSORAVSH"
"FILL_DBVSE"
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
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
System environment
SAP-Release 700
Application server... "gcbeccd"
Network address...... "10.10.4.158"
Operating system..... "HP-UX"
Release.............. "B.11.23"
Hardware type........ "ia64"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 15
Shortdump setting.... "full"
Database server... "gcbeccd"
Database type..... "ORACLE"
Database name..... "RD3"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 5 2008 00:55:24"
create on........ "HP-UX B.11.23 U ia64"
Database version. "OCI_102 (10.2.0.1.0) "
Patch level. 146
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "HP-UX B.11"
Memory consumption
Roll.... 1117216
EM...... 0
Heap.... 0
Page.... 32768
MM Used. 695792
MM Free. 400816
User and Transaction
Client.............. 000
User................ "BGDUSER"
Language key........ "E"
Transaction......... " "
Transactions ID..... "482B8A4C89F0442BE10000000A0A049E"
Program............. "RSORAVSH"
Screen.............. "SAPMSSY0 1000"
Screen line......... 6
Information on where terminated
Termination occurred in the ABAP program "RSORAVSH" - in "FILL_DBVSE".
The main program was "RSORAVSH ".
In the source code you have the termination point in line 48
of the (Include) program "RSORAVSH".
The program "RSORAVSH" was started as a background job.
Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
Job Initiator.. "BGDUSER"
Job Number..... 05251100
Source Code Extract
Line
SourceCde
18
INCLUDE STRUCTURE v_system_event_struc.
19
DATA: END OF v_system_event_tab .
20
21
check sy-dbsys(3) = 'ORA' .
22
23
Get the new snapshots
24
25
PERFORM fill_dbvse TABLES v_system_event_tab.
26
27
28
Get the old snapshots from database table MONI
29
30
startday = sy-datum - days_to_keep .
31
32
33
Save new data now (otherwise these data will be selected twice)
34
35
CONCATENATE 'SYSEVENT' sy-datum sy-uzeit INTO   monikey .
36
37
EXPORT sy-datum
38
sy-uzeit
39
v_system_event_tab
40
TO DATABASE moni(db) ID monikey .
41
42
*&      Form FILL_DBVSE
43
44
FORM fill_dbvse TABLES v_system_event_tab.
45
date = sy-datum .
46
time = sy-uzeit .
47
EXEC sql performing append_v_system_event .
>>>>>
select event,
49
total_waits,
50
total_timeouts,
51
time_waited * 10,
52
average_wait * 10
53
into :v_system_event_struc
54
from v$system_event
55
ENDEXEC .
56
ENDFORM.                               " FILL_DBVSE
57
58
59
*&      Form APPEND_V_SYSTEM_EVENT
60
61
FORM append_v_system_event.
62
v_system_event_tab-date = date .
63
v_system_event_tab-time = time .
64
65
MOVE-CORRESPONDING v_system_event_struc TO v_system_event_tab.
66
APPEND v_system_event_tab .
67
ENDFORM.                               " APPEND_V_SYSTEM_EVENT
Contents of system fields
Name
Val.
SY-SUBRC
0
SY-INDEX
0
SY-TABIX
16
SY-DBCNT
0
SY-FDPOS
0
SY-LSIND
0
SY-PAGNO
0
SY-LINNO
1
SY-COLNO
1
SY-PFKEY
SY-UCOMM
SY-TITLE
Report for Collecting Data from V$SYSTEM_EVENT Hourly
SY-MSGTY
SY-MSGID
SY-MSGNO
000
SY-MSGV1
SY-MSGV2
SY-MSGV3
SY-MSGV4
SY-MODNO
0
SY-DATUM
20080515
SY-UZEIT
062520
SY-XPROG
RSDBRUNT
SY-XFORM
%_INIT_PBO_FIRST
Active Calls/Events
No.   Ty.          Program                             Include                             Line
Name
2 FORM         RSORAVSH                            RSORAVSH                               48
FILL_DBVSE
1 EVENT        RSORAVSH                            RSORAVSH                               25
START-OF-SELECTION
Chosen variables
Name
Val.
No.       2 Ty.          FORM
Name FILL_DBVSE
SY-REPID
RSORAVSH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545455422222222222222222222222222222222
23F2163800000000000000000000000000000000
V_SYSTEM_EVENT_STRUC
00000000000000000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000000000000000000000000000000000000000000000
22222222222222222222222222222222222222222222222222222222222222220000000000000000
0000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
%_SPACE
0
0
2
0
SY
###############################################################################T######## ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
No.       1 Ty.          EVENT
Name START-OF-SELECTION
SY-LDBPG
SAPDB__S
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5454455522222222222222222222222222222222
31042FF300000000000000000000000000000000
%_DUMMY$$
0000
0000
2222
0000
SY-DBSYS+0(6)
ORA
000
000
454
F21
SYST
###############################################################################T######## ####
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000004000000
000000000000000000000000000000000000000100000000000000000000000000000000000000000000000D000400
000001000000000000000000000000000000000F000000000000000000000000000000000000010500000005220000
000000000000000000000000010001000000000E00000000000000000000000000000000000006040000000800000C
V_SYSTEM_EVENT_TAB[]
Table[initial]
V_SYSTEM_EVENT_TAB
00000000000000                                                                ################
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
3333333333333322222222222222222222222222222222222222222222222222222222222222220000000000000000
000000000000000000000000000000000000000000000000000000000000000000000000000000000C000C000C000C
SY-DATUM
20080515
00000000
00000000
33333333
20080515
DAYS_TO_KEEP
30
0001
000E
STARTDAY
00000000
00000000
00000000
33333333
00000000
MONIKEY
0000000000000000000000
0000000000000000000000
2222222222222222222222
0000000000000000000000
SY-UZEIT
062520
000000
000000
333333
062520
SYST-REPID
RSORAVSH
0000000000000000000000000000000000000000
0000000000000000000000000000000000000000
5545455422222222222222222222222222222222
23F2163800000000000000000000000000000000
MONI-CLUSTR
0
00
00
MONI
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
2222222222222222222222220022000000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
Internal notes
The termination was triggered in function "ExecuteCall"
of the SAP kernel, in line 1190 of the module
"//bas/700_REL/src/krn/runt/abexsql.c#2".
The internal operation just processed is "DSQL".
Internal mode was started at 20080515062520.
Internal call code.........: "[DBDS/NEW DSQL]"
Active Calls in SAP Kernel
Lines of C Stack in Kernel (Structure Differs on Each Platform)
(0) 0x4000000003b2b450 CTrcStack + 0x1b0 at dptstack.c:227 [dw.sapRD3_DVEBMGS00]
(1) 0x4000000004d2c470 Z16rabaxCStackSavev + 0x1d0 [dw.sapRD3_DVEBMGS00]
(2) 0x4000000004d32160 ab_rabax + 0x3570 [dw.sapRD3_DVEBMGS00]
(3) 0x40000000047b51e0 Z10abdbdserriPKtiS0_P9DS_HEADERS0_iPv + 0x470 [dw.sapRD3_DVEBMGS00]
(4) 0x4000000003d777f0 Z11ExecuteCallv + 0x11f0 [dw.sapRD3DVEBMGS00]
(5) 0x4000000003d7e7b0 Z8abjdsqlv + 0x1b0 [dw.sapRD3_DVEBMGS00]
(6) 0x400000000402f190 Z8abextriv + 0x440 [dw.sapRD3_DVEBMGS00]
(7) 0x4000000003f53bc0 Z9abxeventPKt + 0x3c0 at abrunt1.c:339 [dw.sapRD3_DVEBMGS00]
(8) 0x4000000003d9f210 Z8abtriggv + 0x110 at abrunt1.c:58 [dw.sapRD3_DVEBMGS00]
(9) 0x4000000003d9ebe0 ab_run + 0xc0 [dw.sapRD3_DVEBMGS00]
(10) 0x4000000001caa820 N_ab_run + 0x20 at dymainstp.c:4739 [dw.sapRD3_DVEBMGS00]
(11) 0x4000000001cb40f0 dynpmcal + 0x3f0 at dymainstp.c:2281 [dw.sapRD3_DVEBMGS00]
(12) 0x4000000001caf260 dynppai0 + 0xcb0 at dymainstp.c:1107 [dw.sapRD3_DVEBMGS00]
(13) 0x4000000001cb1ec0 dynprctl + 0x340 at dymainstp.c:358 [dw.sapRD3_DVEBMGS00]
(14) 0x4000000001c9dff0 dynpen00 + 0xac0 at dymain.c:1628 [dw.sapRD3_DVEBMGS00]
(15) 0x4000000001fea460 Thdynpen00 + 0x510 at thxxhead.c:4830 [dw.sapRD3_DVEBMGS00]
(16) 0x4000000001fb54e0 TskhLoop + 0x5520 at thxxhead.c:3945 [dw.sapRD3_DVEBMGS00]
(17) 0x4000000001faae40 ThStart + 0x460 at thxxhead.c:1164 [dw.sapRD3_DVEBMGS00]
(18) 0x4000000001569ec0 DpMain + 0x5f0 at dpxxdisp.c:1088 [dw.sapRD3_DVEBMGS00]
(19) 0x4000000002c10630 nlsui_main + 0x30 [dw.sapRD3_DVEBMGS00]
(20) 0x4000000002c105c0 main + 0x60 [dw.sapRD3_DVEBMGS00]
(21) 0xc00000000002be30 main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]
List of ABAP programs affected
Index
Typ
Program
Group
Date
Time
Size
Lang.
0
Prg
RSORAVSH
0
30.03.2005
10:21:59
19456
E
1
Prg
SAPMSSY0
1
17.12.2007
15:41:05
92160
E
2
Prg
SAPMSSYD
1
12.09.2006
11:33:31
21504
E
3
Prg
SAPFSYSCALLS
1
09.09.2004
14:18:32
8192
E
4
Prg
RSDBRUNT
0
17.12.2007
16:04:40
254976
E
5
Typ
RSSCR
0
30.03.2005
10:21:45
5120
6
Prg
RSDBSPBL
0
30.03.2005
10:21:58
72704
E
7
Prg
SAPDB__S
0
30.03.2005
10:22:01
19456
E
8
Prg
RSDBSPMC
0
12.09.2006
11:25:01
79872
E
9
Typ
DDSHDESCR
0
03.09.1997
03:05:16
4096
10
Typ
SPPARAMS
0
07.05.1997
13:10:38
2048
11
Prg
SAPLSABE
11
09.09.2004
14:18:36
13312
E
12
Prg
SAPLSECU
12
17.12.2007
15:31:45
87040
E
13
Typ
RSSUBINFO
0
14.10.1999
22:01:03
3072
14
Prg
SAPLSTUP
14
17.12.2007
15:29:58
74752
E
15
Prg
SAPLCNDP
15
11.09.2007
15:24:45
195584
E
16
Prg
SAPLSCNT
16
18.02.2005
14:16:06
30720
E
17
Prg
SAPSHDTV
16
05.01.2005
16:26:16
33792
E
18
Prg
SAPFGUICNTL
1
18.02.2005
14:15:08
24576
E
19
Prg
SAPLOLEA
19
11.09.2007
11:17:30
96256
E
20
Prg
SAPLSGUI
20
17.12.2007
15:41:05
84992
E
21
Prg
SAPLSTTM
21
05.07.2005
13:10:18
69632
E
22
Prg
SAPLSBDC
22
17.12.2007
15:30:54
44032
E
23
Prg
SAPLSFES
23
17.12.2007
16:04:40
260096
E
24
Prg
SAPLTHFB
24
17.12.2007
15:41:05
394240
E
25
Typ
WPINFO
0
26.02.1999
14:49:01
6144
26
Prg
SAPLURFC
26
17.12.2007
15:37:35
22528
E
27
Prg
SAPLSPLUGIN
27
09.09.2004
14:18:36
8192
E
28
Typ
SWCBCONT
0
15.11.2000
17:55:11
3072
29
Typ
OLE_VERBS
0
04.04.1995
16:02:20
2048
30
Typ
OLE_PA
0
04.04.1995
16:02:19
2048
31
Typ
SYST
0
09.09.2004
14:18:12
31744
32
Typ
MONI
0
31.03.2004
16:41:21
5120
Directory of Application Tables
Name                                     Date       Time       Lngth
Val.
Program RSORAVSH
SYST                                     09.09.2004 14:18:12   00004612
\0\0\0\0\0\x0010\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0
MONI                                       . .       : :     00002944
\0\0 \0\0\0\0\0\0\0\0\0\0\0\0\0\0
ABAP Control Blocks (CONT)
Index
Name
Fl
PAR0
PAR1
PAR2
PAR3
PAR4
PAR5
PAR6
Source Code
Line
71
PAR2
03
0000
0014
002B
RSORAVSH
37
73
PAR2
03
0000
0015
002D
RSORAVSH
37
75
PAR2
03
0000
0016
0026
RSORAVSH
37
77
00
0000
RSORAVSH
37
78
PERP
00
0002
RSORAVSH
44
79
PERP
1C
0000
RSORAVSH
44
80
PERP
04
0000
RSORAVSH
44
81
mvqk
10
0005
0044
04EC
RSORAVSH
45
83
mvqk
0C
0005
0054
052E
RSORAVSH
46
85
DSQL
00
0017
RSORAVSH
48
86
DSQL
01
0018
RSORAVSH
48
87
DSQL
04
0025
RSORAVSH
48
>>>>>
DSQL
16
0025
RSORAVSH
48
89
BRAN
05
0004
RSORAVSH
48
90
perf
00
000A
RSORAVSH
48
91
PERP
80
0000
RSORAVSH
48
92
BRAX
00
FFFC
RSORAVSH
48
93
DSQL
23
0000
RSORAVSH
48
94
ENDF
00
0000
RSORAVSH
56
95
00
0000
RSORAVSH
56
===========
===========
Please check and advise.
Also, I am trying to search for the note 6083 in market place, but not getting the same.
Please advise.
Thanks & Regards
Sudip

ST22 Dumps: Shared Objects

Hi SDN,
in our SRM System, SRM Server 5.5, WAS700 ABAP, we get ST22 Short Dumps concerning "shared objects".
This is the Dump Short Analysis:
Runtime Errors         SYSTEM_NO_SHM_MEMORY
Date and Time          19.08.2008 12:20:50
Short text
     No more memory for 2516576 bytes in the shared objects memory.
What happened?
     The shared objects memory is full or an area management specified
     memory limit has be reached.
In heard, that "shared objects" is part of the new WAS 620, 640, 2004s, 700 ... releases
What are exactly these shared objects. And how can we avoid the dumps?
We have an instance profile parameter set:
abap/shared_objects_size_MB                 100
Apparently this is not enough... Are there any recommendations?
thanx, matthias

Take a look at [Note 972757 - Occurence of the SYSTEM_NO_SHM_MEMORY runtime error|https://service.sap.com/sap/support/notes/972757] for further information. You should investigate what is using the shared objects memory, it may be an error in a application. The note will help to determine this.
Regards,
Nelis

ITS Dumps while Approving Shopping cart as Manager

Hi,
I logged into SRM system as a Manager to Approve Shopping cart.
Click Start Enterprise Buyer Inbox link and then Click Approve icon for a shopping cart.
The following errors displayed
Error when processing your request
What has happened?
The URL https://sapdev30.xxx.xxxx.xxx:1443/sap/bc/gui/sap/its/BBP_BGRD_APP/! was not called due to an error.
Note
The following error text was processed in the system E02 : Error message occurred.
The error occurred on the application server sapdev30_E02_00 and in the work process 0 .
The termination type was: RABAX_STATE
The ABAP call stack was:
SYSTEM-EXIT of program SAPMSYST
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system <SID>in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server sapdev30_<SID>_00 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 0 in transaction ST11 on the application server sapdev30_<SID>_00 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Any cluse, please tell me.
Regards
Srinivas.

Hi
Couple of reasons can be possible here for the short dump (on ITS) ->
What all errors you notice in transaction SM21, RZ20, SLG!, and ST22 Transactions ?
Please paste complete short dump details, by saving the same in a notepad(text) file.
1. User attributes missing
http://help.sap.com/saphelp_srm50/helpdata/en/fa/fa7d3cb7f58910e10000000a114084/frameset.htm
2. Missing roles to the Approver user
http://help.sap.com/saphelp_srm50/helpdata/en/a0/10213862f7bd47e10000009b38f8cf/frameset.htm
ALso pls check the following:
-->activate the services through SICF tcode.
> Go to SICF transaction and activate the whole tree under the node Default host>sap>bc>gui>sap>its.
Are all the ITS services published correctly ?
Please ensure IACOR service must be running correctly before publishing the HTML Templates using the report - W3_PUBLISH_SERVICES
When you are using the Internal ITS,you need not run the report W3_PUBLISH_SERVICES.(only SIAC_PUBLISH_ALL_INT report )
Is IACOR running correctly ? chk it out using SMICM Transaction.
What all errors are you getting in ST22, SLG1, SICF and RZ20 transactions. ?
Have you maintained Z roles for the ITS users or maintaied Z roles using PFCG transactions ?
Are you using Integrated ITS or ITS service on a seperate site. ?
Ensure that the Internet sites in SRM system are maintained in table TWPURLSVR using SM30 Transaction.
Other related links ->
Re: why can I not find Service BBPGLOBAL in TA SICF?
Re: Problem on SRM logon
Re: The ABAP call stack was: SYSTEM-EXIT of program BBPGLOBAL
Re: Dump
Re: ITS_CANT_LOAD_INCLUDE in BBPstart service
Let me know the details.
Hope this will help.

ST22 Dump Pointing to ab_inidt?

Anybody ever seen this in a dump?
The termination occurred in the function "ab_inidt" of the SAP
Basis System, specifically in line 336 of the module
"//bas/46D/src/krn/runt/abload4.c#3".
Thank-You.

ABAP runtime errors    LOAD_COMMON_PART
       Occurred on     09/10/2007 at 13:48:27
The length of COMMON PART "PRIPDATA" in program "SAPFV50P" is incorrect.
What happened?
The current ABAP/4 program "SAPMV50A " 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
The structure of the COMMON PART "PRIPDATA" in program "SAPFV50P" is
different from the area in the calling program.

SAP ST22 dump SAPSQL_ARRAY_INSERT_DUPREC

Hi All,
We are getting dump SAPSQL_ARRAY_INSERT_DUPREC in testing system. SAP basis: 701 and Oracle 10.2.0.2
We are getting this dump from yesterday only and the details of the dump are as mentioned below:
============================================================================================
Short text
    The ABAP/4 Open SQL array insert results in duplicate database records.
What happened?
    Error in the ABAP Application Program
    The current ABAP program "SAPLSBAL_DB_INTERNAL" had to be terminated because it
     has
    come across a statement that unfortunately cannot be executed.
Error analysis
    An exception occurred that is explained in detail below.
    The exception, which is assigned to class 'CX_SY_OPEN_SQL_DB', was not caught
     in
    procedure "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(FUNCTION)", 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:
    If you use an ABAP/4 Open SQL array insert to insert a record in
    the database and that record already exists with the same key,
    this results in a termination.
    (With an ABAP/4 Open SQL single record insert in the same error
    situation, processing does not terminate, but SY-SUBRC is set to 4.)
Information on where terminated
    Termination occurred in the ABAP program "SAPLSBAL_DB_INTERNAL" - in
     "BAL_DB_INTERNAL_NO_UPDATE_TASK".
    The main program was "SWNCCOLL ".
    In the source code you have the termination point in line 64
    of the (Include) program "LSBAL_DB_INTERNALU02".
    The program "SAPLSBAL_DB_INTERNAL" was started as a background job.
    Job Name....... "SAP_COLLECTOR_FOR_PERFMONITOR"
    Job Initiator.. "BASIS"
    Job Number..... 08893100
    The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
    procedure "BAL_DB_INTERNAL_NO_UPDATE_TASK" "(FUNCTION)", but it was neither
     handled locally nor declared
    in the RAISING clause of its signature.
    The procedure is in program "SAPLSBAL_DB_INTERNAL "; its source code begins
     line
    1 of the (Include program "LSBAL_DB_INTERNALU02 ".
System environment
    SAP-Release 701
    Application server... "appl543"
    Network address...... "122.99.01.88"
    Operating system..... "AIX"
    Release.............. "5.3"
    Hardware type........ "099DER88BN90000"
    Character length.... 16 Bits
    Pointer length....... 64 Bits
    Work process number.. 27
    Shortdump setting.... "full"
    Database server... "appl543"
    Database type..... "ORACLE"
    Database name..... "Q22"
    Database user ID.. "SAPSR3"
=====================================================================================================
Also some jobs are cancelled and they are forming the above dump. the detials are:
SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 00:43:31
SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 02:43:31
SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 03:43:31
SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 04:43:31
SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 05:43:31
SAP_COLLECTOR_FOR_NONE_R3_STAT                 BASIS        Canceled        17.12.2010 06:43:31
**The cancelled job SAP_COLLECTOR_FOR_NONE_R3_STAT generating the above dump at ST22.**
Please suggest us a solution. Thanks in advance!!!
Regards
Veera
Edited by: Veerab on Dec 17, 2010 11:33 AM

>     1 of the (Include program "LSBAL_DB_INTERNALU02 ".
Try the following:
open http://service.sap.com/notes
Search for "LSBAL_DB_INTERNALU02"
Markus

ABAP dump in ecc 6.0 for F110 transaction

HI All,
We have recently upgraded to ECC 6.0 from 4.6C.
While displaying the proposal/exception list using F110 transaction for the program RFZALI20. The ABAP dump says "Unable to interpret "1 5D " as a number". It is failing for Key for print parameters (PRI_PARAMS-PRKEYEXT).
Has anyone faced this issue?
Thanks in advance.
-APK

HI Balaji,
We could get over this issue by changing the print parameters in the variant we have used.
The variant had some print parameters selected (having green check) even though there are no parameters which are selected. So, I have created a varaint without the print parameters option checked (no more green check in the extended selection).
Hope this is clear.
-Pradeep

Error in Import Java Dump phase while installing SAP solution Manager 7.1

Hi,
While installing SAP solution manager 7.1 I am getting the below error during the phase "Import Java Dump".
An error occurred while processing option SAP Solution Manager 7.1 > SAP Systems > MS SQL Server > Central System > Central System( Last error reported by the step : Execution of JLoad tool 'C:\j2sdk1.4.2_17-x64\bin\java.exe -classpath "C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\MSS\CENTRAL\AS\install\sharedlib\launcher.jar" -showversion -Xmx1024m com.sap.engine.offline.OfflineToolStart com.sap.inst.jload.Jload "C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/MSS/CENTRAL/AS/install/lib/iaik_jce.jar;C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/MSS/CENTRAL/AS/install/sharedlib;D:/usr/sap/SPT/SYS/exe/uc/NTAMD64/mssjdbc/sqljdbc.jar" -sec SPT,jdbc/pool/SPT,
smn/sapmnt/SPT/SYS/global/security/data/SecStore.properties,
smn/sapmnt/SPT/SYS/global/security/data/SecStore.key -dataDir "D:/SAP SOLMAN/Java Components/51040039\DATA_UNITS\SOLMAN_JAVA_EXPORT_JDMP" -job "C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\MSS\CENTRAL\AS\IMPORT.XML" -log jload.log' aborts with return code 1. SOLUTION: Check 'jload.log' and 'C:/Program Files/sapinst_instdir/SOLMAN71/SYSTEM/MSS/CENTRAL/AS/jload.java.log' for more information.
JLOAD.JAVA log details below
java version "1.4.2_17"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_17-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_17-b06, mixed mode)
Jload R 7.12 V 0 A 0
Jload -sec SPT,jdbc/pool/SPT,
smn/sapmnt/SPT/SYS/global/security/data/SecStore.properties,
smn/sapmnt/SPT/SYS/global/security/data/SecStore.key -dataDir D:/SAP SOLMAN/Java Components/51040039\DATA_UNITS\SOLMAN_JAVA_EXPORT_JDMP -job C:\Program Files\sapinst_instdir\SOLMAN71\SYSTEM\MSS\CENTRAL\AS\IMPORT.XML -log jload.log
Connecting to database
Couldn't connect to DB
com.sap.inst.common.exception.DBConnectionException: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed. java.net.ConnectException: Connection refused: connect
     at com.sap.inst.common.db.DBConnection.connect(DBConnection.java:157)
     at com.sap.inst.jload.Jload.main(Jload.java:222)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host has failed. java.net.ConnectException: Connection refused: connect
     at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDriverError(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.loginWithoutFailover(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(Unknown Source)
     at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(Unknown Source)
     at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)
     at com.sap.inst.common.db.DBConnection.connectViaSecureStore(DBConnection.java:111)
     at com.sap.inst.common.db.DBConnection.connect(DBConnection.java:151)
     ... 6 more
An error occured during execution. Please consult SAP note 942766 for first steps on troubleshooting the problem.
I have gone thru with the notes and it didn't help me much.
I have used J2SDK 1.4.2_17 nad JCE_Policy-1.4.2 files.
Please let me know where IO went wrong.
Thanks in advance.
Sai

Hi,
1. Did you select java path (Export CD/DVD) while intsallation? Check once again.
2. Add JAVA_HOME = Java path in environment variable.
3. What is the exact error, you got it, post error here.
Regards,
Srini Nookala

ST22 Dumps in ECC pushed to Slution Manager

Similar Messages

Maybe you are looking for