TSV_TNEW_PAGE_ALLOC_FAILED - Suggest memory parameter values

[former_member201054]

Hi,

I am getting below runtime errors in SCM 7.0 EHP2 system.

TSV_TNEW_PAGE_ALLOC_FAILED

TSV_TNEW_BLCOKS_NO_ROLL_MEMORY

In RZ11, I can see the below values exist for respective memory parameter.

abap/heap_area_dia  =  2000000000

abap/heap_area_total =  2000000000

abap/heap_area_nondia = 2000000000

ztta/roll_area  = 3000000

abap/heap limit = 40000000

ztta/roll_extension = 2000000000

em/initial_size_MB = 4092

rdisp/PG_SHM = 8192

rdisp/PG_MAXFS

Please check below for system memory details(ST02 & ST06) and suggest required new values to resolve the runtime errors ..kindly let me know how you did the calculation and what should be considered.

ST02:

Extended memory ( IN) - 4186112 KB

heap memory  ( IN)  -   0 kb

Roll area -       131072 KB

Page area - 65536   KB

ST06 :

physical memory - 52428800 KB

Configures swap space - 20971520 KB

Free swap size - 20877468 KB

Maximum swap size - 20971520 KB

Actual swap size - 20971520 KB

I will appreciate your help and and explanation for the new value suggestion .. I am stuck up due to these two runtime errors

Thanks a ton

[Former Member · Accepted solution]

Dear Daniel,

You are truly in a very difficult state!! There is no specific formula to maintain a particular value for each memory parameter. It is just a matter of trial and error that works in deciphering on the memory parameter values.

What needs to be understood is that if the dump is caused by a standard SAP program or a custom program. However, i shall assume that the issue is with the custom program's data. Whenever the data in internal tables is stored as pages. Whenever this exceeds a particular limit, the program dumps with the error TSV_TNEW_PAGE_ALLOC_FAILED. The Run Time analysis in ST22 would definitely give you details about the table which was the cause of this dump. Once the table is determined, please find ways to reduce the contents of it by applying suitable logic.

You can also take the help of the tool Memory Analyser. http://help.sap.com/saphelp_nw70/helpdata/en/25/8157f3954486409bb91fed4a27f4da/content.htm

Even this might help you.

Please reach out to me in case you need more details.

Warm Regards,

Ram

[former_member201054 · Accepted solution]

Hi ram,

Thanks a lot..your reponse cools me down...

lets us assume that I adjust the parameters randomly and  gradually..

how the ensure the system will not go down due to the parameters...so that I will not restart the system...

thanks a ton

[Former Member · Accepted solution]

Dear Daniel,

Please do not panic. The issue would definitely get sorted.

Coming to your question, system will not go down just due to the change in parameters. All said and done, Change these values gradually and see how the system is behaving. The tip is not to do a drastic change in the parameter from the current value which might have its negative effects.

On following a trial and error method, you would be able to decipher on the apt parameter value for you. When we recommend changing the parameter in a random way, people might feel it to be dumb. But, the sole reason why this is said is that there is no particular formula to find the appropriate value.

However, i urge you to go through the below link for more details as well as the SAP Notes mentioned(88416 Note might be very useful for you).

Note 88416 - Zero administration memory management for the ABAP server(Specific to Windows)

Note 146289 - Parameter Recommendations for 64-Bit SAP Kernel

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

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCCSTMM/BCCSTMM.pdf

Some values of parameters that I could find are as below.These should help you.

        Parameter             From                  To

rdisp/ROLL_SHM           32768                65536

rdisp/PG_SHM               32768                65536

em/initial_size_MB         4096                  16384

abap/heap_area_total      2000000000       4000000000

I have put in all that I could find for you, Please check and let us know if your query is answered.

Best Wishes!!!

Warm Regards,

Ram

[phil_tallent · Accepted solution]

I see these type errors in a lot of short dumps and my parameters are good based on the recommendations. I have talked to my ABAP people and the end user to find out what exactly is going on and what the user is trying to accomplish. You may be surprised that someone is executing a report and do not understand the ramifications of what they are doing.  I am looking at a short dump now and the program is failing because the internal table is over 30,000,000 million rows. A little detective work goes a long way and working with the end user may resolve the problem.

[former_member201054 · Accepted solution]

Hi Ram,

Fantastic..your suggestion resolved the issue..gradual increase of parameters..

You can be become a good mentor. I wish you all the best..

Please share your blogs/articles if any has been published..

Thanks a ton..

[Former Member · Accepted solution]

Dearest Daniel,

I am very glad that my comments were of help to you. Many congratulations on fixing this issue.

Many many thanks for your appreciation. It indeed does motivate me to do better. Thanks again. I shall share my articles with you as and when I post something on SCN.

Best Wishes,

Ram

[Reagan]

I am getting below runtime errors in SCM 7.0 EHP2 system.
TSV_TNEW_PAGE_ALLOC_FAILED
TSV_TNEW_BLCOKS_NO_ROLL_MEMORY

Have you checked the ABAP dumps ?

First find out what is causing these dumps and then check whether it is a standard program or custom one.

Additionally make sure the parameters have the recommended values (atleast)

Regards

RB

[former_member201054]

Hi Benjamin/Eimler,

First of all , I would like to thank you for your reply.

It's a standard program..seems need to change memory parameters..

I would be greatful to you, If you let me know the memory parameters calculation formula/method

Please advice

Thanks a ton

[Reagan]

You need to review the SAP notes for parameter recommendations specific to the OS and kernel.

Most importantly you need to analyze the dumps.

There is no formula involved. You need make sure that there is sufficient memory available on the machine.

Regards

RB

[willi_eimler]

Hi Reagan,

that's not true. There is a formula:

1 "stupid user" = n shortdumps TSV_TNEW_BLCOKS_NO_ROLL_MEMORY

Sorry Reagan I ate a clown at breakfast.

Best regards

Willi Eimler

[former_member201054]

Hi Regan and elimer,

I thought you both were from SAP and answer with seriousness..this fourm is not a place for joke,..

May bless you...

[Reagan]

Daniel,

You are not going to fix the issue by randomly changing the parameters.

You need to identify where exactly the problem is.

I have already suggested you what should be checked.

All you have replied is "It's a standard program.." and then your assumption "seems need to change memory parameters.."

If I were in your place I would get the program tested on the test system by the application team or I would perform a testing of the program on the test system.

If it get dumped out then analyze the dump and also check the Tx ST02

You should try reducing the dataset and execute the transaction if possible.

You need to check relevant SAP notes bases on the OS.

Note 425207 - SAP memory management, current parameter ranges

Lastly I don't think there is anything offensive in Willi's reply. In fact he has a point.

One user can complain about a transaction getting dumped out if he doesn't know how to run transactions based on the system resources.

Regards

RB

[willi_eimler]

Hi daniel,

first of all take a look at

Note 146289 - Parameter Recommendations for 64-Bit SAP Kernel

Best regards

Willi Eimler

[former_member201054]

Hi,

Please suggest a suitable value for required memory parameter change.

Thanks and regards

Daniel

[former_member201054]

Hi SAP/moderator,

can you please help me on this.

Thanks a ton

Daniel