Oracle Database

Workshop 1

By Hari Krishna Makkini

 Workshop Objectives
• Describe Oracle Database (11g).
• Identify high-level architectural components
of an Oracle Database.
• Identify Oracle Database internal data
structures.
• Define the mechanisms used when
processing Insert/Update/Delete statements.
• Describe DBMS programs used with Oracle
Database.
 Relational Database Evolution

In 1970 Edgar Frank Codd, a data scientist

working for IBM published a paper under the
name "A Relational Model of Data for Large
Shared Data Banks".
IBM accepted this fascinating theory and
subsequently an interactive language
named SEQUEL under the database
SYSTEM R was developed in 1979 by them.
 Oracle Evolution
• This section explains the evolution of Oracle
from its initial entry as a relational database
and then out coming its competitors for the
past 3 decades as the world's most robust and
flexible relational database
• Oracle version 2 (1979) was very first
commercial release and they named it as
version -2 as they believed that any potential
customer will be more hesitant to buy the very
first version of any software. This version had
the complete implementation of SQL but
lacked reliability.
 Oracle Evolution
• Oracle version 11g (2007) introduced
some salient features like flashback data
archive, virtual column, parallel back up of
same files, case sensitive passwords and
wide range of performance and
optimization enhancements making it a
more stable release than ever before.
 Oracle Evolution
• Oracle version 12c (2013)
Oracle 18c is available on-premise, in
Oracle's public cloud and cloud at customer.
The data warehouse version of Oracle 18c
is available in December. The OLTP version
will be available in June 2018. Autonomous
will be available for data warehouse, OLTP,
Express and NoSQL in 2018
Compatible or Version
 Popular Features
•Automatic Shared Memory
Management (ASMM)
•Data Pump
•SQL Tuning Advisor
•Flashback Database
•RMAN - Backupset
Compression
 What is Oracle?
• Oracle is a relational database management system.
• It is a management system which uses the relational
data model.
• In the relational data model, data is seen by the users
in form of tables alone.
• Oracle Server:
• Is a database management system that provides an
open, comprehensive, integrated approach to
information management.
• Consists of an Oracle Instance and an Oracle
database
Most people call it a “Database”
Technically an Oracle Database is broken
into two high-level components

1. INSTANCE – Non-persistent, memory-

based processes and structures
2. DATABASE – Persistent, disk-based data
and control files
Oracle 11g Architecture
 So Why Differentiate?
Most Oracle installations consist of only a
single “Instance” and single “Database”…

Instance

Database
 Oracle RAC is Different
Oracle “Real Application Clusters” allow
multiple “Instances” to interact with a
single “Database” to provide high
availability…
Instance 1 Instance 2 Instance 3

Database
 “Instance”
An Oracle Instance…
– Is a means to access an Oracle Database
– Always opens one and only one Database
– Consists of memory and background process
structures
 Picture of an “Instance”
Instance
SGA
Shared Pool

Library Database Buffer Redo Log

Cache Cache Buffer
Memory
Data Structures
Dictionary Java Pool Large Pool
Cache

Back-
PMON SMON DBWR LGWR CKPT Others Ground
Processes
 “Database”
An Oracle Database…
– Is a collection of data that is treated as a unit
– Consists of three file types
 Picture of a “Database”

Oracle Database

Data Files Control Files Redo Log Files

Parameter Archived
File Log Files

Password
File
 Memory Structure
Oracle’s memory structure consists of two
memory areas known as:
1. System Global Area (SGA): Allocated at
instance start up, and is a fundamental
component of an Oracle Instance
2. Program Global Area (PGA): Allocated
when the server process is started
 System Global Area
• The SGA consists of several memory structures:
– Shared Pool
– Database Buffer Cache
– Redo Log Buffer
– Other structures
• There are two additional memory structures that
can be configured within the SGA:
– Large Pool
– Java Pool
 System Global Area
• The size of the SGA is determined by the
parameters that set the sizes of the
various pools; these parameters are
dynamic
• The SGA_MAX_SIZE parameter sets the
maximum size of the SGA (so you can
limit it) and is not a dynamic parameter

Thanks Ned!
 Picture of an “Instance”
Instance
SGA
Shared Pool

Library Database Buffer Redo Log

Cache Cache Buffer
Memory
Data Structures
Dictionary Java Pool Large Pool
Cache

Back-
PMON SMON DBWR LGWR CKPT Others Ground
Processes
 Shared Pool
