TSV_TNEW_PAGE_ALLOC_FAILED,Parameter wrong set these are abap dump

[Former Member]

We are using windows 2003 server with 32 bit database oracle (500 GB)

all most of the jobs terminated with TSV_TNEW_page_ALLOC_faild ,paramerter rorg sert etc

please advise my sap parameter is ok or some change for the best utlization of the tehe memeory.

what is ths valuse of the phys_memsize

my parameter detils are the following..

rsdb/reco_add_error_codes |-12152 , -12560 , -3114 , -3113 |

abap/heap_area_dia	2000000000
nobuf/max_attempts	1200
rdisp/appc_ca_blk_no	1000
rdisp/wp_ca_blk_no	2050
ztta/roll_area	15000000
rdisp/PG_MAXFS	200000
gw/netstat_once	0
abap/heap_area_nondia	2000000000
rdisp/rfc_min_wait_dia_wp	5
enque/table_size	10000
gw/max_sys	1500
gw/max_overflow_size	25000000
rdisp/max_comm_entries	2000
rdisp/tm_max_no	2000
gw/max_conn	2000
rsdb/obj/max_objects	20000
rsdb/obj/buffersize	40000
sap/bufdir_entries	10000
zcsa/presentation_buffer_area	20000000
zcsa/db_max_buftab	10000
zcsa/table_buffer_area	100000000
rsdb/cua/buffersize	10000
rtbb/buffer_length	60000
rsdb/ntab/irbdsize	8000
rsdb/ntab/ftabsize	60000
rsdb/ntab/entrycount	30000
login/system_client	508
abap/buffersize	800500
rdisp/max_wprun_time	3000
SAPSYSTEMNAME	PRD
INSTANCE_NAME	DVEBMGS51
SAPSYSTEM	51
rdisp/wp_no_dia	10
rdisp/wp_no_btc	4
rdisp/wp_no_vb	4
rdisp/wp_no_vb2	1
rdisp/wp_no_enq	1
rdisp/wp_no_spo	1
SAPGLOBALHOST	PRDSVR
PHYS_MEMSIZE	2458

advans thanks

with best regards

venkat

|

[former_member204746]

read SAP note 88416.

set PHYS_MEMSIZE to 2700

delete all these parameters from instance and default profiles

restart SAP and try again:

em/initial_size_MB	[PM]	[PM]	Mbyte
--- em/max_size_MB	--- 20000	--- 100000	Mbyte
em/address_space_MB	512	4096	Mbyte
ztta/roll_first	1	1	Byte
--- ztta/roll_area	--- 2000000	--- 3000000	Byte
ztta/roll_extension	2000000000	2000000000	Byte
abap/heap_area_dia	2000000000	2000000000	Byte
abap/heap_area_nondia	2000000000	0	Byte
abap/heap_area_total	2000000000	[PM]*1048576	Byte
- rdisp/ROLL_MAXFS	[BE] * 100	[BE] * 100	8KB Block
--- rdisp/ROLL_SHM	[BE] * 100	[BE] * 100	8KB Block
--- rdisp/PG_MAXFS	--- 32768	--- 32768	8KB Block
rdisp/PG_SHM	[BE] * 50	[BE] * 50	8KB Block

thwen also check if it`s always the same program that fails. if it is aZ PROGRAM, ask your programmer to use less Internal memory.

obviously, the long term solution is 64-bit.

[Former Member]

Dear all

We are using windows 2003 server with 32 bit database oracle (500 GB)with GB RAM

thanks

with best regards

venkat

[former_member433984]

do you have active /3GB switch in boot.ini??

<a href="https://service.sap.com/sap/support/notes/110172">Note 110172 - Windows: Transactions with large memory requirements</a>

[Former Member]

yes 3 GB/PAE are enable

thanks with immediate replay

we are waitting positive replay

thanks

with best regards

venkat

[former_member433984]

as long term solution you have to go on 64bit platform (<a href="https://service.sap.com/sap/support/notes/996600,">SAP note 996600</a>)

as workaround you can try to play with memory setting like

abap/buffersize, rdisp/ROLL_SHM, rdisp/PG_SHM and reduce them by 10% from original value

(rdisp/appc_ca_blk_no,rdisp/wp_ca_blk_no in generally should be set to default values)

[Former Member]

can i increase the phys_memsize2458 (old) new(3458)

please guide

thanks with regards'

jainendra

[Former Member]

you can, but it will not help you, because the virtual size of a workprocess is limited to 3 Gigabyte on 32 Bit Windows. that is an architectural limit of Windows 32 Bit.

Windows is supporting more physical memory than on process can allocate.

It is exactly this limitation on which you are currently struggeling.

carefully reading the notes Yaroslav has mentioned will have told you the options you have.

1. reduce transactions memory load by decreasing the number of items which are to be processed

2. reduce other big shared memory segments which will enlarge the address space available for transactional memory.This reduces performance because you are reducing cache sizes.

3. go for 64 bit.

peter