@ViscosityNA

1_Title Slide

RMOUG – Technology Day

ExtremeConsolidation by Nitin Vengurlekar

www.viscosityna.com 1

@ViscosityNA

/company/viscosity-north-america

@ViscosityNA

www.viscosityna.com/blog/

Midway Office Tower

13612 Midway Road

Dallas TX 75244

Follow Us!

www.viscosityna.com 2

Nitin Vengurlekar

• CTO & Chief Architect at Viscosity

Responsible for Service Delivery

Focus on Virtualization, Engineered & Converged

Systems

Developed white papers and Best Practices for

Application/Database High Availability &Consolidation

• 18 Years with Oracle

– 6 years with Oracle Support

– 9 years with RAC Product Management

– 3 years a “Private Database Cloud” Evangelist

• Taking these key customers to reference-ability

• Follow me on Twitter: @dbcloudshifuwww.viscosityna.com

3

www.viscosityna.com

Viscosity – Who We Are What We Do

Oracle Platinum Partner

• Full stack Application to Database Experts

• Experts in Cloud and Virtualization

• Premiere Oracle Services – focus on full stack services

• E-Business Suite, OBIEE to RAC

VMware Partner

• Selected as One of Four Premier VMware Select Partners for Global U2vL Migration

• Converted dozens of Legacy systems to Virtualized systems

• In 2016 Migrated/Virtualized 5 Mission Critical Systems

• Work with VMware engineering for strategic projects

- 5 -

Performance

Health ChecksHow’s it running?

CUSTOMApplication

Development

DBA

ServicesRemote and

On-site

On-Call Support

Managed

Services

ZERO DOWNTIME

Migrations

Professional

ServicesWhere you need it most

Staff Aug Workforce Capacity

on Demand

Oracle License ManagementGet the most out of your Oracle investment

Viscosity – Who we are and what we do

We wrote the books

6

- 8 -

• Three Deployment Use Cases- Oracle Multitenant and VMware- DBaaS initiative

• Process Flow – Thought Process• Rationalization/Simplification• Consolidation• Feature usage

• Consolidation density considerations

• Overall Benefits

NO…NO

THERE WILL BE NO DISCUSSION ON

ORACLE-VMWARE LICENSING

or

SUPPORTABILITY! But For Insights

Come Talk To Us LaterOracle License Optimization

- 10 -

Defined VM Cluster design and feature usage

* Review License

* Oracle Multitenant Deployment

* Define Consolidation Density

* PDB organization and placement Policy * VMware and/or PDB Mobility Considerations

Customer Consolidation Workflow

- 11 -

• Standardize on Product Platform

• Rationalization and Simplification

• Achieve Consistency in Deployment and Enable Platform for DBaaS

• Build Platform With High Availability in the Design

• Enable Platform for Agility in Application Development and Deployment

Goals for InitiativeStabilization/Consolidation – Through Rationalization, Simplification, and Standardization

13

• Determine what consolidation and rationalization means- No big ROI in Simple Server consolidation

- Combine Server and Component Consolidation (reduce instance count)

- Upgrade and standardize the stack

Before you Virtualize …

Rationalize, Standardize, and then Consolidate

- 14 -

• Rationalization and Simplification Management

– Simplify and standardize on set of stack versions (Oracle &

Linux)

– Consistency through Simplification

• Backups

• Monitoring

• Management (stats gathering, space management, etc..)

– Standardized on Oracle Enterprise Manager for Monitoring

Stabilization – Through Rationalization, Simplification, and Standardization – Common Theme

- 15 -

• Oracle Grid Infrastructure-RAC 12c or Oracle Restart 12c

• Oracle Database 12cR1 or 12cR2 with Multitenant feature

• VMware vSphere (5.5U3 and 6.0)

The stack, the full stack and nothing but the stack

- 16 -

• A standalone Server version of Oracle Grid Infrastructure (no license)

• Improves the availability of Oracle database and various Oracle components

• Biggest Value-add -> It provides intra-VM HA

– If there’s a Oracle component failure it can be automatically restarted

– Include pullup, pushdown dependencies and relationships

– Starts up and shutdown all components in correct order

– Fully compliments VMware HA - provides VM level HA

The stack, the full stack and nothing but the stackOracle Restart

- 17 -

• In this architecture, multitenant container database holds many pluggable

databases.

• Share common memory and background processes.

• Significantly improves database consolidation density enforces standardization

• Offering similar benefits to schema-based consolidation but with none of the

major application changes required by that approach.

