cancel
Showing results for 
Search instead for 
Did you mean: 

TSV_TNEW_PAGE_ALLOC_FAILED - SAPOSCOL not running (shared memory not available )

Former Member
0 Kudos

Dear All;

When the user runs the program SAPLSEUT with the transaction PC00_M99_CALC_SIMU he gets the following dump:

TSV_TNEW_PAGE_ALLOC_FAILED

I checked the sap notes 0207534, 1079153, and  1613430. These notes say that the solution to this dump is to increase the memory parameters:

em/initial_size_MB = 16000

ztta/roll_area = 10000000

ztta/roll_extension =   300000000

abap/heap_area_total =  4000000000

So I added the above parameters, and restarted SAP Service, but I kept getting the same dump.

After that I went to ST06 and I faced the error SAPOSCOL not running (shared memory not available ). Could this be related to my memory issue?

I will appreciat your help to solve this dump. Shall I increase the parameters values in RZ10?

Best Regards

~Amal


Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Amal

i like that you always want to change sap parameters

but i suppose that if you want to run a simulation for 1ml of employees with a retro of 10years probably even the best setting can not help you if you know what i mean

If i would be you i would rollback the parameter changes (because that didnt fix the issue), start the saposcol that btw it's not affected by previous changes, and last but not least give us more info regarding the payroll simulation that you or your customer want to run

Let us know

a

Former Member
0 Kudos

Dear Andrea;

So you are saying that saposcol has nothing to do with the  TSV_TNEW_PAGE_ALLOC_FAILED dump.

For the payroll that the functional consultant is trying to run, she informed that last month was working fine with no issues. She gave me only the following information which i already know from st22:

t-code: PC00_M99_CALC_SIMU "

program name: SAPLSEUT

She got this dump While testing one company payroll June 2013 payroll (52) under simulation, and that she got the following message.

I am not sure what is the next step for me to fix this issue.

Best Regards

~Amal

Former Member
0 Kudos

Amal

that message is not giving good feeling

The recommendation from  ipcs -s |grep sid and ipcs -m |grep sid

Start your sap and ask to your py support to run a simulation with only one employee of that company.

In a dreaming world you should be able to split that run with different cycle e.g. with empnum 1 and 1000 then 1001 and 2000 and so on.

Let me know how it goes

a

P.S.saposcol is a collector of system information and ive never seen it creating prolems..

Former Member
0 Kudos

Hi,

is the report running in Dialog or Background?

You have to increase abap/heap_area_dia, abap/heap_area_nondia or ztta/roll_extension!

    Roll area...................... 9723952

    Extended memory (EM)........... 402225408

    Assigned memory (HEAP)......... 2000063584

BR,

Andreas

Former Member
0 Kudos

Dear All;

Thank you so much for your help. I was able to fix the issue by setting the following parameters with the following values:

1- abap/heap_area_nondia = 2000000000

2- abap/heap_area_total = 2000000000

3- ztta/roll_extension = 2000000000

4- ztta/roll_area  = 10000000

Then after I stopped the sap service, I started a clean

Best Regards

~Amal

Answers (2)

Answers (2)

Reagan
Advisor
Advisor
0 Kudos

Hello

What OS is this ? Unix, Windows ?

If this is a Unix system, did you run cleanipc when you were restarting the SAP system ?

If this is a Windows system then you need a restart of the server to cleanup the shared memory segments.

Regarding the problem with the Tx getting dumped out due to lack of memory please analyse the dump in Tx ST22 to see where the problem is.

Regards

RB

Former Member
0 Kudos

Dear Reagan;

My SAP system is running on Linux with

kernel release 700 Source id  0.201 with 4GB of RAM

I run a cleanup but yet saposcol is not working

This is the dump i am getting in st22

Runtime Errors TSV_TNEW_PAGE_ALLOC_FAILED

Date and Time 29.06.2013 07:38:59

What happened?

     You attempted to extend an internal table, but the required space was

     not available.

What can you do?

     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.

     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.

How to correct the error

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

    Roll area...................... 9723952

    Extended memory (EM)........... 402225408

    Assigned memory (HEAP)......... 2000063584

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

    Paging area.................... 212992

    Maximum address space.......... 18446696768452951231

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

"SAPLSEUT" or "LSEUTU16"

"_INSERT_TEXTBUFFER"

Reagan
Advisor
Advisor
0 Kudos

Good Day Amal

The problem you have is with the Extended Memory.

The system is not set with the SAP recommended settings.

You have set the value of ztta/roll_extension to 300000000

This is not even 1 GB

SAP recommends to set the value to 2 GB where in you set it to less than 300 MB

Please read this SAP Note and set the parameter accordingly

Note 146289 - Parameter Recommendations for 64-Bit SAP Kernel

Additionally consider checking the parameter abap/heap_area_dia as well.

Back to the saposcol not running.

Please provide the output of the following command

ipcs -ma

Good Luck

RB

Former Member
0 Kudos

Dear Reagan;

I checked the documentation for the parameter ztta/roll_extension, and it says that the default value of it should be 2GB on windows OS, and 250MB on others. In my case since I am using Linux then I must set it around 250 MB so 300MB is not bad I guess.