• Used to store:
– Most recently executed SQL statements
– Most recently used data definitions
• It consists of two key performance-related
memory structures:
– Library Cache
– Data Dictionary Cache
• Sized by the parameter
SHARED_POOL_SIZE
 Library Cache
• Stores information about the most recently used
SQL and PL/SQL statements
• Enables the sharing of commonly used
statements
• Is managed by a least recently used (LRU)
algorithm
• Consists of two structures
– Shared SQL area
– Shared PL/SQL area
• Size is determined by the Shared Pool sizing
 Data Dictionary Cache
• A collection of the most recently used
definitions in the database
• Includes information about database files,
tables, indexes, columns, users,
privileges, and other database objects
• During the parse phase, the server
process looks at the data dictionary for
information to resolve object names and
validate access
 Database Buffer Cache
• Stores copies of data blocks that have
been retrieved from the data files
• Enables great performance gains when
you obtain and update data
• Managed through an LRU algorithm
• DB_BLOCK_SIZE determines primary
block size
 Redo Log Buffer
• Records all changes made to the
database data blocks
• Primary purpose is recovery
• Changes recorded within are called redo
entries
• Redo entries contain information to
reconstruct or redo changes
• Size defined by LOG_BUFFER
 Large Pool
• An optional area of memory in the SGA
• Relieves the burden place on the Shared Pool
• Used for:
– Session memory for the Shared Server
– I/O server processes
– Backup and restore operations for RMAN
• Does not use an LRU list
• Sized by LARGE_POOL_SIZE
• Can be dynamically resized
 Java Pool
• Services parsing requirements for Java
commands
• Required if installing and using Java
• Sized by JAVA_POOL_SIZE parameter
 Oracle “Process” Structure
• Oracle takes advantage of various types of
Processes:
– User Process: Started at the time a database
user requests connection to the Oracle Server
– Server Process: Connects to the Oracle
instance and is started when a user
establishes a session
– Background Processes: Started when an
Oracle instance is started
 User Process
• A program that requests interaction with the
Oracle server
• Must first establish a connection
• Does not interact directly with the Oracle server

User Server
Process Process
Connection
Established
 Server Process
• A program that directly interacts with the
Oracle server
• Fulfills calls generated and returns results
• Can be dedicated or shared server
 Picture of an “Instance”
Instance
SGA
Shared Pool

Library Database Buffer Redo Log

Cache Cache Buffer
Memory
Data Structures
Dictionary Java Pool Large Pool
Cache

Back-
PMON SMON DBWR LGWR CKPT Others Ground
Processes
 Background Processes
• Maintains and enforces relationships
between physical and memory structures
– Mandatory background processes:
DBWn PMON CKPT
LGWR SMON
– Optional background processes:
ARCn LMDn QMNn
CJQ0 LMON RECO
Dnnn LMS Snnn
LCKn Pnnn
 Database Writer (DBWn)
Instance

Shared DBWn writes when:

Shared Pool
Pool SGA
• Checkpoint occurs
Library Database Buffer Redo Log
Cache Cache Buffer • Dirty buffers reach
Data threshold
Dictionary Java Pool Large Pool • There are no free
Cache
buffers
• Timeout occurs
PMON SMON DBWR LGWR CKPT Others
• Tablespace OFFLINE
• Tablespace READ
ONLY
Oracle Database • Table DROP or
Data Files Control Files Redo Log Files TRUNCATE
• Tablespace BEGIN
BACKUP
 Log Writer (LGWR)
Instance

Shared Pool SGA

LGWR writes:
• At commit
Library Database Buffer Redo Log
Cache Cache Buffer • When one-third full
Data • When there is 1 MB of
Dictionary Java Pool Large Pool redo
Cache
• Every three seconds
PMON SMON DBWR LGWR CKPT Others
• Before DBWn writes

Oracle Database
Data Files Control Files Redo Log Files
 System Monitor (SMON)
Instance

Shared Responsibilities:
Shared Pool
Pool SGA
• Instance recovery
Library Database Buffer Redo Log
Cache Cache Buffer – Rolls forward
changes in online
Data
redo log files
Dictionary Java Pool Large Pool
Cache – Opens database for
user access
PMON SMON DBWR LGWR CKPT Others – Rolls back
uncommitted
transactions
• Coalesces free space
Oracle Database • Deallocates temporary
Data Files Control Files Redo Log Files segments
 Process Monitor (PMON)
