Visit our Google Group Way 2 SAP BASIS

problem while hitting transaction db02 for monitering db?

Moderators: BASIS24x7, Rashed

problem while hitting transaction db02 for monitering db?

Postby raghucharan v »

hi,


i am hitting the transaction db02 for database monitering?
The transaction is not been executed up till now after many repeations. it is consuming lot of time and the process is terminating.


following is the log of the problem?




Runtime errors TIME_OUT
Occurred on 12.03.2008 at 14:53:50
------------------------------------------------------------------------------------------

Time limit exceeded.

--------------
What happened?
--------------

The program "SAPLSTD4 " has exceeded the maximum permitted runtime without
interruption, and has therefore been terminated.


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

After a certain length of time, the program is terminated. In the case
of a work area, this means that
- endless loops (DO, WHILE, ...),
- database accesses producing an excessively large result set,
- database accesses without a suitable index (full table scan)
do not block the processing for too long.

The system profile "rdisp/max_wprun_time" contains the maximum runtime of a
program. The
current setting is 600 seconds. Once this time limit has been exceeded,
the system tries to terminate any SQL statements that are currently
being executed and tells the ABAP processor to terminate the current
program. Then it waits for a maximum of 60 seconds. If the program is
still active, the work process is restarted.

successfully processed, the system gives it another 600 seconds.
Hence the maximum runtime of a program is at least twice the value of
the system profile parameter "rdisp/max_wprun_time".



------------------------
How to correct the error
------------------------

You should usually execute long-running programs as batch jobs.
If this is not possible, increase the system profile parameter
"rdisp/max_wprun_time".

Depending on the cause of the error, you may have to take one of the
following measures:
- Endless loop: Correct program;
- Dataset resulting from database access is too large:
Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
(for example);
- Database has an unsuitable index: Check index generation.

You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:

------------------------------------------------------------------------
"TIME_OUT" C
"SAPLSTD4 " or "LSTD4U11 "
"DB02_ORA_SELECT_SEGMENTS"
------------------------------------------------------------------------
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.............. "620"

Application server....... "shekar"
Network address.......... "169.254.25.129"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "2x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 1
Short dump setting....... "full"

Database server.......... "SHEKAR"
Database type............ "ORACLE"
Database name............ "CHA"
Database owner........... "SAPCHA"

Character set............ "English_United State"

SAP kernel............... "620"
Created on............... "Mar 5 2003 21:32:05"
Created in............... "NT 5.0 2195 Service Pack 2 x86 MS VC++ 12.00"
Database version......... "OCI_817_SHARE "

Patch level.............. "674"
Patch text............... " "

Supported environment....
Database................. "ORACLE 8.1.7.*.*"
SAP database version..... "620"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"

--------------------
User, transaction...
--------------------

Client.............. 000
User................ "SAP*"
Language key........ "E"
Transaction......... "DB02 "
Program............. "SAPLSTD4 "
Screen.............. "SAPMSSY0 1000"
Screen line......... 6

-----------------------------------------
Information on where termination occurred
-----------------------------------------

The termination occurred in the ABAP program "SAPLSTD4 " in
"DB02_ORA_SELECT_SEGMENTS".
The main program was "RSORAUD1 ".

The termination occurred in line 35 of the source code of the (Include)
program "LSTD4U11 "
of the source code of program "LSTD4U11 " (when calling the editor 350).

-------------------
Source code extract
-------------------

