on 07-07-2006 3:22 PM
Hi
We have installed Web AS 6.40 (ABAP + J2EE) on Windows 2003 Server (Enterprise Edition). We have also activated /3gb option. However, SAP is using page file beyond 4 GB memory. System has 4 GB memory available, but SAP is not using it.
Any ideas?
Regards
Chandu
Hi Chandu,
In archive boot.ini set values
[operating systems]
/pae /3GB
During the intalation of the WEB AS , the SAPINST informs only 4GB memory , but pos installation set parameter PHYS_MEMSIZE in RZ10 with the required value.
Check the value parameter PHYS_MEMSIZE in RZ11 later stop/start the instance.
Felipe
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Are you running the 32 or 64 bit version of Windows 2003 Enterprise?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
My main back ground is java only installs. But, some things still apply to ABAP+java. In all the ones I have done Windows will still us page files for system and DB and anything else that is not SAP.
SAP likes to load in low continuous memory. There should not be a problem like that in Win 2003 but, you may want to check note 736462 and it's side notes to make sure.
One portal that I just got done with had the same OS and memory. Until I started getting load on that server it would sit at about 4 gig being used. But, when it was in production I went as high as 7, never used the full 8.
32 bit java has a limit of 1.7 gig per engine. I put mine at 1.536 and it played better. If you one have one engine at one gig, I can see why you are not seeing memory being used up. The ABAP side is not going to take up that much either. I think you page file is coming all from the Windows side. SAP loads into low memory and stays there.
I hope I shed some light here........
Dear Dave,
Im struggling to get a straight answer on a memory problem were currently experiencing and you're clearly a man who know about this subject. Weve had a problem recently in that our servers can blue-screen when they hit 130Mb non-paged memory usage. Weve pretty much isolated our AV software as the culprit thats slowly eating away at this memory, as stopping AV stems the growth in non-paged memory.
Were running with 6Gb RAM on our ECC5 application servers, and weve /3GB and /PAE set within boot.ini to enable Windows to allocate more addressable memory to SAP and to make use of any physical memory over 4Gb. I talked to someone yesterday who mentioned that setting /3Gb reduces the amount of non-paged memory available (from 350Mb to 250Mb in a MS Exchange environment), but our servers are crashing at 130Mb non-paged memory, which is a bit of a mystery. Ive asked our hosting partners to remove the /3Gb switch out of boot.ini on one of our app server to see whether this allows non-paged memory to get past 130Mb before failing.
The part thats really confusing me though, and the part that Im unable to get a straight answer on is /PAE. Microsoft seem to state that /PAE is required to use any RAM over 4Gb, however my most trusted BASIS advisor (been in BASIS for 12 years and has an almost unhealthy interest in it) tells me that its not worth setting /PAE if youve less than 8Gb RAM - we've only 6Gb RAM
I need to tell our hosting partners whether or not to remove /PAE at the same time as theyre removing /3Gb, but I dont know whats best. Were talking ECC5 application servers here, not database servers of LiveCache.
Can you help?
Thanks
Arwel.
Do not use the /3gb switch.
Use the /PAE and this will give you the access to the RAM to and above 4 gig.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.