Oracle Database Administration

Slides:



Advertisements
Similar presentations
Oracle Architecture. Instances and Databases (1/2)
Advertisements

IS 432: DATABASE ADMINISTRATION Lecture 4: Parameter Files. Information Systems Department 1.
ITEC474 Control File Maintenance
Page Footer Keed Education Oracle Database Administration Basic Copyright 2009 Keed Education BV Version Concept.
Harvard University Oracle Database Administration Session 2 System Level.
Managing an Oracle Instance
Advanced Databases Basic Database Administration Guide to Oracle 10g 1.
Oracle Database Instance Management Oracle 10g. Ebtisam Alabdulqader Outline Management Framework. Managing Oracle instance through the Enterprise Manager.
Database Backup and Recovery
RMAN Restore and Recovery
Backup and Recovery (2) Oracle 10g CAP364 1 Hebah ElGibreen.
Backup and Recovery Part 1.
Harvard University Oracle Database Administration Session 11 Database Recovery.
ITEC474 Redo Log Files.
Database Backup & Recovery David Konopnicki. Introduction A major responsibility of the database administrator is to prepare for the possibility of hardware,
CHAPTER 16 User-Managed Backup and Recovery. Introduction to User Managed Backup and Recovery Backup and recover is one of the most critical skills a.
CHAPTER 5 Managing Control Files, Online Redo Logs, and Archiving.
Oracle Architecture. Database instance When a database is started the current state of the database is given by the data files, a set of background (BG)
Oracle9i Database Administrator: Implementation and Administration
Backup Concepts. Introduction Backup and recovery procedures protect your database against data loss and reconstruct the data, should loss occur. The.
Introduction to Oracle Backup and Recovery
Using RMAN to Perform Recovery
CHAPTER 16 User-Managed Backup and Recovery. Introduction to User Managed Backup and Recovery Backup and recover is one of the most critical skills a.
20 Copyright © 2004, Oracle. All rights reserved. Database Recovery.
Oracle Database Administration Database files Logical database structures.
13 Copyright © Oracle Corporation, All rights reserved. RMAN Complete Recovery.
Database Administration TableSpace & Data File Management
CHAPTER 2 Implementing a Database. Introduction to Creating Databases After you’ve installed the Oracle software, the next logical step is to create a.
Chapter 7 Making Backups with RMAN. Objectives Explain backup sets and image copies RMAN Backup modes’ Types of files backed up Backup destinations Specifying.
11 Copyright © Oracle Corporation, All rights reserved. RMAN Backups.
11 Copyright © Oracle Corporation, All rights reserved. RMAN Backups.
16 Copyright © 2007, Oracle. All rights reserved. Performing Database Recovery.
CHAPTER 5 Managing Control Files and Online Redo Logs.
A Guide to Oracle9i1 Database Instance startup and shutdown.
15 Copyright © Oracle Corporation, All rights reserved. RMAN Incomplete Recovery.
IT Database Administration SECTION 01. Starting Up and Shutting Down the Database Database Administration Facilities – A number of tools are available.
Week 3 Lecture 1 The Redo Log Files and Diagnostic Files.
Introduction to Oracle. Oracle History 1979 Oracle Release client/server relational database 1989 Oracle Oracle 8 (object relational) 1999.
7 Copyright © 2005, Oracle. All rights reserved. Managing Undo Data.
IT Database Administration Section 09. Backup and Recovery Backup: The available options Full Consistent (cold) Backup Database shutdown, all files.
Database Storage Structures
Backup Concepts. Introduction Backup and recovery procedures protect your database against data loss and reconstruct the data, should loss occur. The.
Week 2 Lecture 1 Creating an Oracle Instance. Learning Objectives  Learn the steps for creating a database  Understand the prerequisites for creating.
Creating an Oracle Database. Considerations before creating a DB Planning for Database Creation –Select the standard database block size. –Use an undo.
10 Copyright © Oracle Corporation, All rights reserved. User-Managed Backups.
Chapter 1Oracle9i DBA II: Backup/Recovery and Network Administration 1 Chapter 1 Backup and Recovery Overview MSCD642 Backup and Recovery.
Overview of Oracle Backup and Recovery Darl Kuhn, Regis University.
12 Copyright © Oracle Corporation, All rights reserved. User-Managed Complete Recovery.
18 Copyright © 2004, Oracle. All rights reserved. Backup and Recovery Concepts.
6 Copyright © 2007, Oracle. All rights reserved. Performing User-Managed Backup and Recovery.
16 Copyright © 2005, Oracle. All rights reserved. Performing Database Recovery.
Oracle Architecture - Structure. Oracle Architecture - Structure The Oracle Server architecture 1. Structures are well-defined objects that store the.
8 Copyright © 2007, Oracle. All rights reserved. Using RMAN to Duplicate a Database.
18 Copyright © 2004, Oracle. All rights reserved. Recovery Concepts.
14 Copyright © 2007, Oracle. All rights reserved. Backup and Recovery Concepts.
4 Copyright © 2004, Oracle. All rights reserved. Managing the Oracle Instance.
8 Copyright © Oracle Corporation, All rights reserved. Managing Tablespaces and Data files.
Control File Information The database name The timestamp of database creation The names and locations of associated datafiles and redo log files Tablespace.
IS232 Lab 7. What Is a Control File? Every Oracle Database has a control file, which is a small binary file that records the physical structure of the.
 Database Administration Oracle Database Instance Management Starting Up and Shutting Down أ. ندى الغامدي, أ. ندى الطوالة.
