Private Database Cloud

Private Database Cloud
Database Consolidation Planning and Best Practices

Nitin Vengurlekar Viscosity – CTO/Cloud Evangelist
1 Charles Kim Viscosity – President/Oracle Architect
Copyright © 2011, Oracle and/or its affiliates. All rights reserved.
Ni#n Vengurlekar
•  Oracle Product Strategy and Private Cloud Evangelist
•  17 Years with Oracle, 10 years Oracle RAC development
•  Over 24 years of Oracle Expertise, RAC, Data Guard, ASM, RMAN
•  Private Database Cloud Evangelist and author of the Cloud Best

Practices, Isolation and Security Management in Private Database Cloud
•  Author of Oracle Press ASM Cookbook and Oracle Data Guard Handbook
2 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

Charles Kim

Program Agenda
•  What is Private Database Cloud
•  Why Database Cloud Consolidation
•  Private Database Cloud deployment models
•  Database Cloud Consolidation Planning and Considerations
•  Engineered Solutions and the Private Database Cloud

NIST Definition of Cloud Computing
Cloud computing is a model for enabling convenient, on-demand

network access to a shared pool of configurable computing
resources (e.g., networks, servers, storage, applications, and
services) that can be rapidly provisioned and released with
minimal management effort or service provider interaction.
This cloud model promotes availability and is composed of:
5 Essential Characteristics 3 Service Models 4 Deployment Models
•  On-demand self-service •  SaaS •  Public Cloud
•  Resource pooling •  PaaS •  Private Cloud
•  Rapid elasticity •  IaaS •  Community Cloud
•  Measured service •  Hybrid Cloud
•  Broad network access Source: NIST Definition of Cloud Computing v15

Customers Have a Choice of Clouds
•  Own & Operate, Use Managed Services, Subscribe
Private Cloud Managed Cloud Services Public Cloud
Build Managed Subscribe
Customer owns, hosts Customer owns. Customer subscribes.

and manages. Service provider manages. Service provider hosts
Either may host. and manages.

Database Cloud Business Drivers
Lower: Reduce:
•  CapEx •  Configurations
•  Servers •  Services
•  Storage Reduce
Reduce
• OpEx Complex Standardize:
•  Maintenance IT Costs •  OS
ity
•  Management •  DB Versions
Increase
Increase Quality
Enable: Agility of Enhance:
•  Online changes Service •  IT service time
•  Rapid response •  Availability
•  Faster Time to market •  Security

Customers Have a Choice of Clouds
•  IaaS, PaaS or SaaS
Different Users
IT Professional Developer Business End User
Consumer
Customizations Customizations Customizations
Consumer
Application Application
Service Provider
Platform
SaaS Cloud
PaaS Cloud
Provider
Service
IaaS Cloud

Private Database Cloud Architectures
Common building blocks are shared server and storage pools
Infrastructure Cloud Database Cloud

Database Cloud
DW CRM ERP DW ERP CRM DW ERP CRM
DB
DB
DB
DB
DB
DB
DB
OS OS OS
Hypervisor Hypervisor Platform Platform Platform Platform
Server Consolidation Database Consolidation Schema Consolidation

Deploy in dedicated VMs Share server pool Share database instances
Server virtualization Real Application Clusters Real Application Clusters

Infrastructure Cloud
Server - Provision a Database in a VM
•  Reasons for adoption
•  Simple to implement
•  Excellent isolation
•  Mixed workloads DW CRM ERP
•  As-is consolidation
DB
DB
DB
•  Legacy support
•  Customer concerns OS OS OS
•  Lower consolidation density Hypervisor

•  Lower ROI
•  Performance (latency)
•  Managing sprawl

© 2011 Oracle Corporation
Database Cloud
Database Consolidation – Provision Database
•  Consolidation density
•  Good ROI
•  Performance DW ERP CRM
•  Supports any app
DB
DB
DB
OS OS
•  Customer concerns
•  Requires OS standardization
•  Database only

