welcome to dbaas technical trainingfor...• provide oem (grid control) access privileges •...

Welcome to DBaaS Technical Training

Database as a Service

2Copyright © Texas Data Center Services 2013. All Rights Reserved

Introduction to Database as a Service| April 26, 2013

Database-as-a-Service

Platform Overview

Najam QureshiMythics, Inc

DBaaS on the Exadata Platform: Agency Value

Mission impact

Quicker Time to Use

You Can Do More

IT Cost Savings

Assets

HW

SW

Operations

Green

Support

Reduce Complexity

Standardize

Consolidate

Automated Support

Significant storage and backup savingsHelps drive datacenter consolidationDo more for lower costs

Software is included. No licensing costs

Shrink data center sprawl

One vendor to call

Lowers cost of support while increasing maintainability

One admin team, one tool set, etc.

Uses common infrastructure services

A full array of Oracle software and the latest in hardware is included

Pre-configured out of the box

Reduces power and cooling costs

Agency Value

DBaaS Benefits

Reduce Complexity and Better SupportSingle vendor accountability: One call service and support for hardware software, network and storage.

Simplification: Moving parts integrated into a complete system, reducing risk, costs and downtime

Best practices: Includes a full complement of Oracle diagnostic, tuning and management tools. Security,

performance and monitoring all are administered using standardized processes

Improved PerformanceEngineered Platform: Specifically designed to do one thing exceedingly well

Increased Throughput via Reduced Storage Bottlenecks: Faster response time for both OLTP and Data

Warehouse requirements ensure users are not waiting on slow database system response

Continuity of operations: Hardware and software redundancy is built-in with no single points of failure ensuring

better continuity of operations and maximum uptime

Advanced monitoring: Advanced tools and administration capabilities to better monitor and manage

performance. Tools are reports are available to both the service management team and Agency’s DBA staff

Improve EfficiencyGreater Performance, Lower Power and Cooling: Leveraging the engineered system’s high levels of integration

results in higher system performance at lower KW/hrs

Optimized system: Balanced performance environment maximizes throughput without using ‘brut force

DBaaS Benefits, continued

Elasticity Rapidly Changeable: Changes in an Agency’s requirements resulting in changes to their DBaaS database

instances can be accommodated hours or days, not weeks or months.

Encourages ‘Right Sizing’: Agencies can size their database requirements for today’s current workloads, and

then scale up or down with seasonal demands or growth/decline in a service’s demand.

Rapid Provisioning Fast Initial Provisioning: An Agency’s initial DBaaS database instance can be created in about 30 days or less

Faster Adds or Drops of New Database Instance: Adding new database instances, or dropping those no longer

needed can occur in 10 days or less. Structural changes to existing database instances handled via a ‘ticket’

ReliabilityTexas DBaaS Has Engineered Reliability: By design, our DBaaS platform is reliable. There are no single points

of failure, Each platform has 4 to 8 compute node and 7 to 14 storage cells, with Oracle RAC and ASM

included.

Better Monitoring and Diagnostic: Advance monitoring capabilities via enhanced OEM provides early warning of

potential issues, and advanced diagnostic capabilities help speed finding the right resolution

Cost SavingsSave costs of licensing: Due to Exadata’s extreme performance, fewer resources are required and therefore a

lower number of licenses are needed to support the work load.

Standardized and Quick to Deploy

All Exadata Database Machines are the Same

Pre-tested and Completely Configured

Delivered Ready-to-Personalize

Highly Supportable via Single Vendor

Identical to Config Used by Oracle Engineering

Easily runs existing OLTP and DW applications

Database are easily migrated and configured

No special Exadata certification required

Solution is agnostic to current OS

Leverages a well known Oracle ecosystem

Skills, knowledge base, people, partners

Standardized on Oracle DB 11gR2

Exadata Architecture

A Complete System: Compute, Storage, Networking

Database Servers

64 or 128 Intel-based Processors

Up to 2 TB RAM

Special Hardened version of Oracle Linux

Oracle Database 11gR2

Storage Grid

84 or 168 Intel-based Processors

Up to 504 terabytes (raw disk)

Up to 26.4 terabytes Flash storage

Advanced Exadata Storage Software

Connectivity

Internal connectivity 2 x 40Gb/sec Infiniband

Datacenter 80GB/sec via multi 10GB/sec eNet

The Initial Texas DCS Exadata Database Machine

A Highly Redundant and Scalable Solution

4 x64 Dual-procesor Database Servers (Sun Fire X4170 M2)

