Termination occurred in the ABAP program "SAPLTREX_EXT_TM"

[Former Member]

Hello

Users are starting to get this error in some BEx queries, while investigating it i was wondering if you have any clue on this

Cheers

Tansu

Error analysis

The internal table "" could n

further extended. To enable

error handling, the table had to be delete before this log was written

As a result, the table is displayed further down or, if you branch to

the ABAP Debugger, with 0 rows.

At the time of the termination, the following data was determined for

the relevant internal table:

Memory location: "Session memory"

Row width: 1256

Number of rows: 1680080

Allocated rows: 1680080

Newly requested rows: 8 (in 1 blocks)

How to correct the error

The amount of storage space (in bytes) filled at termination time was:

Roll area...................... 2718352

Extended memory (EM)........... 2002743520

Assigned memory (HEAP)......... 2000066208

Short area..................... " "

Paging area.................... 0

Maximum address space.......... " "

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:

"TSV_TNEW_PAGE_ALLOC_FAILED" " "

"SAPLTREX_EXT_TM" or "LTREX_EXT_TMU13"

"TREX_EXT_AGGREGATE"

Information on where terminated

Termination occurred in the ABAP program "SAPLTREX_EXT_TM" - in

"TREX_EXT_AGGREGATE".

The main program was "SAPMSSY1 ".

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

of the (Include) program "LTREX_EXT_TMU13".

Source Code Extract

Line SourceCde

231 text_to_utf8 ls_alias_op-origin_index_id lx_alias_op-origin_index_id.

232 text_to_utf8 ls_alias_op-alias_index_id lx_alias_op-alias_index_id.

233 lx_alias_op-operator = ls_alias_op-operator.

234 APPEND lx_alias_op TO lt_alias_op.

235 ENDLOOP.

236

237 LOOP AT i_comp_descr INTO ls_descr.

238 CLEAR lx_descr.

239 lx_descr-decimals = ls_descr-decimals.

240 lx_descr-field_length = ls_descr-field_length.

241 lx_descr-byte_length = ls_descr-byte_length.

242 lx_descr-byte_offset = ls_descr-byte_offset.

243 text_to_utf8 ls_descr-field_name lx_descr-field_name.

244 text_to_utf8 ls_descr-field_type lx_descr-field_type.

245 text_to_utf8 ls_descr-attr_name lx_descr-attr_name.

246 APPEND lx_descr TO lt_comp_descr.

247 ENDLOOP.

248

249 l_top_type = i_top_type.

250 l_top_max_equals = i_top_max_equals.

251 text_to_utf8 i_top_value l_top_value.

252 text_to_utf8 i_query_id l_query_id.

253

254 l_switch_on_trace = i_switch_on_trace.

255 text_to_utf8 i_trace_components l_trace_components.

256 l_use_dfi = i_use_dfi.

257

258 GET RUN TIME FIELD time3.

259

260 lt_comp_descr_for_next_aggr = lt_comp_descr.

>>>>> CALL FUNCTION 'TREX_RFC_AGGREGATE_SP5'

262 DESTINATION i_rfc_destination

263 EXPORTING

264 index_id = l_index_id

265 result_from = l_result_from

266 result_to = l_result_to

267 requested_search_results = l_requested_results

268 staging = i_staging

269 query_id = l_query_id

270 switch_on_trace = l_switch_on_trace

271 trace_components = l_trace_components

272 top_type = l_top_type

273 top_value = l_top_value

274 top_max_equals = l_top_max_equals

275 use_dfi = l_use_dfi

276 IMPORTING

277 return_code = l_return_code

278 return_text = l_return_text

[former_member93896 · Accepted solution]

Hello Tansu,

this looks to me like a case of reading too much data. Check the recommendations mentioned in

Regards,

Marc

SAP Customer Solution Adoption (CSA)

[Former Member · Accepted solution]

Thanks Marc,

I think the same, couldn't find any OSS note or message about. Looking at the stats it's reading about 80M records, it's nothing for BWA

Tansu