Program terminated: Time limit exceeded, ABAP performance, max_wprun_time

Question

Hi,
I am running an ABAP program, and I get the following short dump:
Time limit exceeded. The program has exceeded the maximum permitted runtime and has therefore been terminated. After a certain time, the program terminates to free the work processfor 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 10000 seconds. After this, the system gives the program a second chance. During the first half (>= 10000 seconds), a call that is blocking the work process (such as a long-running SQLstatement) 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 10000 seconds. Hence the maximum runtime of a program is at least twice the value of the system profile parameter "rdisp/max_wprun_time".
Last error logged in SAP kernel
Component............ "NI (network interface)"
Place................ "SAP-Dispatcher ok1a11cs_P06_00 on host ok1a11e0"
Version.............. 34
Error code........... "-6"
Error text........... "connection to partner broken"
Description.......... "NiPRead"
System call.......... "recv"
Module............... "niuxi.c"
Line................. 1186
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".
Program cannot be started as a background job. We have now identified two options to solve the problem:
- Increase the value of the system profile parameter "rdisp/max_wprun_time"
- Improve the performance of the following SELECT statement in the program:
SELECT ps_psp_pnr ebeln ebelp zekkn sakto FROM ekkn
INTO CORRESPONDING FIELDS OF TABLE i_ekkn
FOR ALL ENTRIES IN p_lt_proj
WHERE ps_psp_pnr = p_lt_proj-pspnr
AND ps_psp_pnr > 0.
In EKKN we have 200 000 entries.
Is there any other options we could try?
Regards,
Jarmo

Answer 1

Thanks for your help, this problem seems to be quite challenging...
In EKKN we have 200 000 entries. 199 999 entries have value of 00000000 in column ps_psp_pnr, and only one has a value which identifies a WBS element.
I believe the problem is that there isn't any WBS element in PRPS which has the value of 00000000. I guess that is the reason why EKKN is read sequantially.
I also tried this one, but it doesn't help at all. Before the SELECT statement is executed, there are 594 entries in internal table p_lt_proj_sel:
  DATA p_lt_proj_sel LIKE p_lt_proj OCCURS 0 WITH HEADER LINE.
  p_lt_proj_sel[] = p_lt_proj[].
  DELETE p_lt_proj_sel WHERE pspnr = 0.
  SORT p_lt_proj_sel by pspnr.
  SELECT ps_psp_pnr ebeln ebelp zekkn sakto FROM ekkn
  INTO CORRESPONDING FIELDS OF TABLE i_ekkn
  FOR ALL ENTRIES IN p_lt_proj_sel
  WHERE ps_psp_pnr = p_lt_proj_sel-pspnr.
I also checked that the index P in EKKN is active.
Can I somehow force the optimizer to use the index?
Regards,
Jarmo