Instance

Shared Cleans up after failed

SharedPool
Pool SGA
processes by:
Library Database Buffer Redo Log
Cache Cache Buffer • Rolling back the
Data
transaction
Dictionary Java Pool Large Pool • Releasing locks
Cache
• Releasing other
resources
PMON SMON DBWR LGWR CKPT Others
• Restarting dead
dispactchers

Oracle Database
Data Files Control Files Redo Log Files
 Checkpoint (CKPT)
Instance

Shared Responsible for:

SharedPool
Pool SGA
• Signaling DBWn at
Library Database Buffer Redo Log
Cache Cache Buffer checkpoints
Data • Updating datafile
Dictionary Java Pool Large Pool headers with
Cache checkpoint information
• Updating control files
PMON SMON DBWR LGWR CKPT Others with checkpoint
information

Oracle Database
Data Files Control Files Redo Log Files
 Archiver (ARCn)
• Optional background process
• Automatically archives online redo log files when
ARCHIVELOG mode is set
• Preserves the record of all changes made to the
database
Oracle Database
Data Files Control Files Redo Log Files Archived Logs
ARCn
 Oracle Data Storage
Oracle keeps all system and user data in
two basic storage containers:
1. Tablespace… a logical entity known
only to Oracle
2. Data Files… physical files that may
(typically) be seen from the operating
system
 Tablespaces
• Can belong to only one database at a time
• Consist of one or more data files
• Are further divided into logical units of
store
 Data Files
• Can belong to only one tablespace and
one database
• Are a repository for schema object data
Database

Tablespace

Data Data
File File
 2 Types of Tablespace
1. Tablespaces required by Oracle for
normal operations
2. Tablespaces that contain data and
indexes that support your applications
 Required Tablespaces
• System – Contains the Oracle Data
Dictionary
• Sysaux - New to 10g; supports historic
monitoring / tuning
• Temporary – Used for disk-based sorting
of data (select...from…order by)
• Undo – Used for transaction consistency
during Insert / Update / Delete statements
 SQL Statements (IUDS)
• Insert What happens when
• Update someone connects to
• Delete the database and
issues one of these
• Select statements?
Connect to Oracle – What Happens
User Server
Process Process
Connect User/Pwd

• Are “User” definition and privileges in SGA

“Dictionary Cache”?
– If not, try to fetch from the “System”
tablespace
– If there, validate Pwd and privileges to login
– Allow connection if all is right; otherwise
decline connection
“Select” – What Happens First?
Select *
From MyTab
Order by 1;

• Is this statement in the “Library Cache”?

– If statement cached then it has been recently
been “parsed” and “executed”
– If not cached then “parse” the statement
– If cached then skip parsing stage and execute
statement
 “Select” – Parsing the Statement
Select *
From MyTab
Order by 1;

• Does “MyTab” exist?

• Does user have Privs to select from
“MyTab”
• What columns are in “MyTab”
• What is the first column in “MyTab”
“Select” – Executing the Statement
Select *
From MyTab
Order by 1;

• Is “MyTab” data in the SGA “Buffer Cache”?

– If not, fetch data into Buffer Cache
• Sort data in “MyTab” by the first column
– If can sort records in memory then do so
– If cannot sort in memory then use “Temporary”
tablespace as disk-based staging area
• Return records to client process
 “I/U/D” – What Happens First?
Insert (a,b,c)
Into MyTab;

• Is this statement in the “Library Cache”?

– If statement cached then it has been recently
been “parsed” and “executed”
– If not cached then “parse” the statement
– If cached then skip parsing stage and execute
statement
 “I/U/D” – Executing the Statement
Insert (a,b,c)
Into MyTab;

• Validate values to be inserted

• Execute the statement
– Keep DB version of the record in “Undo”
tablespace until Commit or Rollback
– Record changes in SGA “Redo Log Buffer”
– Change records in SGA “Buffer Cache”
– DBWn writes changed records to data file(s)
as part of buffer cache management
 “I/U/D” – Executing the Statement
Insert (a,b,c)
Into MyTab;
Commit;
or
Rollback;

• If “Commit” then…
– LGWn writes “Redo Log Buffer” entries to
“Redo Logs”
– Undo entries are invalidated
• If “Rollback” then…
– Migrate DB version of record in Undo back to
tablespace/data file
 Archivelog Mode
