The requirements for taking advantage of this support are:
The computer on which Oracle Database is installed must have more than 4 GB of memory.
The operating system must be configured to take advantage of Physical Address Extensions (PAE) by adding the /PAE switch in
boot.ini. See Microsoft Knowledge Base article Q268363 for instructions on modifying
boot.inito enable PAE.
It is advisable (though not necessary) to enable 4GT support by adding the /3GB parameter in
boot.ini. See Microsoft Knowledge Base article Q171793 for additional requirements and instructions on modifying
boot.inito enable 4GT.
The user account under which Oracle Database runs (typically the LocalSystem account), must have the "Lock memory pages" Windows 2000 and Windows XP privilege.
USE_INDIRECT_DATA_BUFFERS=TRUEmust be present in the initialization parameter file for the database instance that will use VLM support. If this parameter is not set, then Oracle Database 10g Release 1 (10.1) behaves in exactly the same way as previous releases.
DB_BLOCK_SIZEmust be set to values you have chosen for Oracle Database.
- Registry parameter
AWE_WINDOW_MEMORYmust be created and set in the appropriate key for your Oracle home. This parameter is specified in bytes and has a default value of 1 GB.
AWE_WINDOW_MEMORYtells Oracle Database how much of its 3 GB address space to reserve for mapping in database buffers.
Once this parameter is set, Oracle Database can be started and will function exactly the same as before except that more database buffers are available to the instance. In addition, disk I/O may be reduced because more Oracle Database data blocks can be cached in the System Global Area (SGA).
DB_BLOCK_SIZEis large, however, the default
AWE_WINDOW_MEMORYvalue of 1 GB may not be sufficient to start the database.