Oracle System Architecture Interview Preparation Guide

Download PDF

Dedicated Server Configuration and Multi-threaded Server Configuration.

The Oracle call interface (OCI) The Oracle call interface is the lowest level at which client programs are intended to interact with Oracle. This interface is well documented and provides access to most of the functionality of Oracle, including advanced features such as object navigation, and sophisticated transaction and session control. Applications with advanced requirements have to use OCI directly, in order to access the features that are not available in Oracle's other development tools. The user program interface (UPI) OCI is based on the user program interface. There are some UPI facilities that are not yet available via OCI, and so some of the Oracle tools actually call this interface directly. Precompiler programs also call the user program interface, but indirectly via the SQLLIB library, which is an undocumented alternative to OCI. The Oracle program interface (OPI) The user program interface is the lowest layer of the client-side call stack, and the Oracle program interface is the highest layer of the server-side call stack. In most configurations, Net8 bridges the gap between UPI and OPI. However, in single-task executables there is no gap, and the UPI calls correspond directly to OPI calls. The compilation layer (KK) This is the top layer of the Oracle kernel proper. This layer is responsible for the parsing and optimization of SQL statements and for the compilation of PL/SQL program units. The execution layer (KX) This layer handles the binding and execution of SQL statements and PL/SQL program units. It is also responsible for the execution of recursive calls for trigger execution, and for the execution of SQL statements within PL/SQL program units. The distributed execution layer (K2) The distributed execution layer establishes the transaction branches for distributed transactions, and handles the management of the two-phase commit protocol. The network program interface (NPI) When remote objects are referenced in a SQL statement, the network program interface sends the decomposed statement components to the remote database instances and receives the data in return. The security layer (KZ) This layer is called by the compilation and execution layers to validate the required object and system privileges. The query layer (KQ) This layer provides rows to the higher layers. In particular, the query layer is responsible for caching rows from the data dictionary, for use by the security and compilation layers. The recursive program interface (RPI) The recursive program interface is used to populate the dictionary cache from the data dictionary. Row cache recursive SQL statements are executed in a separate call context, but are not parsed and optimized in the compilation layer. The access layer (KA) The access layer is responsible for access to database segments. This is the first layer of the lower half of the kernel. The data layer (KD) This layer is responsible for the management and interpretation of data within the blocks of database segments such as tables, clusters, and indexes. The transaction layer (KT) This layer is responsible for the allocation of transactions to rollback segments, interested transaction list changes within data blocks, changes to rollback segment blocks for undo generation, transaction control facilities such as savepoints, and read consistency. The transaction layer is also responsible for space management, both at the level of segment free lists and at the level of tablespace extent allocation. The cache layer (KC) The cache layer manages the database buffer cache. It uses operating system dependent facilities for data file I/O, provides concurrency control facilities for local access to the cache buffers, and provides parallel cache management (PCM) instance locking facilities for Oracle parallel server. The other main responsibility of the cache layer is the control of redo generation into the log buffer, and the writing of redo to the log files. The cache layer also caches control file information. The services layer (KS) The services layer provides low-level services that are used by all the higher layers, such as error handling, debugging, and tracing facilities, as well as parameter control and memory services. In particular, the service layer is responsible for generic concurrency control facilities such as latches, event waits, enqueue locks, and instance locks. This layer is also responsible for the management of the data structures for background and user processes and sessions, as well as state objects, inter-process messages, and system statistics. The lock management layer (KJ) This layer is responsible for the locking used for synchronization and communication between the instances of a parallel server database. The generic layer (KG) The generic layer provides management for the generic data structures that are used by the higher layers, such as linked lists. Of particular interest are the library cache and the memory allocation heaps used for the shared pool and session memory. The operating system dependencies (S) Oracle uses operating system facilities for I/O, process scheduling, memory management, and other operations. The implementation details are operating system dependent, and so these details are isolated into a separate layer.

Mandatory Processes DBWR -
Database Writer.LGWR -
Log WriterCKPT -
Check PointSMON -
System MonitorPMON -
Process Monitor Optional Process ARCH -
ArchiverRECO -
RecoverDnnn -
Dispatcher, andLCKn -
LockSnnn -
Server.

Server Process handle requests from connected user process. A server process is in charge of communicating with the user process and interacting with ORACLE carry out requests of the associated user process.

A user process is created and maintained to execute the software code of an application program. It is a shadow process created automatically to facilitate communication between the user and the server process.

