TIME_OUT ABAP Dumps

[Former Member]

Hi Guys,

We are getting ABAP Dumps in our systems very frequently. We are currently using 4.6C (DB2, AIX). We are gettting the dumps in many programs, is this because of some error in application. We currently have kernel patch level 2307.

We have already increased the value of "rdisp/max_wprun_time" from 900 to 2500.

I was suggested by SAP to add a new parameter "rdisp/hold_keeps_time_slice"

which we dont have in our systems. Can anybody pls suggest in this case.

I am attaching the dump:

ABAP runtime errors TIME_OUT

Occurred on 10/17/2007 at 20:57:15

-

---

Time limit exceeded.

-

---

What happened?

-

---

The program "SAPLBDMON " has exceeded the maximum permitted runtime

and has therefore been terminated.

-

---

What can you do?

-

---

Note the actions and input that caused the error.

Inform your SAP system administrator.

You can print out this message by choosing "Print". Transaction ST22

allows you to display and manage termination messages, including keeping

them beyond their normal deletion date.

-

---

Error analysis

-

---

After a certain time, the program terminates to free the work process

for other users who are waiting.

This is to stop work processes being blocked for too long by

- Endless loops (DO, WHILE, ...),

- Database acceses with large result sets,

- Database accesses without an apporpriate index (full table scan)

- database accesses producing an excessively large result set,

The maximum runtime of a program is set by the profile parameter

"rdisp/max_wprun_time".

The current setting is 2500 seconds. After this, the system gives the

program a second chance. During the first half (>= 2500 seconds), a

call that is blocking the work process (such as a long-running SQL

statement) can occur. While the statement is being processed, the

database layer will not allow it to be interrupted. However, to

stop the program terminating immediately after the statement has been

successfully processed, the system gives it another 2500 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

-

---

Long-running programs should be started as background jobs. If

this is not possible, you can increase the value of the system

profile parameter "rdisp/max_wprun_time".

One or more of the following may also be useful:

following measures:

- Endless loops: Correct in program;

- Database access with large result set:

Use "SELECT * INTO itab" instead of "SELECT ... ENDSELECT";

- Database access without suitable index: Check the index generation.

If the error occurred in a non-modified SAP program, you may be

able to find a solution in the SAP note system.

If you have access to the note system yourself, use the following

search criteria:

-

---

"TIME_OUT"

"SAPLBDMON " or "LBDMONU15 "

"ALE_CCMS_EVALUATE_GRP"

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.

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.

Thank you.

Irshad Mohammed

[Former Member]

Hi Guys,

We are getting ABAP Dumps in our systems very frequently. We are currently using 4.6C (DB2, AIX). We are gettting the dumps in many programs, is this because of some error in application. We currently have kernel patch level 2307.

We have already increased the value of "rdisp/max_wprun_time" from 900 to 2500.

I was suggested by SAP to add a new parameter "rdisp/hold_keeps_time_slice"

which we dont have in our systems. Can anybody pls suggest in this case.

I am attaching the dump:

ABAP runtime errors TIME_OUT

Occurred on 10/17/2007 at 20:57:15

-

---

Time limit exceeded.

-

---

What happened?

-

---

The program "SAPLBDMON " has exceeded the maximum permitted runtime

and has therefore been terminated.

-

---

What can you do?

-

---

Note the actions and input that caused the error.

Inform your SAP system administrator.

You can print out this message by choosing "Print". Transaction ST22

allows you to display and manage termination messages, including keeping

them beyond their normal deletion date.

-

---

Error analysis

-

---

After a certain time, the program terminates to free the work process

for other users who are waiting.

This is to stop work processes being blocked for too long by

- Endless loops (DO, WHILE, ...),

- Database acceses with large result sets,

- Database accesses without an apporpriate index (full table scan)

- database accesses producing an excessively large result set,

The maximum runtime of a program is set by the profile parameter

"rdisp/max_wprun_time".

The current setting is 2500 seconds. After this, the system gives the

program a second chance. During the first half (>= 2500 seconds), a

call that is blocking the work process (such as a long-running SQL

statement) can occur. While the statement is being processed, the

database layer will not allow it to be interrupted. However, to

stop the program terminating immediately after the statement has been

successfully processed, the system gives it another 2500 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

-

---

Long-running programs should be started as background jobs. If

this is not possible, you can increase the value of the system

profile parameter "rdisp/max_wprun_time".

One or more of the following may also be useful:

following measures:

- Endless loops: Correct in program;

- Database access with large result set:

Use "SELECT * INTO itab" instead of "SELECT ... ENDSELECT";

- Database access without suitable index: Check the index generation.

If the error occurred in a non-modified SAP program, you may be

able to find a solution in the SAP note system.

If you have access to the note system yourself, use the following

search criteria:

-

---

"TIME_OUT"

"SAPLBDMON " or "LBDMONU15 "

"ALE_CCMS_EVALUATE_GRP"

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.

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.

Thank you.