• If Instance in “Archivelog” mode Redo Log
Files are “Archived” to Archive Logs; which
may be used to recover your database in
the case of disaster

Oracle Database
Data Files Control Files Redo Log Files Archived Logs
ARCn
Creating new Database
Managing and Organizing a
Database
• Creating a database is the first step in
managing a database system
• A database may have been created
automatically as part of Oracle9i
Server installation, or you can create
a new one later
• Oracle Data Migration Assistant is
used to migrate from an earlier
version of the database
 Creation Prerequisites
To create a new database, you must
have the following:
• A privileged account authenticated in
one of the following ways:
– By the operating system
– Using a password file
• Sufficient memory to start the
instance
• Sufficient disk space for the planned
database
 Planning Database File
Locations
• Keep at least two active copies of a
database control file on at least two
different devices.
• Multiplex the redo log files and put
group members on different disks.
• Separate data files whose data:
– Will participate in disk resource
contention across different physical disk
resources
– Have different life spans
– Have different administrative
 Creating a Database

An Oracle database can be created

using:
• Oracle Database Configuration
Assistant
• The CREATE DATABASE command
 Using the Database Configuration Assistant
The Database Configuration Assistant
allows you to:
• Create a database
• Configure database options
• Delete a database
• Manage templates
– Create new template using pre-defined
template settings
– Create new template from an existing
database
– Delete database template
Create a Database
 Database Information
Specify:
• Global database name and SID
• The features you want to use for your database,
such as:
– Oracle Spatial
– Oracle OLAP Services
– Example Schemas
• Mode in which you want the database to operate
– Dedicated server mode
– Shared server mode
 Typical or Custom Install
Choose between typical or custom
install
 Other Parameters
• Archive Parameters
– Use for database recovery
– May also be used for a standby
database
• Data Block Sizing
– Sets the default database block size
– Helps to determine the
SORT_AREA_SIZE
• File Locations
– Specify paths for trace files
– Specify paths for parameter files
• Database storage
Complete Database Creation

Complete database creation using the

following options:
• Create database
• Save as a database template
• Generate database creation scripts
 Creating a Database
Manually
• Decide on a unique instance and database name
• Choose a database character set
• Set the operating system variables
• Edit / Create the initialization parameter file
• Start the instance (nomount)
• Execute the CREATE DATABASE command
• Run scripts to generate the data dictionary and
accomplish post creation steps
Preparing the Parameter File

• Create the new initSID.ora

$ cp init.ora $ORACLE_HOME/dbs/initdb01.ora

• Modify the initSID.ora by editing

the parameters
 Creating SPFILE

Create the SPFILE from initSID.ora

CREATE SPFILE FROM PFILE;
 Starting the Instance

• Connect as SYSDBA
• Start the instance in NOMOUNT stage
STARTUP NOMOUNT
 Creating the Database
@crdbdb01.sql
SQL> create database db01
2 logfile
3 GROUP 1 ('/u01/oradata/db01/log_01_db01.rdo') SIZE 15M,
4 GROUP 2 ('/u01/oradata/db01/log_02_db01.rdo') SIZE 15M,
5 GROUP 3 ('/u01/oradata/db01/log_03_db01.rdo') SIZE 15M
6 datafile '/u01/oradata/db01/system_01_db01.dbf' SIZE 100M
7 undo tablespace UNDO
8 datafile '/u01/oradata/db01/undo_01_db01.dbf' SIZE 40M
9 default temporary tablespace TEMP
10 tempfile '/u01/oradata/db01/temp_01_db01.dbf' SIZE 20M
11 extent management local uniform size 128k
12 character set AL32UTF8
13 national character set AL16UTF16
14 set time_zone = 'America/New_York'
15 ;
 Creating a Database Using
OMF
• Define the OMF initialization
parameters in the
parameter file
– DB_CREATE_FILE_DEST
– DB_CREATE_ONLINE_DEST_n
STARTUP NOMOUNT
CREATE DATABASE
DEFAULT TEMPORARY TABLESPACE TEMP;
 Troubeshooting
Creation of the database fails if:
• There are syntax errors in the SQL
script
• Files that should be created already
exist
• Operating system errors such as file
or directory permission or insufficient
space errors occur
 After Database Creation
The database contains:
• Datafiles, control files, and redo log
files
• User SYS with the password
change_on_install
• User SYSTEM with the password
manager
• Internal tables (but no data dictionary
views)