Database – Provision Schema
•  Most efficient
•  Extremely fast provisioning
•  Best ROI
DW ERP CRM
•  Performance
•  Efficient memory use
DB
•  Customer concerns
•  App qualification required OS OS
•  Requires OS and DB standardization
•  Isolation

Private Database Cloud Deployment
Schema Consolidation - Provision a Schema
•  Most efficient
•  Highest consolidation density. Capability to consolidate large number of
applications.
•  Efficient use of memory. Single large SGA opposed to several disparate SGAs
•  Minimizes items to manage. Less OS, databases, and configurations to manage
•  Reduces overall operational costs and overhead
•  Extremely fast provisioning DW ERP CRM
•  Provisioning is simply a schema and tablespace creation
DB
•  Performance
•  Native performance
OS OS

Schema Consolidation Considerations
•  Requires OS and DB standardization
•  Application certification required
•  Isolation Management

Greatest consolidation, maximum ROI
Database Cloud
Schema
ROI
Database
Infrastructure Storage
Cloud
Servers
Consolidation

A View of the Private Database Cloud
Cloud, An Aggregation of Cloud Pools
Cloud Pool
Schema Consolidation
Cloud Pool
11gR1 Cloud Pool Infrastructure Cloud
Database Consolidation
Cloud Pool
Schema Consolidation
Dev/test Cloud
Pool
11gR2 Cloud Pool Infrastructure
Exadata - Database Consolidation Cloud

Cloud Architectural Assessment
Pick the architecture that best suits your needs
Infrastructure Database Schema

Business Value
Consolidation Consolidation Consolidation
Implementation Easy Easy Difficult*
Application Suitability Some All Some
Isolation Highest High Limited

Availability High Highest Highest
Scalability Limited Excellent Excellent
Consolidation Density Low High Highest
ROI Low High Highest

* = Need to ensure application schemas can co-exist
17 Copyright © 2011, Oracle and/or its affiliates. All rights reserved. © 2011 Oracle Corporation
Recommended Cloud Architectures
Each architecture has unique capabilities that warrant its use for
specific workloads:
Workload Type Optimal Cloud Architecture
Mission or Business Critical Deployment Database (Dedicated Pool)
Infrastructure,Database or
Packaged Applications
Schema
Data Warehouse Applications Database or Schema
Standardized environment Database or Schema
Internal Applications Database or Schema
Rapid provisioning (i.e. Test and Dev) Database or Infrastructure
Mixed workload consolidation Infrastructure

As-Is consolidation Infrastructure
PRIVATE DATABASE CLOUD PLANNING

Planning
•  Before designing and implementing a Discovery
Cloud, it is critical to carefully plan for
the deployment. Selling the Rationalize/
Plan Consolidate
•  Many of the Cloud benefits are

delivered from rationalizing the existing
Application
environment and standardizing the Migration
Architecture
Selection
deployment model.
Exception
Handling
•  A thorough and complete planning

phase will ensure that a customer’s
Cloud environment is optimal and
Cloud Planning Process
provides the most benefit.

Rationalize Infrastructure
•  IT rationalization determines the best use of IT services to reduce
non-productive redundancy in enterprise IT solutions
•  By standardizing on a set of building blocks, IT departments can

easily deploy pre-defined configurations and scale-out using modular
components.
•  Standardization results in a more homogeneous environment that is

easier to manage, lower cost, less complex, and more agile.

•  Can the customer reduce the number of OS and DB versions?

–  Standardizing OS & DB versions will result in improved ROI
–  Customers should look for opportunities to do this
•  Can the customer standardize its hardware infrastructure?

–  Reduce server and storage configurations
–  Consider pre-integrated hardware platforms (Exadata)
•  Can the customer standardize its workloads to run against a single

database?

How will the customer rationalize the Cloud infrastructure?
•  Can the customer reduce the number of OS and DB versions?
–  Standardizing OS & DB versions will result in improved ROI
–  Customers should look for opportunities to do this
•  Can the customer standardize its hardware infrastructure?

