Dump TSV_LIN_ALLOC_FAILED , when run job : SAP_COLLECTOR_FOR_JOBSTATISTIC

[Former Member]

hi all the experts,

When the job SAP_COLLECTOR_FOR_JOBSTATISTIC ,

I searched in service.sap.com notes and have not achieved anything specific.

This is canceled and when I check the st22 said that there is not enough space in memory. annex the dump TSV_LIN_ALLOC_FAILED.

thanks and regards.

Gustavo Gonzalez

####################################################################################

ShrtText

No roll memory available to extend the index of an internal table.

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.

Make a note of the actions and input which caused the error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

Error analysis

The linear index of an internal table was supposed to be extended.

However, the 2293776 bytes of memory requested for it were not available

in the roll area.

Storage location: "Session memory"

-

---

Last error logged in SAP kernel

-

---

Component............ "EM"

Place................ "SAP-Server sapsrv01_D01_01 on host sapsrv01 (wp 2)"

Version.............. 37

Error code........... 7

Error text........... "Warning: EM-Memory exhausted: Workprocess gets PRIV "

Description.......... " "

System call.......... " "

Module............... "emxx.c"

Line................. 1886

How to correct the error

Decide by analysis whether this request is reasonable or whether there

is a program error. Pay particular attention to the internal table

entries listed below.

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

Roll area...................... 1708928

Extended memory (EM)........... 114982560

Assigned memory (HEAP)......... 276176080

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

Paging area.................... 24576

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

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

-

---

"TSV_LIN_ALLOC_FAILED" C

"RSBPCOLL" or "RSBPCOLL"

"START-OF-SELECTION"

-

---

System environment

SAP Release.............. "640"

Application server....... "sapsrv01"

Network address.......... "10.0.0.15"

Operating system......... "Windows NT"

Release.................. "5.2"

Hardware type............ "4x Intel 801586"

Character length......... 8 Bits

Pointer length........... 32 Bits

Work process number...... 2

Short dump setting....... "full"

Database server.......... "SAPSRV01"

Database type............ "MSSQL"

Database name............ "D01"

Database owner........... "d01"

Character set............ "English_United State"

SAP kernel............... "640"

Created on............... "Oct 3 2007 00:34:24"

Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"

Database version......... "SQL_Server_8.00 "

Patch level.............. "203"

Patch text............... " "

Supported environment....

Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"

SAP database version..... "640"

Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,

Windows NT 6.0"

Memory usage.............

Roll..................... 1708928

EM....................... 114982560

Heap..................... 276176080

Page..................... 24576

MM Used.................. 379558912

MM Free.................. 10752584

SAP Release.............. "640"

[former_member189546]

Hello,

Make sure you have /3Gb and /pae switches set in boot.ini file on c drive

if you have 32 bit Windows

Also set these parameters in the instance profile and restart SAP

rdisp/ROLL_SHM = 6000

rdisp/PG_SHM = 6000

regards,

John Feely

[Former Member]

Hi ,

You can increase the roll area and see if this problem persists.

The parameter is ztta/roll_area .

Also , you can increase the Heap memory too (abap/heap_area_total).

But before increasing the meory , find out if there is any possibility to correct the program , by reducing the size ofthe internal table.

Regards,

Ponni.

from Eric Brunelle: begging for points is totally against forum rules. read them

[Former Member]

Hi,

You need to have to increase the roll memory.

Mahesh

[Former Member]

Hi Mahesh,

thanks for your response, but what is the parameter??

thanks

Gustavo