Dump Error TSV_TNEW_PAGE_ALLOC_FAILED

[Former Member]

Hello All,

We are getting this dump error, "TSV_TNEW_PAGE_ALLOC_FAILED" in our system.

Short text

No more storage space available for extending an internal table.

What happened?

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

not available.

OS AIX 5.3 64 bit

Total Memory : 19 GB

Total Swap Space : 45.91 GB

The present values of the Profile parameters are,

ztta/roll_area - 3000320

ztta/roll_extension - 2000683008

abap/heap_area_total - 2000683008

abap/heap_area_dia - 2000683008

abap/heap_area_nondia - 2000683008

em/initial_size_MB - 4092

Kindly suggest,

Thank You,

Hasan

[former_member189725]

Please use SAP note 789477 for setting the extended memory on AIX.

Please set the parameters mentioned in the section Recommended parameters in the instance profile in the note .

I would suggest setting the parameter EM/TOTAL_SIZE_MB = 20480 and the rest of the parameters as mentioned in the note.

Also check the parameter ztta/roll_extension . Set it to 4096MB.

Once done , remove the parameter em/initial_size_mb from the instance profile.

[Former Member]

Addition to above replies, Take a look at SAP Note 369726 TSV_TNEW_PAGE_ALLOC_FAILED

Regards,

Nick Loy

[Former Member]

Hello Hasan,

As per the dump, your paging file didn't have enough space to process that request. If this dump is generated by one or two users then ask them to tune up the program or shorten the selection criteria to minimize the memory usage.

You have to increase the value of rdisp/PG_MAXFS to resolve the issue. It's strongly not recommended to increase the memory values for sake of few users until unless it's required to run business critical transactions.

Hope it helps,

Thanks,

Siva Kumar

[Former Member]

Hello All,

Thanks for your suggestions.

As it is solman system, when i checked in SM04.

Clnt User TCODE Roll Page Mem(Total) Mem(Priv.)

1 SOLMAN_BTC 0 0 4.541.332 0

1 SOLMAN_BTC 106.496 0 2.351.226 0

1 SOLMAN_BTC 0 0 4.542.228 0

1 SOLMAN_BTC 106.496 0 2.349.850 0

1 USERA 106.496 40.96 2.508.076 0

1 SMD_RFC 106.496 0 806.526 0

1 USERA 106.496 0 8.917.850 0

1 USERA 106.496 40.96 2.657.604 0

1 SMDAGENT_SID 106.496 0 796.868 0

1 SAPJSF 106.496 0 797.174 0

1 USERB SM04 352.256 98.304 11.117.992 0

[Former Member]

Hello Siva Kumar,

What is the value that can be set for the parameter rdisp/PG_MAXF?

At present it is 32768..

Also in the Error Analysis in ST22,

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

Roll area...................... 2718272

Extended memory (EM)........... 2002720576

Assigned memory (HEAP)......... 2000767216

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

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

Maximum address space.......... 4294967295

Thanks,

Regards,

Hasan

[Former Member]

Hello Hasan,

There is no standard value to be maintained for this parameter. 32768 is the default value.

You can give a try by increasing it 1/4th of 32768 or more. Please make sure you have enough physical memory on the box.

Thanks,

Siva Kumar

[Former Member]

Hi,

There could be many causes for the memory issue here.

But it can be categorized in one of the two situations:

1. Your memory profile parameters are not properly set

2. Your memory profile parameters are set fine. Only that some user is using a lot more memory than he/she is supposed to use.

So, to find which of the above holds true, I would suggest to monitor the user memory consumption via tcode SM04 -> Goto -> Memory. If someone is using exceptionally high amount of memory especially in dailog mode, check with the respective user if that memory is really required.

If all looks fine, then check the dump details in ST22. It would shows exactly how much memory was required an was not found. Further check parameters in ST02 for high number of swaps. Typically increasing parameter value for abap/buffersize should solve the issue.

But you need to check if the requirement is really necessary.

Regards,

Srikishan