The purpose of this page is to solve the error which may occur when we execute SAP Extractor Program SAPLZCAST_SAP_EXTRACTOR_FGR has exceeded the maximum uninterrupted runtime and has therefore been terminated.
For more information, refer to:
- Official Documentation For 8.4: CAST SAP Extractor NG - Documentation - 8.4.x
- Official Documentation For 8.3: CAST SAP Extractor NG - ABAP source code extraction - 8.3.x - 8.2.x - 8.0.x
- TKB page for Information Guides : Source Extractor - ABAP
Release | Yes/No |
|---|---|
| 8.4x |  |
| 8.3x | |
RDBMS | Yes/No |
|---|---|
| CSS | |
After installing the CAST SAP extractor, when the tool from the SAP environment is launched and the extraction performed, the process ends up during extraction with an error in the SAP error log : Program "SAPLZCAST_SAP_EXTRACTOR_FGR" has exceeded the maximum uninterrupted runtime and has therefore been terminated.
|Testo breve | | Time limit exceeded | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |Causa dell'errore | | Program "SAPLZCAST_SAP_EXTRACTOR_FGR" has exceeded the maximum uninterrrupted | | runtime and has | | therefore been terminated. | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |Possibili soluzioni | | 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. | ---------------------------------------------------------------------------------------------------- ---------------------------------------------------------------------------------------------------- |Analisi errori | | 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 | | 3600 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. |
This happens because there is a huge transaction load on the SAP Server and it takes longer to serve the request. From the logs, it can be seen that the maximum runtime of a program is set by the system profile parameter "rdisp/scheduler/prio_[high|normal|low]/max_runtime". The current setting is 3600 seconds. Once this limit has been exceeded, the system attempts to interrupt the SQL statement or instruct the ABAP processor to terminate the program. It waits for a maximum of 60 seconds. If the program is still active, the work process is restarted.
To solve the issue
- Either increase the max_runtime time more than what it is taking to get results or run the extraction at a time when there is less load on the server in a back ground mode.
- If you do not find the information you are looking for or a solution for your problem, contact CAST Technical Support and provide the relevant input to help the CAST Support team investigate your problem or procure the required information.
# 43562
