Scribd
Upload
353 views

Oracle Slide

This document provides an overview of Oracle database architecture and the process for creating an Oracle database. It describes the key components of an Oracle instance, including the buffer cache, shared pool, redo log buffer, and background processes. It also explains how to create a database using the Oracle Flexible Architecture method, including setting initialization parameters, creating datafiles and redo log files, and running scripts to build the data dictionary. The document concludes with a brief description of system and non-system tablespaces.

Uploaded by

shyam rana
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
353 views

Oracle Slide

This document provides an overview of Oracle database architecture and the process for creating an Oracle database. It describes the key components of an Oracle instance, including the buffer cache, shared pool, redo log buffer, and background processes. It also explains how to create a database using the Oracle Flexible Architecture method, including setting initialization parameters, creating datafiles and redo log files, and running scripts to build the data dictionary. The document concludes with a brief description of system and non-system tablespaces.

Uploaded by

shyam rana
Copyright
© Attribution Non-Commercial (BY-NC)
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 30

SHYAM SINGH

Roll no 1807362
Computer science 3RD year
Haryana Engg college
Contents

 Oracle architecture
 Creating database
ORACLE ARCHITECTURE

 INSTANCE
 DATABASE
INSTANCE

 BUFFER CACHE
 SHARED POOL
LIBRARY CACHE
DATA DICTIONARY CACHE
 REDO LOG BUFFER
 JAVA POOL
 LARGE POOL
SHARED POOL
 LIBRARY CACHE
SHARED SQL AREA
SHARED PL\SQL AREA
 DATA DICTIONARY CACHE
DATABASE BUFFER CACHE

 DIRTY BUFFER
REDO LOG BUFFER

 REDO ENTRY

 IN CASE OF INSTANCE FAILURE


IT IS USED FOR RECOVERY
PURPOSES
DATABASE

 TABLE SPACE
 CONTRO FILES
 ONLINE REDO FILES
CONTROL FILE
 Defines current state of physical
database
 Maintains integrity of database
 Required:
– At MOUNT state during
database start up
– To operate the database
 Linked to a single database
 Loss may require recovery
TABLE SPACE

 A table space is a logical database


structure
 That is designed to store other
logical database structures
 Oracle sees a table space as large
area of space into which Oracle can
place new objects.
ONLINE REDO LOG FILE
 Record all changes made to data
 Provide a recovery mechanism
 Can be organized into groups
 At least two groups required
 Online redo log files provide the
means to redo transaction in the
event of database failure
BACKGROUND PROCESS

 PMON
 SMON
 CKPT
 LGWR
 DBWR
PMON (Process Monitor)

Cleans up after failed processes by:


 Rolling back the transaction
 Releasing locks
 Releasing other resources
SMON
 Automatically recovers the instance:
– Rolls forward changes in the redo logs
– Opens the database for user access
– Rolls back uncommitted transactions
 Coalesces free space

Deallocates temporary segments
LOG WRITER

• There is a COMMIT
• The redo buffer log
is one-third full
• There is more than
1 MB of redo
CKPT

→ Updating datafiles headers with


checkpoint information
→ Updatting controlfile with
checkpoint information
Database Writer (DBW0)

DBW0 writes when:


 There are many dirty buffers
 There are few free buffers
 Timeout occurs
 Checkpoint occurs
CREATE DATABASE

THREE METHODS TO CREATE THE DATABASE


 OFA (ORACLE FLEXIBLE ARCHITECTURE)
 ORACLE CONFIGURATION ARCHITECTURE
 OMF (ORACLE MANAGE FILE)
OFA
 MAKE A FOLDER IN ADMIN , USALLY NAMED THE NAME OF YOUR
DATABASE
 MAKE FIVE FOLDER IN THAT FOLDER NAMED AS :
1. PFILE
2. CREATE
3. UDUMP
4. CDUMP
5. BDUMP
PFILE

 IN PFILE WE MAKE INIT.ORA FILE


INIT.ORA
 IT CONTAIN THE VALUE OF THE PARAMETERS
db_name=first
instance_name=frist
db_block_size=4096
shared_pool_size=30000
log_buffer=20000
background_dump_dest='E:\oracle\admin\frist\bdump'
core_dump_dest='E:\oracle\admin\frist\cdump'
user_dump_dest='E:\oracle\admin\frist\udump'
undo_management=auto
undo_tablespace=undotbs
compatible=9.2.0.0.0
remote_login_passwordfile=exclusive
control_files='E:\oracle\oradata\frist\control01.ctl'
CREATE

 IN
CREATE FOLDER WE MAKE A TEXT
DOCUMENT NAMED AS CREATE.SQL
CREATE.SQL
 IT CONTAIN THE SCRIPT AS FOLLOW:-
create database frist
Datafile 'E:\oracle\oradata\frist\system01.dbf' size 40m
logfile group1("E:\oracle\oradata\frist\redo01a.log","E:\oracle\oradata\frist\redo01b.log") size
20m group2("E:\oracle\oradata\frist\redo02a.log","E:\oracle\oradata\amrit1\redo02b.log")
size 20m
undo tablespace undotbs
datafile 'E:\oracle\oradata\frist\undo01.dbf' size 100m
default temprary tablespace temp
tempfile 'E:\oracle\oradata\frist\tempfile01.dbf' size10m
max logfiles 5
maxlogmembers 5
maxinstances 1
maxdatafiles 50
maxloghistory 1
CREATE SERVICE
 Create a service to make database
compatible with the operating
system
 oradim –new –sid first –intpwd sys
 Initpwd create a password file in
ora92
LOGIN
 LOGIN AS
 USER NAME:SYS
 PASSWORD:SYS
STARTING INSTANCE
 WRITE THE STATEMENT
STARTUP PFILE ‘PFILE PATH’ NOMOUNT
THEN YOU WILL CONNECT TO A
IDIAL INSTANCE
 THE INFORMATON ABOUT THE
PARAMETER IS THEN SHOWN
Creating database
 Run the script create.sql which is stored in the create folder
 Run two another script
catalog.sql and catproc.sql are to make the data dictionary and making
database compatible with the sql and pl\sql
TABLE SPACE

 Table space are of two


types
1. System table space 2 Non system tablespace
-> Created with the database -> Separate undo, temporary,
-> Required in all database application data and application
index segments
-> Contains the data dictionary
-> Enable more flexibility in database
-> Should not contain user data,
administration
although
it is allowed -> Separate data by backup
requirements
-> Separate dynamic and static data
-> Control amount of space allocated to
a user
THANKS
ANY
OUERY….?

You might also like