Hi Guys,
On BI Production system I am getting ST22 : ABAP Run time error (TIME_OUT)
The Parameter value of rdisp/max_wprun_time = 3600 (1hr) which is maximum value. Even then we are getting around 20 to 30 Dumps. Can any suggest a Note, so that tell my application team to run their programs in Background.
Thanks in Advance for Reply.
| Kernel release | 720 |
| Runtime Errors | TIME_OUT |
| Date and Time | 15.04.2013 14:19:05 |
Short text
| Time limit exceeded. |
What happened?
| The program "CL_SQL_STATEMENT==============CP" has exceeded the maximum | |
| permitted runtime without | |
| interruption and has therefore been terminated. |
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
| After a specific time, the program is terminated to make the work area | |
| available to other users who may be waiting. | |
| This is to prevent a work area being blocked unnecessarily long by, for | |
| example: | |
| - Endless loops (DO, WHILE, ...), | |
| - Database accesses with a large result set | |
| - Database accesses without a suitable index (full table scan) | |
| The maximum runtime of a program is limited by the system profile | |
| parameter "rdisp/max_wprun_time". The current setting is 3600 seconds. If this | |
| time limit is | |
| exceeded, the system attempts to cancel any running SQL statement or | |
| signals the ABAP processor to stop the running program. Then the system | |
| waits another 60 seconds maximum. If the program is then still active, | |
| the work process is restarted. |
How to correct the error
| Programs with long runtime should generally be started as background | |
| jobs. If this is not possible, you can 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 unsuitable index: Check index generation. | |
| 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: | |
| "TIME_OUT" " " | |
| "CL_SQL_STATEMENT==============CP" or "CL_SQL_STATEMENT==============CM004" | |
| "EXECUTE_QUERY" |