–  Reduce server and storage configurations
–  Consider pre-integrated hardware platforms (Exadata)
•  Can the customer standardize its workloads to run against a single

database?

Customer Case Study
Example of services for large commercial bank
Service Levels
Silver OLTP Gold OLTP Pla2num OLTP Pla2num OLAP Pla2num OLTP+OLAP
High Availability VM High Availability Dual Node Cluster 2N+1 Clustering 2N+1 Clustering 2N+1 Clustering
Support Hours Office Hours Only Extended Office Hours 24 x 7 24 x 7 24 x 7
Zero Data Loss Zero Data Loss Zero Data Loss Zero Data Loss Zero Data Loss
Disaster Recovery Point Objec2ve
2 Business Days < 4 Hours < 4 Hours < 4 Hours < 4 Hours
Disaster Recovery Time Objec2ve
Dedicated Benchmark Dedicated Benchmark Dedicated Benchmark
Not Defined Defined Minimum
Performance Environment Environment Environment
1 Weekly + Daily Incremental 1 Weekly + Daily incremental +

Historical Data Management Historical Data Management Historical Data Management
Backup REDO Logs
Point-‐in-‐Time Recovery
Enterprise TransacQon
Departmental ApplicaQons Line of Business ApplicaQons Enterprise Datawarehouse Near-‐Real Time AnalyQcs
Typical Applica2ons Processing ApplicaQons
Infrastructure Database Database

Cloud Cloud Cloud
(OVM) (ODA) (on Exadata)

DB Cloud changes how you think about deployment
•  Tenant Isolation
•  Resource
•  Operational
•  Security
•  Fault
•  Bottom line : Contain “Noisy” neighbor

•  Resource Management
–  Enable Instance Caging with default resource plan
–  Enable Resource Profile limits
–  Enable Oracle QoS Management

•  Trades-off resources just-in-time to maintain SLAs
•  Ensure business critical applications get serviced and meet response
time SLAs
–  Quarantine application by shutting down service or move workload

•  Instance Caging: Partitioning Approach
Provides maximum isolation

16 CPUs 32
28
DBA DBB DBC DBD

•  For performance-critical databases
24
20
•  If one database instance is idle,
its CPU allocation is unused 16
Instance D: 4 CPUs
12
Instance C: 4 CPUs
8
Instance B: 4 CPUs
16 OS 4
•  Set CPU_COUNT minimally to 2 Instance A: 4 CPUs
0

•  Instance Caging: Over-Provisioning Approach
•  Best used for non-critical databases that
are typically well-behaved 22 CPUs 32
28
DBA DBB DBC DBD

•  Best approach if the goal 24
is fully utilized CPUs
20
Instance D: 8 CPUs
16
•  CPU contention typically not enough
contention to destabilize OS or DB 12
Instance C: 6 CPUs
instances 8
•  If assumptions listed are met. Instance B: 4 CPUs
16 OS 4
•  If the load is significant and of Instance A: 4 CPUs
longer duration, system stability 0
can get impacted.

•  Patch and Upgrade
–  Define a Patching and planned outage strategy
–  Leverage Rolling Upgrades
•  Minimize downtime using out of place patching
•  Leverage 11.2 Standby Apply First feature
–  Emergency patch scenarios for specific application
•  Clone new ORACLE_HOME
•  Unplug/plug schema using TTS into new database but same diskgroup
•  Patch the new database and new ORACLE_HOME

•  Recovery strategies
–  How you backup affects your recoverability
–  Recovery Granularity Objective (RGO) becomes very important
–  Recover the application using least impacting method
•  Flashback technologies (Flashback transaction, table, query)
•  TTS/PIT recovery or Datapump restore
•  Flashback DB