48 cores (12 per server)

576 GB memory (144 GB per server)

10 GigE connectivity to Data Center

4 x Bonded 10GbE ports

7 Exadata Storage Server Cells

All with High Capacity 3 TB SAS disks

High Speed Flash - 2.6 TB

3 Sun Datacenter InfiniBand Switch 36

36-port Managed QDR (40Gb/s) switch

1 “Admin” Cisco Ethernet switch

Keyboard, Video, Mouse (KVM) hardware

Redundant Power Distributions Units (PDUs)

Exadata Machines at ADC and SDC

Exadata Hardware Architecture - Full Rack

Database Compute NodesIntelligent Storage Cells

InfiniBand Network

• Redundant Dual 40Gb/s switches

• Unified server & storage network

• 7 - 14 High-performance low-cost

storage servers

8 Dual-processor, 6 or 8 cores

48 - 128 cores total

Scaleable Grid of industry standard servers for Compute and Storage

Eliminates long-standing tradeoff between Scalability, Availability, Cost

• 252 - 504 TB High Capacity disk

• 2.6 - 26 TB PCI Flash

•Data mirrored across storage

servers

Traditional Platforms = Storage Bottlenecks

Today, database performance is very largely limited by storage throughputStorage systems limit data bandwidth from storage to database servers

Storage array have significant internal bottlenecks

SAN Storage has additional bottlenecks

Random I/O bottlenecks due to physical disk speeds

Data Bandwidth limits severely restrict performance for data warehousing

Random I/O limits performance of OLTP applications

Exadata is Database Servers and Smart Storage

Database ServersPerform database processing such as joins,

aggregation, etc.

Exadata Storage Server CellsStorage Server Cell… very smart storage,

Storage remains an independent tier

Off-Load Storage Management from Compute Nodes

Dedicated Computing Resources

Executes Hyper-Columnar Compression

Searches tables and indexes, filtering out data that is

not relevant to a query

Manages data encryption and decryption

independently of the Compute nodes

Simplicity, and robustness of storage appliance

Compute and Memory Intensive Processing

Data IntensiveProcessing

Onboarding Process Overview

Exadata – On-boarding Process Flow

Exadata – Scope of the Sandbox

• Sandbox is primarily provided for customers to experiment running Oracle database (DBaaS) on Exadata

• One extra small or small Sandbox Instance is provided per project upon request by the customer.

• The trail period is usually 60 days.• Once the trail period is over, the sandbox is decommissioned or converted

to a billable instance• Simple one-time migration ( Export/Import) may be supported• Complex database migration ( schema consolidation, phased migration) is

not supported in the sandbox environment• Backup/monitoring/additional storage are not supported

Exadata – Acceptance Criteria

• Acceptance Period – with in 30 days• Setup Database Instances according to approved SDP/CET• Ensure DB Connectivity from LDC/SDC network• Provide OEM (Grid Control) Access Privileges• Verification of the database connectivity and configuration by customer• Database Migration is a separate activity

• DBA to provide support for data migration according to the project schedule




DBaaS Migration


Oracle DBaaS Product Catalog

Offering Catalog Cores Memory StorageEquv.Server

Entry/Very Small 1 6 GB 100GB Min2 - 3 Cores, 12 GB RAM~ 500 GB

Small/Typical 2 12 GB 200GB Min

4 - 6 Cores, 24 GB RAM~ 1000 GB

Medium/Demanding

4 24 GB 300GB Min

8 -12 Cores, 48 GB RAM~ 1500 GB

Large/Complex 8 36 GB 400GB Min

16 -24 Cores, 72 GB RAM~ 2000 GB

Extra RAM and/or Storage can be added to meet mission requirements

Oracle DBaaS Product Catalog – Cont.

DBaaS Exadata

Assessed size Small - Silver Medium - Silver Large - Silver

Oracle version 11 R2 RDBMS 11 R2 RDBMS 11 R2 RDBMS

Core(s) 2 cores 4 cores 8 cores

Memory (GB) 12 GB 24 GB 36 GB

Database Disk Storage 200 GB 300 GB 400 GB

OS disk space (GB) Local SAS shared disk Local SAS shared disk Local SAS shared disk

Oracle/Logs/etc. (GB) Local SAS shared disk Local SAS shared disk Local SAS shared disk

RAC nodes 2 node RAC 2 node RAC 2 node RAC

Disk fail-over Normal Redundancy (dual ) Normal Redundancy (dual ) Normal Redundancy (dual )