The stack, the full stack and nothing but the stackOracle Multitenancy

• Hot Clones

– Oracle 12.2 Multitenant option, fully integrates the concept of “hot clones” with

the ability to perform on-line cloning of PDBs.

• With hot clones, the source database is still open for read-write mode.

• All PDB clones in Oracle 12.2 are hot clones and will be referred to as

clones.

• Read-Only Refreshable PDBs

– On Oracle 12.2, PDBs can be cloned while the source PDB is online.

– With Refreshable PDBs, we can have the PDB refresh data from the source

PDB with delta changes, since the last refresh automatically (define in nnn

Minutes) or on demand.

The stack, the full stack and nothing but the stackOracle Multitenancy – Key Features to leverage

RU and RUR for 12.2

• In July 2017 Oracle will release

• a Database RU ( = Proactive Bundle Patches (BPs)),

• a Grid Infrastructure RU,

• and an OJVM RU.

• No More PSUs or Bundle Patches for the 12.2.0.1 release

• The first RUR ( = Patch Set Updates (PSUs)) for 12.2.0.1 is planned for

October 2017

• October 2017, the 2nd RU for Oracle Database 12.2.0.1 is expected

• January 2018, the 3rd RU is expected and the 2nd RUR is expected

• Speculations: Are to release only 2 RURs per RU

• PDB Hot Clone

– Online test master instantiation

• PDB Refresh

– Incremental refresh of clone with latest data

CRM

Oracle Cloud

Pricing Retail

On-Premises

CRM

Snap Clone

Snap Clone

CRM Dev1CRM Dev2

Developers

TIME

Changes made to database

Cloned version no longer in sync

Only changes copied and applied

The stack, the full stack and nothing but the stackOracle Multitenancy

• PDB Hot Clone

– Online test master instantiation

• PDB Refresh

– Incremental refresh of clone with latest data

• PDB Relocate

– Relocate with no downtime

2121

CRM

HR

Oracle Cloud

Pricing Retail

On-Premises

CRM

The stack, the full stack and nothing but the stackOracle Multitenancy

- 22 -

Customer Example of Standardized on sizes

VM Type VM Sizing (vCPU and Memory) SGA sizing (SGA & HugePage Setting)

Small 2 vCPU and 8GB 6GB SGA

Basic Medium 4 vCPU and 64GB 58GB SGA

Large 8+ vCPUs and 128GB 100GB+

• Size VM for only minimal/appropriate number of CPUs and memory.

• If exact workload is not known, start with fewer vCPUs and increase as needed.

• Use Capacity Planner to analyze current environment and provide resource utilization metrics

for sizing.

• Overcommitting CPU is practical, as long as ESXi host is not saturated or while VMs are not

bottlenecked on system resources.

• For lower-tiered workloads, reasonable over commitment can increase aggregate throughput

and maximize license savings - The consolidation ratio varies depending on workloads.

The stack, the full stack and nothing but the stackVMware Configuration

- 23 -

• Followed all the Oracle – VMware best practices as per the following

• NUMA adherence

• vCPUs + Memory standard sizes

• Noop IO scheduler

• Lazy-eager thick disks

• ASM

• Datastore management

The stack, the full stack and nothing but the stackVMware Configuration

USE CASE #1

Consolidation using 12.2 Multitenant and Oracle Restart

- 25 -

Three node Vmcluster, each with 3-4 VMs @ 4-6 vCPUs/64 GB4-8 PDBs/CDB

CDB4

CDB2

CDB1

ESXi hostESXi hostESXi host

Use Case#2Consolidation using 12.2 Multitenant and Oracle Restart

CDB3

CDB11

CDB8

CDB9

CDB10

CDB5

CDB6

CDB7

- 26 -

• Various methods to deliver DBaaS

• Model will be driven by the granularity of service being deployed and technology

used to deploy

– Deploy Linux VM and install Oracle software, and instantiate CDB

– Deploy new CDB on existing VM

– Deploy new PDB on existing CDB on existing VM

• In all cases, have a template-tized provisioning mode for faster MTTDeploy

– VM templates

– DBCA for CBD setup

– DBCA for fresh PDB enablement, or clone from baseline seed PDB

Use #1Consolidation/DBaaS using 12.2 Multitenant and Oracle Restart

- 27 -

• Define PDB placement policy

– Organize PDBs into CDB by Operational or Business alignment

• Evaluate consolidation density thresholds of DBaaS, or “degree of fullness”.

– Density of VMs/node.

– Density of CDBs/VM.

