cancel
Showing results for 
Search instead for 
Did you mean: 

Short Dump During the Begining of SCCL TSV_TNEW_PAGE_ALLOC_FAILED

Former Member
0 Kudos

Hello All,

Accepted Solutions (1)

Accepted Solutions (1)

former_member214355
Contributor
0 Kudos

Hello Sean

The error TSV_NEW_PAGE_ALLOC_FAILED means that more memory was requested

because the program needed to expand an internal table, but not is

available.

When Extended Memory is used up, the process will go into PRIV mode

as it starts using Heap Memory (or vise-versa). No other user will

be able to use this wp while it is in PRIV mode. If there is enough

heap for it to finish, you will not see the error

TSV_NEW_PAGE_ALLOC_FAILED and the wp will be freed.

Please check note 146289.

This note shows how to Implement the SAP profile parameters.

See SAP Note 425207 for parameter limitations

Setting of em/initial_size_MB usually depends on the physical RAM

on the server and if you have any other instanecs on that same

server. According to note #146289 this can be increased to very high

values if there is sufficent RAM on the box.

Also, see the SAP notes:

#020527 Runtime error TSV_TNEW_PAGE_ALLOC_FAILED

#217262 Runtime error text for TSV_TNEW_PAGE_ALLOC_FAILED

#185185 Application: Analysis of memory bottlenecks

Thanks

Kenny

Answers (2)

Answers (2)

Former Member
0 Kudos

Current Parameters on my System

ztta/roll_area =20000000

ztta/roll_extension = 4000000000

abap/heap_area_total = 2000000000

abap/heap_area_dia = 2000000000

abap/heap_area_nondia = 2000000000

em/initial_size_MB = 6968 (7 GB physical Ram in VMware) 20 GB swap

em/max_size_MB = 20470

I have advanced some of these parameters and I have also tried the SAP note 601196 with no luck

Kenny it seems i have moved these parameters to the correct sizing according to those two notes do you see something that i need to fix with these parameter ?

former_member214355
Contributor
0 Kudos

Hello Sean

Is your system 64-bit?

Please refer to Note 146289.

This has solved this problem for other customers.

Kenny

former_member214355
Contributor
0 Kudos

Hi

Any update?

Did this help?

Former Member
0 Kudos

Hey Kenny i am sorry i had a family emergency yesterday and today was the earliest i could get to this.

I did look at SAP note 146289 and made the recommended changes for a Linux x86_64 bit system. However i am still receiving this short dump at the beginning of every local Client copy. I have also noticed that the parameter for PHYS_MEMSIZE = 64 i believe that this is exceptionally to low could this be causing issues ? I can show any parameters you need thanks soo much for this help.

markus_doehr2
Active Contributor
0 Kudos

A client copy on 7.00 makes excessive use of shared memory objects. The parameters you need to increase are

rsdb/esm/buffersize_kb
rsdb/esm/max_objects

The default for the first one is 4096 which is too low. Increase it to 16384 and restart the instance. Then try the system copy again.

Markus

Former Member
0 Kudos

Thanks Markus,

I reverted the changes i have made already back to before i started running into these client copy errors ,made the changes to rsdb/esm/buffersize_kb = 16384 rsdb/esm/max_objects =8000 , then restarted the instance. I kicked off the Client Copy and soon after received the same short dumps as before. Do I need to make the changes from Kenny as well as yours ?

Then the next thing to tell the both of you is i made the changes to PHYS_MEMSIZE = (5GB) and interesting enough the short dump did occur however i did not get a FINB_TR_CC_EXIT FIN-FB Application Exit Error . I hope this give a bit more insight. Again thanks so much for both of your help! IT is very much appreciated!!!!

former_member214355
Contributor
0 Kudos

Hello Sean

This issue occures due to some problems in RFC configuration.

Kindly refer the below note for the issue:

568784 - Termination with client copy (Financials Basis)

Thanks

Former Member
0 Kudos

Kenny thanks for this note .

I have been creating this RFC connection at the beginning of each of the client copies however I am having problems getting a system user to log with this RFC. And i have been listing this RFC connection as well in FINB_TR_DEST. I think i m going to have to set up to get some help from SAP thanks for the help !

p.s i will update the points after i talk with SAP

Edited by: Sean Siegmund on Feb 8, 2010 8:49 PM

Former Member
0 Kudos

Hello, The issue with short dump 'TSV_TNEW_PAGE_ALLOC_FAILED' in the context of client copy involving FINBASIS component can be resolved by using recommendation from SAP Note 741864 - FinBasis: Termination TSV_TNEW_PAGE_ALLOC_FAILED.

- Increase the system profile parameter abap/shared_objects_size_MB from default value 20 MB to 200 MB, restart the SAP instance and start new client copy.

Best Regards,

Chandrashekhar

Former Member
0 Kudos

Hello Everyone,

I m sorry it took so long to wrap this question up but i m hoping to help someone else with this same issue.

After having a chat with a Basis Guru , who's name will not be mentioned, but he knows who he is. He had me add a couple parameters to this specific machine and i was able to push through this error. These parameters are only specific to my installation because of sizing. I m just giving a list of what was changed ! So it is up to however the Basis guy is to make the correct sizing estimates to solve the problem. Please look at these profile parameters.

PHYS_MEMSIZE

abap/shared_objects_size_MB

enque/table_size

em/global_area_MB

em/max_size_MB

abap/buffersize

Maybe Optional

abap/fieldexit

rsdb/obj/max_objects

rsdb/ntab/irbdsize

rsdb/ntab/ftabsize

rsdb/ntab/entrycount

rsdb/obj/buffersize

Former Member
0 Kudos

Hello All,

I have installed a ECC 6.0 installation on Linux and Oracle 10 with ENHP 4 for an IDES system. I have completed close to 12 Client Copies with no problems however i keep receiving this short dump at the very beginning of every background client copy. I have worked to check the parameters mentioned in the short dump however everything seems fine and the in DB02 , ST02. There is enough space for this machine to extend external tables. Here is a short version of the ST22 report.

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.

Error analysis

The internal table "\AREA=CL_UGMD_META2\INSTANCE=UGMD_FIELDINFO_LOCAL\VERSID=15

\OBJ=\DATA=DT_DFIES" could not be

further extended. To enable

error handling, the table had to be delete before this log was written.

As a result, the table is displayed further down or, if you branch to

the ABAP Debugger, with 0 rows.

At the time of the termination, the following data was determined for

the relevant internal table:

Memory location: "\AREA=CL_UGMD_META2\INST=UGMD_FIELDINFO_LOCAL\CLNT="

Row width: 1342

Number of rows: 0

Allocated rows: 6

Newly requested rows: 3016 (in 377 blocks)

The Client Copy will move everything to the new client however an Application Exit Error will tell me about this short dump that occurs in the source system. I am not to hot in the Database Performance area so if anyone can shed some light on what i might do to correct this issue I will be greatly appreciated.