Добавил:
Upload Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:
Semestr2 / 1 - Oracle / Oracle selected docs / Database concepts.pdf
Скачиваний:
29
Добавлен:
12.05.2015
Размер:
6.96 Mб
Скачать

System Global Area (SGA) Overview

See Also:

"Shared SQL Areas and Private SQL Areas" on page 7-12 for more information about the location of the private SQL area

Chapter 15, "Dependencies Among Schema Objects" for more information about the invalidation of SQL statements and dependency issues

Oracle9i SQL Reference for information about using ALTER SYSTEM FLUSH SHARED_POOL

Oracle9i Database Reference for information about V$SQL and

V$SQLAREA dynamic views

Large Pool

The database administrator can configure an optional memory area called the large pool to provide large memory allocations for:

Session memory for the shared server and the Oracle XA interface (used where transactions interact with more than one database)

I/O server processes

Oracle backup and restore operations

Parallel execution message buffers, if the initialization parameter PARALLEL_ AUTOMATIC_TUNING is set to true (otherwise, these buffers are allocated to the shared pool)

By allocating session memory from the large pool for shared server, Oracle XA, or parallel query buffers, Oracle can use the shared pool primarily for caching shared SQL and avoid the performance overhead caused by shrinking the shared SQL cache.

In addition, the memory for Oracle backup and restore operations, for I/O server processes, and for parallel buffers is allocated in buffers of a few hundred kilobytes. The large pool is better able to satisfy such large memory requests than the shared pool.

The large pool does not have an LRU list. It is different from reserved space in the shared pool, which uses the same LRU list as other memory allocated from the shared pool.

Memory Architecture 7-15

System Global Area (SGA) Overview

See Also:

"Shared Server Architecture" on page 8-15 for information about allocating session memory from the large pool for the shared server

Oracle9i Application Developer’s Guide - Fundamentals for information about Oracle XA

Oracle9i Database Performance Planning for more information about the large pool, reserve space in the shared pool, and I/O server processes

"Degree of Parallelism" on page 18-8 for information about allocating memory for parallel execution

Control of the SGA’s Use of Memory

Dynamic SGA provides external controls for increasing and decreasing Oracle’s use of physical memory. Together with the dynamic buffer cache, shared pool, and large pool, dynamic SGA allows the following:

The SGA can grow in response to a database administrator statement, up to an operating system specified maximum and the SGA_MAX_SIZE specification.

The SGA can shrink in response to a database administrator statement, to an Oracle prescribed minimum, usually an operating system preferred limit.

Both the buffer cache and the SGA pools can grow and shrink at runtime according to some internal, Oracle-managed policy.

Other SGA Initialization Parameters

You can use several initialization parameters to control how the SGA uses memory.

Physical Memory

The LOCK_SGA parameter locks the SGA into physical memory.

SGA Starting Address

The SHARED_MEMORY_ADDRESS and HI_SHARED_MEMORY_ADDRESS parameters specify the SGA’s starting address at runtime. These parameters are rarely used. For 64-bit platforms, HI_SHARED_MEMORY_ADDRESS specifies the high order 32 bits of the 64-bit address.

7-16 Oracle9i Database Concepts

Соседние файлы в папке Oracle selected docs