OCA/OCP Oracle Database 11g All-in-One Exam Guide- P5 ppsx

OCA/OCP Oracle Database 11g All-in-One Exam Guide
xxxiv
ID Name Chapter
052.3 Creating an Oracle Database
052.3.1 Create a database by using the Database Configuration Assistant (DBCA) 2
052.4 Managing the Oracle Instance
052.4.1 Setting database initialization parameters 3
052.4.2 Describe the stages of database startup and shutdown 3
052.4.3 Using alert log and trace files 3
052.4.4 Using data dictionary and dynamic performance views 3
052.5 Configuring the Oracle Network Environment
052.5.1 Configure and manage the Oracle network 4
052.5.2 Using the Oracle Shared Server architecture 4
052.6 Managing Database Storage Structures
052.6.1 Overview of tablespace and datafiles 5
052.6.2 Create and manage tablespaces 5
052.6.3 Space management in tablespaces 5
052.7 Administering User Security
052.7.1 Create and manage database user accounts 6
052.7.2 Grant and revoke privileges 6
052.7.3 Create and manage roles 6
052.7.4 Create and manage profiles 6
052.8 Managing Schema Objects
052.8.1 Create and modify tables 7
052.8.2 Manage constraints 7
052.8.3 Create indexes 7
052.8.4 Create and use temporary tables 7
052.9 Managing Data and Concurrency
052.9.1 Manage data using DML 8
052.9.2 Identify and administer PL/SQL objects 8
052.9.3 Monitor and resolve locking conflicts 8

052.10 Managing Undo Data
052.10.1 Overview of undo 8
052.10.2 Transactions and undo data 8
052.10.3 Managing undo 8
052.11 Implementing Oracle Database Security
052.11.1 Database security and the principle of least privilege 6
ID Name Chapter
052.11.2 Work with standard database auditing 6
052.12 Database Maintenance
052.12.1 Use and manage optimizer statistics 24
052.12.2 Use and manage Automatic Workload Repository (AWR) 24
052.12.3 Use advisory framework 24
052.12.4 Manage alerts and thresholds 24
052.13 Performance Management
052.13.1 Use Automatic Memory Management 25
052.13.2 Use Memory Advisors 25
052.13.3 Troubleshoot invalid and unusable objects 25
052.14 Backup and Recovery Concepts
052.14.1 Identify the types of failure that can occur in an Oracle database 14
052.14.2 Describe ways to tune instance recovery 14
052.14.3 Identify the importance of checkpoints, redo log files, and archived log files 14
052.14.4 Overview of flash recovery area 14
052.14.5 Configure ARCHIVELOG mode 14
052.15 Performing Database Backups
052.15.1 Create consistent database backups 15
052.15.2 Back up your database without shutting it down 15
052.15.3 Create incremental backups 15
052.15.4 Automate database backups 15
052.15.5 Manage backups, view backup reports, and monitor the flash recovery area 15
052.16 Performing Database Recovery

052.16.1 Overview of Data Recovery Advisor 16
052.16.2 Use Data Recovery Advisor to perform recovery (control file, redo log
file and data file)
16
052.17 Moving Data
052.17.1 Describe and use methods to move data (directory objects,
SQL*Loader, external tables)
23
052.17.2 Explain the general architecture of Oracle Data Pump 23
052.17.3 Use Data Pump Export and Import to move data between Oracle
databases
23
052.18 Intelligent Infrastructure Enhancements
052.18.1 Use the Enterprise Manager Support Workbench 27
052.18.2 Managing patches 27
Introduction
xxxv
OCA/OCP Oracle Database 11g All-in-One Exam Guide
xxxvi
Examination 1Z0-053, Oracle Database 11g:
Administration II, Objectives
ID Name Chapter
053 Oracle Database 11g: Administration Workshop II
053.1 Database Architecture and ASM
053.1.1 Describe Automatic Storage Management (ASM) 20
053.1.2 Set up initialization parameter files for ASM and database instances 20
053.1.3 Start up and shut down ASM instances 20
053.1.4 Administer ASM disk groups 20
053.2 Configuring for Recoverability
053.2.1 Configure multiple archive log file destinations to increase availability 14

