Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
20 Cards in this Set
- Front
- Back
- 3rd side (hint)
area of the SGA that stores shared memory structures such as shared SQL statements and internal information.
|
shared pool
|
This is important because an insufficient amount of memory allocated to this can cause performance degradation
|
|
The shared pool consists of?
|
sql area and data dictionary cache
|
|
|
contains a set of tables and views that Oracle uses as a reference to the database.
|
data dictionary cache
|
Oracle stores information here about the logical and physical structure of the database (i.e. user info, defined integrity constraints, column name/data types, etc..)
|
|
If multiple applications issue this, this shared area can be accessed to reduce the amount of memory needed.
|
sql area
|
reduces the processing time used for parsing and execution planning.
|
|
contains a set of tables and views that Oracle uses as a reference to the database.
|
data dictionary
|
Stores information such as user info, defined integrity constraints, names and data types of columns. Frequently accessed to parse sql statements.
|
|
you will see a severe performance degradation if you don't have enough memory here?
|
data dictionary cache
|
|
|
memory area that contains data and control information for the Oracle server processes.
|
program global area (pga)
|
|
|
The PGA consists of these 3 components?
|
stack space, session information, private sql area.
|
|
|
If you are not running the multithreaded server, this is stored in the PGA?
|
session information
|
If you are running multithreaded server, this is stored in the SGA.
|
|
This is an area in the PGA where information such as binding variables and runtime buffers is kept.
|
private sql area
|
|
|
The PGA memory that holds the session's variables and arrays.
|
stack space
|
|
|
are the user's connections to the RDBMS system
|
user processes
|
is also used to display the information requested by the user
|
|
perform functions for users. Oracle processes
|
oracle processes
|
can be split into two groups: server processes (which perform functions for the invoking process) and background processes (which perform functions on behalf of the entire RDBMS).
|
|
communicate with the user and interact with Oracle to carry out the user's requests
|
server process
|
also known as shadow processes. if the user process requests a piece of data not already in the SGA, this is responsible for reading the data blocks from the datafiles into the SGA
|
|
This performs tasks such as communicating with other Oracle instances and performing system maintenance and cleanup, to writing dirty blocks to disk.
|
background processes
|
|
|
is responsible for writing dirty data blocks from the database block buffers to disk.
|
database writer (DBWR)
|
Doesn't always write to disk immediately. Writes at most efficient time.
|
|
This process is responsible for writing data from the log buffer to the redo log.
|
Log Writer (LGWR)
|
|
|
This is an event in which all modified database buffers are written to the datafiles by the DBWR
|
checkpoint
|
|
|
This is responsible for keeping track of database processes and cleaning up if a process prematurely dies. Also responsible for restarting any dispatcher processes that might have failed.
|
Process Monitor (PMON)
|
|
|
This does cleaning temporary segments and recovering transactions that have died because of a system crash.
also defragments the database by coalescing free extents within the database. |
System Monitor (SMON)
|
|