Olá,
Para quem quiser colocar Oracle em 32 Bits (Windows Server) com mais memória. Segue explicação abaixo (exemplo). Funciona 100%. Rodei 4 anos assim. Abraço, Adio Garda AWE memory configuration on Windows 32-bit AWE (Address Windowing Extensions) or VLM On 32-bit Windows a process can only attach memory segments to a maximum of 2GB. However if you have more than 4GB of memory installed, you may configure Windows to port a process wanting to use more than 2GB to use the memory above 4GB. This note explains how to do this with an Oracle 9i database running on Windows 2003 enterprise edition. Note: AWE can NOT be used on the following versions of Windows: * Windows 2000 Server (Standard) * Windows 2000 Professional * Windows XP Home Edition * Windows XP Professional * Windows 2003 Standard Edition * Windows 2003 Web Edition To enable VLM configuration on Windows 32-bit systems you need to set a number of parameters. This post explains which parameters need to be set, how to calculate them and which function they serve. * Operating system parameters: boot.ini: You must first edit the file C:\boot.ini which is normally hidden and write protected. There are two parameters available: /3GB and /PAE /3GB enables a single process to attach 3GB of memory. /PAE enables access to memory above 4GB to be mapped for a process. You can set either one of these parameters to fulfill your purpose. However, you may not set the /PAE if you have a maximum of 4GB of physical RAM available since this parameter maps to the memory space above 4GB. If you have more than 4GB, you may set both parameters simultaneously. If you have both parameters set, you will only be able to address up to 16GB of RAM. To address more, you must remove the /3GB switch. Your boot.ini would look something like this: [boot loader] timeout=5 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=Windows Server 2003, Enterprise /fastdetect /3GB /PAE /NoExecute=OptOut Registry settings: The parameter AWE_WINDOW_MEMORY should be set. This parameter has a default value of 1GB. So, if you dont set this parameter at all, the value will be 1GB. The AWE_WINDOW_MEMORY uses memory within the 3GB address space. Calculating the parameter AWE_WINDOW_MEMORY: To be able to calculate this parameter you must first have the following facts: - number of CPUs (if hyperthreading you must use the physical number) - physical RAM - database block size You calculate the value in 4 steps: 1. SETS_PER_POOL = 2 * CPU_COUNT 2. MAX_BUFFER_POOLS = 8 (constant) 3. _DB_BLOCK_LRU_LATCHES = SETS_PER_POOL * MAX_BUFFER_POOLS 4. AWE_WINDOW_MEMORY = (4096 * DB_BLOCK_SIZE * _DB_BLOCK_LRU_LATCHES) / 8 Note: If the AWE_WINDOW_MEMORY registry parameter is left unset (1GB) and if you have not set the /3GB switch, Oracle will try to allocate 1GB within the 2GB memory area. This will leave you with very small settings for all parameters that do not use the AWE like shared_pool_size. * Oracle parameters (init.ora): To use VLM in your database you must use some old parameters. DB_CACHE_SIZE, DB_*_CACHE_SIZE, DB_KEEP_CACHE_SIZE and DB_RECYCLE_CACHE_SIZE are replaced with their previous parameters: - DB_BLOCK_BUFFERS - BUFFER_POOL_KEEP - BUFFER_POOL_RECYCLE In order to activate VLM you MUST set the USE_INDIRECT_DATA_BUFFERS parameter to TRUE. It is not a must but is recommended that you even set the parameter _DB_BLOCK_LRU_LATCHES in your init.ora or spfile to the value that you calculated above. Example configuration for a server with 2 physical CPUs and 8GB RAM: /PAE and /3GB switch set in boot.ini AWE_WINDOW_MEMORY set to 419430400 (400M) Init.ora file: SGA_TARGET=0 DB_CACHE_SIZE=0 Sem Prioridade _db_block_lru_latches 32 shared_pool_size 1468006400 pga_aggregate_target 1048576000 optimizer_index_caching 95 optimizer_index_cost_adj 50 buffer_pool_keep 0 db_block_buffers 480000 log_buffer 8388608 use_indirect_data_buffers TRUE db_writer_processes 2 sort_area_size 16777216 workarea_size_policy AUTO NOTE: only the database buffer goes into the AWE part of the memory. Shared_pool, log_buffer, sort_area_size, pga etc. all use the 3GB memory area. So if you configure an AWE_WINDOW_MEMORY larger than the default 1GB you have to take into calculation that this space plus the variable part of the SGA must not exceed 3GB. This is why you wont be able to allocate more than 1.4GB for the shared pool. However, if you max out the shared_pool, you will run into ORA-4030 errors on database startup. Therefore, try to keep the shared_pool around 1GB OR migrate to a 64-bit platform :-) Be careful on allocating a too high AWE_WINDOW_MEMORY parameter. There is a good document on Metalink concerning performance issues when setting this parameter too high or too low. De: oracle_br@yahoogrupos.com.br [mailto:oracle_br@yahoogrupos.com.br] Em nome de Vitor Junior Enviada em: quarta-feira, 25 de janeiro de 2012 14:20 Para: oracle_br@yahoogrupos.com.br Assunto: [oracle_br] Res: Re: Configurar a Memoria Oracle - URGENTE Esse eu tive que parabenizar! Chiappa, bela explicação e principalmente parabéns pelas fontes e recursos fornecidos. Esse foi "favoritado". :) Vitor Jr. Infraestrutura/Infrastructure Team Oracle 11g DBA Certified Professional Oracle Database 11g Performance Tuning Certified Expert vitor.jun...@ilegra.com <mailto:vitor.junior%40ilegra.com> fone : 55 51 3212 8444 - 3254 rua washington luiz, 820 cj. 902 centro | poa rs | brasil | cep: 90010-460 www.ilegra.com [As partes desta mensagem que não continham texto foram removidas] [As partes desta mensagem que não continham texto foram removidas]