In a Dedicated Server Configuration a Server Process handles requests for a Single User Process.

A configuration for loosely coupled systems where multiple instance share a single physical database is called Parallel Server.

In a Multi-threaded Server Configuration many user processes share a group of server process.

Database writer writes modified blocks from the database buffer cache to the data files.

Though a single LCK process is sufficient for most Parallel Server systemsupto Ten Locks (LCK0,....LCK9) are used for inter-instance locking.

Archiver (ARCH) copies the on-line redo log files to archival storage when they are full. ARCH is active only when a database's redo log is used in ARCHIVELOG mode.

Process Monitor (PMON) performs process recovery when a user process fails PMON is responsible for cleaning up the cache and Freeing resources that the process was using PMON also checks on dispatcher and server processes and restarts them if they have failed.

Dispatcher (Dnnn) process is responsible for routing requests from connected user processes to available shared server processes and returning the responses back to the appropriate user processes.

RECOver (RECO) is used to resolve distributed transactions that are pending due to a network or system failure in a distributed database. At timed intervals,the local RECO attempts to connect to remote databases and automatically complete the commit or rollback of the local portion of any pending distributed transactions.

Lock (LCKn) are used for inter-instance locking when the ORACLE Parallel Server option is used.

Atleast one Dispatcher process is created for every communication protocol in use.

That is Acl . Those levels are

Manager,
designer,
editor,
author,
reader,
depositor,
no access

Program Global Area. The PGA is a memory region containing data and control information for a single process (server or background). One PGA is allocated for each server process; the PGA is exclusive to that server process and is read and written only by Oracle code acting on behalf of that process. A PGA is allocated by Oracle when a user connects to an Oracle database and a session is created

Database buffer contains the data which server process reads recently from disk. Database buffer may have three parts: 1. free buffer 2. dirty buffer 3. pinned buffer Free buffer area is free to be used to store data. Dirty buffer area contains the data which is updated since read from disk, but not written to the disk till now. Pinned buffer is a area where processing on specific data for current transaction is going on. Database buffer may be of three types: 1. keep 2. recycle 3. default Database buffer may be divided into five different block size buffers: 2k,4k,8k,16k,32k and 64k also but supported by most of the servers (HP, IBM AIX, SOLARIS 10)

sga stands fro system global area.. which is the part of the oracle instance(includes memory struture and background processes). for faster executon and better performance everthing comes in the sga.so sga is located in oracle instance,,, which itself consist of two parts.
1>database buffercache: which stores the recently executed database blocks,, when user fires a query oracle searches that block in dictionary and stores it into buffer cache.. so if the next time when the user fires the same query ... users gets output from the buffer cache itself.. no need for parsing again.. only fetch and execute will work.
2> redolog buffer: it stores all the changes made in the database,, and also all DMLs,, when user fires an commit statement,, lgwr back process writes it into the redolog files.. which can be used for recovery of database during instance crash .when u install an oracle in ur machine ,,, system will become slow because of the unstructured sga configuration and also ur system configuration , once the oracle instance instants starts .. oracle itself will allocate the space from system .for example : if u have system confi 512 mb and if will install oracle with specified sga congi. obviously system performance will go low.so in order to increase the system performance,,, use the system configu should be well enough to run the oracle instance.... and also allocates enough space for sga....

Oracle introduced the Unbreakable Enterprise Kernel for Oracle Linux during Sep 2010 which runs directly on Oracle LINUX 5 with fast, modern, reliable kernel that is optimized for Oracle software and hardware.

Components of SGA are :
1> Shared pool : consists of shared sql area and shared pl/sql area
2> Data Base buffer cache(DB cache) : contains most recently used blocks & dirty blocks(modified but not yet written to datafile)
3> Redolog Buffer : contains changed/redo data
4> Large pool : used only in parellel sever environment
5> Java pool : used when you are using java strored procedures etc.

The deployment of a single database across a cluster of servers—providing unbeatable fault tolerance, performance and scalability

Please share your answers.

System Monitor (SMON) performs instance recovery at instance start-up. In a multiple instance system (one that uses the Parallel Server), SMON of one instance can also perform instance recovery for other instance that have failed SMON also cleans up temporary segments that are no longer in use and recovers dead transactions skipped during crash and instance recovery because of file-read or off-line errors. These transactions are eventually recovered by SMON when the tablespace or file is brought back on-line SMON also coalesces free extents within the database to make free space contiguous and easier to allocate.