First page Back Continue Last page Graphics
Large Pool / Java Pool
Large pool is in the SGA area
- Caches large memory requests
- E.g. MTS allocations for UGA
- Keeps segregated from Shared pool
- Keeps shared pool for SQL caching
Java pool is in the SGA
- Required to cache Java code
- Oracle uses Java, even if you don't
- Minimum 1MB
Notes:
Oracle8i introduced the Large Pool and the Java Pool.
The Large Pool is an optional structure designed in part to eliminate user session information (UGA) from being stored in the Shared Pool when multi-threaded server is active; this allows the Shared Pool to be used primarily for SQL caching. See the LARGE_POOL_SIZE parameter in the Oracle9i Database Reference manual for sizing information.
The Java Pool caches the Java class states and Java objects. Note that Oracle uses Java – even if you do not. For example, the UTL_TCP package incorporates Java classes. Thus, the minimum size for the Java pool is 1MB (see the JAVA_POOL_SIZE parameter).