000050 *" VALUE(SEG_NAME) LIKE SEGMENTS_F-SN DEFAULT '*'
000060 *" VALUE(TB_SPACE) LIKE SEGMENTS_F-TS DEFAULT '*'
000070 *" VALUE(SEG_TYPE) LIKE SEGMENTS_F-S_TYPE DEFAULT '*'
000080 *" VALUE(KBYTES) LIKE SEGMENTS_F-KBYTES DEFAULT 0
000090 *" VALUE(NR_EXTENTS) LIKE SEGMENTS_F-EXTENTS DEFAULT 0
000100 *" VALUE(WITH_BITMAP) LIKE TST04HELP-FLAG DEFAULT ' '
000110 *" TABLES
000120 *" DBA_SEGMENTS STRUCTURE SEGMENTS_F OPTIONAL
000130 *"----------------------------------------------------------------------
000140
000150
000160 DATA: bytes TYPE p.
000170 DATA: index_type LIKE segments_s-s_type.
000180 DATA: root(30).
000190
000200 DATA: ORA_RELEASE_EXACT LIKE DBRELEASE-DBRELEASE.
000210
000220 CALL FUNCTION 'GET_DB_RELEASE_ORA'
000230 IMPORTING
000240 ORA_RELEASE = ORA_RELEASE_EXACT.
000250
000260 bytes = kbytes * 1024.
000270 CLEAR segments. REFRESH segments.
000280
000290 PERFORM convert_string USING seg_name.
000300 PERFORM convert_string USING tb_space.
000310 PERFORM convert_string USING seg_type.
000320
000330 IF ORA_RELEASE_EXACT(5) >= 'ORA81'.
000340 EXEC SQL PERFORMING app_segments_f.
-----> SELECT
000360 owner, segment_name, segment_type, tablespace_name,
000370 header_file, header_block, bytes/1024, blocks,
000380 extents, initial_extent/1024, next_extent/1024,
000390 min_extents, max_extents, pct_increase, partition_name, 0
000400 FROM dba_segments INTO :segments
000410 WHERE ( segment_name LIKE :seg_name OR
000420 partition_name LIKE :seg_name ) AND
000430 tablespace_name LIKE :tb_space AND segment_type LIKE :seg_type
000440 AND bytes > :bytes AND extents > :nr_extents
000450 ENDEXEC.
000460 ELSE.
000470 EXEC SQL PERFORMING app_segments_f.
000480 SELECT
000490 owner, segment_name, segment_type, tablespace_name,
000500 header_file, header_block, bytes/1024, blocks,
000510 extents, initial_extent/1024, next_extent/1024,
000520 min_extents, max_extents, pct_increase, segment_name, 0
000530 FROM dba_segments INTO :segments
000540 WHERE segment_name LIKE :seg_name AND

-------------------------
Contents of system fields
-------------------------

SY field contents..................... SY field contents.....................
-------- ----------------------------- -------- -----------------------------
SY-SUBRC 0 SY-INDEX 0
SY-TABIX 18312 SY-DBCNT 18312
SY-FDPOS 17 SY-LSIND 0
SY-PAGNO 0 SY-LINNO 1
SY-COLNO 1 SY-PFKEY
SY-UCOMM SY-TITLE Update entries from MONI table
SY-MSGTY SY-MSGID
SY-MSGNO 000 SY-MSGV1
SY-MSGV2 SY-MSGV3
SY-MSGV4

---------------------
Active calls / events
---------------------

No.... Type........ Name..........................
Program
Include Line
Class
-----------------------------------------------------
1 FUNCTION DB02_ORA_SELECT_SEGMENTS
SAPLSTD4
LSTD4U11 35

2 EVENT START-OF-SELECTION
RSORAUD1
RSORAUD1 166


----------------
Chosen variables
----------------


------------------------------------------------------------------------------------------
1 FUNCTION DB02_ORA_SELECT_SEGMENTS
SAPLSTD4
LSTD4U11 35
------------------------------------------------------------------------------------------
KBYTES ########
00000000
0000000C
NR_EXTENTS ########
00000000
0000000C
SEG_NAME %
2222222222222222222222222222222222222222
5000000000000000000000000000000000000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80
2
0
SEG_TYPE %
22222222222222222
50000000000000000
TB_SPACE %
222222222222222222222222222222
500000000000000000000000000000
WITH_BITMAP
2
0
DBA_SEGMENTS[] Table IT_11[0x324]
000023B500000000000040000000FFFF00002000
000083616000B000000041000000FFFF40000500
... + 40
2000C000
00001E00
%_DUMMY$$
2222
0000
FREE_SPACE_CACHE-BLOCKS ########
00000000
0000000C
SY-DATUM 20080312
33333333
20080312
DBA_SEGMENTS-INITIAL_EXT 0
0000
0000
BYTES ########
00000000
0000000C
SEGMENTS_CACHE-NEXTEXTENT ########
00000000
0000000C
SEGMENTS SAPCHA STXB
5454442222222222222222222222225554222222
3103810000000000000000000000003482000000
... + 40
2222222222222222222222222222222222222222
0000000000000000000000000000000000000000
... + 80 TABLE
2222222222222222222222222222222544442222
0000000000000000000000000000000412C50000
... + 120 PSAPCHA ##
2222222255454442222222222222222222222200
0000000003103810000000000000000000000000
... + 160 #####L#####2`Å“######pL#######Å’##########
0000040000036900000074000000080000000100
00000C0000120C0000000C0000008C0000001C00
... + 200 #####l####################tÆ’d\########
0000060000000000000001000178650000000022
00001C0000000C0000000C0024434C0000000C00
... + 240
222222222222222
000000000000000
%_SPACE
2
0

