Exadata Workshop Part1
Exadata Workshop Part1
Exadata Workshop Part1
Administration Workshop
Student Guide
D67016GC20
Edition 2.0
January 2011
D71669
Authors
Peter Fusek
Disclaimer
Jean-Francois Verrier
Mark Fuller
Dave Winter
Technical Contributors
and Reviewers
Andrew Babb
Sue Lee
Bharat Baddepudi
Juan Loaiza
Maria Billings
Barb Lundhild
Robert Carlin
Varun Malhotra
Michael Cebulla
Louis Nagode
Nilesh Choudhury
Dan Norris
Christian Craft
Michael Nowak
Ravindra Dani
Sriram Palapudi
Aslam Edah-Tally
Umesh Panchaksharaiah
Boris Erlikhman
Sugam Pandey
Amit Ganesh
Robert Pastijn
Ed Gilowski
Marshall Presser
Joel Goodman
Georg Schmidt
Scott Gossett
Akshay Shah
Jim Hall
Kam Shergill
Roger Hansen
Tim Shelter
James He
Eric Siglin
David Hitchcock
Sundararaman Sridharan
Bill Hodak
Vijay Sridharan
Vimala Jacob
Mahesh Subramaniam
Martin Jensen
Lawrence To
Kevin Jernigan
Alex Tsukerman
Caroline Johnston
Kodi Umamageswaran
Larry Justice
Douglas Utzig
Vikram Kapoor
Bruce Kyro
Sumeet Lahorani
Dave Winter
Publishers
Sujatha Nagendra
Giri Venugopal
Contents
Introduction
Course Objectives 1-2
Audience and Prerequisites 1-3
Course Scope 1-4
Course Contents 1-5
Terminology 1-6
Additional Resources 1-7
Practice 1 Overview: Introducing the Laboratory Environment 1-8
Exadata Overview
Objectives 2-2
Traditional Enterprise Database Storage Deployment 2-3
Exadata Storage Deployment 2-4
Exadata Implementation Architecture Overview 2-6
Introducing Exadata 2-7
Exadata Hardware Details (Sun Fire X4270 M2) 2-8
Exadata Specifications 2-9
InfiniBand Network 2-10
Classic Database I/O and SQL Processing Model 2-11
Exadata Smart Scan Model 2-12
Exadata Smart Storage Capabilities 2-13
Exadata Smart Scan Scale-Out Example 2-16
Exadata Hybrid Columnar Compression 2-19
Exadata Hybrid Columnar Compression Architecture Overview 2-20
Exadata Smart Flash Cache 2-21
Exadata Storage Index 2-23
Storage Index with Partitions Example 2-25
Database File System 2-26
I/O Resource Management 2-27
Benefits Multiply 2-28
Exadata Key Benefits for Data Warehousing 2-29
Exadata Key Benefits for OLTP 2-31
Quiz 2-32
Summary 2-34
iii
Exadata Architecture
Objectives 3-2
Exadata Software Architecture Overview 3-3
Exadata Software Architecture Details 3-5
Exadata Smart Flash Cache Architecture 3-7
Exadata Monitoring Architecture 3-9
Disk Storage Entities and Relationships 3-10
Interleaved Grid Disks 3-12
Flash Storage Entities and Relationships 3-13
Disk Group Configuration 3-14
Quiz 3-15
Summary 3-17
Additional Resources 3-18
Practice 3 Overview: Introducing Exadata Cell Architecture 3-19
Exadata Configuration
Objectives 4-2
Exadata Installation and Configuration Overview 4-3
Initial Network Preparation 4-4
Configuration of New Exadata Servers 4-6
Answering Questions During the Initial Boot Sequence 4-7
Exadata Administrative User Accounts 4-11
Configuring a New Exadata Cell 4-12
Important I/O Metrics for Oracle Databases 4-13
Testing Performance Using CALIBRATE 4-14
Configuring the Exadata Cell Server Software 4-15
Creating Cell Disks 4-16
Creating Grid Disks 4-17
Creating Flash-Based Grid Disks 4-18
Configuring Hosts to Access Exadata Cells 4-19
Configuring ASM and Database Instances for Exadata 4-20
Configuring ASM Disk Groups for Exadata 4-21
Optional Configuration Tasks 4-22
Exadata Storage Security Overview 4-23
Exadata Storage Security Implementation 4-24
Quiz 4-26
Summary 4-29
iv
vi
Quiz 11-13
Summary 11-15
Additional Resources 11-16
Practice 11 Overview: Bulk Data Loading with Database Machine 11-17
12 Backup and Recovery with Database Machine
Objectives 12-2
Backup and Recovery Overview 12-3
Using RMAN with Database Machine 12-4
General Recommendations for RMAN 12-5
Disk Based Backup Strategy 12-7
Disk Based Backup Configuration 12-8
Tape Based Backup Strategy 12-10
Tape Based Backup Configuration 12-11
Hybrid Backup Strategy 12-15
Restore and Recovery Recommendations 12-16
Backup and Recovery of Database Machine Software 12-17
Quiz 12-18
Summary 12-20
Additional Resources 12-21
Practice 12 Overview: Using RMAN Optimizations for Database Machine 12-22
13 Monitoring and Maintaining Database Machine
Objectives 13-2
Monitoring Tools Overview 13-3
ILOM Overview 13-4
ILOM Example 13-6
DCLI Overview 13-7
DCLI Examples 13-8
InfiniBand Diagnostic Utilities 13-9
Database Machine Support Overview 13-11
Patching and Updating Overview 13-12
Maintaining Exadata Software 13-13
Maintaining Database Server Software 13-14
Maintaining Other Software 13-15
Quiz 13-16
Summary 13-18
Additional Resources 13-19
Practice 13 Overview: Using the distributed command line utility (dcli) 13-20
viii
ix
I t d ti
Introduction
Course Objectives
After completing this seminar, you should be able to:
Describe the key capabilities of Exadata and Database
Machine
Identify the benefits of using Database Machine for
different application classes
Describe the architecture of Database Machine and its
integration with Oracle Database, Clusterware and ASM
Complete the initial configuration of Database Machine
Describe
D
ib various
i
recommended
d d approaches
h ffor migrating
i ti
to Database Machine
Configure Exadata I/O Resource Management
Monitor Database Machine health and optimize
performance
Copyright 2010, Oracle and/or its affiliates. All rights reserved.
Course Scope
Course Scope
This course covers two main subject areas:
The first section introduces students to Exadata Storage Server X2
X2-2
2 (formerly known
as Exadata Storage Server Version 2). Students learn about the architecture and key
capabilities of Exadata along with how to configure, monitor and optimize it.
The second section introduces students to Oracle Exadata Database Machine. Students
learn about the various Database Machine configurations. The installation and
configuration process is covered so that students are equipped to make appropriate upfront configuration decisions. They also learn how to maintain, monitor and optimize
Database Machine after initial configuration. Students are introduced to various options
for migrating to Database Machine and learn how to select the best approach.
Although the hardware components of Database Machine are introduced and described to
varying degrees throughout this course, you should consult the hardware documentation for
specific hardware installation and maintenance details.
Course Contents
1.
2.
3.
4.
5.
6.
7.
8.
9.
10
10.
11.
12.
13.
Introduction
Exadata Overview
Exadata Architecture
Exadata Configuration
Exadata Monitoring and Maintenance
Exadata and I/O Resource Management
Optimizing Database Performance with Exadata
Database Machine Overview and Architecture
Database Machine Configuration
Migrating Databases to Database Machine
Bulk Data Loading with Database Machine
Backup and Recovery with Database Machine
Database Machine Monitoring and Maintenance
Course Contents
The slide shows the ordering of lessons in this course.
Terminology
Terminology
The slide indicates the conventions used throughout this course to abbreviate the formal
product names for Exadata Storage Server and Oracle Exadata Database Machine
Machine.
Additional Resources
Demonstrations (Viewlets)
http://www.oracle.com/technetwork/tutorials/index.html
Enter the Oracle Learning Library and conduct a search for
content in the Database Machine functional category.
g y Look
out for demonstrations with Exadata and Database Machine
Version 2 Series in the title.
Practice 1 Overview:
Introducing the Laboratory Environment
In this practice you will be introduced to the laboratory
environment used to support all the practices during this
course.
E d t Overview
Exadata
O
i
Objectives
After completing this lesson, you should be able to:
Contrast the Exadata storage architecture with traditional
shared storage offerings
Describe the hardware components of Exadata
Outline the capabilities of Exadata
Describe the main advantages of using Exadata compared
to traditional storage servers
Storage Arrays
Smart
storage
operations
Data compression
p
Copyright 2010, Oracle and/or its affiliates. All rights reserved.
In addition to Smart Scan, Exadata has other smart storage capabilities including the
ability to offload incremental backup optimizations, file creation operations, and more. This
approach yields substantial CPU
CPU, memory
memory, and I/O bandwidth savings in the database
server resulting in potentially massive performance improvements.
Exadata includes Exadata Hybrid Columnar Compression. This feature provides very high
levels of data compression implemented inside Exadata. Exadata Hybrid Columnar
Compression allows the database to reduce the number of I/Os required to scan a table.
For example, for data with a compression ratio of 10 to 1, the I/Os required to scan the
data are reduced from 10 to 1 as well.
Exadata ensures that I/O resources are made available whenever, and to whichever,
database needs them based on priorities and policies that you can define. The Database
Resource Manager (DBRM) and Exadata I/O Resource Management (IORM) work
together to manage intradatabase and interdatabase I/O resource usage to ensure that
your defined service-level agreements (SLAs) are met when multiple applications and
databases share Exadata storage.
Finally, even for queries that do not use Smart Scan, Exadata has many advantages over
conventional storage. Exadata is highly optimized for fast processing of large queries. It
has been carefully architected to ensure no bottlenecks in the controller or in other
components inside the storage server. It makes intelligent use of high-performance flash
memory to boost performance and also uses a state-of-the-art InfiniBand network that has
much higher throughput than conventional storage networks.
Exadata Cell
Exadata
software
Disk
Linux OS
Exadata Cell
Exadata
software
Disk
Linux OS
Introducing Exadata
Exadata Storage
Server
Introducing Exadata
Exadata is highly optimized for use with Oracle Database. Exadata delivers outstanding I/O
and SQL processing performance for data warehousing and online transaction processing
(OLTP) applications.
Exadata is based on a 64 bit Intel-based Sun Fire server. Oracle provides the storage server
software to impart database intelligence to the storage, and tight integration with Oracle
Database and its features. Each cell is shipped with all the hardware and software
components preinstalled including the Exadata Storage Server Software, Oracle Linux
x86_64 operating system and InfiniBand protocol drivers.
Since March 2010, Exadata is no longer offered as a standalone storage product. Now
Exadata is only available for use in conjunction with Database Machine. Individual Exadata
servers can still be purchased, however they must be connected to Database Machine.
Custom configurations using Exadata are no longer supported for new installations.
Processors
Memory
24 GB (6 x 4 GB)
Local Disks
Flash
Disk Controller
N t
Network
k
T InfiniBand
Two
I fi iB d 4X QDR (40Gb/
(40Gb/s)) ports
t
(1 dual-port PCIe 2.0 HCA)
Four embedded Gigabit Ethernet ports
Remote Management
Power Supplies
Exadata Specifications
HP Disks
HC Disks
384 GB
384 GB
7.2 TB
24 TB
2 TB
7 TB
1,800
1,000
3,600
3,600
3,600
1,440
Flash I/Os p
per Second (IOPS)
(
)
75,000
75,000
1 - Raw capacity calculated using 1 GB = 1000 x 1000 x 1000 bytes and 1 TB = 1000 x 1000 x 1000 x 1000 bytes.
2 - User Data: Actual space for uncompressed end-user data, computed after single mirroring (ASM normal redundancy)
and after allowing space for database structures such as temporary space, logs, undo space, and indexes. Actual user data
capacity varies by application. User Data capacity calculated using 1 TB = 1024 * 1024 * 1024 * 1024 bytes.
Exadata Specifications
Exadata is available in two configurations: with high performance (HP) disks or with high
capacity (HC) disks.
disks The table in the slide lists the key capacity and performance
specifications for both configuration options.
Note: MBPS stands for megabytes per second, IOPS stands for I/Os per second.
Note: These metrics do not take into account compression. With compressed data, you can
achieve much higher effective throughput rates. In all cases, actual performance will vary by
application.
InfiniBand Network
InfiniBand:
Is the Exadata storage network:
Provides highest performance available 40 Gb/sec each direction
Is widely used in high-performance computing since 2002
Looks
oo s like
e normal
o a Ethernet
e e to
o host
os so
software:
ae
All IP-based tools work transparently TCP/IP, UDP, HTTP, SSH,
and so on
InfiniBand Network
InfiniBand is the only storage network supported by Exadata because of its performance and
proven track record in high-performance
p
g p
computing.
p
g InfiniBand works like normal Ethernet but
much faster. It has the efficiency of a SAN, using zero copy and buffer reservation. Zero copy
means that data is transferred across the network without intermediate buffer copies in the
various network layers. Buffer reservation is used so that the hardware knows exactly where
to place buffers ahead of time. These are two important characteristics that distinguish
InfiniBand from normal Ethernet.
InfiniBand is also supported as a unified network fabric for Exadata and the Oracle RAC
interconnect. This facilitates easier configuration and fewer cables and switches. You can
also
l use it ffor hi
high-performance
h
f
external
t
l connectivity,
ti it such
h as tto connectt b
backup
k servers or
ETL servers.
On top of InfiniBand, Exadata uses the Zero Data loss UDP (ZDP) protocol. ZDP is open
source software that is developed by Oracle. It is like UDP but more reliable. Its full technical
name is RDS (Reliable Datagram Sockets) V3. The ZDP protocol has a very low CPU
overhead with tests showing only a 2 percent CPU utilization while transferring 1 GB/sec of
data.
E hE
Each
Exadata
d t server iis configured
fi
d with
ith one d
dual-port
l
t InfiniBand
I fi iB d card
dd
designed
i
d tto b
be
connected to two separate InfiniBand switches for high availability. Each InfiniBand link is
able to carry the full data bandwidth of the entire cell, which means you can lose an entire
network without losing any performance.
Exadata and Database Machine Administration Workshop 2 - 10
Row returned
Extents identified
SQL processing:
2 MB returned
I/O issued
I/O executed:
10 GB returned
iDB command
2
constructed
and sent to Exadata cells
SQL processing
in Exadata
Row returned
Consolidated result
set built from all
Exadata cells
2 MB returned
to server
Predicate filtering:
Only the rows requested are returned to the database server
rather than all the rows in a table.
Column filtering:
g
Only the columns requested are returned to the database
server rather than all the columns in a table.
Join processing:
Simple star join processing is performed within Exadata.
Exadata performs join processing for star schemas (between large tables and small
lookup tables)
tables). This is implemented using Bloom Filters
Filters, which is a very efficient
probabilistic method to determine whether an element is a member of a set.
Exadata performs Smart Scans on encrypted tablespaces and encrypted columns. For
encrypted tablespaces, Exadata can decrypt blocks and return the decrypted blocks to
Oracle Database, or it can perform row and column filtering on encrypted data.
Significant CPU savings can be made within the database server by offloading the CPUintensive decryption task to Exadata cells.
Smart Scan works in conjunction with Exadata Hybrid Columnar Compression so that
column projection and row filtering can be executed along with decompression at the
storage level to save CPU cycles on the database servers.
Exadata can perform scoring functions for data mining models. All data mining scoring
functions, such as PREDICTION_PROBABILITY, are offloaded to Exadata cells for
processing. This accelerates warehouse analysis while it reduces database server CPU
consumption
p
and the I/O load between the database server and Exadata.
Backups:
I/O for incremental backups is much more efficient because
only changed blocks are returned to the database server.
Create/extend tablespace:
p
Exadata formats database blocks.
The speed and efficiency of incremental database backups is enhanced with Exadata.
The granularity of change tracking in the database is much finer with Exadata
Exadata. With
Exadata, changes are tracked at the individual Oracle block level rather than at the level
of a large group of blocks. This results in less I/O bandwidth being consumed for
backups and faster running backups.
With Exadata, the create/extend tablespace operation is also executed much more
efficiently. Instead of formatting blocks in database server memory and writing them to
storage, a single iDB command is sent to Exadata instructing it to format the blocks.
Database server memory usage is reduced and I/O associated with the creation and
formatting of the database blocks is eliminated with Exadata.
Database
Server
dbs1
Exadata
Cell
edsc1
edsc2
edsc13
edsc14
dbs1
Exadata
Cell
edsc1
edsc2
edsc13
edsc14
0 357 GB/s
0.357
Disks are throttled
by the network bandwidth!
Disks
(12/cell)
dbs1
Exadata
Cell
1 8 GB/s
1.8
Disks
(12/cell)
edsc1
edsc2
edsc13
edsc14
Each
E
h cellll can scan att a
speed of 1.8 GB/s,
and send its matching
rows to the database
instance. This represents
a total scan at a speed
of 25.2 GB/s!
Warehouse Compression
Archival Compression
10
10x average storage
t
savings
i
10x scan I/O reduction
Optimized for query performance
Reclaim Disks
Keep Data Online
Block Header
Block Header
Block Header
C2
C5
C7
C3
C8
C4
C5
C6
Tens of Thousands
of I/Os per Second
Region Index
B:1/5
B:3/8
E:a/j
G:4/9
1 ASM AU
1MB
Storage Region
1 ASM Disk
DBA
Min B = 1
Max B = 5
Table T2
Table T1
Table T1
A B C D
A B C D
a 4
Min B = 3
Max B = 8
d 7
j
ORDER_DATE
SHIP_DATE
ITEM
(Partition Key)
2007
2007
008
2008
2008
008
2009
2009
RDBMS
I/O
Requests
Traditional
Storage Server
H L H L L L
Y cannott
You
influence the
I/O scheduler.
High-priority
workload
request
Exadata
RDBMS
I/O
Requests
Low-priority
workload
request
H H
L L L L
L H H H
Benefits Multiply
Results in
real-time on
Database
Machine
Benefits Multiply
This is an example that shows you how the main Exadata features that were introduced in this
lesson can work together to multiply the benefits of Exadata
Exadata.
Assume you have a multi-terabyte table and somebody runs a query that is interested in a
small subset of the data, but causes a full table scan. Traditionally, the system would have to
scan the terabytes of data.
However, using Exadata Hybrid Columnar Compression could reduce the size of the table.
If the table is partitioned, the optimizer could use partition pruning to eliminate a substantial
proportion of the data
data.
Using storage indexes, Exadata might further reduce the amount of physical I/O that is
executed.
Finally, because of Smart Scan, the only data returned to the database is the data of interest
to the query, some of which may have been cached inside Exadata Smart Flash Cache.
This example shows how the various Exadata and Oracle Database features can work in
harmony to improve the performance of a single operation using Database Machine
Machine.
Tens of Thousands
of I/Os per Second
Quiz
Exadata and Database Machine are two different names that
designate the same thing.
1. TRUE
2 FALSE
2.
Answer: 2
Quiz
What are the three unique benefits of Exadata compared to
traditional storage servers?
1. Larger disk sizes
2 Smart storage capabilities
2.
3. Higher storage network bandwidth
4. Higher RAM capacity
5. Integrated database I/O resource management
Answer: 2, 3, 5
Summary
In this lesson, you should have learned how to:
Contrast the Exadata storage architecture with traditional
shared storage offerings
Describe the hardware components of Exadata
Outline the capabilities of Exadata
Describe the main advantages of using Exadata compared
to traditional storage servers
Additional Resources
http://stcurriculum.oracle.com/demos/db/11g/r2/dbmach/021ExadataSmartScanIntro
/021exadatasmartscanintro_viewlet_swf.html
http://stcurriculum.oracle.com/demos/db/11g/r2/dbmach/022ExadataCompressionInt
ro/022exadatacompressionintro_viewlet_swf.html
http://stcurriculum.oracle.com/demos/db/11g/r2/dbmach/023ExadataFlashCacheIntr
o/023exadataflashcacheintro_viewlet_swf.html
http://sthtt
// t
curriculum.oracle.com/demos/db/11g/r2/exadatav2/smartscanscaleoutexamp
le/smartscanscaleoutexample.swf
Storage Index
http://stcurriculum.oracle.com/demos/db/11g/r2/exadatav2/storageindex/storageinde
x.swf
Practice 2 Overview:
Introducing Exadata Features
In these practices, you are introduced to four major capabilities
of Exadata, namely:
Smart Scan
Exadata Hybrid Columnar Compression
Exadata Smart Flash Cache
Storage Index
Exadata Architecture
Objectives
After completing this lesson, you should be able to describe:
The Exadata architecture
The relationship between the various storage abstractions
used in Exadata
Single-instance DB
DB Server
Single
ASM cluster
DB Server
DB Server
DB Instance
DB Instance
DB Instance
DBRM
DBRM
DBRM
ASM
ASM
ASM
LIBCELL
LIBCELL
LIBCELL
Enterprise
Manager
Oracle Linux
Cell Control
CLI
(cellcli/dcli)
Oracle Linux
Oracle Linux
CELLSRV
MS
CELLSRV
MS
CELLSRV
MS
IORM
RS
IORM
RS
IORM
RS
SSH
Exadata Server
Exadata Server
Exadata Server
Single-instance DB
DB Server
Single
ASM cluster
DB Server
DB Server
DB Instance
DB Instance
DB Instance
DBRM
DBRM
DBRM
ASM
ASM
ASM
LIBCELL
LIBCELL
LIBCELL
Enterprise
Manager
Oracle Linux
Cell Control
CLI
(cellcli/dcli)
Oracle Linux
Oracle Linux
CELLSRV
MS
CELLSRV
MS
CELLSRV
MS
IORM
RS
IORM
RS
IORM
RS
SSH
Exadata Server
Exadata Server
Exadata Server
Database Server
Data
ASM instance
RDBMS instance
Smart
Flash Cache
SGA
SGA
ASM
ASM
dskm
I/O
Proc
dskm
I/O
Proc
LIBCELL
/opt/oracle/cell/
cellsrv/deploy/
config
LIBCELL
CellCLI
cellsrv
MS
diskmon
adrci
cell_disk_
config.xml
iDB Protocol
RS
cellinit.ora
CELLSRV
ADR
css
iDB Protocol
/etc/oracle/cell/network-config
cellip.ora
cellinit.ora
bond0
MS internal
dictionary
and
CELLSRV internal
parameters and
local interface IP
List accessible
Exadata cells
List local
interface IP
InfiniBand switch
LIBCELL
C
Library:
b a y Provides
o des U
UNIX-like
e I/O
/O primitives
p
t es a
and
d iss linked
ed with
t ASM,
S , RDBMS,
S, a
and
d
ASM utilities. It uses the iDB Protocol to communicate with Exadata.
DISKMON (Network/Cell Monitor): Checks the network interface state and cell liveness. It
uses a nodewide master process and one slave process (dskm) for each RDBMS or ASM
instance. The master performs monitoring and propagates state information to the slaves.
Slaves use the SGA to communicate with RDBMS or ASM processes. If there is a failure
in the cluster, DISKMON performs I/O fencing to protect data integrity. Cluster
Synchronization Services (CSS) still decides what to fence
fence. Master DISKMON starts with
the clusterware processes. DISKMON also performs DBRM plan propagation.
Cell-side Exadata software:
Management Server (MS) is an OC4J application that provides storage cell management
and configuration functions, such as cell administration, and metrics and alerts generation.
It also communicates with CELLSRV and the operating system.
Exadata and Database Machine Administration Workshop 3 - 5
Restart Server (RS): Monitors CELLSRV and MS and restarts them, if necessary.
CellCLI: Executes user cell administration commands. The user must connect to the cell
to use CellCLI
CellCLI. CellCLI communicates with MS using Web Services
Services.
ADRCI: CELLSRV uses the Automatic Diagnostic Repository (ADR) to log software errors.
An Exadata administrator may use the ADR viewer (ADRCI) to view and package ADR
incidents.
DB
DB
3
cellsrv
cellsrv
on uncached data
cellsrv
Acknowledgement
Read Reque
est
Read Operation
DB
Read Operation
on previously cached data
Read Reque
est
Write Operation
Exadata Smart
Flash Cache
A cache hint, which is assigned by the database based on the reason for the I/O:
- CACHE indicates that the I/O should be cached. For example, the I/O is for an
index lookup.
- NOCACHE indicates that the I/O should not be cached. For example, the I/O is for
a mirrored block of data or is a log write.
- EVICT indicates that data should
sho ld be removed
remo ed from the cache.
cache For e
example,
ample when
hen
an ASM rebalance operation moves data between different disks, the cached
copies that correspond to the original location are removed from the cache.
Exadata and Database Machine Administration Workshop 3 - 7
Current cache load: Smart table scans are usually directed to disk. However, if the object
has a CELL_FLASH_CACHE setting of KEEP, some reads may be satisfied using Exadata
Smart Flash Cache in order to best utilize the combined throughput of the disks and the
cache.
Exadata Smart Flash Cache uses all of the aforementioned information to make intelligent
decisions about which data is suitable for caching and which is not.
Exadata Smart Flash Cache is a write-through cache. This means that for write operations,
CELLSRV writes data to disk and sends an acknowledgement to the database so it can continue
without any interruption. Then, if the data is suitable for caching, it is written to Exadata Smart
Flash Cache. Write performance is not improved or diminished using this method. However, if a
subsequent read operation needs the same data, it is likely to benefit from the cache.
For read operations, CELLSRV must first determine if the requested data is already in Exadata
S
Smart
t Flash
Fl h C
Cache.
h CELLSRV maintains
i t i an iin-memory hash
h h ttable,
bl which
hi h it uses tto quickly
i kl
determine which data blocks reside in Exadata Smart Flash Cache. If the requested data is
cached, a cache lookup is used to satisfy the I/O request.
For read operations that cannot be satisfied using Exadata Smart Flash Cache, a disk read is
performed and the requested information is sent to the database. Then if the data is suitable for
caching, it is written to Exadata Smart Flash Cache.
When suitable data is inserted into a full cache
cache, a prioritized least recently used (LRU) algorithm
determines which data to replace. Objects with a CELL_FLASH_CACHE setting of KEEP are
subject to a different cache retention policy than objects with a CELL_FLASH_CACHE setting of
DEFAULT. KEEP objects have priority over DEFAULT objects so that new data from a DEFAULT
object will not push out cached data from any KEEP objects. To prevent KEEP objects from
monopolizing the cache, they are allowed to occupy no more than 80% of the total cache size.
Also, to prevent unused KEEP objects from indefinitely occupying the cache, they are subject to
an additional aging policy
policy, which periodically purges unused KEEP object data
data.
Smart
Flash Cache
Data
OMS
agent
dcli
CellCLI
cellsrv
MS
adrci
SSH / CellCLI
CELLSRV
ADR
eth0
eth0
Network switch
CELLDISK
LUN
Exadata Cell
Data
Storage
Partition
GRIDDISK
ASM disk
Grid
Disk
System Area
OR
Cell
Disk
OR
Visible to
ASM
Grid Disk
LUN
(hot part)
Other ten
LUNs
Grid Disk
(cold part)
50%
Slower Tracks
50%
Slowest Tracks
Grid Disk 2
Grid Disk 3
Fastest Tracks
Slower Tracks
50%
Fast Tracks
50%
Slowest Tracks
The perform
mance of Grid Diisk 3 and
Grid Disk 4 is more evenly balanced
b
Grid Dis
sk1 benefits from
m the higher
performa
ance outer tracks
s of the disk
Grid Disk 1
Fastest Tracks
Grid Disk 4
LUN
CELLDISK
OR
GRIDDISK
ASM disk
FLASHCACHE
Exadata Cell
Flash
Cache
Flash
LUN
Cell
Disk
OR
Flash Cache
Grid Disk
Visible to
ASM
Exadata Cell
Exadata Cell
DATA
Disk Group
FRA
Disk Group
Quiz
What are the three main Exadata services?
1. OMS
2. MS
3 GMON
3.
4. CELLSRV
5. RS
Answer: 2, 4, 5
Quiz
If you use NORMAL ASM redundancy for all of your disk groups
in conjunction with ASM failure groups spread across two
Exadata cells, under which of the following scenarios will you
maintain data availability?
1. A single disk failure in a single cell
2. Simultaneous failure of multiple disks in a single cell
3. Simultaneous failure of a single disk in both cells
4. Complete failure of a single cell
Answer: 1 ,2, 4
The prescribed configuration may provide protection against failure scenario 3 if, and only if,
guarantee data availability
y in
there are no data extents mirrored to both of the failed disks. To g
cases where simultaneous failures affect two cells, you must use HIGH ASM redundancy in
conjunction with failure groups spread across at least three Exadata cells.
Summary
In this lesson, you should have learned to describe:
The Exadata architecture
The relationship between the various storage abstractions
used in Exadata
Additional Resources
http://stcurriculum.oracle.com/demos/db/11g/r2/dbmach/034ExadataFlashCacheAdmin/034exad
ataflashcacheadmin_viewlet_swf.html
http://stcurriculum.oracle.com/demos/db/11g/r2/dbmach/033ExadataInterleavedGridDisks/033ex
adatainterleavedgriddisks_viewlet_swf.html
http://stcurriculum.oracle.com/demos/db/11g/r2/dbmach/032ExadataStorageObjects/032exadata
i l
l
/d
/db/11 / 2/db
h/032E d t St
Obj t /032
d t
storageobjects_viewlet_swf.html
http://stcurriculum.oracle.com/demos/db/11g/r2/dbmach/031ExadataProcessIntro/031exadatapr
ocessintro_viewlet_swf.html
http://stcurriculum.oracle.com/demos/db/11g/r2/exadatav2/smartflashcachearchitecture/smartfla
shcachearchitecture.swf
Oracle Reliable Datagram Sockets (RDS) and InfiniBand (IB) Support for RAC
Interconnect and Exadata Storage
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=745616.1
Practice 3 Overview:
Introducing Exadata Cell Architecture
In these practices, you will be familiarized with the Exadata cell
architecture. You will:
Examine the Exadata processes
Examine the hierarchy of cell objects
Create interleaved grid disks
Examine Exadata Smart Flash Cache
E d t C
Exadata
Configuration
fi
ti
Objectives
After completing this lesson, you should be able to:
Perform the initial Exadata boot sequence
Configure Exadata software
Create and configure ASM disk groups using Exadata
Use the CellCLI Exadata administration tool
1
6
Configuring
ASM disk group
for Exadata
Configuring
ASM and Database
instances
for Exadata
Initial network
preparation
Configuration
of new Exadata
servers
Configuring
Exadata software
4
Configuring hosts
to use Exadata
Repeat
for each
cell
The Reliable Datagram Sockets (RDS) protocol should be used over the InfiniBand
network for database server to cell communication and Oracle Real Application Clusters
(RAC) communication. Check the database alert log to verify that the private network for
Oracle RAC is running the RDS protocol over the InfiniBand network. The following
message should be in the log:
cluster interconnect IPC version: Oracle RDS/IP (generic)
Dedicate a block of IP addresses for the InfiniBand network and ensure that you allow for
f t
future
expansion.
i
Dedicate a block of IP addresses for the general administration interfaces and the lights
out management interfaces. The general administration interfaces and the lights out
management interfaces may be on the same subnet and may share that subnet with other
hosts. For example, on the 192.168.200.0/24 subnet, you might assign the block of IP
addresses between 192.168.200.31 and 192.168.200.50 for your Exadata general
administration interfaces and the lights
g
out management
g
interfaces. Other hosts sharing
g
the subnet would be allocated IP addresses outside the dedicated block. If you want, you
can place the general administration interfaces and the lights out management interfaces
on separate subnets; however, this is not required.
Do not allocate addresses that end in .0, .1, or .255, or those that would be used as
broadcast addresses for the specific netmask that you have selected. For example, avoid
addresses such as 192.168.200.0, 192.168.200.1, and 192.168.200.255.
Exadata cells do not require Domain Name System (DNS) however DNS is recommended
for use in conjunction with Database Machine. If DNS is available in your network,
configure your DNS with the IP addresses and host names associated with the general
administrative network on each Exadata cell.
Repeat
for each
cell
Gateway
10.XXX.XXX.1
Hostname
cell01.company.com
cell01-priv.company.com
settings:
cell01-ilom.company.com
10.XXX.XXX.YYY
255.255.248.0
10.XXX.XXX.1
mynameserv.company.com
enabled
ntp1.company.com
none
America/Denver
Repeat
for each
cell
Channel bandwidth
Metric = IOPS
Metric = MBPS
Need large
I/O channel
OLTP
DW/OLAP
CALIBRATE
CellCLI>
normal
normal
normal
normal
normal
normal
CellCLI>
Use fastest
disk portion
Before
After
Grid
disks
Cell
disk
active
active
active
active
active
Before
After
Flash
Cache
Flash
Cache
Grid disk
active
Repeat
for each
host.
Repeat
for each
host
o/<cell01 IP address>/data_cd_00_cell01
o/<cell01 IP address>/data_cd_01_cell01
...
o/<cell01 IP address>/data_cd_11_cell01
o/<cell02 IP address>/data_cd_00_cell02
o/<cell02 IP address>/data_cd_01_cell02
...
o/<cell02 IP address>/data_cd_11_cell02
o/<cell01 IP address>/fra_cd_00_cell01
o/<cell01 IP address>/fra_cd_01_cell01
...
o/<cell01 IP address>/fra_cd_11_cell01
o/<cell02 IP address>/fra_cd_00_cell02
o/<cell02 IP address>/fra_cd_01_cell02
...
o/<cell02 IP address>/fra_cd_11_cell02
ASM cluster A
RAC
DB
Instances
Non-RAC
DB
Instance
Grid
disk
Exadata Cell 1
Exadata Cell 2
RAC
DB
Instances
Non-RAC
DB
Instance
Database-scoped
security mode
ASM cluster B
A
S
M
A
S
M
/etc/oracle/cell/network.config
cellkey.ora
Each
cell
ASSIGN KEY
FOR <ASM>
Each
database
Each
disk
D
B
CREATE/ALTER
GRIDDISK
availableTo
<ASM>
$ORACLE_HOME/admin/<db_unique_name>/pfile
cellkey.ora
D
B
CREATE KEY
Each
disk
Each
cell
ASSIGN KEY
FOR <DB>
CREATE/ALTER
GRIDDISK
availableTo <DB>
Quiz
Grid disks are seen by ASM by using a discovery string that
starts with:
1. c/
2 o/
2.
3. g/
4. e/
Answer: 2
Quiz
The first grid disk you create uses the slowest tracks of the
corresponding physical disk.
1. TRUE
2 FALSE
2.
Answer: 2
Quiz
When you create a disk group for which you want Exadata
smart storage capabilities enabled, what three attributes must
you specify?
1. compatible.rdbms
p
2. compatible.asm
3. au_size
4. disk_repair_time
5. cell.smart_scan_capable
Answer: 1, 2, 5
Summary
In this lesson, you should have learned how to:
Perform the initial Exadata boot sequence
Configure Exadata software
Create and configure ASM disk groups using Exadata
Use the CellCLI Exadata administration tool
Additional Resources
http://stcurriculum.oracle.com/demos/db/11g/r2/dbmach/043ExadataConsumingGridDisks/
043exadataconsuminggriddisks_viewlet_swf.html
http://sthttp://st
curriculum.oracle.com/demos/db/11g/r2/dbmach/042ExadataStorageProvisioning/0
42exadatastorageprovisioning_viewlet_swf.html
http://stcurriculum.oracle.com/demos/db/11g/r2/dbmach/041ExadataCellConfig/041exadat
acellconfig_viewlet_swf.html
http://stcurriculum.oracle.com/demos/db/11g/r2/exadatav2/cellfirstboot/cellfirstboot.swf
http://st-curriculum.oracle.com/demos/db/11g/r2/exadatav2/cellcli/cellcli.swf
Practice 4 Overview:
Configuring Exadata
In these practices, you will perform a variety of Exadata
configuration tasks, including cell configuration and storage
provisioning. You will also consume Exadata storage using
ASM and exercise the privileges associated with the different
cell user accounts.
E d t P
Exadata
Performance
f
M
Monitoring
it i
and
d
Maintenance
Objectives
After completing this lesson, you should be able to:
Describe the various performance monitoring facilities
available for Exadata
Monitor Exadata from directly within a cell,
cell from a
database instance, and through Enterprise Manager
Interpret SQL execution plans that use Smart Scan
Outline probable maintenance scenarios
Monitoring Overview
1
Metrics
2
Alerts
3
Active requests
4
Execution
plans
5
V$
views
6
Wait
events
Monitoring Overview
After Exadata is configured and in use, the administrative focus shifts to ongoing monitoring
and maintenance
maintenance. To monitor Exadata
Exadata, you can use the following tools and information:
1. Exadata cell metrics
2. Exadata cell alerts
3. Exadata active requests
4. Database SQL statement execution plans
5. Database V$ views
6. Database wait events
7. Oracle Enterprise Manager Exadata monitoring plug-in
Metric
thresholds
exceeded
CELLSRV
internal
errors
CELLSRV
collects
metrics
ADR
CELLSRV
One hour of
in-memory
metric values
Every hour MS
flushes metric
values to disk.
MS
Cell
software
issues
Cell
Cell
hardware
issues
LIST METRICCURRENT
Disk
ALTER CELL
Seven days
metrics
Email
and/or
SNMP
1h
hour
alerts
LIST METRICHISTORY
LIST ALERTHISTORY
Metrics
CREATE|ALTER THRES
SHOLDS
normal
warning
critical
number
% (percentage)
F (fahrenheit)
C (celsius)
Th h ld
Thresholds
name
comparision
critical
occurances
observation
warning
name
cumulative
instantaneous
rate
transition
IORM_CONSUMER_GROUP
IORM_DATABASE
IORM_CATEGORY
CELL
CELLDISK
CELL_FILESYSTEM
GRIDDISK
HOST_INTERCONNECT
FLASHCACHE
Alerts
alertSource
severity
BMC
ADR
Metric
warning
critical
clear
info
alertType
metricObjectName
examinedBy
metricName
name
stateful
stateless
alertAction
alertMessage
failedMail
f il dSNMP
failedSNMP
beginTime
0
1
2
3
EndTime
notificationState
CellCLI> LIST ALERTHISTORY WHERE severity = 'critical' AND examinedBy = '' DETAIL
The CREATE THRESHOLD command creates a threshold that specifies the conditions for
generation of a metric alert. The example creates a threshold for the CT_IO_WT_LG_RQ
g y This metric specifies
p
the average
g
metric associated with the INTERACTIVE category.
number of milliseconds that large I/O requests issued by the category have waited to be
scheduled by IORM in the past minute. A large value indicates that the I/O workload from
this category is exceeding the allocation specified for it in the category plan. The alert is
triggered by two consecutive measurements (occurrences=2) over the threshold values:
one second for a warning alert (warning=1000) and two seconds for a critical alert
(critical=2000). The observation attribute is the number of measurements over
which measured values are averaged.
Active Requests
ioGridDisk
ioBytes
ioOffset
ioReason
ioType
objectNumber
id
name
asmDiskGroupNumber
parentID
asmFileIncarnation
requestState
sessionID
sessionSerNumber
file initialization
read
write
predicate pushing
filtered backup read
predicate push read
asmFileNumber
consumerGroupName
t bl
tablespaceNumber
N b
dbN
dbName
instanceNumber
sqlID
fileType
The data is encrypted and cell-based decryption is disabled: In order for Exadata to
perform decryption, Oracle Database needs to send the decryption key to Exadata. If
there are security concerns about keys being shipped across the storage network, you
can disable cell-based decryption by setting the CELL_OFFLOAD_DECRYPTION
parameter to FALSE.
V$SYSSTAT
- NAME
- VALUE
...
V$SQL
cellip.ora
cell p
physical
y
IO
bytes saved during
optimized RMAN file
restore
cell physical IO
interconnect bytes
SQL_TEXT
PHYSICAL_READ_BYTES
PHYSICAL_WRITE_BYTES
IO_INTERCONNECT_BYTES
IO CELL OFFLOAD ELIGIBLE BYTES
IO_CELL_OFFLOAD_ELIGIBLE_BYTES
IO_CELL_UNCOMPRESSED_BYTES
IO_CELL_OFFLOAD_RETURNED_BYTES
OPTIMIZED_PHY_READ_REQUESTS
...
cell physical IO
bytes saved by
storage index
physical read
total bytes
cell physical IO
bytes saved during
optimized file
creation
cell IO
uncompressed
bytes
V$BACKUP_DATAFILE
- DATAFILE_BLOCKS
- BLOCKS_READ
- BLOCKS_SKIPPED_IN_CELL
...
Wait Event
Description
Application
More Information
Integrated Lights
Out Manager (ILOM)
Primarily
storage server
hardware
Also network
net ork
and operating
system
http://docs.sun.com/app/docs/coll/ilom3.0 for
more information about ILOM
Standard Linux
monitoring tools and
utilities (vmstat,
iostat, top,
syslog, and so on)
Primarily
storage server
operating
system
Also network
and hardware
Planned maintenance
Examples
Procedure overview
1. Take the corresponding ASM failure groups offline.
2. Execute your planned maintenance operation.
3. Bring the ASM failure groups back online.
Unplanned maintenance
Examples
p
Procedure overview
1. Remedy the failure.
2. Bring online or re-create the affected ASM failure groups.
CellCLI> LIST ALERTHISTORY WHERE ALERTMESSAGE LIKE "Logical drive lost.*" DETAIL
Logical drive lost. Lun:0_5. Status: normal. Physdisk: 20:5.
Celldisk on it: CD_05_cell01.
CD 05 cell01. Griddisks on it: data_CD_05_cell01.
data CD 05 cell01.
The suggested action is: Refer to section Maintaining Physical Disks in
the User Guide.
Replace
physical disk.
20:5
LIST PHYSICALDISK
normal
Power down
the cell.
Replace the
flash card.
Power up
the cell.
New
Original
New
The following rescue options are available for the rescue procedure:
Partial reconstruction recovery: During partial reconstruction recovery, the rescue
process re-creates
t partitions
titi
on the
th system
t
disks
di k and
d checks
h k th
the disks
di k ffor th
the
existence of a file system. If a file system is discovered, then the process attempts to
boot. If the cell boots successfully, then you use the CellCLI commands, such as
LIST CELL DETAIL, to verify the cell is usable. You must also recover any data
disks, as appropriate. If the boot fails, then you must use the full original build
recovery option.
Full original build recovery: This option rewrites the system area of the system disks to
restore the Exadata software. It also allows you to erase any data on the data disks,
and data partitions on the system disks.
Re-creation of the CELLBOOT USB flash drive: This option is used to make a copy of
the CELLBOOT USB flash drive.
To perform a rescue using the CELLBOOT USB flash drive:
1. Connect to Exadata using the console.
2. Boot the cell, and as soon as you see the "Oracle Exadata" splash screen, press any
key on the keyboard. The splash screen remains visible for only 5 seconds.
3. In the displayed list of boot options, scroll down to the last option,
CELL_USB_BOOT_CELLBOOT_usb_in_rescue_mode, and press Enter.
4. Select the rescue option, and proceed with the rescue.
5. After a successful rescue, you must reconfigure the cell to return it to the pre-failure
configuration,
fi
ti
and
d reinstall
i t ll th
the kernel-debuginfo and
d kernel-debuginfocommon rpms to use crash kernel support. If you chose to preserve the data when
prompted by the rescue procedure, then import the cell disks. If you chose not to
preserve the data, then you should create new cell disks, and grid disks.
Quiz
You can define thresholds for all Exadata metrics?
1. TRUE
2. FALSE
Answer: 2
Thresholds are supported on cell disk and grid disk I/O error count metrics (CD_IO_ERRS_MIN
and GD_IO_ERRS_MIN), along with the cell memory utilization (CL_MEMUT ) and cell file system
utilization (CL_FSUT) metrics. In addition, you can set thresholds for I/O Resource Management
(IORM) related metrics. The CellCLI LIST ALERTDEFINITION command lists the metrics for
which thresholds can be set.
Quiz
You enable SQL processing offload using the
CELL_OFFLOAD_PLAN_DISPLAY initialization parameter.
1. TRUE
2 FALSE
2.
Answer: 2
The CELL_OFFLOAD_PROCESSING parameter is used to enable SQL processing offload.
Summary
In this lesson, you should have learned how to:
Describe the various performance monitoring facilities
available for Exadata
Monitor Exadata from directly within a cell,
cell from a
database instance and through Enterprise Manager
Interpret SQL execution plans that use offloading
Outline probable maintenance scenarios
Additional Resources
http://stcurriculum.oracle.com/demos/db/11g/r2/dbmach/051ExadataMe
tricsAlerts/051exadatametricsalerts_viewlet_swf.html
http://stcurriculum.oracle.com/demos/db/11g/r2/dbmach/052ExadataDB
Monitoring/052exadatadbmonitoring_viewlet_swf.html
g
g_
_
http://stcurriculum.oracle.com/demos/db/11g/r2/dbmach/053ExadataHig
hAvailability/053exadatahighavailability_viewlet_swf.html
Practice 5 Overview:
Monitoring Exadata
In these practices, you will monitor Exadata using metrics,
alerts and active requests. You will also monitor Exadata
statistics using dynamic performance views (V$ views) in your
database. Finally, you will exercise Exadata high availability by
examining the effect of a cell crash.
E d t and
Exadata
d I/O Resource
R
Management
M
t
Objectives
After completing this lesson, you should be able to use Exadata
I/O Resource Management to manage workloads within a
database and across multiple databases.
Applications
Databases
Database B
Finance
OnlineQuery
consumer group
Interactive
consumer group
category
HR
BatchQuery
consumer group
consumer group
Reporting
Batch
ETL
consumer group
category
consumer group
I/O
Resource
Management
Inside
one
database
Intradatabase
Resource
Plan
Across
multiple
databases
Interdatabase
Resource
Plan
Category
g y
Resource
Plan
IORM Plan
IORM Architecture
Database A
Database
sends
IO requests
to cells
cells.
Database A
CG1Database
queue A
CG1Database
queue A
CG1Database
queue A
CG2 queue
CG1 queue
CG2 queue
CG2 queue
CG2 queue
Exadata Cell
CELLSRV
CG queue
CGn
CGn queue
CGn
queue
CGn
queue
IO request tag:
- DB name
- Type
- Consumer group
BG queues
BG queues
BG queues
Database
BGZqueues
Database
CG1 queue Z
CG1Database
queue Z
CG1Database
queue Z
CG2 queue
CG1 queue
CG2 queue
CG2 queue
CG2 queue
IORM
CGn queue
Disk queue
CGn queue
CGn
queue
CGn
queue
Database Z
BG queues
BG queues
BG queues
BG queues
Resource
plans
Cell disk
Performance
statistics
IORM Architecture
IORM manages Exadata I/O resources on a per-cell basis. Whenever the I/O requests start to
saturate the cell, IORM schedules incoming I/O requests according to the configured resource
plans.
l
IORM schedules
h d l I/O b
by selecting
l ti requests
t ffrom diff
differentt CELLSRV queues. The
Th resource
plans are used to determine the order in which the queued I/O requests are issued to disk. The
goal of IORM is to fully utilize the available disk resources. Any allocation that is not fully utilized
is made available to other workloads in proportion to the configured resource plans.
IORM only intervenes when needed. For example, IORM does not intervene if there is only one
active consumer group on one database because there is no possibility of contention with
another consumer group or database.
Background I/Os are scheduled based on their priority relative to the user I/Os.
I/Os For example,
example
redo writes and control file I/Os are critical to performance and are always prioritized above all
user I/Os. Writes by the database writer process (DBWn) are scheduled at the same priority level
as user I/Os.
The diagram in the slide illustrates the high-level implementation of IORM. For each cell disk,
each database accessing the cell has one I/O queue per consumer group and three background
I/O queues. The background I/O queues correspond to high, medium, and low priority requests
with different I/O types mapped to each queue. If you do not set an intradatabase resource plan,
all nonbackground I/O requests are grouped into a single consumer group called
OTHER_GROUPS.
Note: IORM is only used to manage I/O requests to physical disks. IORM does not manage
requests to flash-based grid disks or requests serviced by Exadata Smart Flash Cache.
Exadata and Database Machine Administration Workshop 6 - 7
Database B
(Single Inst)
(RAC)
Intradatabase Plan A
Intradatabase Plan B
(DBMS_RESOURCE_MANAGER)
(DBMS_RESOURCE_MANAGER)
Disk
DB A Plan
Interdatabase Plan
(CellCLI)
Database A
Database B
Disk
DB B Plan
IORM Plan
: 70%
: 30%
Category Plan
(CellCLI)
INTERACTIVE : 60%
BATCH
: 40%
Database A
Database A
Database B
IORM
allocation
Intradatabase
45%
15%
40%
35%
18%
22%
10%
15%
Interdatabase
30%
70%
30%
70%
Categories
40%
60%
BATCH
INTERACTIVE
All
User I/Os
(100%)
Copyright 2010, Oracle and/or its affiliates. All rights reserved.
Automatically:
Consumer Group
SYS_GROUP
Level 1
Level 2
100%
HIGH_PRIORITY
80%
LOW_PRIORITY
20%
OTHER_GROUP
Level 3
100%
Percentages
are used
sed for both
CPU and I/O
resources.
Database
Level 1
sales_prod
80%
finance_prod
20%
sales_dev
Level 2
Level 3
100%
sales_test
50%
other
50%
CATEGORY
--------------ADMINISTRATIVE
BATCH
INTERACTIVE
MAINTENANCE
OTHER
OTHER
OTHER
OTHER
DBMS_RESOURCE_MANAGER.CREATE_CATEGORY
Category
Level 1
Interactive
90%
Batch
Level 2
Level 3
80%
Maintenance
CellCLI> alter iormplan
>
dbplan= ''
Other
>
catplan=(
catplan
(
>
(name=interactive, level=1, allocation=90),
>
(name=batch, level=2, allocation=80),
>
(name=maintenance, level=3, allocation=50),
>
(name=other, level=3, allocation=50)
>
)
50%
50%
-
Complete Example
Database A
BEGIN
DBMS_RESOURCE_MANAGER.CREATE_SIMPLE_PLAN(SIMPLE_PLAN => DB_A_Plan',
CONSUMER_GROUP1 => CG1', GROUP1_PERCENT => 15,
CONSUMER_GROUP2 => CG2', GROUP1_PERCENT => 10,
CONSUMER_GROUP3 => CG3', GROUP1_PERCENT => 35,
CONSUMER_GROUP4 => CG4, GROUP2_PERCENT => 40);
DBMS_RESOURCE_MANAGER.CREATE_PENDING_AREA();
DBMS_RESOURCE_MANAGER.UPDATE_CONSUMER_GROUP(CONSUMER_GROUP => CG1,
NEW_CATEGORY => BATCH);
DBMS_RESOURCE_MANAGER.UPDATE_CONSUMER_GROUP(CONSUMER_GROUP => CG2,
NEW_CATEGORY => BATCH);
DBMS_RESOURCE_MANAGER.UPDATE_CONSUMER_GROUP(CONSUMER_GROUP => CG3,
NEW_CATEGORY => INTERACTIVE);
DBMS RESOURCE MANAGER UPDATE CONSUMER GROUP(CONSUMER GROUP => CG4,
DBMS_RESOURCE_MANAGER.UPDATE_CONSUMER_GROUP(CONSUMER_GROUP
CG4
NEW_CATEGORY => INTERACTIVE);
DBMS_RESOURCE_MANAGER.SUBMIT_PENDING_AREA();
END;
/
ALTER SYSTEM SET RESOURCE_MANAGER_PLAN = DB_A_Plan';
Complete Example
This slide is the first in a series of 3 slides which provide a more complete example showing
the use of the different IORM plan types at the same time.
time The example is based on the
scenario introduced on pages 8, 9 and 10 of this lesson.
On this slide, the commands required to configure DBRM on Database A are shown.
Note that the example does not show the creation of any categories using
DBMS_RESOURCE_MANAGER.CREATE_CATEGORY because the categories used in the
scenario (BATCH and INTERACTIVE) are categories that are predefined inside Oracle
Database byy default.
Complete Example
Database B
BEGIN
DBMS_RESOURCE_MANAGER.CREATE_SIMPLE_PLAN(SIMPLE_PLAN => DB_B_Plan',
CONSUMER_GROUP1 => CG5', GROUP1_PERCENT => 22,
CONSUMER_GROUP2 => CG6', GROUP1_PERCENT => 18,
CONSUMER_GROUP3 => CG7', GROUP1_PERCENT => 15,
CONSUMER_GROUP4 => CG8, GROUP2_PERCENT => 45);
DBMS_RESOURCE_MANAGER.CREATE_PENDING_AREA();
DBMS_RESOURCE_MANAGER.UPDATE_CONSUMER_GROUP(CONSUMER_GROUP => CG5,
NEW_CATEGORY => BATCH);
DBMS_RESOURCE_MANAGER.UPDATE_CONSUMER_GROUP(CONSUMER_GROUP => CG6,
NEW_CATEGORY => BATCH);
DBMS_RESOURCE_MANAGER.UPDATE_CONSUMER_GROUP(CONSUMER_GROUP => CG7,
NEW_CATEGORY => INTERACTIVE);
DBMS RESOURCE MANAGER UPDATE CONSUMER GROUP(CONSUMER GROUP => CG8,
DBMS_RESOURCE_MANAGER.UPDATE_CONSUMER_GROUP(CONSUMER_GROUP
CG8
NEW_CATEGORY => INTERACTIVE);
DBMS_RESOURCE_MANAGER.SUBMIT_PENDING_AREA();
END;
/
ALTER SYSTEM SET RESOURCE_MANAGER_PLAN = DB_B_Plan';
Complete Example
Exadata Cells
CellCLI> alter iormplan
>
dbplan=((name=Database_A, level=1, allocation=70),
>
(
(name=Database_B,
b
level=1,
l
l
allocation=30)),
ll
i
))
>
catplan=((name=INTERACTIVE, level=1, allocation=60),
>
(name=BATCH, level=1, allocation=40))
Description
DB_IO_RQ_SM
DB_IO_RQ_LG
DB_IO_RQ_SM_SEC
DB_IO_RQ_LG_SEC
DB_IO_WT_SM
DB_IO_WT_LG
Quiz
If a consumer group does not require its full resource allocation,
what happens to the leftover allocation?
1. It remains unused.
2 It is divided equally among other consumer groups
2.
groups.
3. It is allocated to other active consumer groups, according
to the resource plan.
Answer: 3
Quiz
Which of the following conditions are required for IORM to
intervene and control the allocation of I/O resources?
1. The IORM plan must be active.
2 More than one consumer group must be active.
2.
active
3. The disks must be heavily utilized.
Answer: 1, 2, 3
All of the conditions listed in this question must be present for IORM to intervene.
Quiz
In which order are the different I/O resource plans applied to
allocate I/O resources?
1. Category, intradatabase, interdatabase
2 Interdatabase,
2.
Interdatabase category
category, intradatabase
3. Category, interdatabase, intradatabase
4. Interdatabase, intradatabase, category
5. Intradatabase, interdatabase, category
Answer: 3
Quiz
You can create categories using the CellCLI utility.
1. TRUE
2. FALSE
Answer: 2
You can create your own categories using the CREATE_CATEGORY procedure in the
DBMS_RESOURCE_MANAGER package, and then assign your category to a consumer group
using the CREATE_CONSUMER_GROUP or UPDATE_CONSUMER_GROUP procedures.
You can then manage I/O resources based on categories by creating a category plan. The
category plan can be created using the CellCLI utility.
Summary
In this lesson, you should have learned how to use Exadata I/O
Resource Management to manage workloads within a
database and across multiple databases.
Additional Resources
http://stcurriculum.oracle.com/demos/db/11g/r2/dbmach/061ExadataIntr
aDBIORM/061exadataintradbiorm_viewlet_swf.html
http://stcurriculum.oracle.com/demos/db/11g/r2/dbmach/062ExadataInt
erDBIORM/062exadatainterdbiorm_viewlet_swf.html