on 11-23-2009 9:22 AM
Hello,
<br>
<br>
<br>
Please Help to solve this redundant error appearing on SM21 :
<br>
<br>
<br>
<blockquote><p align=left><font size=+2> <b> </b> </font></p><p align=left> <font style="font-family:Courier"><font face="courier" size="1"><font face="courier" size="1"><span style= background:#5dcbfd id=l0001002>Details Page 3 Line 18 System Log: Local Analysis of SERVER01 1 </span></font></font><br><strike>--
</strike><br><font face="courier" size="1"><font face="courier" size="1"><span style= background:#5dcbfd id=l0036002>Technical details </span></font></font><br><font face="courier" size="1"><font face="courier" size="1"><span style= background:#eef9ff id=l0037002>File................ 005791</span></font></font><br><font face="courier" size="1"><font face="courier" size="1"><span style= background:#eef9ff id=l0038002>Position............ 0000224820</span></font></font><br><font face="courier" size="1"><font face="courier" size="1"><span style= background:#eef9ff id=l0039002>Entry type.......... n ( Transaction Termination )</span></font></font><br><font face="courier" size="1"><font face="courier" size="1"><span style= background:#eef9ff id=l0040002>Message ID.......... D0 1</span></font></font><br><font face="courier" size="1"><font face="courier" size="1"><span style= background:#eef9ff id=l0041002>Variable parts...... V1 519 </span></font></font><br> </p></blockquote>
<br>
<br>
<br>
Thank you
<br>
<br>
You should be able to find more information on the error in your ABAP dumps - Check ST22
--
Nelis
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Runtime Errors TIME_OUT
Occurred on 23.11.2009 at 13:43:31
-
Time limit exceeded.
-
What happened?
-
The program "ZVM15" 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
"ZVM15" or "ZVM15"
"READ_ENTREGAS"
-
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.
Hi,
The online transaction has exeeded it's permitted time rdisp/max_wprun_time
What is your limit ?
In Rz11 check the amount of seconds you have given for an online transaction to run before timing out.
Sorry just read the dump properly 600 seconds is he default you will need to make the decsion
on how much to increase it depending how your system is set-up
To increase this dynamically in RZ11 Then place it in the Instance profile, it will only come into affect when you restart the system.
Mark
<b>By RZ11 i get this informations on that parameter : </b>
Param. Name
rdisp/max_wprun_time
Short description(Engl) max workprocess run time
Appl. area General system
ParameterTyp Time value
Changes allowed Change permitted
Valid for oper. system All operating systems
Minimum 300
Maximum 0
DynamicallySwitchable
Same on all servers
Dflt value 600
ProfileVal 600
Current value 600
Increasing the timeout of rdisp/max_wprun_time without analyzing the problem would be a foolish thing to do, especially if the long running program is a non SAP standard program as is in your case.
If this program(ZVM15) has been badly coded or is not making good use of indexes it could end up effecting the performance of your system overall. I would run a trace on this specific program and see what tables it accesses and then analise the SQL statements to see if they a) cannot be optimized and b) are making good use of available indexes. Only once you have verified all of the above and there is no other way to solve the problem then should you increase the work processes runtime. The default timeout of 10 minutes should be fine for running programs but it may be that your hardware is not performing optimally too which is another thing to check.
--
Nelis
Hi,
can you trace this back in Transaction SM13 ?
Mark
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I wanted to post the results of the SM13 in HTML mode but i got the error <b>Your message exceeds the maximum length of 15000 characters. </b> :
<br>
<br>
The results in SM13 :
<br>
0 Update records found
Cln User Date Time TCode I n f o Status
List contains no data
<br>
<br>
User: AOTCX100 Client: 222 Transaction:VL01N
Date: 06.10.2009Time: 10:49:58Report: SAPMV50A
Update key: 4ACA2611E453018EE10080000A20BF30Status: Error
Number Module name (function) Type Status
1 REFER_TEXT_AFTER_COMMIT V1 Initial
2 RV_DELIVERIES_SAVE V1 (no retry) Error
3 RV_MESSAGE_UPDATE V1 Initial
4 MCV_STATISTICS_UPD_V1_DELIVER V1 Initial
5 MCV_STATISTICS_UPD_V2_DELIVER V2 Initial
6 SD_CRM_ORDERDATA_FROM_DLV_INV V1 Initial
<br>
<br>
User: GASJX001 Client: 222 Transaction:ME22N
Date: 07.10.2009Time: 17:16:42Report: SAPLMEPO
Update key: 4ACCEC9F787C0148E10080000A20BF30Status: Error
Number Module name (function) Type Status
1 ME_UPDATE_DOCUMENT V1 Initial
2 EINKBELEG_WRITE_DOCUMENT V1 Initial
3 MCE_STATISTICS_UPD_V1 V1 Initial
4 MCE_STATISTICS_UPD_V2 V2 Initial
5 ME_CREATE_MRPRECORD_PO V1 Initial
6 ME_UPDATE_QUOTA_DIALOG V1 Initial
7 RV_MESSAGE_UPDATE V1 Error
<br>
<br>
User | Count |
---|---|
80 | |
9 | |
9 | |
7 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.