Internal memory structure DBMS

Table spaces and Types of table spaces

A tablespace is a box for messages (tables, spiders, etc). A collection involves one or more tablespaces, each created up of one or more information. Furniture and spiders are designed within a particular tablespace.
Oracle has a control of 64,000 information per collection.
Default tablespaces
When a new collection is designed, it will have the following tablespaces (as designed by the Database Settings Assistant):
SYSTEM (the information dictionary)
SYSAUX (optional collection components)
TEMP (temporary tablespace, see tablespace kinds below)
UNDOTBS1 (undo tablespace, see tablespace kinds below)
USERS (default people tablespace created)
Tablespace creation
To create tablespace in CREATE TABLESPACE statement uses this syntax:-
CREATE TABLESPACE <tblspc_name>;
Tablespace types
Permanent tablespaces

Lasting tablespaces are used to store person data and person designed physical objects like furniture, spiders and materialized opinions. Example creates statements:
CREATE TABLESPACE tools DATAFILE '/u01/oradata/orcl/tools/file_1.dbf' SIZE 100M;
Temp tablespaces

Short-term or temporary tablespaces are used to retail store information with short life (transient data), for example: international quickly furniture or form results.
CREATE TEMPORARY TABLESPACE temp TEMPFILE '/u01/oradata/orcl/temp/file_1.dbf' SIZE 100M;
Undo tablespaces
Fix tablespaces are used to retail shop "before image" information that can be used to undo transactions
CREATE UNDO TABLESPACE undots DATAFILE '/u01/oradata/orcl/undo/file_1.dbf' SIZE 20M;

 
Internal memory structure

Oracle uses storage to retail shop details such as the following:
Program code
Information about an attached procedure, even if it is not currently active
Information wanted during application performance (for example, the present condition of a problem from which series are being fetched)
Information that is discussed and proclaimed among Oracle methods (for example, lock information)
Cached information that is also forever saved on side-line storage (for example, information hinders and update log entries)
The primary storage components associated with Oracle include:
System International Region (SGA), which is discussed by all web server and historical past methods.
Program International Places (PGA), which is personal to each web server and historical past process; there is one PGA for each procedure.

Overview of the System Global Area
A program international region (SGA) is a number of discussed storage components that contain details and control details for one Oracle collection example. If many people are as well attached to the same example, then the details in the instance's SGA is discussed among the people. Consequently, the SGA is sometimes called the discussed international region.
An SGA and Oracle methods comprise an Oracle example. Oracle immediately allocates storage for an SGA when you start an example, and the os reclaims the storage when you turn down the example. Each example has its own SGA.
The SGA is read/write. All people attached to a multiple-process collection example can go through details included within the instance's SGA, and several methods produce to the SGA during performance of Oracle.
The SGA contains the following details structures:
Database stream cache
Redo log buffer
Shared pool
Java pool
Large damages (optional)
Streams pool
Data book cache
Other varied information

Background processes
Oracle as a large software, but in fact, Oracle is a selection of many applications known as “background processes”, with each application given to a particular job.  The Oracle selection can have a lot of methods managing based on how you have designed your selection. There are two different types of historical past methods associated with Oracle, required methods and suggested methods.
Oracle Database Required Processes
SMON
System Monitor process rejuvenates after example disaster and screens short-term messages and extents. SMON in a non-failed example can also perform bad example restoration for other bad RAC example.
PMON
Procedure Check process rejuvenates bad process sources. If MTS (also known as Discussed Web server Architecture) is being used, PMON screens and restarts any bad dispatcher or server methods. In RAC, PMON’s position as support signing up representative is particularly important.
DBWR
Collection Creator or Filthy Stream Creator process is liable for creating dirty buffers from the database prevent storage cache to the database information. Usually, DBWR only creates hinders back to the information on make, or when the storage cache is full and space has to be made for more hinders. The possible many DBWR methods in RAC must be matched through the lock and international storage cache methods to guarantee effective control is attained.
LGWR
Log Creator procedure is liable for creating the log buffers out to the update records. In RAC, each RAC example has its own LGWR procedure that keeps that instance’s place of update records.
ARCH
The suggested Database procedure creates chock-full update records to the archive log location(s). In RAC, the various ARCH methods can be used to guarantee that reports of the aged update records for each example are available to the other cases in the RAC create should they be wanted for restoration.

·  Characteristics of the database
·  Database Systems Concepts and Architecture
·  Data Models and Data Modeling Concepts
·  Database Schema and Instances
·  DBMS architecture and data independence
·  Database Languages and Database Interfaces
·  Specifying constraints and indexes in SQL
·  View and queries in SQL
·  Relational algebra and Relational model concepts
·  SQL A relational database language
·  Hierarchical, Network & Relational Database Management Systems
·  Oracle Architecture
·  Logical Data Structures Physical Data Dtructure
·  User Defined Functions and Stored Procedures
·  Defining Cursors
·  Overview of PL SQL Error Handling
·  Declare Triggers
·  Roles and Privileges
·  Relational Database Design
·  Database Normalization
·  Distributed Database Management Systems
·  Concepts of object oriented database management systems
·  Locking Techniques
·  Time Stamp Ordering
·  Recovery Techniques
·  Database Transaction and the ACID Rules