enterprise manager dbaas


Enterprise Manager DBaaS: Database, Schema, or Terabytes of Data in Minutes

Adeesh FulayConsulting Product Manager

Matthew McKerleyVice President of Development

Nilanjay Bhattacharjee Assistant Vice President IT, HDFCBANK LTD


Description Session: CON9530

Title: Oracle Enterprise Manager DBaaS: Database, Schema, or Terabytes of Data in Minutes

Description: Database as a service (DBaaS) is the latest trend in providing automated database services to a wide set of end users. In this session, you will learn about the latest features in DBaaS, including schema-based consolidation, thin provisioning of data, and other exciting features.


Safe Harbor

The following is intended to outline our general product direction. It is intended for information purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described for Oracle’s products remains at the sole discretion of Oracle.


What is DBaaS?

Key Challenges

Oracle’s Cloud Solution

– Database and Schema Consolidation

– Rapid Template based Provisioning

– Data Cloning (Storage Copy on Write and RMAN Backups)

Customer Story – HDFC Bank

Table of Contents


Total Cloud Control

Complete Cloud Lifecycle Management

Integrated Cloud Stack Management

Business-Driven Application Management

Self-Service IT Simple and Automated Business Driven | |


Customers Have a Choice of Clouds

Private Cloud Public CloudHybrid Cloud

• OpEx• Fast & inexpensive to start• Outsourced services• Multiple tenants sharing

resources

• CapEx & OpEx• Lower total costs• Control & visibility• Multiple apps sharing

resources

• Cloudbursting – overdraft for peak loads

• Dev/Test & production• B2B integration

Exclusive Shared by multiple organizations


Private PaaS• Enforces standardization and consolidation• Provides Security and Compliance• Maximizes component re-use• Minimizes hand coding• Maximizes flexibility and control

Private Cloud: PaaS vs IaaSIncreasing Enterprise value with Private PaaS


Three Key

Challenges

The problem of many and varied

Manual, time consuming provisioning

Data, lots of data!


Key Challenge 1: The problem of many and varied

Solution: Standardization and Consolidation


Need for Standardization and Consolidation

ServiceDelivery

“a mixture of versions, operating systems, hardware; rapidly falling

into legacy”

Highcost of operation

High cost of deployment

PoorUtilizationH/W, CPU,Storage

Workloadmultiple skills,lots of disparatesystems, poor automation

Poor service,long lead times

Complex and ever growing database estate


Consolidation at PaaS and IaaS Layers

App

IaaS

PaaS

Consolidate onto shared IaaS without standardization

Consolidate onto standard, shared and elastically scalable PaaS

vs.

App App

App App App

App App App

• Cost savings from less hardware, power and data center space

• Software stack heterogeneity, cost and complexity persists

• No administration (O&M) cost savings

• Standardized PaaS for all applications reduces heterogeneity, cost and complexity

• Accelerated new application development• Cost savings from less hardware, power and

data center space


DBaaS Cloud ModelsInfrastructure Cloud

Shared ServerShared pool of hypervisors

Hypervisor

CRMDW ERP

OS

DB

OS

DB

OS

DB

OS

ERPDW CRM

DB

OS

DB

DB

Database Cloud

Shared ClusterShared pool of servers

OS

ERPDW CRM

OS

DB

Database Cloud

Increasing Consolidation

Shared DatabaseShared database instances


Considerations for Choosing the Right Model

Brownfield or Greenfield? Commodity Servers Vs Engineered Systems? Applications to be deployed, and their database footprint? Expected SLAs from business users? Isolation or Security requirements? Ease of management? Available skill set? Is self service needed? If yes, who is the user, and what do they expect from

this service?

Most Customers Settle On a Combination these Models


Comparison of DBaaS Cloud ModelsShared Server Shared Cluster Shared Database

Consolidation Density

Low High Highest

Maintenance Very complex (VM Sprawl) EasyEasy to Involved (based on required resource isolation)

ROI Low (Server and Storage Only)

High (Servers, storage, and OS)

Highest (Servers, Storage, OS, and DB)

Isolation Excellent Good Least