•  Security Management
–  Only Cloud DBA should have SYSDBA, SYSOPER and SYSASM
privileges
–  Tenant DBAs should only have schema level access
–  Use database roles and privileges to further limit data access
–  Secure each application/schema with an Oracle Database Vault Realm
–  Deploy Multi-factor rules to enforce who, where, when, and how data is
accessed
–  Enable encryption on the tablespace

Provisioning
How will tenants request Cloud Services?
POLL:
•  How many customers have implemented Self-Service
Provisioning?
–  If so, what tools or products are they using
•  How are customers implementing IT Provisioning?

–  What is the workflow process
•  What is the turnaround time for typically database

deployments?
Planning
Database Cloud Considerations
•  What type of database provisioning
–  Self Service
•  Requires a robust Self Service Catalog
•  Need UI for provisioning
•  Provisioning Workflow
–  IT Based
•  Very Manual
•  Need a method for queuing and reconcillation

Metering and Chargeback
Customer Consideration and Questions
POLL
•  How many customers have or will implement chargeback
–  What chargeback tools are used, are they home grown or off-the-
shelf?
–  How are customers measuring resource consumption?

Planning
Metering-Chargeback Considerations
•  Chargeback
–  Provides cost relief
–  Chargeback is a good mechanism to prevent database sprawl
–  Many customers have chosen not to implement any chargeback
•  Show-back
–  Don’t actually do chargeback, but do “show-back “
–  Makes tenants and consumers cost conscious and consumption aware
–  Provides accounting of usage patterns
–  Can easily switch to chargeback model if needed.

What are your Chargeback models?
•  Typical Fixed Costs
•  Tenancy (i.e. Monthly charge, configuration)
•  Resource allocations (storage, CPU)
•  Deployment options - Data Guard, GoldenGate, etc.
•  Service levels
–  Charge for addiQonal service level support or higher availability
•  Typical Variable Costs

•  Resource utilization
–  CPU Used - peak, average, time of day (common)
–  Network, IOPS (rarer), Storage
Do you charge for operational changes?
•  Service charge for operational changes
–  Prevents excessive changes in the environment
–  Define quantity and type of pre-paid operational requests.
•  What is considered an additional request (i.e. first 3 change
requests could be built-in to the deployment)?
–  Additional changes in a calendar year are subject to cost/
change
•  Init.ora change
•  Create test/dev environment
•  Additional physical backup
•  Additional Patching
DB Cloud Planning
Application Migration Readiness
•  Applications may be in various states of technical readiness for a cloud
environment, based on application characteristics and requirements
–  Name-space conflicts (relevant for schema consolidation)
–  Character set requirements (relevant for schema consolidation)
–  I/O rate requirements
•  Applications may have business constraints on their ability to be migrated to

the cloud
–  Service level agreements
–  Security
–  Compliant restrictions – PCI-DSS, HIPPA, etc. datasets cannot be co-
mingled

DB Cloud Planning
Application Migration Readiness
•  Special requirements for a given application may make it difficult to migrate
•  Decide whether the cloud will be used for new deployments only, or existing
deployments as well
•  Determine when applications will be migrated
–  During an existing maintenance window?
–  As part of a stand alone event for the application to be migrated?
•  Plan a migration process that will cause minimal disruption
•  Choose applications that will provide the biggest benefit
•  Choose “low hanging fruit” first; Go for quick wins
•  Ensure that early migrations are successful!

Application Selection
Customer Example
1 .... 19 ...
2 .... 20 ...)
Immediate Platform 3 21
No .... ..
candidates 35
4 22
constraints .... ...
5 .. 23 ...
37 6 24
34 28 26
23 .... ...
13 10 7 25
2 25 3 .... ...
11
Constraint to Migrate
29 24 8 ... 26 ...
27 12
30 31 9 27 ...
...
10 .. 28 ...
11 ... 29 ...
22 6
Unlikely to be 17
12 ... 30 ....
33 15 13 31
migrated 32
16
... ...
8 9 14 ... 32 ...
15 33 ....
...
16 ... 34 ...
21 5 18 17 ... 35 ....
14 18 . 36 ...
37 ....
4
7 36 Workload Legend
1 19 20 OLTP
Many Longer term Platform OLQP
constraints prospects DW /BI
Not Ready Technical readiness for the Platform Very Ready Hybrid

