RE: Implementing ADDRESS WINDOWING EXTENSIONS (AWE) for increased memory

From: M Rafiq <>
Date: Thu, 7 Feb 2008 14:52:43 -0500
Message-ID: <BAY107-W15BB74F2282677B1AB4D3EA12E0@phx.gbl>


Thanks for sharing. It is a vendor supported application database and they required us to bump us sga size. Let us see how it goes. Normal dedicated connections to databases remains in the range of 40-60.  


Date: Thu, 7 Feb 2008 12:26:03 -0500From: bdbafh_at_gmail.comTo: rafiq9857_at_hotmail.comSubject: Re: Implementing ADDRESS WINDOWING EXTENSIONS (AWE) for increased memoryCC:;; On Thu, Feb 7, 2008 at 12:08 PM, M Rafiq <> wrote:

I just applied the following 2 coomands and restarted database without any issues. It is Window 2003 with 4GB ram. No other changes made to any other parameter or any file. SQL> ALTER SYSTEM SET SGA_MAX_SIZE = 1500M SCOPE = SPFILE;System altered.SQL> ALTER SYSTEM SET SGA_TARGET = 1500M SCOPE = SPFILE;System altered.  Instance_Name   Host_Name   Db_version    startup_time      Status   Db_Status--------------- ------------ ---------- ------------------ ---------- ----------ABC                WINDOWS2003 07-FEB-08 11:43:24 OPEN       ACTIVESQL> show parameter sgaNAME                                 TYPE        VALUE------------------------------------ ----------- ------------------------------lock_sga                             boolean     FALSEpre_page_sga                         boolean     FALSEsga_max_size                         big integer 1577058304sga_target                           big integer 1577058304SQL>RegardsRafiq
Rafiq,If the /3GB flag isn't set, I'd bet a hefty sum that if you throw 300 dedicated server sessions at that with enough usage to work the pga, populate the buffer cache and the shared pool ... and you'd see ora-4031 errors and TNS: internal restriction exceeded messages during connection attempts.The OS limit for the oracle.exe process isn't 2*1024*1024*1024 bytes. Its much lower.It also kicks in for the virtual memory, not the committed memory.This brings back memories, albeit not fond ones.good luck.Paul

Date: Wed, 6 Feb 2008 14:44:19 -0800From: jkstill_at_gmail.comTo: davidg.oraclel_at_live.comSubject: Re: Implementing ADDRESS WINDOWING EXTENSIONS (AWE) for increased memoryCC:

From the ML Note:

The size of this window is defined by a registry setting in the HOME key for     Oracle (HKLM\Software\Oracle\Homex) called AWE_WINDOW_MEMORY.  By default, 
    this value is 1GB, so if this value is not set in the registry,      AWE_WINDOW_MEMORY will be 1GB.  This is set on a per instance basis.
On Feb 1, 2008 1:22 PM, David Grosser <> wrote:

Hi, I'm trying to implement ADDRESS WINDOWING EXTENSIONS (AWE) to take advantage of all of the memory on my server. The server details are: Windows server 2003 enterprise edition, 4 processors, 8 GB memory, Oracle I tried to implement awe according to metalink note 225349.1 but my instance is not coming up. I did the following:

added switches /PAE and /3GB to the boot.ini

removed sga_target from the spfile added USE_INDIRECT_DATA_BUFFERS=TRUE to the spfile

added DB_BLOCK_BUFFERS to the spfileThe error I get when I start the database is :ORA-27102: out of memoryOSD-00034: additional error informationO/S-Error: (OS 8) Not enough storage is available to process this command. I've tried raising and lowering the memory but nothing works. Has anyone implemented AWE? If so, how did you get it to work? Thanks,David GrosserDBANSTAR Electric and Gas

Need to know the score, the latest news, or you need your Hotmail®-get your "fix". Check it out.-- Jared StillCertifiable Oracle DBA and Part Time Perl Evangelist

Shed those extra pounds with MSN and The Biggest Loser! Learn more.-- -----------------------------------------------------------------USADA and WADA are broken and not worth fixing. Boycott professional sports. Avoid patronizing their advertisers. Don't buy tickets to NBA, NFL, MLBB, NHL and especially Pro Cycling. 
Helping your favorite cause is as easy as instant messaging. You IM, we give.
Received on Thu Feb 07 2008 - 13:52:43 CST

Original text of this message