Implementation & Onboarding

Easy EasyDifficult (standardize on DB

and OS version)

Application Suitability

Some (excessive in many cases)

AllHome grown; requires app

validation


Examples of DBaaS Cloud Model Usage

Shared Server

Junior DBABuild test environment to verify a database patch

Application DeveloperProvision application middleware and database on the same VM

Shared Cluster

Application DBAProvision database for a complex packaged application e.g. eBiz

Application TesterClone a production database for performance testing

Shared Database

Application DeveloperProvision one or more schemas for a homegrown custom application

Sales EngineerProvision schema with data for a training app


Key Challenge 2: Manual and admin based provisioning

Solution: Rapid provisioning of Standardized Templates


Traditional App Deployment(Admin driven)

Database-as-a-Service Deployment(End-user driven)Specify and procure

hardware

Configure hardware

Deploy hardware

Deploy operating system and configure storage

Deploy database

Request database deployment

Adjust capacity as demand changes

Self-Service ProvisioningSelf-Service Provisioning

Retire database when not needed

Database

Server Hardware

OS and Storage

DEPLOYMENT PORTAL

User unaware of underlying infra

Databases

Need for Rapid Template based Provisioning


EM 12c: Most Comprehensive DBaaS Solution

Self service paradigm for database deployment and management

– Pre-packaged, pre-configured database configurations

– One-click provisioning and deployment of databases

– On-demand scalability of underlying platform

Support for all three DBaaS deployment models Metering and chargeback/showback for IT

accountability Data cloning using Storage copy on write and RMAN

Backups Intelligent Auto-placement, Quota Management, Role

based access, and so on ..


Schema as a Service

• Ultimate consolidation of databases (shared database deployment model)

• Each application user gets one or more database schema(s)

• Service level guarantee through Database Resource Manager

• Security isolation through Data Vault

• Integrated with Database 12c Pluggable Databases• Multiple pluggable databases within a single container

database


Schema as a Service User: Portal• Out-of-box console ; no additional

set up required– Supports custom background

• Rich service catalog:- Database instances- Schemas

• Database portal functions– List all databases and

schemas– List requests, quota usage,

and notifications– Resource Monitoring– Backup/restore

• RESTful Web Service based APIs and CLIs


Schema as a Service User: Features

A ‘Schema’ request provides– 1 Database (Application) Service

– N schemas/users

– 1 master account that has grants over other schemas

– 1 tablespace

Request for a ‘Schema’ instance– Choose service templates with/without seed data

– Rename and set passwords for schemas

– Upload custom SQL scripts for execution

– Pick duration

Home page for management of provisioned instances


DBaaS Setup: Schema as a ServiceRoles and Responsibilities

Provision Databases

Setup Zones and Pools

Create Profiles

Publish Service Templates to Service Catalog

Set Quota, and Metering & Chargeback

Provision Servers, Storage, and Network

Manage Cloud Resources

Configure EM and Software Library

Setup Roles and Users

Manage Security and Policies

Cloud Administrator Self Service Administrator


DBaaS Cloud Resource Model

PaaS Zone Collection of various pools – MW & DB Based on geography, cost center, …

Database Pool Defines a homogeneous collection of Databases

or Oracle Homes

Mandatory criteria - platform, db version, availability (SI/RAC) Optional criteria - SLAs, security, product lifecycle, …

Databases and Oracle Homes – Single instance and clustered

N = NodeSI = Single InstanceRAC = Real Application Clusters

4N RAC DB 11.2.0.3

RAC 11.2.0.2

RAC 11.2.0.2

SI 10.2.0.5

SI 10.2.0.5

SI 10.2.0.5


Setup Service CatalogCapture -> Publish to Catalog

Capture Database Provisioning Profiles• Capture schema and data from existing databases• Uses datapump for export/import

Publish Service Template to Service Catalog• Schemas with or without data and objects• Assign roles and privileges for master account• Register pre and post creation SQL• Tablespace encryption for secure environments


Setup Service Catalog contd.Workload Sizing and Placement

Placement Algorithm• Simple: By number of services• Advanced: Based on projected workload characteristics