Shall I increase it to more than the default value? knowing that I have only 4GB of RAM.

I do not have abap/heap_area_dia in my profile yet, so I will add it now with the default value 2GB.

It is just I am worried that the values of these parameters need more RAM.

Best Regards

~Amal

Former Member
0 Kudos

The output of  ipcs -ma is :

------ Shared Memory Segments --------

key        shmid      owner      perms      bytes      nattch     status

0x000027ac 338919433  uhpadm    740        534608     4

0x00000000 323256330  uhpadm    777        1024       1

0x00002732 323289099  uhpadm    740        4194304    1

0x00000000 323321868  uhpadm    777        1024       1

0x00000000 491533     uhpadm    777        556742     1          dest

0x000027ad 323354638  uhpadm    740        1160812    37

0x0000277e 326762511  uhpadm    740        134000000  38

0x0382be84 57671696   uhpadm    666        4096       2

0x00002775 326795281  uhpadm    740        576        39

0x00002776 326828050  uhpadm    740        6743112    39

0x0382be85 57770003   uhpadm    666        4096       39

0x00002777 326860820  uhpadm    740        13059200   39

0x000027a8 326893589  uhpadm    740        72968      39

0x00002793 326926358  uhpadm    740        5771512    39

0x000027a7 326959127  uhpadm    740        18243332   36

0x000027b2 327024664  uhpadm    740        86132792   37

0x00002782 330432537  uhpadm    740        4400000    35

0x0000277d 330465306  uhpadm    740        268435456  35

0x0000277c 330498075  uhpadm    740        268435456  35

0x00002786 330530844  uhpadm    740        2622496    35

0x0000279c 330563613  uhpadm    740        146000000  35

0x0000277b 330596382  uhpadm    740        12176      35

0x00002778 330661919  uhpadm    740        598216     35

0x00002789 330694688  uhpadm    740        954592     1

0x0000279d 334102561  uhpadm    740        40297576   35

0x00002787 334135330  uhpadm    740        59999856   35

0x00002795 334168099  uhpadm    740        18431832   35

0x000027aa 334200868  uhpadm    740        10331160   35

0x000027b5 334233637  uhpadm    740        8704024    35

0x000027b4 334266406  uhpadm    740        5243112    35

0x000027b3 335216679  uhpadm    740        29712      1

0x0000277a 335446056  uhpadm    740        1280000000 35

0x00002792 335478825  uhpadm    740        72758      35

0x000027ae 335511594  uhpadm    740        2076       35

0x00004dbe 339607595  root      777        530242     0

------ Semaphore Arrays --------

key        semid      owner      perms      nsems

0x00004e3a 120717313  uhpadm    740        1

0x00004eb2 124026882  uhpadm    740        1

0x00004e88 124059651  uhpadm    740        1

0x00004e89 124092420  uhpadm    740        1

0x00004ecb 124125189  uhpadm    740        1

0x00004e8d 124157958  uhpadm    740        1

0x00004ea6 124190727  uhpadm    740        1

0x00004e9b 124223496  uhpadm    740        1

0x00004e86 124256265  uhpadm    740        1

0x00004e87 124289034  uhpadm    740        1

0x002e14df 124321803  uhpadm    740        1

0x002e14de 124354572  uhpadm    740        1

0x002e14dd 124387341  uhpadm    740        1

0x002e14dc 124420110  uhpadm    740        1

0x002e14db 124452879  uhpadm    740        1

0x002e14da 124485648  uhpadm    740        1

0x002e14d9 124518417  uhpadm    740        1

0x002e14d8 124551186  uhpadm    740        1

0x002e14d7 124583955  uhpadm    740        1

0x002e14d6 124616724  uhpadm    740        1

0x002e14d5 124649493  uhpadm    740        1

0x002e14d4 124682262  uhpadm    740        1

0x002e14d3 124715031  uhpadm    740        1

0x002e14d2 124747800  uhpadm    740        1

0x002e14d1 124780569  uhpadm    740        1

0x002e14d0 124813338  uhpadm    740        1

0x002e14cf 124846107  uhpadm    740        1

0x002e14ce 124878876  uhpadm    740        1

0x002e14cd 124911645  uhpadm    740        1

0x002e14cc 124944414  uhpadm    740        1

0x002e14cb 124977183  uhpadm    740        1

0x002e14ca 125009952  uhpadm    740        1

0x002e14c9 125042721  uhpadm    740        1

0x002e14c8 125075490  uhpadm    740        1

0x002e14c7 125108259  uhpadm    740        1

0x002e14c6 125141028  uhpadm    740        1

0x002e14c5 125173797  uhpadm    740        1

0x002e14c4 125206566  uhpadm    740        1

0x002e14c3 125239335  uhpadm    740        1

0x002e14c2 125272104  uhpadm    740        1

0x002e14c1 125304873  uhpadm    740        1

0x002e14c0 125337642  uhpadm    740        1

0x002e14bf 125370411  uhpadm    740        1

0x002e14be 125403180  uhpadm    740        1

0x002e14bd 125435949  uhpadm    740        1

0x00004ea4 125468718  uhpadm    740        1

