TSV_TNEW_BLOCKS_NO_ROLL_MEMORY

[Former Member]

Dear Friend,

We are getting these dumps in ECC.

Following is the detailed error.

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 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.

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...................... 16128

Extended memory (EM)........... 351956336

Assigned memory (HEAP)......... 0

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

Paging area.................... 65536

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

Can you pl let us know which parameter needs to be changed.

Regards

Jiggi,

[Former Member]

Jiggi,

You can check the following regarding this:

Are these dumps arising from a single or a few custom-built Z* ABAP programs or are these coming for many SAP Standard programs as well?

Becuase if this dump is coming for only one or 2 Z* programs and not for others, the you will have to check with an ABAPer to modify this program to avoid many nested loops or huge data input which generally consumes lot of memory and resultes in this dump.

Extending parameters is also a solution but if this issue is with Z programs then better to modify the programs rather than increasing parameter values.

On the other hand, if this dump is coming for many programs which include standard SAP programs,

then proceed to increase the memory parameters.

You can raise a OSS note with SAP and they will provide very good sugesstions as to which parameters need to be changed.

Hope this resolves your issue.

Cheers,

Hari Kishan.

[anindya_bose]

you can try to increase the size of temporary tablespace and see whether you are getting the same error.

[former_member204746]

what is your OS?

if Windows, check SAP note 88416.

[Former Member]

Hello

This is memory problem, you need to really go through some SAP Notes for memory parameter recommendations and perfomance issues or specifically for ABAP accomodations

thanks

Bhudev