Best Practices
Consolidate & Share as much as possible
•  Dedicate resources to pools Physical resources 16 CPUs
Servers
DBADBBDBCDBD
•  Share as much as possible CPU, Memory
within a pool Storage
–  Dedicate when necessary to Capacity, IOPS
meet SLAs Network
–  Some resources should not be Logical resources 16 OS
shared OS images, Homes,
Instances, Schemas,
•  Partitioning vs. Over- Configurations
32 32
28
subscription models 24
28
24
20
•  Focus on both physical and 16
20
16
Instance D: 8 CPUs
logical resources
Instance D: 4 CPUs
12 12 Instance C: 6 CPUs
Instance C: 4 CPUs
8 8
Instance B: 4 CPUs
4 4 Instance B: 4 CPUs
0 Instance A: 4 CPUs
0 Instance A: 4 CPUs

Best Practices
Implement Dynamic DB Services
Load Balancing
•  Dynamic Database Services Load Balance Advisory
enable Cloud functionality Connection Load Balancing
–  Virtualize service location Runtime Load Balancing
–  Availability Agility
SCAN
–  Agility Availability
–  Resource management Fast Application Notification
Fast Connection Failover
–  Performance
Transparent Application Failover
Performance
Data affinity
•  Required to get most value from Temporal affinity
deployment

How are Customers Deploying Private Database
Cloud
–  Some call it by a different name - OaaS, DBaaS, Private Oracle Cloud
–  Most use modularized building blocks (standard server type, storage,
network)
–  Typically use fixed number of Cloud Pool nodes with Data Guard for DR
–  Schema Consolidation very common consolidation model for in-house
applications
•  Typically configurations
•  Typically 20-30 consolidated schemas in Schema Consolidation Model and
10-20 databases in Database Consolidation Model
•  Use Database Vault and/or tablespace encryption (ASO) andDatabase
Resource Manager

ENGINEERED SOLUTIONS

Build vs Buy
•  Build-your-own Database Cloud
–  Requires customers to purchase, validate and configure all
components
–  Must ensure all components are certified with each other
–  Requires installing and testing of configuration
•  Exadata is a pre-built environment for Database Clouds
–  Pre-tested, pre-configured, pre-installed
–  All components are ensured to work together
–  Reduces overall time-to-market