3 Copyright © Oracle Corporation, All rights reserved. 管理数据库事例.
Initialization Parameters
Maintaining Online Redo Log Files
Is 221: Database Administration
Oracle9i Database Administrator: Implementation and Administration
Recovering from Noncritical Losses
Duplicating a Database
Performing Database Recovery
ISYS366, Oracle Disk Internals
Chapter 5 The Redo Log Files.
Presentation transcript:

Oracle Database Administration Database files

Database files Oracle Database uses the following types of files: Data files Control files Redo log file (or just: Log files) Archive log files Parameter files

Database startup process Database startup involves 3 steps: Instance startup PARAMETER FILE is read Parameter file contains location of control file(s) Mount database CONTROL FILE is opened Control File contains location of data files and log files Open database Data files and log files are opened

Data files Data files: all database data is stored there data files can automatically extend if required (the AUTOEXTEND clause) one or more datafile form a logical unit of database storage called a tablespace Oracle does not write modified data immediately, if the database is not closed properly, the datafiles can contain incorrect data

Data files Data files: all database data is stored there data files can automatically extend if required (the AUTOEXTEND clause) one or more datafile form a logical unit of database storage called a tablespace Oracle does not write modified data immediately, if the database is not closed properly, the datafiles can contain incorrect data

Control files Control file contains: Control file: database name, timestamp of database creation location of database datafiles and redo log files system change number (SCN), every transaction increases SCN Control file: is modified every time there is structural change to the database (e.g. new datafile, redo log file) is required for the database to operate can be multiplexed is used during database recovery

Redo log files Redo log files: must be at least two, usually three or more are written sequentially record every change to the database can be multiplexed redo log files are used by recovery operations: automatic recovery after instance failure (for example after SHUTDOWN ABORT), loss of a redo log file can prevent from opening the database manual recovery from backup, loss of a redo log file can make it impossible to perform complete recovery (and some transactions will be lost)

Archive log files Redo log files can be archived before they are overwritten, then they become archive log files Archive log files: are used by manual recovery only can be multiplexed

Parameter files Parameter file contains instance and database parameters, for example: instance name location of control files database block size amount of memory used by Oracle Parameters can be stored in: parameter file (regular text file) server parameter file (binary file)

Example parameter file imm.__db_cache_size=138412032 imm.__java_pool_size=4194304 imm.__large_pool_size=4194304 imm.__shared_pool_size=58720256 imm.__streams_pool_size=0 *.audit_file_dest='C:\oracle\admin\imm\adump' *.background_dump_dest='C:\oracle\admin\imm\bdump' *.compatible='10.2.0.1.0' *.control_files='C:\oracle\oradata\imm\control01.ctl','C:\oracle\oradata\im m\control02.ctl','C:\oracle\oradata\imm\control03.ctl' *.core_dump_dest='C:\oracle\admin\imm\cdump' *.db_block_size=8192 *.db_domain='' *.db_file_multiblock_read_count=16 *.db_name='imm' *.db_recovery_file_dest='C:\oracle\flash_recovery_area' *.db_recovery_file_dest_size=2147483648 *.job_queue_processes=10 *.nls_language='AMERICAN' *.nls_territory='POLAND' *.open_cursors=300 *.pga_aggregate_target=69206016 *.processes=150 *.remote_login_passwordfile='EXCLUSIVE'

Parameter files Oracle can use PFILE or SPFILE SPFILE can be modified by Oracle commands, PFILE must be modified manually When using SPFILE: some parameters can be changed while the database is running Oracle can adjust some parameters automatically at runtime (e.g. memory distribution)

Using parameter files Normally Oracle uses PFILE or SPFILE from default locations It is possible to override default locations: STARTUP PFILE=‘path_to_pfile.ora’ STARTUP SPFILE=‘path_to_spfile.ora’ It is possible to create PFILE from SPFILE and SPFILE from PFILE: CREATE SPFILE FROM PFILE CREATE PFILE FROM SPFILE CREATE PFILE=‘path_to_pfile.ora’ FROM SPFILE

Adjusting database parameters When using PFILE – modify the text file and restart the database When using SPFILE: alter system set db_cache_size = 30000000 scope=memory; alter system set db_cache_size = 30000000 scope=spfile Scope parameter can be: memory – change the parameter immediately, do not write to spfile spfile – write to spfile, do not change until restart both – change immediately and write to spfile