|Oracle® Database Reference
11g Release 2 (11.2)
|PDF · Mobi · ePub|
|Parameter type||Big integer|
Otherwise, derived from the values of
Note that a value derived in this way does not take into account the requirements used for Automatic Storage Management files. As a general guideline, you should add 600K to the size of the SGA on a database instance using ASM.
|Range of values||Minimum: the granule size
Maximum: operating system-dependent
LARGE_POOL_SIZE specifies (in bytes) the size of the large pool allocation heap. 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 disk I/O buffers. Parallel execution allocates buffers out of the large pool only when
SGA_TARGET is set.
Caution:When Oracle derives a default value, it adds 250K for each session for the shared server if
DISPATCHERSis configured. The final derived value also includes a port-specific amount of memory for backup I/O buffers. The total derived default value can either be too large to allocate or can cause performance problems. In that case, set
LARGE_POOL_SIZEto a number sufficiently small so that the database can start.
You can specify the value of this parameter using a number, optionally followed by K or M to specify kilobytes or megabytes, respectively. If you do not specify K or M, then the number is taken as bytes.