The Evolution of the DBA
Kind of DBA Timeline
CLI DBA Early 90’s DBAs
GUI DBA Late 90’s and Dot Com
Google DBA Dot Com and 2000’s
iDBA Dot Com, IOUG iDBA Master Curriculum
RAC DBAs 2000+ a[er 9.2 (but major spike with 10.2)
DMA 2010+ Database Machine Administrator
vDBA / vRAC DBA 2010+ Evolving role of a DBA in the virtual world
Cloud DBA 2011+

Oracle Engineered SoluQons

•  All Engineered Systems are the same
•  Delivered tested and ready-to-run
•  Highly optimized
•  No unique configuration issues
•  Runs existing OLTP and DW applications
–  No special certification required
•  Features optimized for mixed workloads
–  IORM, DBRM

Why Exadata
Storage
Flash Index
Instance Cache
Caging XTreme Performance
Up to 1.5 Million IOPs
Infiniband – 40gigE
EHCC
IORM
DBRM DBFS

Oracle Database Appliance (ODA)
•  4 TB of Usable Space Triple Mirrored
•  All of RAC Best Practices in a box
•  4 SSD for Redo Logs and performance
•  Ideal for SMB
•  Pre-configured - ready to use out of the box
•  Leverage ZFS to increase
•  Provision in hours not weeks
storage requirements beyond
4TB
•  Leverage ZFS with HCC

Support

Business Drivers
•  Reduce number of databases
•  Reduce OpEx
–  Cost to managed services provider for tape backups
–  Less number of personnel to manage the Exa Stack
•  Reduce CapEx
–  Reduce storage requirements with HCC

Private Cloud Database Consolidation
•  Oracle enables all levels of consolidation
–  Infrastructure, Database, Schema
•  The higher the consolidation density
–  The greater the return on investment
•  Oracle Exadata Database Machine
–  Ideal Private Cloud consolidation platform
–  Fastest time-to-market
•  Customers already saving with consolidation

Backup Architecture Infiniband
GigE
D2D Forever Incrementals Exadata 1/4 Rack
Exadata 1/2 Rack ZFSSA
Development
Production Production
IB1 Leaf Switch-A
IB2 Leaf Switch-B
Net0 for Mgt and Data

IB1 Leaf Switch-A
IB2 Leaf Switch-B
ZFSSA
DR
Non-EXA Non-EXA
Production Development

Tiered Storage Model – Customer Case Study
•  Leverage high transactional data on
DATA disk group as Tier 1 storage
Tier1
DATA •  Move data that is older than 3
months from Tier 1 to Tier 2
Tier2
RECO
•  Move data that is older than 3 years
from Tier 2 to Tier 3
Tier3
ZFSSA •  Free up 11+ TB of storage from
RECO disk group

Information Life Cycle Management
Save more space as you go to the ZFSSA
•  Leverage Warehouse Compression for Tier
1 storage
Tier1
DATA
•  Leverage Partitioning strategy to
move data from different tiers of
storage
Tier2 •  Leverage Deeper HCC (Archive High) as we
RECO
move data from Tier 1 to Tier 2
•  Make Datafiles on Tier 2 storage to be

Tier3 READ-ONLY so that we can skip RMAN
ZFSSA backups (backup once and forget about it)
•  After three years convert data to external

tables or move the datafiles to the ZFS

Benefits of ZFS Appliance
•  With Exadata, we can only perform backups over network
•  Perform disk to disk backups over extremely low latency 40 GigE
Infiniband
•  Leverage Oracle’s Direct NFS
•  Provides deep de-duplication and Exadata Hybrid Columnar
Compression (EHCC)
•  Provides cloning capabilities
•  Perform backups and restores of 4+ TB Per hour

Summary - Roadmap to Database Cloud
Oracle
DB-as-a-Service
Oracle DB Service
Catalog
Oracle DB on
Exadata
Standardize on
Oracle
Heterogeneous DB
Environments

Summary
•  Private Database Clouds consolidate servers, storage, operating systems,
databases, and workloads
–  Many customers are successfully deploying Private Database Clouds today
–  They are benefiting from high quality of service, low cost, reduced complexity and
increased agility
•  Oracle EM 12c provides customers with end to end Cloud Management

–  Self-service paradigm for database deployment and management
–  On-demand scalability of underlying platform
–  Metering and chargeback for IT accountability
–  Extreme “agility” for developers, with “enterprise” control for IT

Expert Panel:
The Perfect Marriage: Oracle Exadata Exadata Data Protection Best
with Sun ZFS Storage Appliance Practices
Session ID: UGF4410 Session ID: CON8435
Sunday 30-SEP-2012 9:00AM 10/1/12 (Monday) 12:15 PM
Moscone West - 2018
Moscone South - 252
Questions ?


Content
•  Oracle Cloud Site :
•  http://www.oracle.com/technetwork/database/focus-areas/database-cloud/index.html
•  Private Database Cloud White Papers
–  Database Consolidation onto Private Clouds
–  Private Database Cloud on Oracle Database Appliance
–  Best Practices for Database Consolidation in Private Clouds
–  Best Practices for Database Consolidation on Exadata Database Machine
–  Multiple Public Networks in Private Database Clouds Network
–  Isolation in Private Database Clouds
•  DbaaS Cookbook
http://www.oracle.com/technetwork/oem/cloud-mgmt/em12c-dbaas-cookbook-1432364.pdf


Private Database Cloud

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Private Database Cloud

Enviado por

Direitos autorais:

Formatos disponíveis

Private Database Cloud

Database Consolidation Planning and Best Practices

• Oracle Product Strategy and Private Cloud Evangelist

• 17 Years with Oracle, 10 years Oracle RAC development

• Over 24 years of Oracle Expertise, RAC, Data Guard, ASM, RMAN

• Private Database Cloud Evangelist and author of the Cloud Best

2 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

3 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

• Why Database Cloud Consolidation

• Private Database Cloud deployment models

• Database Cloud Consolidation Planning and Considerations

• Engineered Solutions and the Private Database Cloud

4 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

Cloud computing is a model for enabling convenient, on-demand

5 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

Private Cloud Managed Cloud Services Public Cloud

Build Managed Subscribe

Customer owns, hosts Customer owns. Customer subscribes.

6 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

7 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

IT Professional Developer Business End User

8 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

Infrastructure Cloud Database Cloud

Hypervisor Hypervisor Platform Platform Platform Platform

Server Consolidation Database Consolidation Schema Consolidation

9 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

• Lower consolidation density Hypervisor

10 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

• Supports any app

11 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

12 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

• Provisioning is simply a schema and tablespace creation

13 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

• Application certification required

14 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

© 2011 Oracle Corporation

16 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

Infrastructure Database Schema

Implementation Easy Easy Difficult*

Application Suitability Some All Some

Isolation Highest High Limited

Consolidation Density Low High Highest

ROI Low High Highest

Mission or Business Critical Deployment Database (Dedicated Pool)

Rapid provisioning (i.e. Test and Dev) Database or Infrastructure

Mixed workload consolidation Infrastructure

19 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

• Many of the Cloud benefits are

• A thorough and complete planning

20 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

• By standardizing on a set of building blocks, IT departments can

• Standardization results in a more homogeneous environment that is

21 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

• Can the customer reduce the number of OS and DB versions?

• Can the customer standardize its hardware infrastructure?

• Can the customer standardize its workloads to run against a single

22 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

• Can the customer standardize its hardware infrastructure?

• Can the customer standardize its workloads to run against a single

23 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

1 Weekly + Daily Incremental 1 Weekly + Daily incremental +

Infrastructure Database Database

24 Copyright © 2011, Oracle and/or its affiliates. All rights reserved.

• Bottom line : Contain “Noisy” neighbor

•  Oracle Product Strategy and Private Cloud Evangelist

•  17 Years with Oracle, 10 years Oracle RAC development

•  Over 24 years of Oracle Expertise, RAC, Data Guard, ASM, RMAN

•  Private Database Cloud Evangelist and author of the Cloud Best

•  Why Database Cloud Consolidation

•  Private Database Cloud deployment models

•  Database Cloud Consolidation Planning and Considerations

•  Engineered Solutions and the Private Database Cloud

•  Lower consolidation density Hypervisor

•  Supports any app

•  Provisioning is simply a schema and tablespace creation

•  Application certification required

•  Many of the Cloud benefits are

•  A thorough and complete planning

•  By standardizing on a set of building blocks, IT departments can

•  Standardization results in a more homogeneous environment that is

•  Can the customer reduce the number of OS and DB versions?

•  Can the customer standardize its hardware infrastructure?

•  Can the customer standardize its workloads to run against a single

•  Can the customer standardize its hardware infrastructure?

•  Can the customer standardize its workloads to run against a single

•  Bottom line : Contain “Noisy” neighbor

–  Enable Resource Profile limits

–  Enable Oracle QoS Management

•  How are customers implementing IT Provisioning?

•  What is the turnaround time for typically database

•  Typical Variable Costs

•  Applications may have business constraints on their ability to be migrated to

•  Leverage ZFS with HCC

•  Make Datafiles on Tier 2 storage to be

•  After three years convert data to external

•  Oracle EM 12c provides customers with end to end Cloud Management