053.2.2 Define, apply, and use a retention policy 17
053.2.3 Configure the Flash Recovery Area 14
053.2.4 Use Flash Recovery Area 14
053.3 Using the RMAN Recovery Catalog
053.3.1 Identify situations that require RMAN recovery catalog 17
053.3.2 Create and configure a recovery catalog 17
053.3.3 Synchronize the recovery catalog 17
053.3.4 Create and use RMAN stored scripts 17
053.3.5 Back up the recovery catalog 17
053.3.6 Create and use a virtual private catalog 17
053.4 Configuring Backup Specifications
053.4.1 Configure backup settings 15
053.4.2 Allocate channels to use in backing up 15
053.4.3 Configure backup optimization 15
053.5 Using RMAN to Create Backups
053.5.1 Create image file backups 15
053.5.2 Create a whole database backup 15
053.5.3 Enable fast incremental backup 15
053.5.4 Create duplex backup and back up backup sets 15
053.5.5 Create an archival backup for long-term retention 15
053.5.6 Create a multisection, compressed, and encrypted backup 15
053.5.7 Report on and maintain backups 15
053.6 Performing User-Managed Backup and Recovery
053.6.1 Recover from a lost TEMP file 18
053.6.2 Recover from a lost redo log group 18
053.6.3 Recover from the loss of password file 18
ID Name Chapter
053.6.4 Perform user-managed complete database recovery 18
053.6.5 Perform user-managed incomplete database recovery 18
053.6.6 Perform user-managed and server-managed backups 18

053.6.7 Identify the need of backup mode 18
053.6.8 Back up and recover a control file 18
053.7 Using RMAN to Perform Recovery
053.7.1 Perform complete recovery from a critical or noncritical data file loss
using RMAN
16
053.7.2 Perform incomplete recovery using RMAN 16
053.7.3 Recover using incrementally updated backups 16
053.7.4 Switch to image copies for fast recovery 16
053.7.5 Restore a database onto a new host 17
053.7.6 Recover using a backup control file 16
053.7.7 Perform disaster recovery 17
053.8 Using RMAN to Duplicate a Database
053.8.1 Creating a duplicate database 17
053.8.2 Using a duplicate database 17
053.9 Performing Tablespace Point-in-Time Recovery
053.9.1 Identify the situations that require TSPITR 17
053.9.2 Perform automated TSPITR 17
053.10 Monitoring and Tuning RMAN
053.10.1 Monitoring RMAN sessions and jobs 17
053.10.2 Tuning RMAN 17
053.10.3 Configure RMAN for asynchronous I/O 17
053.11 Using Flashback Technology
053.11.1 Restore dropped tables from the recycle bin 19
053.11.2 Perform Flashback Query 19
053.11.3 Use Flashback Transaction 19
053.12 Additional Flashback Operations
053.12.1 Perform Flashback Table operations 19
053.12.2 Configure, monitor Flashback Database, and perform Flashback
Database operations

19
053.12.3 Set up and use a Flashback Data Archive 19
053.13 Diagnosing the Database
053.13.1 Set up Automatic Diagnostic Repository 27
053.13.2 Using Support Workbench 27
053.13.3 Perform Block Media Recovery 16
Introduction
xxxvii
OCA/OCP Oracle Database 11g All-in-One Exam Guide
xxxviii
ID Name Chapter
053.14 Managing Memory
053.14.1 Implement Automatic Memory Management 25
053.14.2 Manually configure SGA parameters 25
053.14.3 Configure automatic PGA memory management 25
053.15 Managing Database Performance
053.15.1 Use the SQL Tuning Advisor 25
053.15.2 Use the SQL Access Advisor to tune a workload 25
053.15.3 Understand Database Replay 25
053.16 Space Management
053.16.1 Manage resumable space allocation 23
053.16.2 Describe the concepts of transportable tablespaces and databases 23
053.16.3 Reclaim wasted space from tables and indexes by using the segment
shrink functionality
23
053.17 Managing Resources
053.17.1 Understand the database resource manager 21
053.17.2 Create and use database resource manager components 21
053.18 Automating Tasks with the Scheduler 22
053.18.1 Create a job, program, and schedule 22

053.18.2 Use a time-based or event-based schedule for executing Scheduler jobs 22
053.18.3 Create lightweight jobs 22
053.18.4 Use job chains to perform a series of related tasks 22
053.19 Administering the Scheduler
053.19.1 Create windows and job classes 22
053.19.2 Use advanced Scheduler concepts to prioritize jobs 22
053.20 Globalization
053.20.1 Customize language-dependent behavior for the database and
individual sessions
26
053.20.2 Working with database and NLS character sets 26
PART I
Oracle Database 11g
Administration
■ Chapter 1 Architectural Overview of Oracle Database 11g
■ Chapter 2 Installing and Creating a Database
■ Chapter 3 Instance Management
■ Chapter 4 Oracle Networking
■ Chapter 5 Oracle Storage
■ Chapter 6 Oracle Security
This page intentionally left blank
CHAPTER 1
Architectural Overview of
Oracle Database 11g
Exam Objectives
In this chapter you will learn to
• 052.1.1 Explain the Memory Structures
• 052.1.2 Describe the Process Structures
• 052.1.3 Identify the Storage Structures
3

