The default pool is
named DEFAULT, so you can use the alter table command to redirect a table to the DEFAULT
pool at a later date. Here is an example of assigning a table to the KEEP buffer pool:
create table state_cd_lookup
(state_cd char(2),
state_nm varchar2(50)
)
storage (buffer_pool keep);
You can use the LARGE_POOL_SIZE initialization parameter to specify the size of the large
pool allocation heap in bytes. The large pool allocation heap is used in shared server systems
for session memory, by parallel execution for message buffers, and by backup processes for I/O
buffers. By default, the large pool is not created.
As of Oracle Database 10g, you can use Automatic Shared Memory Management (ASMM). To
activate ASMM, set a nonzero value for the SGA_TARGET database initialization parameter. After
you set SGA_TARGET to the size of the SGA you want (that is, all of the caches added together),
you can then set the other cache-related parameters (DB_CACHE_SIZE, SHARED_POOL_SIZE,
JAVA_POOL_SIZE, and LARGE_POOL_SIZE) each to 0; if you provide values for these parameters,
those values will serve as the lower bound for the automatic tuning algorithm. Shut down and
restart the database for the changes to take effect; the database will then begin actively managing
the size of the different caches. You can monitor the size of the caches at any time via the
V$SGASTAT dynamic performance view. Oracle Database 11g takes the automation a step
farther: you can set MEMORY_TARGET to the total amount of memory available to Oracle.
Pages:
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429