cancel
Showing results for 
Search instead for 
Did you mean: 

TIME_OUT in VK13 / VK33 on IDES system

Former Member
0 Kudos

We are receiving the following timeout when running VK13 and VK33 on our IDES system. This is standard code, and there is no notes regarding this TIME_OUT.

The Termination occurred in the ABAP program "SAPLV12A" - i

"ACCESS_REPORT_GENERATE".

The main program was "SAPMV13A ".

The whole ST22 dump is as follows:

Runtime Errors TIME_OUT

Date and Time 18.08.2010 19:35:25

Short text

Time limit exceeded.

What happened?

Error analysis

If you have access to SAP Notes, carry out a search with the following

keywords:

"TIME_OUT" " "

"SAPLV12A" or "LV12AU07"

"ACCESS_REPORT_GENERATE"

System environment

SAP-Release 700

Application server... "sap6ides"

Network address...... "10.3.3.125"

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "2x AMD64 Level"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 3

Shortdump setting.... "full"

Database server... "sapC10ides"

Database type..... "ADABAS D"

Database name..... "C10"

Database user ID.. "SAPC10"

Char.set.... "C"

SAP kernel....... 700

created (date)... "May 22 2007 00:12:17"

create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"

Database version. "SQLDBC 7.6.0.035 CL 139084 "

Patch level. 111

Patch text.. " "

Database............. "MaxDB 7.6, MaxDB 7.7"

SAP database version. 700

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2, Windows

NT 6.0"

Memory consumption

Roll.... 16192

EM...... 16759360

Heap.... 0

Page.... 2342912

MM Used. 4880016

MM Free. 3496816

User and Transaction

Client.............. 800

User................ "MEASLE"

Language key........ "E"

Transaction......... "VK13 "

Program............. "SAPLV12A"

Screen.............. "SAPMV13A 0100"

Screen line......... 24

Information on where terminated

Termination occurred in the ABAP program "SAPLV12A" - in

"ACCESS_REPORT_GENERATE".

The main program was "SAPMV13A ".

In the source code you have the termination point in line 177

of the (Include) program "LV12AU07".

Source Code Extract

Line SourceCde

147 dff_desc_ref_field = dd08v_tab-reffldname

148 EXCEPTIONS

149 OTHERS = 1.

150 IF sy-subrc NE 0.

151 CLEAR: dd08v_tab-txttabname,

152 dd08v_tab-reffldname,

153 dd08v_tab-txtfldname.

154 ENDIF.

155 * und aufnehmen

156 READ TABLE dd08v_tab WITH KEY tabname = dd08v_tab-tabname

157 fieldname = dd08v_tab-fieldname

158 TRANSPORTING NO FIELDS.

159 IF sy-subrc EQ 0.

160 MODIFY dd08v_tab INDEX sy-tabix

161 TRANSPORTING txttabname reffldname txtfldname

162 arbgb msgnr.

163 ELSE.

164 APPEND dd08v_tab.

165 ENDIF.

166 LOOP AT dd05m_tab WHERE

167 tabname = t681-kotab AND fieldname = xt681e_tab-sefeld.

168

169 READ TABLE dd03v_tab INDEX dd05m_tab-primpos.

170 IF sy-subrc = 0 AND dd03v_tab-datatype NE 'CLNT'.

171 MOVE-CORRESPONDING dd05m_tab TO dd05v_sel.

172 dd05v_sel-forfldname = dd03v_tab-fieldname.

173 IF dd08v_tab-reffldname IS INITIAL.

174 dd05v_sel-reffldname = dd03v_tab-fieldname.

175 ELSE.

176 TABLES dd05p.

>>>>> SELECT * FROM dd05p

178 WHERE tabname = dd08v_tab-txttabname

179 AND fieldname = dd08v_tab-reffldname

180 AND checktable = dd08v_tab-checktable

181 AND checkfield = dd03v_tab-fieldname.

182 dd05v_sel-reffldname = dd05p-forkey.

183 EXIT.

184 ENDSELECT.

185 IF sy-subrc = 4.

186 dd05v_sel-reffldname = dd08v_tab-reffldname.

187 ENDIF.

188 ENDIF.

189 APPEND dd05v_sel.

190 ENDIF.

191 ENDLOOP.

192 ENDIF.

193 IF NOT dd08v_tab-txttabname IS INITIAL AND

194 NOT dd08v_tab-txtfldname IS INITIAL.

195 * Fremdtabelle lesen (Text)

196 CALL FUNCTION 'RV_TABLE_READ'

2

0

0

0

Accepted Solutions (0)

Answers (3)

Answers (3)

markus_doehr2
Active Contributor
0 Kudos

> Database version. "SQLDBC 7.6.0.035 CL 139084 "

You seem to use a VERY OLD MaxDB database software.

I suggest:

- Update your MaxDB to a recent release, the version you use is very old.

- Update your database statistics to make sure the access paths for the data is optimal

- check the database parameters against Note 814704 - MaxDB Version 7.6 parameter settings for OLTP/BW

If you still use the default settings that came with the installation then it's rather obvious why your system is so slow.

Markus

JPReyes
Active Contributor
0 Kudos

This means that the process was running in Dialog and reached the maximun allowed dialog runtime defined in parameter rdisp/max_wprun_time.

Increase the value of the parameter or run it in background

Regards

Juan

Former Member
0 Kudos

Yes we have run SGEN and we have already increased the timeout param to 1200 from the default of 600.

ANy other ideas? Seems ridiculous that I would have to wait 20 minutes to access VK13.

Former Member
0 Kudos

..