Number of storage servers 4 Cell Servers 4 Cell Servers 4 Cell Servers

IO Network TCP/IP TCP/IP TCP/IP

IO Network speed 40 GB 40 GB 40 GB

Flash Cache IO Read Enabled Enabled Enabled

Flash Cache IO Write Enabled Enabled Enabled

IORM Yes Yes Yes

Power fail-over enabled Dual setup Dual setup Dual setup

Backup/Recovery RMAN point-in-time recovery RMAN point-in-time recovery RMAN point-in-time recovery

Backup Compression Enabled Enabled Enabled

Backup Encryption Enabled Enabled Enabled

Data-Guard On-Demand On-Demand On-Demand

Fast Recovery Area 20 GB setup in ASM 20 GB setup in ASM 40 GB setup in ASM

Standard Compression OLTP OLTP OLTP

Advance Compression Exadata HCC Exadata HCC Exadata HCC

Encryption AES 256 AES 256 AES 256

Instance caging Yes Yes Yes

Scalable Yes Yes Yes

R2

10.2.0.2

7.3.4

8.0.6

8.1.7.4

9.0.1.4

9.2.0.4

R2

R2R2

DBaaS: Migration Path to 11gR2

No Premium Support Costs After Migration

10.1.0.5

DBaaS: Migration Path to 11gR2

Migration Strategy

Migration Methods

Scenarios

Migrating from 10gR2/11gR1 on big endian platform

Migrating from 10gR2/11gR1 on little endian platform

Bulk Data Movement

Logical Migration Methods

Method When to use

Data Pump Data type restriction with other methods

Oracle GoldenGate Minimal downtime requirement Different source

platform

What is Oracle Data Pump?

Enables very fast bulk data and metadata movement between

Oracle databases using expdp/impdp program.High-speed, parallel Export and Import utilities (expdp and

impdp) to copy data between different databases

10-20x Performance improvement compared to standard

exp/imp process.

Web-based Oracle Enterprise Manager 12C interface.

Data Pump – Features

DBaaS Logical migration – Agency Database

Migration Steps

Stop ApplicationRestart database to close all database connections.

