Skip to Content
0
Former Member
Dec 13, 2007 at 03:24 AM

Display Infocube Content produces Runtime Errors = TIME_OUT

239 Views

Hi,

Upon trying to display content of an InfoCube (200 records only), I received the following error:

Runtime Errors TIME_OUT

Date and Time 13.12.2007 11:16:24

Short text

Time limit exceeded.

What happened?

The program "CL_SQL_RESULT_SET=============CP" has exceeded the maximum

permitted runtime without

interruption and has therefore been terminated.

Error analysis

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

example:

- 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.

Trigger Location of Runtime Error

Program CL_SQL_RESULT_SET=============CP

Include CL_SQL_RESULT_SET=============CM006

Row 32

Module type (METHOD)

Module Name NEXT_PACKAGE

Source Code Extract

Line SourceCde

2 *

3 * Fetches the next bulk of rows into an internal table.

4 *

5

6 DATA:

7 sql_code TYPE i,

8 sql_msg TYPE dbsqlmsg.

9

10 FIELD-SYMBOLS:

11 <line> TYPE ANY,

12 <outtab> TYPE STANDARD TABLE.

13

14

15 IF me->cursor = c_invalid_cursor.

16 * result set has already been closed

17 RAISE EXCEPTION TYPE cx_sql_exception

18 EXPORTING invalid_cursor = 'X'.

19 ENDIF.

20

21 * check that a reference to the output table has been set by

22 * a preceeding call of SET_PARAM_TABLE; in this case the attribute

23 * LINE_REF contains a reference to a data structure of the

24 * table's line type

25 IF me->itab_ref IS INITIAL.

26 RAISE EXCEPTION TYPE cx_parameter_invalid

27 EXPORTING parameter = 'ITAB_REF'.

28 ENDIF.

29 ASSIGN me->itab_line_ref->* TO <line>.

30 ASSIGN me->itab_ref->* TO <outtab>.

31

>>>>> CALL 'C_DB_FUNCTION' ID 'FUNCTION' FIELD 'DB_SQL'

33 ID 'FCODE' FIELD c_fcode_next_package

34 ID 'CONNAME' FIELD me->con_ref->con_name

35 ID 'CONDA' FIELD me->con_ref->con_da

36 ID 'CURSOR' FIELD me->cursor

37 ID 'BOUND' FIELD me->outvals_bound

38 ID 'OUTVALS' FIELD me->parameters->param_tab

39 ID 'OUTTAB' FIELD <outtab>

40 ID 'LINE' FIELD <line>

41 ID 'UPTO' FIELD upto

42 ID 'ROWCNT' FIELD rows_ret

43 ID 'SQLCODE' FIELD sql_code

44 ID 'SQLMSG' FIELD sql_msg.

45

46 IF sy-subrc = 0.

47 * some rows fetched

48 ADD rows_ret TO rows_fetched.

49

50 * set the OUTVALS_BOUND flag; this avoids "reassignement" of the

51 * output variables the next time this method is called, i.e. the

Can someone help me to solve this problem. Thanks!