OCA/OCP Oracle Database 11g All-in-One Exam Guide
4
This guide is logically structured to enable a thorough understanding of the Oracle
server product and the fundamentals of SQL (Structure Query Language, pronounced
sequel). The authors seek to relate your learning as much to the real world as possible
to concretize some of the abstract concepts to follow, by introducing a hypothetical
scenario that will be systematically expanded as you progress through the book. This
approach involves nominating you as the DBA in charge of setting up an online store.
You will appreciate the various roles a DBA is expected to fulfill as well as some of the
technology areas with which a DBA is expected to be familiar.
The nonexaminable discussion of the Oracle product stack is followed by considering
several prerequisites for fully understanding the tasks involved in setting up an Oracle 11g
database system. This discussion leads into the examinable objectives in this chapter,
which are the Single-Instance Architecture and the Memory, Process, and Storage
Structures.
Oracle Product Stack
No Oracle guide is complete without contextualizing the product under study. This
section discusses the three core product families currently available from Oracle
Corporation. End users of Oracle technology typically use a subset of the available
products that have been clustered into either the server, development tools, or
applications product families.
Oracle Server Family
The three primary groupings of products within the server technology family consist of
the database, application server, and enterprise manager suites. These form the basic
components for Oracle’s vision of grid computing. The concept underlying the Grid is
virtualization. End users request a service (typically from a web-based application), but
they neither know nor need to know the source of that service. Simplistically, the
database server is accessible to store data, the application server hosts the infrastructure
for the service being requested by the end user, and the enterprise manager product
provides administrators with the management interface. The platforms or physical

servers involved in supplying the service are transparent to the end user. Virtualization
allows resources to be optimally used, by provisioning servers to the areas of greatest
requirement in a manner transparent to the end user.
Database Server
The database server comprises Oracle instances and databases with many features like
Streams, Partitioning, Warehousing, Replication, and Real Application Clusters (RAC),
but ultimately it provides a reliable, mature, robust, high-performance enterprise-
quality data store, built on an object-relational database system. Historically, one of
the projects undertaken in the late 1970s to animate the relational theory proposed
by Dr. E.F. Codd resulted in the creation of a relational database management system
(RDBMS) that later became known as the Oracle Server. The Oracle Server product
is well established in the worldwide database market, and the product is central to
Chapter 1: Architectural Overview of Oracle Database 11g
5
PART I
Oracle Corporation’s continued growth, providing the backbone for many of its other
products and offerings. This book is dedicated to describing the essential features of
the Oracle Server and the primary mechanisms used to interact with it. It covers the
aspects that are measured in the certification exams, but by no means explores the
plethora of features available in the product.
An Oracle database is a set of files on disk. It exists until these files are deleted.
There are no practical limits to the size and number of these files, and therefore no
practical limits to the size of a database. Access to the database is through the Oracle
instance. The instance is a set of processes and memory structures: it exists on the
CPU(s) and in the memory of the server node, and its existence is temporary. An
instance can be started and stopped. Users of the database establish sessions against
the instance, and the instance then manages all access to the database. It is absolutely
impossible in the Oracle environment for any user to have direct contact with the
database. An Oracle instance with an Oracle database makes up an Oracle server.
The processing model implemented by the Oracle server is that of client-server

processing, often referred to as two-tier. In the client-server model, the generation of the
user interface and much of the application logic is separated from the management of
the data. For an application developed using SQL (as all relational database applications
will be), this means that the client tier generates the SQL commands, and the server
tier executes them. This is the basic client-server split, usually with a local area
network dividing the two tiers. The network communications protocol used between
the user process and the server process is Oracle’s proprietary protocol, Oracle Net.
The client tier consists of two components: the users and the user processes. The
server tier has three components: the server processes that execute the SQL, the instance,
and the database itself. Each user interacts with a user process. Each user process
interacts with a server process, usually across a local area network. The server processes
interact with the instance, and the instance with the database. Figure 1-1 shows this
relationship diagrammatically. A session is a user process in communication with a
server process. There will usually be one user process per user and one server process
per user process. The user and server processes that make up sessions are launched on
demand by users and terminated when no longer required; this is the log-on and log-
off cycle. The instance processes and memory structures are launched by the database
administrator and persist until the administrator deliberately terminates them; this is
the database startup and shutdown cycle.
Figure 1-1 The indirect connection between a user and a database