Solved: Migration to oracle 11.2.0.4 and Kernal 720_EXT_RE...

Former Member · ‎01-28-2014

Hi,

We have migrated to oracle 11.2.0.4 and Kernal 720_EXT_REL. After migration we are unable to run few Tcodes and they are getting timed out(IQ09 Tcode for instance gets timed out). We have already implemented SAP note 1431798. Is there any other note which would help us resolve the timeout error?

Regards,

Anand.

Former Member · ‎01-28-2014

Hi,

Below is the data from ST22

Runtime Errors TIME_OUT
Date and Time 28.01.2014 14:45:21

Short text
Time limit exceeded.

What happened?
The program "SAPLSDH3" has exceeded the maximum permitted runtime without
interruption 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 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 1800 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.

How to correct the error
    Programs with long runtime should generally be started as background
    jobs. If this is not possible, you can increase the system profile
    parameter "rdisp/max_wprun_time".

    Depending on the cause of the error, you may have to take one of the
    following measures:
    - Endless loop: Correct program;
    - Dataset resulting from database access is too large:
      Instead of "SELECT * ... ENDSELECT", use "SELECT * INTO internal table
      (for example);
    - Database has unsuitable index: Check index generation.

    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:

    "TIME_OUT" " "
    "SAPLSDH3" or "LSDH3U03"
    "F4_GET_RESULT"

