Skip to Content
0
Former Member
Mar 24, 2009 at 05:27 AM

Error while executing interface

42 Views

Hello Friends

The team is trying to integrate 3 sap standard tables into 1 table.

The have a requirement to interface @ 25 sap standard tables.

with 2 tables joining it works fine.

The 2 interfaces run a ABAP program in the form of background job; in the SAP system which integrates these tables.

While executing the program in the SAP system we get the memory dump as mentioned below;

Runtime Errors TSV_TNEW_BLOCKS_NO_ROLL_MEMORY

Date and Time 24.03.2009 10:27:20

Short text

No roll storage space of length 1994768 available for internal storage.

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=ZODI_18011_18011\DATA=IT_FINAL[]" could not

enlarged further.

Memory location: "Session memory"

You attempted to extend the data structure for the management of the

memory blocks for table "\FUNCTION=ZODI_18011_18011\DATA=IT_FINAL[]". Howe

the 1994768 bytes required for

this were no longer available in the specified memory area.

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

Extended memory (EM)........... 4189840

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

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

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

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

System details;

ECC 6.0 SP level 13 Oracle data base release 10.2.0.2.0.

64 bit 16 GB RAM

I have checked with the sap notes but not sure enough with what tuning can be done for the same.

Basis memory checks are performed.

Thanks and Regards

Pooja