------------------------------------------------------------------------------------------
2 EVENT START-OF-SELECTION
RSORAUD1
RSORAUD1 166
------------------------------------------------------------------------------------------
No dump information available

-----------------
Application Calls
-----------------

No dump information available

-----------------------
Application Information
-----------------------

No dump information available

--------------
Internal notes
--------------

The termination occurred in the function "ThTimeout" of the SAP
Basis System, specifically in line 1405 of the module
"//bas/620/src/krn/th/thhiserv.c#8".
The internal operation just processed is "DSQL".
The internal session was started at 20080312144224.

--------------------------
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=3176)
When : 3/12/2008 14:53:8.843
Threads : 2
Computer Name : SHEKAR
User Name : SAPServiceCHA
Number of Processors: 2
Processor Type: x86 Family 15 Model 6 Stepping 5
Windows Version : 5.2 Current Build: 3790
State Dump for Thread Id c6c
eax=003a5d30 ebx=003a5814 ecx=003a5d44 edx=00000000 esi=003a5814 edi=003a57e8
eip=7c82ed54 esp=02c679bc ebp=02c679cc iopl=0 nv up ei pl nz na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00000202
function : KiFastSystemCallRet
7c82ed54 c3 ret
7c82ed55 8da42400000000 lea esp,[esp] ss:02c679bc=00000001
7c82ed5c 8d642400 lea esp,[esp] ss:058ce8e3=00000000
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
02c679cc 00000000 017ee41c 017ee414 00000001 017ba388 ntdll!KiFastSystemCallRet
State Dump for Thread Id de8
eax=00000001 ebx=00000103 ecx=0441fe9c edx=7c82ed54 esi=00000000 edi=00000000
eip=7c82ed54 esp=0441fe74 ebp=0441feb8 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:0441fe74=7c821514
7c82ed5c 8d642400 lea esp,[esp] ss:07086d9b=00000000
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0441feb8 00db9b31 000006ec 00000000 00000000 0319f430 ntdll!KiFastSystemCallRet
0441ff84 77bcb530 00000000 00000000 00000000 0319f300 disp+work!SigIMsgFunc >
> [signt.c (556)]
0441ffb8 77e66063 0319f300 00000000 00000000 0319f300 MSVCRT!endthreadex
0441ffec 00000000 77bcb4bc 0319f300 00000000 00000000 kernel32!GetModuleFileNameA

------------------------------
List of ABAP programs affected
------------------------------

