自己看吧，我只见过1G内存的服务器。
羡慕你呀。Oracle8i Support for Very Large Memory (VLM) ConfigurationsA new feature in Oracle8i for Windows NT is support for Very Large Memory (VLM) configurations, which allows Oracle8i to access more than the 4 gigabyte (GB) of RAM traditionally available to Windows NT applications.
--------------------------------------------------------------------------------
Note: This feature is only available on Intel Pentium II and Pentium III Xeon 32-bit processor.
--------------------------------------------------------------------------------
Specifically, Oracle8i Enterprise Edition on Windows NT 4.0 (in conjunction with Intel's PSE36 driver) can now allocate substantially more database buffers than previous releases. Further details are posted at: http://www.intel.com/ebusiness/server/resources/pentiumii/xeon/esma.pdf
On Windows 2000, Oracle8i uses the Address Windowing Extensions (AWE) built into the operating system to access more than 4 GB of RAM. For more information, see the Microsoft Web site: http://www.microsoft.com/WINDOWS2000/news/fromms/intelpae.asp
To take advantage of this support, you must do the following: More than 4 GB of RAM must be present in the server on which Oracle8i will run. On Windows NT 4.0: Service Pack 3 or later must be installed. The Intel PSE36 driver must be installed and operational. See http://developer.intel.com/vtune/pse36/index.htm for further PSE36 system requirements and for download instructions. On Windows 2000, the user account under which Oracle8i runs (typically the local SYSTEM account), has the "Lock memory pages" Windows 2000 privilege. USE_INDIRECT_DATA_BUFFERS=TRUE must be present in the INIT.ORA file for the database instance that will use the VLM support. If this parameter is not set, then Oracle8i behaves in exactly the same way as previous releases. Set the INIT.ORA parameters DB_BLOCK_BUFFERS and DB_BLOCK_SIZE as desired for the database. Note that the total number of bytes of database buffers (that is, DB_BLOCK_BUFFERS multiplied by DB_BLOCK_SIZE) is no longer limited to 3 GB as was the case in previous releases. The VLM_BUFFER_MEMORY (for Windows NT 4.0) or AWE_WINDOW_MEMORY (for Windows 2000) registry parameter must be created and set in the appropriate key for your Oracle home in the Windows NT registry. This parameter is specified in bytes and has a default of 1 GB. When using Windows NT 4.0, this parameter tells Oracle8i how much non-PSE36 memory to use for database buffers. When using Windows 2000, this parameter tells Oracle8i how much of its 3 GB address space to reserve for mapping in database buffers. For both implementations, this memory comes from Oracle8i's 3 GB virtual address space, so its value must be less than 3 GB. Setting this parameter to a large value has the effect of using more of Oracle8i's address space for buffers and using less PSE36 or AWE memory for buffers. However, since accessing PSE36 or AWE buffers is somewhat slower than accessing virtual address space buffers, tune this parameter to be as large as possible without adversely limiting database operations. For example, assume that the Oracle8i database is running on an Windows NT 4.0 machine with 8 GB of RAM, which means that the PSE36 driver has control of 4 GB of RAM. If DB_BLOCK_BUFFERS=2500000 and DB_BLOCK_SIZE=2048, then a total of 5 GB of database buffers needs to be allocated. If VLM_BUFFER_MEMORY is set to 1 GB, then 1 GB of buffers come from the Oracle8i virtual address space and 4 GB come from the PSE36 driver. If you set VLM_BUFFER_MEMORY to 500 MB, an error occurs at startup because there is not 4.5 GB of memory available to the PSE36 driver for database buffers. Likewise, if you set VLM_BUFFER_MEMORY to 3 GB, an error occurs because the Oracle8i address space is limited to 3 GB on Windows NT, and this address space must also hold Oracle8i code, shared pool, PGA memory, and other structures. In general, the higher the VLM_BUFFER_MEMORY or AWE_WINDOW_MEMORY is set, the fewer connections and memory allocations will be possible for Oracle8i. The lower VLM_BUFFER_MEMORY or AWE_WINDOW_MEMORY is set, the lower the performance. Once these parameters are set, the Oracle8i 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 since more Oracle data blocks can be cached in the SGA. If out of memory errors occur during the startup sequence, verify the following: PSE36 driver is installed and functional DB_BLOCK_BUFFERS is not set too high for the amount of memory in the computer. Note that more memory than just the database buffers themselves is required when starting up the database. For each database buffer, a database buffer header is also allocated in Oracle8i's virtual address space. When allocating 2,000,000 database buffers, the memory for these buffer headers amounts to several hundred megabytes. This must be considered when setting DB_BLOCK_BUFFERS and VLM_BUFFER_MEMORY. VLM_BUFFER_MEMORY is not set too high for the amount of address space available to Oracle8i. In Windows NT's Performance Monitor, under the Process object, monitor the Virtual Bytes counter for the "ORACLE" process. If this counter approaches 3 GB, then out of memory errors can occur. If this happens, reduce DB_BLOCK_BUFFERS and/or VLM_BUFFER_MEMORY until the database is able to start. Currently, there is a limitation in Server Manager for Windows NT whereby the amount of database buffers displayed during database startup is incorrect if more than 4 GB of buffers are in use. For instance, if 5 GB of buffers are used, Server Manager incorrectly reports that 1 GB is being used. This limitation will be fixed in the next release of Oracle8i.
羡慕你呀。Oracle8i Support for Very Large Memory (VLM) ConfigurationsA new feature in Oracle8i for Windows NT is support for Very Large Memory (VLM) configurations, which allows Oracle8i to access more than the 4 gigabyte (GB) of RAM traditionally available to Windows NT applications.
--------------------------------------------------------------------------------
Note: This feature is only available on Intel Pentium II and Pentium III Xeon 32-bit processor.
--------------------------------------------------------------------------------
Specifically, Oracle8i Enterprise Edition on Windows NT 4.0 (in conjunction with Intel's PSE36 driver) can now allocate substantially more database buffers than previous releases. Further details are posted at: http://www.intel.com/ebusiness/server/resources/pentiumii/xeon/esma.pdf
On Windows 2000, Oracle8i uses the Address Windowing Extensions (AWE) built into the operating system to access more than 4 GB of RAM. For more information, see the Microsoft Web site: http://www.microsoft.com/WINDOWS2000/news/fromms/intelpae.asp
To take advantage of this support, you must do the following: More than 4 GB of RAM must be present in the server on which Oracle8i will run. On Windows NT 4.0: Service Pack 3 or later must be installed. The Intel PSE36 driver must be installed and operational. See http://developer.intel.com/vtune/pse36/index.htm for further PSE36 system requirements and for download instructions. On Windows 2000, the user account under which Oracle8i runs (typically the local SYSTEM account), has the "Lock memory pages" Windows 2000 privilege. USE_INDIRECT_DATA_BUFFERS=TRUE must be present in the INIT.ORA file for the database instance that will use the VLM support. If this parameter is not set, then Oracle8i behaves in exactly the same way as previous releases. Set the INIT.ORA parameters DB_BLOCK_BUFFERS and DB_BLOCK_SIZE as desired for the database. Note that the total number of bytes of database buffers (that is, DB_BLOCK_BUFFERS multiplied by DB_BLOCK_SIZE) is no longer limited to 3 GB as was the case in previous releases. The VLM_BUFFER_MEMORY (for Windows NT 4.0) or AWE_WINDOW_MEMORY (for Windows 2000) registry parameter must be created and set in the appropriate key for your Oracle home in the Windows NT registry. This parameter is specified in bytes and has a default of 1 GB. When using Windows NT 4.0, this parameter tells Oracle8i how much non-PSE36 memory to use for database buffers. When using Windows 2000, this parameter tells Oracle8i how much of its 3 GB address space to reserve for mapping in database buffers. For both implementations, this memory comes from Oracle8i's 3 GB virtual address space, so its value must be less than 3 GB. Setting this parameter to a large value has the effect of using more of Oracle8i's address space for buffers and using less PSE36 or AWE memory for buffers. However, since accessing PSE36 or AWE buffers is somewhat slower than accessing virtual address space buffers, tune this parameter to be as large as possible without adversely limiting database operations. For example, assume that the Oracle8i database is running on an Windows NT 4.0 machine with 8 GB of RAM, which means that the PSE36 driver has control of 4 GB of RAM. If DB_BLOCK_BUFFERS=2500000 and DB_BLOCK_SIZE=2048, then a total of 5 GB of database buffers needs to be allocated. If VLM_BUFFER_MEMORY is set to 1 GB, then 1 GB of buffers come from the Oracle8i virtual address space and 4 GB come from the PSE36 driver. If you set VLM_BUFFER_MEMORY to 500 MB, an error occurs at startup because there is not 4.5 GB of memory available to the PSE36 driver for database buffers. Likewise, if you set VLM_BUFFER_MEMORY to 3 GB, an error occurs because the Oracle8i address space is limited to 3 GB on Windows NT, and this address space must also hold Oracle8i code, shared pool, PGA memory, and other structures. In general, the higher the VLM_BUFFER_MEMORY or AWE_WINDOW_MEMORY is set, the fewer connections and memory allocations will be possible for Oracle8i. The lower VLM_BUFFER_MEMORY or AWE_WINDOW_MEMORY is set, the lower the performance. Once these parameters are set, the Oracle8i 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 since more Oracle data blocks can be cached in the SGA. If out of memory errors occur during the startup sequence, verify the following: PSE36 driver is installed and functional DB_BLOCK_BUFFERS is not set too high for the amount of memory in the computer. Note that more memory than just the database buffers themselves is required when starting up the database. For each database buffer, a database buffer header is also allocated in Oracle8i's virtual address space. When allocating 2,000,000 database buffers, the memory for these buffer headers amounts to several hundred megabytes. This must be considered when setting DB_BLOCK_BUFFERS and VLM_BUFFER_MEMORY. VLM_BUFFER_MEMORY is not set too high for the amount of address space available to Oracle8i. In Windows NT's Performance Monitor, under the Process object, monitor the Virtual Bytes counter for the "ORACLE" process. If this counter approaches 3 GB, then out of memory errors can occur. If this happens, reduce DB_BLOCK_BUFFERS and/or VLM_BUFFER_MEMORY until the database is able to start. Currently, there is a limitation in Server Manager for Windows NT whereby the amount of database buffers displayed during database startup is incorrect if more than 4 GB of buffers are in use. For instance, if 5 GB of buffers are used, Server Manager incorrectly reports that 1 GB is being used. This limitation will be fixed in the next release of Oracle8i.
解决方案 »
免费领取超大流量手机卡，每月29元包185G流量+100分钟通话, 中国电信官方发货