Getting Run-time error "TIME_OUT" occurred
In my Solution manager Development system every day when I check ABAP Runtime errors using ST22 transaction code I am getting a runtime error of TIME_OUT.I has also searched the SAP notes but I am not getting a proper solution to my issue of TIME_OUT.Please suggest solutions to overcome of my above mentioned issue.Below is the log for runtime error"TIME_OUT" :
Time limit exceeded.
The program "/BDL/SAPLBDL4" 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
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.
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
- 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 600 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.
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
Depending on the cause of the error, you may have to take one of the
- Endless loop: Correct program;
- Dataset resulting from database access is too large:
Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
- 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
"TIME_OUT" " "
"/BDL/SAPLBDL4" or "/BDL/LBDL4U01"
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
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
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
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
Application server... "sapsm4dev"
Network address...... "10.102.10.34"
Operating system..... "Windows NT"
Hardware type........ "2x Intel 80686"
Character length.... 8 Bits
Pointer length....... 32 Bits
Work process number.. 0
Shortdump setting.... "full"
Database server... "SAPSM4DEV"
Database type..... "ORACLE"
Database name..... "SMD"
Database user ID.. "SAPSR3"
Char.set.... "English_United State"
SAP kernel....... 700
created (date)... "Oct 23 2007 00:57:10"
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. 133
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
MM Used. 1516976
MM Free. 572168
Thanks and Regards,