Users complain about the slow response time of queries. While investigating the cause you find that
the Oracle Instance is not configured to cache all of the data blocks to satisfy the users’ queries.
Which component of the Oracle Instance would you change to improve performance?
A.
Java pool
B.
Large pool
C.
Shared pool
D.
Streams pool
E.
Library cache
F.
Redo log buffer
G.
Data dictionary cache
H.
Database buffer cache
For many types of operations, Oracle Database uses the buffer cache to store data blocks read from disk.
In the phrase database buffer cache, the term buffer refers to database blocks. A database block is the minimum amount of storage that Oracle reads or writes. All storage segments that contain data are made up of blocks. When you request data from disk, at minimum Oracle reads one block.
The database buffer cache, also called the buffer cache, is the memory area that stores copies of data blocks read from data files. A buffer is a main memory address in which the buffer manager temporarily caches a currently or recently used data block.
Oracle’s Automatic Shared Memory Management feature manages the size of the Streams pool when the SGA_TARGET initialization parameter is set to a nonzero value. If the STREAMS_POOL_SIZE initialization parameter also is set to a nonzero value, then Automatic Shared Memory Management uses this value as a minimum for the Streams pool.
If the STREAMS_POOL_SIZE initialization parameter is set to a nonzero value, and the SGA_TARGET parameter is set to 0 (zero), then the Streams pool size is the value specified by the STREAMS_POOL_SIZE parameter, in bytes.
If both the STREAMS_POOL_SIZE and the SGA_TARGET initialization parameters are set to 0 (zero), then, by default, the first use of Streams in a database transfers an amount of memory equal to 10% of the shared pool from the buffer cache to the Streams pool.
INSTANCE – CACHE