Dump : TSV_TNEW_OCCURS_NO_ROLL_MEMORY

[Former Member]

Hi Gurús,

I am submitting a dump this on my production system, attached detailed dump.

Short text

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

What happened?

Each transaction requires some main memory space to process

application data. If the operating system cannot provide any more

space, the transaction is terminated.

What can you do?

Try to find out (e.g. by targetted data selection) whether the

transaction will run with less main memory.

If there is a temporary bottleneck, execute the transaction again.

-

If the error persists, ask your system administrator to check the

following profile parameters:

o ztta/roll_area (1.000.000 - 15.000.000)

Classic roll area per user and internal mode

usual amount of roll area per user and internal mode

o ztta/roll_extension (10.000.000 - 500.000.000)

Amount of memory per user in extended memory (EM)

o abap/heap_area_total (100.000.000 - 1.500.000.000)

Amount of memory (malloc) for all users of an application

server. If several background processes are running on

one server, temporary bottlenecks may occur.

Of course, the amount of memory (in bytes) must also be

available on the machine (main memory or file system swap).

Caution:

The operating system must be set up so that there is also

enough memory for each process. Usually, the maximum address

space is too small.

Ask your hardware manufacturer or your competence center

about this.

In this case, consult your hardware vendor

abap/heap_area_dia: (10.000.000 - 1.000.000.000)

Restriction of memory allocated to the heap with malloc

for each dialog process.

Parameters for background processes:

abap/heap_area_nondia: (10.000.000 - 1.000.000.000)

Restriction of memory allocated to the heap with malloc

for each background process.

Other memory-relevant parameters are:

em/initial_size_MB: (35-1200)

Extended memory area from which all users of an

application server can satisfy their memory requirement.

Note which actions and input led to the error.

For further help in handling the problem, contact your SAP administrator

.

You can use the ABAP dump analysis transaction ST22 to view and manage

termination messages, in particular for long term reference.

Error analysis

The internal table "FUNCTION-POOL=SCD0FORM=SENT_TO_CHANGEPOINTERSDATA=LT_BDI

_CDPOS" could not be filled.

Memory location: "Session memory"

You attempted to create an OCCURS area 15328 bytes long for the internal

table "FUNCTION-POOL=SCD0FORM=SENT_TO_CHANGEPOINTERSDATA=LT_BDI_CDPOS". This

is because the first entry is to be stored

in the internal table.

The amount of memory requested is no longer available.

How to correct the error

Try to decide by analysis whether this request is

reasonable or whether there is a program error. You should pay

particular attention to the internal table entries listed below.

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

Roll area...................... 4710368

Extended memory (EM)........... 447386688

Assigned memory (HEAP)......... 163633824

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_OCCURS_NO_ROLL_MEMORY" " "

"SAPLSCD0" or "LSCD0F04"

"SENT_TO_CHANGEPOINTERS"

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.

The detail tells me that I should set parameters, they tell me you.

thanks and regards

[ken_halvorsen2]

Hi Gustavo

1st if it's a new report and this hasn't happened in your system before, I truly suspect the new report. Either it's grabbing too much memory between commits and\or the variant size used needs to be set smaller.

Was there any other (large) programs running at the same time as this one ran?

But if this does happen frequently in your system with other programs as well, I'd check the parameters mentioned in the short dump.

For example:

ztta/roll_area (1.000.000 - 15.000.000)

ztta/roll_extension (10.000.000 - 500.000.000)

abap/heap_area_total (100.000.000 - 1.500.000.000)

abap/heap_area_dia: (10.000.000 - 1.000.000.000)

abap/heap_area_nondia: (10.000.000 - 1.000.000.000)

em/initial_size_MB: (35-1200)

Increase them a little and re-boot your system then test again.

[Former Member]

Hi Gustavo,

details do tell that we should set the parameters but is this dump occuring frequently in the production system

if it occuring frequently then we need to set these parameters but if comes once in a while we can ignore this

Also check for which report is this dump coming,is it a standard report or z report build by your developer

Let me know

Rohit

[Former Member]

Hi Rohi

The report is z ,Developers have reviewed, and I commented that this report is great, my system is based on 32 bits, but you put the / PAE and / 3GB switch to allocate more memory to process and anything, I still bursting this dump . parameters that can adjust?.

note: I also give this another dump, TSV_TNEW_PAGE_ALLOC_FAILED

thanks and regards

Gustavo

[former_member204746]

Have you adapted SAP memory parameter PHYS_MEMSIZE as per SAP note 88416?