topic Re: Dump in standard program when running Z program in Application Development and Automation Discussions

Dump in standard program when running Z program

Former Member — Fri, 02 Oct 2009 17:50:24 GMT

Hello Experts,

I'm running Z program in the background, but I'm getting the dump TSV_TNEW_OCCURS_NO_ROLL_MEMORY in standard program SAPLATP3, include LATP3FA1, form ADDING_NEST_TABLE.

I have reviewed old posts but the dump is in different programs.

Dump details:

Runtime Error TSV_TNEW_OCCURS_NO_ROLL_MEMORY

No roll storage space of length 13824 available for OCCURS area.

Source code extract:

000180 FORM ADDING_NEST_TABLE TABLES P_TAB LIKE ATPHX[]

000190 USING OPERATOR TYPE OPERATOR

000200 VALUE(P_TAB_IX) LIKE SY-TABIX

000210 S_TAB_WA TYPE ATP_TIME_AXIS.

000220 * building one entry table

000230 REFRESH P_TAB-ATPTX.

> APPEND S_TAB_WA TO P_TAB-ATPTX.

000250 CASE OPERATOR.

000260 WHEN 'insert'.

000270 INSERT P_TAB INDEX P_TAB_IX.

000280 WHEN 'append'.

000290 APPEND P_TAB.

000300 ENDCASE.

000310 ENDFORM. " ADDING_NEST_TABLE

Do you have any idea what could be causing this issue?

Thank you very much in advance for your help!!

Re: Dump in standard program when running Z program

RichHeilman — Fri, 02 Oct 2009 18:01:28 GMT

You application is using too much session memory. YOu need to clear and free any internal tables that are no longer needed in your program.

Regards,

RichHeilman

Re: Dump in standard program when running Z program

Former Member — Fri, 02 Oct 2009 18:02:28 GMT

put a break point on this.

APPEND S_TAB_WA TO P_TAB-ATPTX.

run it again.. and check what values are there in both.. and what type are those

you can contact BASIS guys to solve this issue about ROLL_AREA

Re: Dump in standard program when running Z program

former_member156446 — Fri, 02 Oct 2009 18:07:29 GMT

ROLL_MEMORY remind me of the issue I had before...

In Dev and Quality and Prod environement the memory allocated to a program or LUW is limited to some size say 1MB. When it cannot handle more than that space this error would occur.

Remember the space would not be same in all the environments, so the one dumped in Dev MIGHT not in Q and PRD

Solution: Clear all the internal tables which you think you would not sure... use FREE itab statements... and clear all the work areas or header table you are using and create table type and use that for creating internal tables, when needed.

Re: Dump in standard program when running Z program

Former Member — Fri, 02 Oct 2009 18:21:53 GMT

Thanks for your quick replies

This is the extract of the variables

Chosen variables

29 FORM ADDING_NEST_TABLE

SAPLATP3

LATP3FA1 24

P_TAB-ATPTX Table IT_1098[0x108]

ESTKZV V

S_TAB_WA 0000000000001LC 0000000000

3333333333333442222222222333333333322222

0000000000001C30000000000000000000000000

... + 40 ##############

2222222000000000000002222222222222222222

0000000000000C000000C0000000000000000000

... + 80 ####################ÿÿÿÿ

222200000000000000000000FFFF

0000000000C000000C000000FFFF

SY-REPID SAPLATP3

Could this be a Basis memory configuration issue?

Re: Dump in standard program when running Z program

former_member156446 — Fri, 02 Oct 2009 18:24:06 GMT


> Could this be a Basis memory configuration issue?

This would be a Basis config issue, if you cannot solve it with ABAP. Do all possible things to free some memory and if it still dumps, then its a Basis issue.

Re: Dump in standard program when running Z program

Former Member — Fri, 02 Oct 2009 22:20:16 GMT

check how much memory is getting occupied. check ST03 and processor loads as well.. ask BASIS guys to do it. they can explain you whats the amount of memory is being used for the application server at that time. and can increase the memory area.

Re: Dump in standard program when running Z program

Clemenss — Fri, 02 Oct 2009 23:33:59 GMT

Hi Emanuel ,

we can see only a part of your program.

I'd like to bet that there is some kind of loop at an internal table and INSIDE the loop you append or Insert rows. This leads usually to a never-ending process of table expansion only stopped by a memory overflow as you have it here.

When the program dumps, you may have the chance to start debugger and see one of your interbal tables has millions of records.

Regards,

Clemens