------------------------------------------------------------------------------------------
| Type| Program | Gen. Date Time | Load Size |
------------------------------------------------------------------------------------------
| Prg | RSORAUD1 | 08.01.2003 14:14:35 | 39936 |
| Prg | SAPMSSY0 | 13.12.2002 12:30:03 | 60416 |
| Prg | SAPMSSYD | 05.06.2002 17:09:33 | 16384 |
| Prg | SAPFSYSCALLS | 14.02.2002 14:22:47 | 6144 |
| Prg | RSDBRUNT | 08.01.2003 14:14:34 | 218112 |
| Typ | RSSCR | . . : m:15 | 4096 |
| Prg | RSDBSPBL | 13.12.2002 12:24:35 | 57344 |
| Prg | SAPDB__S | 14.02.2002 14:22:47 | 15360 |
| Prg | RSDBSPMC | 05.06.2002 17:09:26 | 65536 |
| Typ | DDSHDESCR | 03.09.1997 03:05:16 | 3072 |
| Typ | SPPARAMS | 07.05.1997 13:10:38 | 1024 |
| Prg | SAPLSABE | 14.02.2002 14:22:47 | 11264 |
| Prg | SAPLSECU | 24.01.2003 13:53:54 | 62464 |
| Prg | SAPLSCNT | 14.02.2002 14:22:47 | 22528 |
| Prg | SAPLSVSM | 13.12.2002 12:16:46 | 22528 |
| Prg | SAPLSGUI | 13.12.2002 12:27:47 | 29696 |
| Prg | SAPLSTTM | 13.12.2002 12:13:58 | 70656 |
| Prg | SAPLSBDC | 13.12.2002 12:13:58 | 37888 |
| Prg | CL_DATAPROVIDER===============CP | 14.02.2002 14:22:46 | 38912 |
| Prg | %_CCNTL | 14.02.2002 14:22:46 | 13312 |
| Typ | OBJ_RECORD | 14.02.1998 08:30:43 | 2048 |
| Prg | SAPLSTUP | 24.01.2003 13:50:43 | 62464 |
| Prg | SAPLCNDP | 13.12.2002 12:13:58 | 144384 |
| Prg | SAPFGUICNTL | 13.12.2002 12:30:03 | 20480 |
| Prg | SAPLOLEA | 13.12.2002 12:13:58 | 76800 |
| Prg | SAPLSFES | 24.01.2003 13:52:29 | 129024 |
| Prg | SAPLSPLUGIN | 14.02.2002 14:22:48 | 6144 |
| Prg | SAPLGRFC | 14.02.2002 14:22:47 | 13312 |
| Prg | SAPSHDTV | 05.06.2002 17:04:36 | 27648 |
| Prg | SAPLSTD4 | 07.02.2003 12:54:55 | 117760 |
| Prg | SAPLSORA | 13.12.2002 12:14:17 | 58368 |
| Prg | SAPLSDBI_DBINFO | 14.02.2002 14:22:48 | 12288 |
| Typ | SEGMENTS_F | 08.01.2003 14:13:00 | 3072 |
| Typ | FREE_SP_S | 13.05.1997 12:50:28 | 2048 |
| Typ | SYST | 04.12.2000 14:54:51 | 24576 |
| Typ | SEGMENTS_F | 08.01.2003 14:13:00 | 3072 |
------------------------------------------------------------------------------------------

-----------------------
List of internal tables
-----------------------

Header of \FUNCTION-POOL=STD4\DATA=SEGMENTS[]
TABH+ 0(20) = B89CB75100000000090000000C00000088470000
TABH+ 20(20) = 4401000000000000FFFFFFFF041D0000300F0000
TABH+ 40( = 10000000C12E2000
store = 0xB89CB751
ext1 = 0x00000000
id = 9 (0x09000000)
label = 12 (0x0C000000)
fill = 18312 (0x88470000)
leng = 324 (0x44010000)
lopc = 0 (0x00000000)
loop = -1 (0xFFFFFFFF)
xtyp = TYPE#000060
occu = 16 (0x10000000)
access = 1 (ItAccessStandard)
idxKind = 0 (ItIndexNone)
uniKind = 2 (ItUniqueNon)
keyKind = 1 (default)
cmpMode = 7 (cmpManyEq)
occu0 = 1
collHash = 0
lock = 0
shrd = 0
visited = 0
unShareable = 0
wasShared = 0
iterIsValid = 0
isShareable = 1
>>>>> Shareable Table Header Data <<<<<tabi>>>>> 1st level extension part <<<<<regHook>>>>> 2nd level extension part <<<<<tabhBack>>>>> DSQL 16 122
5267 BRAN 05 Branch to 5271
5268 perf 00 70
5269 PERP 80
5270 BRAX 00 Branch to 5266
5271 DSQL 23
LSTD4U11 46 ELSE.
5272 BRAX 00 Branch to 5291
LSTD4U11 48 SELECT
5273 DSQL 00 263

-----------------------
End of runtime analysis
-----------------------










my system has only 512 mb ram? is that a problem? why i am not able to execute db02 transaction on ma system?
raghucharan v
 
Posts: 17

Postby naveedahmed »

Hi,

Raghu...

Try to exceed the parameter "rdisp/max_wprun_time" value .....



Regards....

naveed ahmed.
naveedahmed
 
Posts: 56

Postby Rajnikanth »

Hi Raghu,


Try executing the report rsorAT0D in background and in NetWeaver RSORATDB and get the result in spool list. I am sure your problem will be solved.






Regards
Rajnikanth
Rajnikanth
 
Posts: 46

Re: problem while hitting transaction db02 for monitering db?

Postby rukku »

hi raghucharan u problem resolved r not.please let me know.both are given right answer.
rukku
 
Posts: 39


Return to SAP DBA Forum

Who is online

Users browsing this forum: No registered users and 1 guest

Visit our Google Group Way 2 SAP BASIS
cron