Consistent Data Pump Exportexpdp system/***** r full=y directory=exp_data_dir dumpfile=full%$dbname.dmp parallel=4 logfile=full%dbname.log

Import Data using Data Pump ExportCopy export dmp file to DBaaS platform.

Load data (in parallel) using impdp program.

Impdp system/***** r schemas=app1,app2 directory=exp_data_dir dumpfile=full%$dbname.dmp parallel=4

logfile=full%dbname.log

Oracle GoldenGate 11g

Low-Impact Real-Time Data Integration & Transactional Replication

New DB/HW/OS/APP

Fully Active Distributed DB

Reporting Database

Data Warehouse

Global Data Centers

ODSData Integrator

Zero Downtime Upgrade & Migration

Query Offloading, Disaster Recovery

Data Synchronization across the Enterprise

Real-time BI, Operational

Reporting, MDM

Event Driven Architecture,

SOA

Highly Available / Disaster Recovery

Log-based,changed data

Database

Message Bus

Legacy

Message Bus

How Oracle GoldenGate Works

Source

Oracle & Non-Oracle

Database(s)

Target

Oracle & Non-Oracle

Database(s)

Capture: committed transactions are captured (and can be filtered) as

they occur by reading the transaction logs.


Source

Oracle & Non-Oracle

Database(s)

Target

Oracle & Non-Oracle

Database(s)



Trail: stages and queues data for routing.


Source

Oracle & Non-Oracle

Database(s)

Target

Oracle & Non-Oracle

Database(s)




Pump: distributes data for routing to target(s).


Source

Oracle & Non-Oracle

Database(s)

Target

Oracle & Non-Oracle

Database(s)





Route: data is compressed, encrypted for routing to

target(s).


Source

Oracle & Non-Oracle

Database(s)

Target

Oracle & Non-Oracle

Database(s)






target(s).Delivery: applies data with transaction

integrity, transforming the data as

required.






target(s).Delivery: applies data with transaction

integrity, transforming the data as

required.

Source

Oracle & Non-Oracle

Database(s)

Target

Oracle & Non-Oracle

Database(s)Bi-directional


Databases O/S and Platforms

Oracle GoldenGate Capture:

Oracle

DB2 for v 9.7

DB2 for v 10 on z/OS

Microsoft SQL Server for 2008 R1, R2

Sybase ASE, 15.5

Teradata

Enscribe

SQL/MP

SQL/MX

MySQL

JMS message queues

Oracle GoldenGate Delivery:

All listed above, plus:

TimesTen, IBM System I, Netezza & Greenplum

ETL product

Linux

Sun Solaris

Windows 2000, 2003, XP, 2008

HP NonStop

HP-UX

IBM AIX

IBM z Series

zLinux

31

Oracle GoldenGate 11g Supported Platforms

Eliminate Downtime During Upgrades to Oracle 11g R2Goldengate Active-Active Replication

• Zero database

downtime for

upgrades from 8i, 9i,

10g to 11g

• Leverage new

features of Oracle

Database 11g

without impacting

business operations

• Minimize risks with

failback optionFailback Data Flow

Oracle Database8i/9i/10g

DBaasOracle

Database11g Release 2

Application

Switchover

Compare & Verify

With Oracle GoldenGate

Veridata

Logical migration – Minimal downtime

GoldenGate

OverviewCreate and upgrade replica on DBMStop applyImplement best practices on replica (e.g. unload, recreate, reload)Start apply to catch upDisconnect users from primary, reconnect to DBM

Source system criteria10.1 or later on any platform (GoldenGate allows different DBMS, too)

Outage timeApplication reconnection

ConsiderArchivelog mode, LOGGING, and supplemental logging requiredData type supportCan apply catch up?




EM12c Capability – DBaaS Platform


What Makes Exadata Better?

Compute Intensive Processingat the Database Server

CPU intensive processing on

Results Pipelined from Storage

Server

• Complex JOINS

• Aggregation (GROUP BY, SORT)

• Functions on COLUMNS

• Data Conversion

I/O Intensive Processingat the Storage Server

Data intensive processing

directly from Disk in the

Storage Server

• Index/Table SCANS

• Primitive JOINS

• “WHERE” Filtering

• COLUMN Filters

Exadata Features…Benefits Multiply

200 GB with Smart

Scan eliminates IO

over network

200 GB of user data

Requires 200 GB of

IO over network

200 GB reduced to 30

GB with Exadata

Compression

Predicate Filter on

Storage Server

reduces data result

over network

Storage Index

eliminates

unnecessary IO

completely

Sub-second On

Database Machine

Data is 10x Smaller, Scans are 2000x faster




Business Continuity : Disaster Recovery &

Active Data Guard

Najam Qureshi

Mythics, Inc

WAN

Maximum Availability Architecture

HA, DR, Backup

Protection fromServer FailuresStorage FailuresNetwork FailuresSite Failures

Real-time remote standby open for queriesHuman error correction

Database, table, row, transaction level

Online indexing and table redefinitionOnline patching and upgrades

Real

Application

Clusters

ASM

Fast

Recovery Area

Active

Data Guard

Backup

Customize

Active Data Guard and Exadata

Get Disaster Recovery and Leverage DR Hardware

Primary

databaseStandby

database

Exadata Racks

ADC Exadata Rack

SCD

Redo transport

Ora

cle

Ne

t

Backups

Reporting

Exports

TX DCS Maximum Availability Architecture

Austin San Angelo

WAN

Centralized

Management

Oracle Data Guard

Exadata

ASM

Mirroring

Primary

Database

Nodes

RAC

Cluster

Exadata

ASM

Mirroring

Secondary

Database

Nodes

RAC

Cluster




Schema Consolidation

Najam Qureshi

Mythics, Inc

DBaaS, Database Consolidation via Schema

Consolidation

Multiple Database Instances verses Consolidated DatabasesCreate Several Small Database Instances…

Potential Cost ConsiderationsFlexibilityPerformance Consideration; Tuning/Diagnostic Methods; Stopping and RestartingNo Limitations on Schema Naming

Create a Single Larger Database InstanceFilling Up ‘White Space’ Making ‘Right Sizing’ EasierUsing Off-Hours Processing ResourcesEasing Administration During Common Maintenance ActivitiesEliminating Database Sprawl

Roles and Responsibilities – Implementation

SQL Query Performance tuning• Writing SQL for business needs

• Triggers, stored procedures, SQL packages

• Tuning SQL queries to run optimally

• Reduce CPU utilization

Tune the Data & Application Design• Data model

• Data cardinality

• Separate the data by use (OLTP, DW, temp data)

• Tune and optimized application that utilizes the data design to provide maximum performance




Q & A

Feed-back

welcome to dbaas technical trainingfor...• provide oem (grid control) access privileges •...

Documents