Time limit exceeded
What happened?
Program "SAPLM61X" has exceeded the maximum uninterrupted runtime 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 certain time, the program is terminated in order to free the
workspace for other users. This prevents workspaces from being blocked
unnecessarily, for example by an endless loop (DO, WHILE, ...), by
database accesses where the result set is too large or by database
accessess without a suitable index Index (full table scan).
The maximum runtime of a program is set by system profile parameter
"rdisp/scheduler/prio_[high|normal|low]/max_runtime". The current setting is
600 seconds. Once this limit has been
exceeded, the system attempts to interrupt the SQL statement or to
instruct the ABAP processor to terminate the program. It waits for a
maximum of 60 seconds. If the program is then still active, the work
process is restarted.
How to correct the error
It is best to start programs that take a long time to run as batch
jobs. If this is not possible, system profile parameter
"rdisp/scheduler/prio_[high|normal|low]/max_runtime" can be
increased.
Depending on the cause of the error, the following actions might also
be necessary:
- Endless loop: correction in program;
- Database where the result set is too large: Use "SELECT * INTO
internal table" for example instead of "SELECT * ... ENDSELECT";
- Database access without suitable index: Check generation of index.
If the error occurs in a non-modfied SAP program, you might be able to
find a solution in the SAP Notes system. If you have access to the SAP
Notes system, check there first using the following keywords:
"TIME_OUT"
"SAPLM61X" bzw. LM61XF1K
"SELECT_MDBS_BS"
If you cannot solve the problem yourself, please send the following
information to SAP:
1. This description of the problem (short dump)
To do this, choose System -> List -> Save -> Local File (unconverted)
on the screen you are in now.
Program "SAPLM61X" has exceeded the maximum uninterrupted runtime 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 certain time, the program is terminated in order to free the
workspace for other users. This prevents workspaces from being blocked
unnecessarily, for example by an endless loop (DO, WHILE, ...), by
database accesses where the result set is too large or by database
accessess without a suitable index Index (full table scan).
The maximum runtime of a program is set by system profile parameter
"rdisp/scheduler/prio_[high|normal|low]/max_runtime". The current setting is
600 seconds. Once this limit has been
exceeded, the system attempts to interrupt the SQL statement or to
instruct the ABAP processor to terminate the program. It waits for a
maximum of 60 seconds. If the program is then still active, the work
process is restarted.
How to correct the error
It is best to start programs that take a long time to run as batch
jobs. If this is not possible, system profile parameter
"rdisp/scheduler/prio_[high|normal|low]/max_runtime" can be
increased.
Depending on the cause of the error, the following actions might also
be necessary:
- Endless loop: correction in program;
- Database where the result set is too large: Use "SELECT * INTO
internal table" for example instead of "SELECT * ... ENDSELECT";
- Database access without suitable index: Check generation of index.
If the error occurs in a non-modfied SAP program, you might be able to
find a solution in the SAP Notes system. If you have access to the SAP
Notes system, check there first using the following keywords:
"TIME_OUT"
"SAPLM61X" bzw. LM61XF1K
"SELECT_MDBS_BS"
If you cannot solve the problem yourself, please send the following
information to SAP:
1. This description of the problem (short dump)
To do this, choose System -> List -> Save -> Local File (unconverted)
on the screen you are in now.
2. A suitable system log
To do this, call the system log in transaction SM21. Restrict the time
interval to ten minutes before the short dump and five minutes after
it. In the display, choose System -> List -> Save -> Local File
(unconverted).
3. If these are programs of your own, or modified SAP programs: Source
code of these programs
To do this, choose More Utilities -> Upload/Download -> Download in
the Editor.
4. Details regarding the conditions under which the error occurred or
which actions and input caused the error.
Comments
Post a Comment