Workload Sizes• Based on projected usage of CPU, Memory, and Storage• Define Small/ Medium/ Large workloads• Attach to Service Templates

• Resource Manager for CPU allocation• Fixed Datafile Size for storage allocation

Resource Management

Intelligent Placement

Capacity Planning

Service Level Guarantees


Chargeback Reporting

• Rollup based on LDAP hierarchy

• Summary and Trending reports for Usage and Charge

• Drilldowns

Chargeback Administrator Self-Service Portal User Line of Business User

• Charge Trend reports broken down by resource

• Selectable detail levels

• Charge Plan configuration

• Integrate with BI Publisher

• Generate Reports in variety of formats

• Excel, Word, HTML, PowerPoint, PDF

• Email or FTP reports


Chargeback Database Metrics

Database Instance Shared Database (Service)

Configuration

Edition

Memory Usage

Option

Storage Usage

Release

Version

RAC Node Count

Option

Edition

Release

RAC Node Count

Usage

CPU Time

CPU Utilization (%)

CPU Utilization (SPECInt)

Network IO

Disk Read (Physical) Operations

Disk Write (Physical) Operations

SQL Executes

User Transactions

CPU Time Per Service

CPU Utilization Per Service

DB Time Per Service

Disk Read (Physical) Operations Per Service

Disk Write (Physical) Operations Per Service

SQL Executes Per Service

User Transactions Per Service


Key Challenge 3: Data, lots of data!

Solution: Data Cloning using Storage copy-on-write technology and RMAN backups


Data Cloning Overview

Functional Testing of Applications– Most functional tests require minimal data changes

– Testers frequently need to rollback data

Most storage based solutions lack lifecycle management capabilities– DBA Friendly. Clone ‘Databases’ instead of ‘Storage Volumes’

– Monitoring and configuration management of the cloned database

– Upstream Test Master creation workflows (integrated with Masking, Subsetting, etc)

– Monitor, implement quota and chargeback based on QoS


Data Cloning OptionsTechnology Comparison

• Storage based technology• Saves space and time• Ideal for "use and throw“ i.e. short lived databases• Storage Admin involved

• Oracle Database based technology; Storage neutral

• Restore time proportional to backup size

• Leverages existing technology and infrastructure

• Completely managed by DBAs

Data Cloning

Copy on Write RMAN Backup


Database Instant Cloning Using Copy on Write

NAME SSN SALARY

AGUILAR 203-33-3234 40,000

BENSON 323-22-2943 60,000

Test MasterDatabase

NAME SSN SALARY

MILLER 112-23-456740,000

SMITH 111-22-333360,000

Masking &Sub setting

ProductionDatabase

010110011101001010000111010 Functional Copies – User

can create multiple copies for functional testing without consuming space

• Initial Support for Sun ZFS Storage and NetApp Storage

• More than just storage volume cloning• Users can create snapshots and ‘timetravel’ to an

earlier snapshot


DBaaS Setup: Database Instant CloningRoles and Responsibilities

Enable Databases for cloning


Create Profiles using Storage Snapshots










Database Cloning Using RMAN Backups

RMAN Duplicate

1. Backup-Based Duplication With a Target Connection

2. Backup-Based Duplication Without a Target Connection

3. Backup-Based Duplication Without a Target Connection or a Recovery Catalog Connection

1

2

Connect Target

Connect Catalog

Connect Auxillary

3


DBaaS Setup: RMAN BackupsRoles and Responsibilities

Stage RMAN Backup Archives


Create Profiles using RMAN Backups










HDFC BANK DBaaS Journey into Oracle Database Cloud with EM12c

Nilanjay BhattacharjeeAssistant Vice President ITLead Database COE


About HDFC Bank

• Incorporated in August 1994 • India’s second largest Private Bank with a nationwide network of

– Branches: 2,564– ATMs: 10,000 (In 1,416 Indian towns and cities) & 20 million customers

– Debit Cards: 14.9 Million – Credit Cards: 5.8 Million

• Industry: Retail & Corporate Banking

• Employees: 56,000

• Revenue: USD 5 Billion