Irshad Mohammed

[Former Member]

Hi,

BASIS consultants usually set the MAXIMUM RUNTIME FOR A FOREGROUND PROGRAM to a certain value.

If your execution time excees the limit set by BASIS then you will get this dump.

Ask your BASIS consultant to increase the time by 1 or 2 minutes, if this is happening for all programs. If only for few programs, then you need to performance tune the programs.

Best regards,

Prashant

[Former Member]

Hi,

This error will occur when the time set to execute the report exceeds the time limit, then this error will come.

Try to improve the performance of the report.

Thanks,

Sriram Ponna.

[Former Member]

hi irshad,

can u post here where its get the error?

at run time error u can found it.

it's maybe help us to help u.

Regards

Allan Cristian

[Former Member]

I am getting this error in both custom programs and standard SAP programs.

[Former Member]

I think it's a bad idea to increase the run time parameter. It will just allow long running jobs to run even longer and tie up dialogue processes. The correct approach is to find the souce of the problem and fix it. This sounds like a basis issue.

Rob

[Former Member]

I am a Basis person. Do u have any suggestion as what to check ?

[Former Member]

Have you set the parameter suggested by SAP?

Rob

[Former Member]

Hi,

The program will be terminated, if it takes longer time, than which is set by the BASIS team. It is not advisable to increase the time slot; but you can try performance tuning in the program; so that the program will take lesser time. If the program is coded perfectly, and if it is taking time because of the huge data, try scheduling it in background.

[Former Member]

hi

use function module progress_indicator. it resets the run time value.

use this where ever extraction of data is more were program needs much time, just call this function module it works.

check this code,

• This program uploads material number from excel sheet and does

******modifications to material number if required by the user

******and updates the table zmatnr with new material against the old material number

*************************************************************************

REPORT zmat_no message-id zebg.

TYPE-POOLS truxs.

TABLES:zmatnr.

DATA : itab LIKE alsmex_tabline OCCURS 0 WITH HEADER LINE.

DATA row LIKE alsmex_tabline-row.

data : g_matnr like mara-matnr.

data : count type i.

data : itab_count type i.

data : gi_final like zmatnr occurs 0 with header line.

*data : begin of gi_final occurs 0,

• mat_old like mara-matnr,

• mat_new like mara-matnr,

• end of gi_final.

***********************Selection Screen*************************

SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.

PARAMETER : pfname LIKE rlgrap-filename OBLIGATORY.

select-options : records for count.

SELECTION-SCREEN END OF BLOCK b1.

*******************************************************************

*********************At Selection Screen*************************

AT SELECTION-SCREEN ON VALUE-REQUEST FOR pfname.

PERFORM search.

*******************************************************************

START-OF-SELECTION.

perform process.

form process.

CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'

EXPORTING

filename = pfname

i_begin_col = 1

i_begin_row = 2

i_end_col = 12

i_end_row = 65000

TABLES

intern = itab

EXCEPTIONS

inconsistent_parameters = 1

upload_ole = 2

OTHERS = 3.

IF sy-subrc <> 0.

• MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

• WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.

ENDIF.

describe table itab lines itab_count.

row = 1.

loop at itab.

if itab-row <> row.

append gi_final.

clear gi_final.

endif.

case itab-col.

when '1'.

CLEAR G_MATNR.

gi_final-OLD_MATNR = itab-value.

CONCATENATE 'NEW' gi_final-old_matnr INTO itab-value.

gi_final-new_MATNR = itab-value.

endcase.

row = itab-row.

endloop.

append gi_final.

clear gi_final.

• CALL FUNCTION 'PROGRESS_INDICATOR'

• EXPORTING

• I_TEXT = 'File Has Been Successfully Uploaded from Workstation ' .

if not gi_final[] is initial.

if not records-low is initial .

if not records-high is initial.

records-high = records-high + 1.

DESCRIBE TABLE gi_final LINES count.

IF records-high < count.

DELETE gi_final FROM records-high TO count.

ENDIF.

IF records-low <> 1.

IF records-low <> 0.

DELETE gi_final FROM 1 TO records-low.

ENDIF.

ENDIF.

endif.

endif.

endif.

IF NOT GI_FINAL[] IS INITIAL.

CALL FUNCTION 'PROGRESS_INDICATOR'

EXPORTING

I_TEXT = 'Processing zmatnr table'

I_OUTPUT_IMMEDIATELY = 'X'.

• if itab_count <> count.

*

• message i000 with 'records are not matching'.

*

• exit.

*

• else.

modify zmatnr from table gi_final.

message i000 with 'data base table modified successfully'.

• endif.

endif.

endform.

&----

---

*& Form search

&----

---

• text

----

---

• --> p1 text

• <-- p2 text

----

---

FORM search .

CALL FUNCTION 'KD_GET_FILENAME_ON_F4'

EXPORTING

static = 'X'

CHANGING

file_name = pfname.

ENDFORM. " search

regards

siva