If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File
(Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which
actions and input led to the error.

System environment
SAP-Release 701

    Application server... "XXXXXX"
    Network address...... "10.11.112.37"
    Operating system..... "AIX"
    Release.............. "6.1"
    Hardware type........ "00C48D174C00"

Character length.... 8 Bits
Pointer length....... 64 Bits
Work process number.. 2
Shortdump setting.... "full"

Database server... "XXXXX"
Database type..... "ORACLE"
Database name..... "MD1"
Database user ID.. "SAPSR3"

Terminal.......... "CSCGBLAF620086"

Char.set.... "en_US.ISO8859-1"

SAP kernel....... 720
created (date)... "Sep 14 2013 04:47:06"
create on........ "AIX 1 6 00F8709C4C00"
Database version. "OCI_112, 11.2.0.3.0, V1, default"

Patch level. 500
Patch text.. " "

Database............. "ORACLE 10.1.0.*.*, ORACLE 10.2.0.*.*, ORACLE 11.2.*.*
SAP database version. 720
Operating system..... "AIX 1 6, AIX 1 7"

Memory consumption
Roll.... 0
EM...... 8379712
Heap.... 0
Page.... 385024
MM Used. 2838848
MM Free. 1348400

User and Transaction

    Client.............. 400
    User................ "DM123"
    Language key........ "E"
    Transaction......... "IQ09 "
    Transactions ID..... "52E7FCECB85F0FA0E10080000A0B7025"

    Program............. "SAPLSDH3"
    Screen.............. "SAPMSSY0 1000"
    Screen line......... 6

Information on where terminated
Termination occurred in the ABAP program "SAPLSDH3" - in "F4_GET_RESULT".
The main program was "RIEQUI21 ".

In the source code you have the termination point in line 149
of the (Include) program "LSDH3U03".

Source Code Extract

Line SourceCde

119                    %_HINTS ORACLE '&SUBSTITUTE LITERALS&'.
120         ENDIF.
121       ELSE.
122         IF sort = space.
123           OPEN CURSOR cursor-c FOR

124 SELECT * UP TO max_select ROWS FROM (sel_method)

125 WHERE (where_clause)

126 %_HINTS ORACLE '&SUBSTITUTE LITERALS&'.

127 ELSE.

128 OPEN CURSOR cursor-c FOR

129 SELECT * UP TO max_select ROWS FROM (sel_method)

130 WHERE (where_clause)

131 ORDER BY PRIMARY KEY

132 %_HINTS ORACLE '&SUBSTITUTE LITERALS&'.

133 ENDIF.

134 ENDIF.

135

136 ENDIF.

137 IF max_select = 0.

138 max_select = 500.

139 ENDIF.

140 FETCH NEXT CURSOR cursor-c INTO TABLE <itab>

141 PACKAGE SIZE max_select.

142 if cursor-with_cursor ne 'P'.

143 CLOSE CURSOR cursor-c.

144 endif.

145 ELSE.

146 * Jetzt kann mit dieser Where-Bedingung selektiert werden.

147 IF sort = space.

148 * Dynamische Suche

>>>>> SELECT * UP TO max_select ROWS FROM (sel_method)

150 INTO TABLE <itab>

151 WHERE (where_clause)

152 %_HINTS ORACLE '&SUBSTITUTE LITERALS&'.

153 ELSE.

154 SELECT * UP TO max_select ROWS FROM (sel_method)

155 INTO TABLE <itab>

156 WHERE (where_clause)

157 ORDER BY PRIMARY KEY

158 %_HINTS ORACLE '&SUBSTITUTE LITERALS&'.

159 ENDIF.

160 IF result_tab IS REQUESTED.

161 CLEAR result_tab[].

162 ASSIGN result_tab TO <x2> CASTING.

163 CREATE DATA wa TYPE (sel_method).

164 ASSIGN wa->* TO <wa>.

165 ASSIGN <wa> TO <x1> CASTING.

166 LOOP AT <itab> INTO <wa>.

167 <x2> = <x1>.

168 APPEND result_tab.

Contents of system fields

Name Val.

SY-SUBRC 0

SY-INDEX 0

SY-TABIX 1

SY-DBCNT 1

SY-FDPOS 45

SY-LSIND 0

SY-PAGNO 0

SY-LINNO 1

SY-COLNO 1

SY-PFKEY

SY-UCOMM

SY-TITLE Display Serial Numbers

SY-MSGTY

SY-MSGID

SY-MSGNO 000

SY-MSGV1

SY-MSGV2

SY-MSGV3

SY-MSGV4

SY-MODNO 0

SY-DATUM 20140128

SY-UZEIT 141421

SY-XPROG SAPCNVE

SY-XFORM CONVERSION_EXIT

Active Calls/Events

No. Ty. Program Include Line

Name

5 FUNCTION SAPLSDH3 LSDH3U03 149

F4_GET_RESULT

4 FUNCTION SAPLSDH3 LSDH3U04 92

F4_SELECT_FROM_SEARCH_HELP

3 FORM SAPDBEQI SAPDBEQI 324

FILL_ADRNR

2 FORM RIEQUI21 MIEQUI20 944

SELECTION_L

1 EVENT RIEQUI21 MIEQUI20 415

START-OF-SELECTION

Chosen variables

Name

Val.

ABAP Control Blocks (CONT)

Index Name Fl PAR0 PAR1 PAR2 PAR3 PAR4 PAR5 PAR6 Source Code Line

507 BRAF 02 0010 LSDH3U03 147

508 lreg 03 0002 0000 0020 LSDH3U03 149

510 SQLS 0A 0000 LSDH3U03 149

511 SQLS 09 8000 LSDH3U03 149

512 SQLS 24 0012 LSDH3U03 149

513 PAR1 00 0011 LSDH3U03 149

514 PAR1 00 0103 LSDH3U03 149

515 WHER 1E 0000 C000 0000 LSDH3U03 149

517 SQLS 38 0001 LSDH3U03 149

518 PAR1 08 0039 LSDH3U03 149

519 SQLS 82 0002 LSDH3U03 149

520 SQLS 3B 0000 LSDH3U03 149

>>>>> SQLS 0C 800C LSDH3U03 149

522 BRAX 00 0010 LSDH3U03 153

523 lreg 03 0002 0000 0020 LSDH3U03 154

525 SQLS 0A 0000 LSDH3U03 154

526 SQLS 09 8000 LSDH3U03 154

527 SQLS 24 0012 LSDH3U03 154

528 PAR1 00 0011 LSDH3U03 154

529 PAR1 00 0103 LSDH3U03 154

Regards,

Anand.

Reagan · ‎01-28-2014

Hello

If there was a change in the release of the kernel then you need to run SGEN.

If that is not the case then you need to provide more information to the issue you are facing.

Regards

RB

Former Member · ‎01-28-2014

in the short dump (ST22) you need to findout which program / transaction is getting time out. Then you need to search for the notes for the affected program. If the time out in report then may be the selection criteria is too much.

Whats the value you have set for parameter rdisp/max_wprun_time

Migration to oracle 11.2.0.4 and Kernal 720_EXT_REL.

Accepted Solutions (1)

Accepted Solutions (1)

Answers (2)

Answers (2)

Re: Consuming on-Premise Service in CAP Project

Re: Abap code to get data from table EKKO

Re: CF Deployment Error: Error getting tenant t0

Lumira document dependency

Where did XVBPA get populated in program MV45AFZZ