High paging in Windows 2003 server - Oracle 10.2.0.4

[Former Member]

Hi ,

SAP instance running on Windows 2003 server , DB-oracle 10.2.0.4.

Currently we have 16 GB of physical memory and 12 gb of virtual memory set in the system.As the sap system is started immediately the paging goes high to 25 gb used.

Checked market place and found this note

Note 1009297 and implemented the windows patches given in the note ,still the issue exists.Please help to resolve the issue.

SAP system:Solution managaer 7.0

Oracle:10.2.0.4

OS:Windows 2003 server 64-bit machine. service pack 2

Basis-Team .

[Sriram2009 · Accepted solution]

Hi Peter

As per the Sap Notes 1518419, basic information about how to calculate the page file and virtual memory in your SAP systems, in your live environment we need to see some time it may require to increase more then 2 or 3 time. Kindly check below link about the memory management.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70642622-7bd2-2b10-c290-a297e346c...

Regards

Sriram

[Former Member · Accepted solution]

.

[Sriram2009]

Hi Peter

As per the sap note 88416 ZERO MEmory Administration

Regards

Sriram

[Former Member]

have a look at note 1518419 because in meantime the reality is a little more complex.

note 88416 is still valid, but only if there is only one system on the box and if your pagefiles has 2-3 times the size of the physical ram of the box (which is litte too much if the box has 250 GB of it).

The reason why the system is using pagefile directly after startup is following:

SAP configures large portions of memory for caches and transaction memory for the users connecting to the system.

This amount is allocated during the startup of the system. Only some parts (so called privat memory) is allocated on demand.

This is the reason why the system needs so much virtual memory after being started up. How much - see note 1518419.

regards

Peter

[Sriram2009]

Hi

As per the Note 1009297 - Windows Server 2003 Family: High Paging Rates apply the hot fix and then check

Regards

Sriram

[Former Member]

hi all,

please be sure to not mix up terminolgy:

note 1009792 is describing a situation where the operating system show high pageout-rages (that is page writes on the pagefile per second). This has necessarily nothing to do with the page file size which is obviously mentioned in this thread.

may I put your attention the newly created note 1518419 Page file and virtual memory required by the SAP.

Maybe you'll find the answer to your question there.

regards

Peter

[Sriram2009]

Hi

Kindly go thru the Microsoft link - http://support.microsoft.com/?kbid=931308 apply and check

Regards

Sriram

[Former Member]

.

[former_member204746]

on Windows, pagefile should set to a minimum of RAM + 8Gb, so, 24Gb in your case.

[Former Member]

Yes,you right on windows 2003 server the page file should be set to 1.5 times the physical memory.we set it to 24gb now,still the paging is shooting up to 25gb when the sap system is started.

Though enough physical memory is free why the paging goes high to 25gb.Ideally swap space is not required when you have enough physical memory.

Can somebody help to resolve the issue.

Thanks

[Former Member]

12 GB Page file are small , try at least 30 GB...

I'm have 10.2.0.2 on same 2003 server and PF used are 17 Gb (this are ok, no problem) How you configure Oracle and SAP Memory ? What exactly is your problem ?

Regards.

[Former Member]

For 64 bit minimum 20 G.B VM is required

[Former Member]

Hi !

For 64 bit minimum 20 G.B VM should be allocated. You can set 30 G.B VM on your Server.

Also swapping upto 30% is acceptable in an SAP system. Also check how much free memory you have in os06 and also check the buffer parameters in st02. Fine tune them if you have free memory.

[Former Member]

You may need to look at various big shared memory configuration in the system

1. Oracle SGA

2. ABAP extended memory and buffers

3. Java Heap Memory

Your Windows pagefile configuration need to be optimized as well. Use 20GB minimum for a 64-bit system. More safest value will be 32GB (double the physical memory)