0x00004ea5 125501487  uhpadm    740        1

0x00004eab 125534256  uhpadm    740        1

0x00004eb8 125567025  uhpadm    740        1

0x00004e85 125599794  uhpadm    740        1

0x00004e8a 125632563  uhpadm    740        1

0x00004e8b 125665332  uhpadm    740        1

0x00004e8f 125698101  uhpadm    740        1

0x00004e90 125730870  uhpadm    740        1

0x00004e91 125763639  uhpadm    740        1

0x00004e92 125796408  uhpadm    740        1

0x00004e94 125829177  uhpadm    740        1

0x00004e95 125861946  uhpadm    740        1

0x00004e96 125894715  uhpadm    740        1

0x00004e97 125927484  uhpadm    740        1

0x00004e98 125960253  uhpadm    740        1

0x00004e99 125993022  uhpadm    740        1

0x00004e9a 126025791  uhpadm    740        1

0x00004e9c 126058560  uhpadm    740        1

0x00004e9d 126091329  uhpadm    740        1

0x00004e9e 126124098  uhpadm    740        1

0x00004e9f 126156867  uhpadm    740        1

0x00004ea0 126189636  uhpadm    740        1

0x00004ea1 126222405  uhpadm    740        1

0x00004ea2 126255174  uhpadm    740        1

0x00004ea3 126287943  uhpadm    740        1

0x00004ea7 126320712  uhpadm    740        1

0x00004eaa 126353481  uhpadm    740        1

0x00004eae 126386250  uhpadm    740        1

0x00004eaf 126419019  uhpadm    740        1

0x00004eb0 126451788  uhpadm    740        1

0x00004eb3 126484557  uhpadm    740        1

0x00004eb5 126517326  uhpadm    740        1

0x00004eb4 126550095  uhpadm    740        1

0x00004eb7 126582864  uhpadm    740        1

0x00004eb9 126615633  uhpadm    740        1

0x00004eba 126648402  uhpadm    740        1

0x00004ebb 126681171  uhpadm    740        1

0x00004ebc 126713940  uhpadm    740        1

0x00004ebd 126746709  uhpadm    740        1

0x00004ebe 126779478  uhpadm    740        1

0x00004ec9 126812247  uhpadm    740        1

0x00004e8e 126845016  uhpadm    740        1

0x002deeeb 126877785  uhpadm    740        60

0x00004ebf 126910554  uhpadm    740        1

0x00004eb6 126943323  uhpadm    740        1

0x00004e93 126976092  uhpadm    740        1

0x00004eb1 127008861  uhpadm    740        1

0x00004ec6 127041630  uhpadm    740        1

0x00004e8c 127074399  uhpadm    740        1

0x00004ec3 127107168  uhpadm    740        1

0x00004ec2 127139937  uhpadm    740        1

0x00004ecc 127172706  uhpadm    740        1

------ Message Queues --------

key        msqid      owner      perms      used-bytes   messages

Reagan
Advisor
Advisor
0 Kudos

Hello Amal

I am not sure where exactly it says that the default value of 2 GB is for Windows.

Please review the parameters for the system and set them accordingly.

For sure you will need to increase it.

Note 386605 - SAP Memory Management for Linux (32-bit)

Note 941735 - SAP memory management for 64-bit Linux systems

I suggest you to set the value of ztta/roll_extension to 2 GB and restart the system.

As the user to execute the Tx and see whether it gets dumped out.

Regards

RB

Reagan
Advisor
Advisor
0 Kudos

For saposcol issue please follow any of these SAP Notes

Note 548699 - FAQ: OS collector SAPOSCOL

1627564  - SAPOSCOL:  Clearing Shared Memory and Updating Saposcol

Just remove the shared memory segment as mentioned in the note and restart saposcol from ST06

Regards

RB

Former Member
0 Kudos

Hi Amal,

please check how much memory the report is allocating.

You can check this via STAD or SM50.

Is the report running in background or dialog?  Please check the parameters abap/heap_area_dia and abap/heap_area_nondia.

Best Regards,

Andreas

Former Member
0 Kudos

Dear Andreas;

The report is running as a dialog. The only parameters I have now on the system related to memory are:

abap/heap_area_total = 4000000000

ztta/roll_extension = 300000000

ztta/roll_area = 10000000

em/initial_size_MB = 16000

Do you recommend me to set the parameters:

abap/heap_area_dia

abap/heap_area_nondia.

If yes then how much I should set them? A note to mention that I have only 4GB of RAM.

How can I know how much memory used via sm50?

Best Regards

~Amal

Former Member
0 Kudos

Hi,

please increase ztta/roll_extension to 2GB.

The parameters abap/heap_area_dia and abap/heap_area_nondia are set by default to 2GB, this is normally sufficient.  Your problem is the small portion of EM memory, please increase ztta/roll_extension.  

You should think of increasing you OS memory 4 GB is very small.

BR,

Andreas

Former Member
0 Kudos

Dear Andres;

So you think if I increase ztta/roll_extension to 2GB with the small amount of RAM (4GB) it would solve the issue? would it be save to do this?

Best Regards

~Amal Aloun