– Density of PDBs/VM

– CDB/PDB organization. Are PDBs organized into specific CDBs?

• Evaluate Noisy neighbor management and exception handling

• Operational

• Management

• Performance

• Security

Use #1Consolidation using 12.2 Multitenant and Oracle Restart

- 28 -

Considerations - Mobility in Virtualized environment, which mechanism fits best for the scenario

Object Technology-Utility Use Case

VM VMware vMotion Move VM to another ESXi host in cases of unplanned or preparation planned outages

CDB Traditional Database Migration tools; e.g., Data Pump, RMAN, TTS, etc.

Migrate CDB to another ESXi host or bare-metal host in preparation for planned outages or system upgrades.

PDB In Oracle Database 12.2, there are numerous [online] methods to move PDBs between CDB; whether these PDB will be on the same server or different servers:

• Hot Clone• PDB Relocate

Migrate PDB to another ESXi host or bare-metal host in preparation for noisy neighbor contained, planned outages, or system upgrades.

Use #1Consolidation using 12.2 Multitenant and Oracle Restart

USE CASE #2

Consolidation using 12.1 Multitenant and Oracle RAC

- 30 -

• A Oracle Grid Infrastructure/Oracle RAC and Multitenant (license required)

– Three node VMcluster

– Deployed three RAC clusters in three node VMcluster

– Sized servers and storage appropriately to support the [expected] workload

• Database scale and HA provided by Oracle RAC

– Disabled many VM mobility features – DRS, vMotion, DPM

• Consolidation density driven by CDB/PDB and RAC Instances

Use Case#2Consolidation using 12.1 Multitenant and Oracle RAC

- 31 -

Three node VMcluster

RAC Prod1 Cluster

RAC QA Cluster

RAC Patching Test Cluster

ESXi hostESXi hostESXi host

Use Case#2Consolidation using 12.1 Multitenant and Oracle RAC

CDB

CDB

CDB

CDB

CDB

CDB

CDB

CDB

USE CASE #3

Consolidation using Mixed Bag

- 33 -

• A combination of Oracle RAC and non-RAC deployments

–Driven by Chargeback Model

–Business Units choose degree of HA and Scale

• Consolidation driven by CDB/PDB and RAC Instances

• VM mobility features – DRS, vMotion, DPM enabled for single

instance (non-RAC VMs)

Use Case#3Consolidation using Mixed Bag

- 34 -

Use Case#3Consolidation using Mixed Bag

CLOSING COMMENTS

• Flashback PDB

• Per-PDB character set

• 4k PDBs per CDB

(4,096 - increased from 252)

• AWR data at PDB level

• Memory & I/O resource prioritization in addition to CPU

– MAX_IOPS & MAX_MBPS

– CPU_COUNT

– SGA Parameters

• Configurable isolation via Lockdown Profiles

• PDB-level failover capability with Data Guar

• Support for PDBs with Different Time Zone File

Versions and Database Time Zones

Isolation with Economies of Scale

OLTPODS

Multitenant Container

- 37 -

• Define the success factors for consolidation

• What Application KPIs define success factors

What is the Success Factor

- 38 -

Goal: With Standardization in place, provide a platform for High Availability and Agility

• Reduce impact of planned and unplanned outages

• Move towards Autonomous Computing –Proactively catch issues and/or Self Healing -Mitigate before they become exposed or soften the exposure

• Transparent Application Failover and Application Continuity

• Improve HA for Development environments as well Production

• Enable platform for DevOps – Agility and Faster Mean time to Market

Improve High Availability and Scalability

- 39 -

Standardize on Product and Platform

• Server Consolidation via VMware virtualization

• Database Consolidation using Oracle 12c

Multitenant

• Combination of Consolidation Platforms

– Server Footprint Reduction

– Improved CPU/Memory utilization

– Reduced TCO

– Increase efficiency for development and test environments

• Provided agility in deployment and configuration consistency

Stabilization – through rationalization, simplification, and StandardizeOverall Benefits

- 40 -

• Standardization and Rationalization are not static parameters

– Standards need to evolve with changing Business Drivers

• Adaptability is Key

– Always have to create or respond to changes in the market to ensure their viability and success

• Business Agility

– Continue to provide value-add services to meet Mean Time to Market needs

Conclusion – evolve or dissolve

More detailed information is available at

viscosityna.com or by talking to a real

person at 469.444.1380

41

Our Clients

42

More detailed information is available at

viscosityna.com or by talking to a real

person at 469.444.1380

43