Business Drivers

• Retail Assets Segment [Lending Business]

• 50% of HDFC Bank’s Top Line

• Always under pressure to launch “New Schemes” to compete and stay ahead in this segment

• IT must respond to this Business need because each new Scheme means – changes to application and testing against Production data [UAT database]

• Agility in launching new business initiatives

Life Before Database Cloud

• Average 3.5 days to provision UAT Database for Loan Management Application

• Silo’ed environment with Average 30% utilization

• Compliance requirement consume UAT testing resources.

• DBA activities mean $$ paid to SI for provisioning databases manually

• Overhead in managing configuration drift between production and test environments.

• Rollout impact/delay on new business initiatives

Database Consolidation – Application Classification• Classify application based on system availability requirement/criticality

System classification Application Classification

Tier 1 Top 15 in terms of systemic risk Customer facing mission critical systems

Tier 2 Top end & middle tier High visibility & enterprise wide usage

Tier 3 Bottom end of middle tier Smaller user base but critical business function

Tier 4 Low tier Surround Systems - Satellite system build around core system

Database Consolidation Planning• Identify candidate application for Cloud • Further Group them based on availability requirement and sub classification based on OS/DB

Cloud Zone Zone based on criticality Sub category based on version

Exadata Zone Highly critical 11g zone UAT system 11g zone (For pilot)

AIX zone Highly Critical 10 g zone

11g zone UAT system 11g zone (For pilot)

Windows Medium critical 11g zone 10g zone

Database Cloud Solution Architecture

• Zones Exadata Zone AIX zone

• Role for each application on Exadata and AIX zone• Quota is set based on existing infra available

7 Databases on LOS Application 5 Databases on LMS Application 5 Databases on Web collection Application

• Universal charge plan• Service Templates

Exadata -Three templates with data Exadata -Three templates with only structure AIX template for Small, Medium, Large database only structure

Cloud Administration Setup

Provision Databases using RMAN Backups• Beta Customer for RMAN restoration integration feature with DBaaS• Level 0 RMAN Backups of Production Databases from

Standby[Bunker Copies]• Service Templates created for each of Level 0 Backups• Process to Provision Databases through RMAN is same as Empty

Databases

Life after Database Cloud Go-live – Time to Provision Sno List of activity during New DB infra requirement

1 IT team fill tech questionnaire and submit for discussion 0.5 0.5 02 Discussion and TCO in 3 days from discussion 3 0 03 Floating of funding proposal based on TCO 10 0 04 Approved funding raising PO for infra procurement 3 0 05 Delivery of server and infra structure 28 0 06 Asset code allocation and movement to DC 3 0 07 OS and other infra configuration 3 0 08 Identify server (compute+ memory ) 0 0.5 09 Storage allocation and publishing for new DB instance 3 0 0

10 Database installation and database creation 1 1 011 Database restoration 1 1 312 OEM or monitoring configuration 0.5 0.5 0

Day 56 Day 3.5 Hour 3

If Da

taba

se in

fra no

t availa

ble tim

e take

n

If Da

taba

se in

fra available time take

n

Post DBa

aS im

plen

tatio

n using EM

12c

Total time taken in days /hour


Summary DBaaS supports three different DBaaS models

– Database in a dedicated VM

– Databases in a shared cluster or installation, and

– Schemas in a shared database

Special focus on data cloning– Storage copy-on-write technology, and

– RMAN backups

Out of box portal to deliver all types of services


DBaaS is the Sweet Spot for Enterprise Clouds

Business

• Faster time-to-market

• Optimum utilization of development resources

• Quantifies cost and liability

Development

• No waiting days for provisioning environments

• Focus on application development instead of environments

• Minimize friction

IT

• Offer flexibility, while retaining control

• Quantifies business accountability

• Prevents platform-creep in development environments

• Makes your developers happy

Benefits All Stakeholders


Graphic Section Divider

enterprise manager dbaas

Technology

oracle andor

solediscretion of oracle

information purposes

hdfcbank ltd2 copyright

timesinto legacy11 copyright

shared iaas cost savings

service dbaas

cost andcomplexity