Oracle Multitenant meets Oracle RAC 12c OOW13 [CON8706]

9/30/13&

1&

Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 1

The Oracle Multitenant Option meets Oracle RAC Patrick Wheeler, Senior Director of Product Management Markus Michalewicz, Director of Product Management

9/30/13&

2&


Safe Harbor Statement

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.


Agenda

!  Introduction !  Oracle Multitenant and Oracle RAC Basics

!  Why Use Database Services

!  Improved Agility with Changing Workloads

!  Creating an Oracle RAC-based CDB

!  Administering an Oracle RAC-based CDB

!  Summary and Q&A

9/30/13&

3&


Oracle Multitenant and Oracle RAC Winning combination of scalability & reliability for consolidated databases

Oracle Multitenant & Oracle RAC

•  Scalability •  Flexibility •  Reduced Costs

Oracle RAC: Scalable, Reliable

Oracle Multitenant •  Consolidation means

“putting all your eggs in one basket”

•  Consolidating many databases into one demands scalable platform

Oracle RAC •  Means managing

many nodes in the cluster as one system

•  Provides resiliency against individual server failures

•  Allows for horizontal scaling

Multitenant: Simplify Consolidation


Standardize on Oracle RAC and Oracle Multitenant The new standard for Oracle Database Consolidation

Oracle GI

Oracle RAC One Node

Consolidation

Agi

lity

Oracle GI

Oracle RAC

9/30/13&

4&


Agenda

!  Introduction

!  Oracle Multitenant and Oracle RAC Basics







Oracle Multitenant Architecture Components of a Multitenant Container Database (CDB)

Pluggable Databases (PDBs)

PDBs

Root

CDB

9/30/13&

5&


Oracle Multitenant Architecture – Dynamics

!  PDBs share common SGA and background processes

!  Foreground sessions see only the PDB they connect to


Advantages of Oracle Multitenant Architecture Reduced CapEx & OpEx, Increased Agility, Easy Adoption

Self-contained PDB for each application !  Applications run unchanged !  Rapid provisioning (via clones) !  Portability (via pluggability)

Shared memory and background processes !  More applications per server

Common operations performed at CDB level !  Manage many as one (upgrade, HA, backup) !  Granular control when appropriate

9/30/13&

6&


Oracle RAC support for Oracle Multitenant Start off with a Single Instance, non-CDB

Server

Database Instance

Services

Server

Database Instance

CRM North

CRM South Services CRM

Reporting


Oracle RAC support for Oracle Multitenant Convert to a RAC Database, non-CDB

Node 1

RAC Instance 1

Services

Node 1

RAC Instance 1

CRM North

CRM South Services

Node 2

RAC Instance 2

CRM Reporting

9/30/13&

7&


Oracle RAC support for Oracle Multitenant Convert to a CDB RAC Database

Node2

CDB Instance 2

Node1

CDB Instance 1

CDB

Services


Agenda

!  Introduction







9/30/13&

8&


HRg1wc

Why Use Services? In a Single Instance environment the default service may be enough

!  The default service of the CDB is started when the CDB is started. This is an admin-service.

!  The default service of the PDB is available for connectivity as soon as PDB is mounted with the startup of the CDB.

!  If an application uses the default service for connectivity, it can connect to this service as soon as it is registered with the listener.

–  How to prevent an application from connecting?

rudolph

cdb1

sqlplus <user>/<pwd>@MySCAN/crmsvc

CRM PDB Default service HR PDB CRMSVC


HRg1wc

Why Use Services? Using the default service is not enough when moving PBS around

!  PDBs provide location independency (plug / unplug / clone), but exist within an environment

!  Moving PDBs between environments may require changing names of PDBs.

!  Use services to provide a “dial in number” for your application. If the PDB moves to another location, you can keep the number.

–  This requires uniqueness of service names

rudolph

cdb1

CRM PDB HR PDB CRMSVC

cupid

cdb1

NewHR PDB

9/30/13&

9&


Use Services with Policy Managed Databases For better HA and workload management

!  Oracle RAC-based systems allow for management of services based on policies.

!  Server Pools are used to group workload to run on either one or a group of servers in the pool.

!  Using policies allows for adapting to changes in demand (Dynamic Database Services)

HRg1wc HR PDB

CRM PDB CRMSVC

vixen srvpool: backoffice comet srvpool: frontoffice

dancer srvpool: frontoffice dasher srvpool: frontoffice Oracle GI for a cluster Oracle GI for a cluster

Oracle GI for a cluster Oracle GI for a cluster

Oracle RAC Oracle RAC


raccdb1

raccdb1_1

raccdb1_4 Raccdb1_3

Raccdb1_2


Policy-Managed Databases with Oracle RAC 12c Improved HA Management - Startup

raccdb1

!  Defining a Service Startup Order –  Ensure services are started in specified groups

and specified order.

–  Leverages Serverpool Min and Importance properties

dasher srvpool: frontoffice Oracle GI for a cluster

Oracle RAC

raccdb1_4

1st

vixen srvpool: frontoffice Oracle GI for a cluster

Oracle RAC

raccdb1_3

2nd

comet srvpool: backoffice Oracle GI for a cluster

Oracle RAC

raccdb1_1

4th

dancer srvpool: backoffice Oracle GI for a cluster

Oracle RAC

raccdb1_2

3rd

9/30/13&

10&



Oracle RAC

raccdb1_2

dancer srvpool: frontoffice Oracle GI for a cluster

Oracle RAC

raccdb1_2

Policy-Managed Databases with Oracle RAC 12c Improved HA Management – New Failover Strategy

raccdb1


Oracle RAC

raccdb1_4


Oracle RAC

raccdb1_3


Oracle RAC

raccdb1_1

!  Servers “Move” to Replace Failed node –  Protects against cascade failures due to load

–  Ensures workload isolation between pools

–  Less important workloads shutdown transactionally



Oracle RAC

raccdb1_2


Oracle RAC

raccdb1_2


Oracle RAC

raccdb1_1

comet srvpool: frontoffice Oracle GI for a cluster

Oracle RAC

raccdb1_1

Policy-Managed Databases with Oracle RAC 12c Improved HA Management – Manage Last Service Standing

raccdb1


Oracle RAC

raccdb1_4


Oracle RAC

raccdb1_3

!  Business Critical Services survive multiple failures –  Most important pool always gets the servers

–  Services preserved across multiple failures

–  Less important workloads shutdown transactionally

9/30/13&

11&


Agenda

!  Introduction








Expand Cluster to Support Flexible Consolidation Model Services

Single SGA per CDB Instance

Improved Agility With Changing Workloads

Node1

CDB Instance 1

Node2

CDB Instance 2

Multitenant Container Database (CDB)

9/30/13&

12&


Expand Cluster to Support Flexible Consolidation Model Services

Single SGA per CDB Instance

Node1

CDB Instance 1

Node2

CDB Instance 2

Node3

CDB Instance 3

Improved Agility With Changing Workloads

Multitenant Container Database (CDB)


Improved Agility With Changing Workloads Facilitating Policy-Managed Dynamic Database Services

HRg1wc HR PDB

CRM PDB CRMSVC

vixen srvpool: backoffice comet srvpool: frontoffice



Oracle RAC


raccdb1

raccdb1_1

raccdb1_4


Oracle RAC

raccdb1_3

raccdb1_2


SQL> select instance_name,host_name from v$instance; INSTANCE_NAME HOST_NAME ------------------------------------ raccdb1_3 dancer

9/30/13&

13&


Improved Agility With Changing Workloads Facilitating Policy-Managed Dynamic Database Services

HRg1wc HR PDB

CRM PDB CRMSVC


SQL> select instance_name,host_name from v$instance; INSTANCE_NAME HOST_NAME ------------------------------------ Raccdb1_1 vixen

vixen srvpool: frontoffice comet srvpool: backup

dancer srvpool: backup dasher srvpool: backoffice Oracle GI for a cluster Oracle GI for a cluster




raccdb1

raccdb1_1

raccdb1_4 raccdb1_3

raccdb1_2

backup



Oracle RAC

raccdb1_3

Improved Agility With Changing Workloads Stopping a PDB once it was opened r/w or ro using services

vixen srvpool: frontoffice comet srvpool: frontoffice Oracle GI for a cluster Oracle GI for a cluster


raccdb1

raccdb1_1 Raccdb1_2

sqlplus <user>/<pwd>@MySCAN/crmsvc " ERROR: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor

!  Services regulate user access to a database –  The first service assigned to a PDB opens

the PDB in read/write mode (default)

–  Stopping a service does not close the PDB

!  User access to this PDB is prevented.

–  The buffers held by the PDB not actively used will be subject to regular buffer aging operations

!  Use SQL to stop a PDB (on an instance) as required

Buffers HRg1wc HR PDB CRMSVC

CRM PDB

9/30/13&

14&


Agenda

!  Introduction








Create an Oracle RAC Database What is the default when keeping the preselection in steps 1-4…?

!  Policy-managed

!  Oracle RAC-based

!  Non-CDB Database

9/30/13&

15&


Create an Oracle RAC-based CDB Create a CDB instead…

Create an empty multitenant CDB.


Milestone What has been installed and configured so far?

vixen srvpool: frontoffice comet srvpool: backoffice

dancer srvpool: backoffice dasher srvpool: frontoffice

OS OL 6.4 OS OL 6.4

OS OL 6.4 OS OL 6.4





raccdb1

raccdb1_2

raccdb1_1

[RAC]> srvctl status database -d raccdb1 Instance raccdb1_1 is running on node comet Instance raccdb1_2 is running on node dancer [RAC]>srvctl status srvpool -serverpool backoffice -detail Server pool name: backoffice Active servers count: 2 Active server names: comet,dancer NAME=comet STATE=ONLINE NAME=dancer STATE=ONLINE [RAC]> srvctl status srvpool Server pool name: Free Active servers count: 0 Server pool name: Generic Active servers count: 0 Server pool name: backoffice Active servers count: 2 Server pool name: frontoffice Active servers count: 2

9/30/13&

16&


Create Pluggable Databases Create HR PDB on running instances


dancer srvpool: backoffice dasher srvpool: frontoffice Oracle GI for a cluster Oracle GI for a cluster




raccdb1

raccdb1_2

raccdb1_1

Create a PDB on a node that hosts a multintenant

CDB instance


Create Pluggable Databases Create CRM PDB on running instances






raccdb1

raccdb1_2

raccdb1_1

9/30/13&

17&


Post-Creation Steps Create services – part 1






raccdb1

raccdb1_2

raccdb1_1 [RAC]> srvctl add service -d raccdb1 -s hrsvc -pdb hr -serverpool backoffice [RAC]> srvctl add service -d raccdb1 -s crmsvc -pdb crm -serverpool frontoffice [RAC]> srvctl start service -d raccdb1 -s hrsvc [RAC]> srvctl start service -d raccdb1 -s crmsvc

!  Dynamic Database Services –  For easier management of multitenant CDBs

–  For better workload management in the cluster


!  Pluggable Databases –  By default are in mount status after creation

–  They need to be opened in either r/o or w/r

–  Startup and distribution of Pluggable databases can be automated and optimized using services

Post-Creation Steps Create services – part 2






raccdb1

raccdb1_3

raccdb1_4 raccdb1_2

raccdb1_1

[RAC]> srvctl status database -d raccdb1 Instance raccdb1_1 is running on node comet Instance raccdb1_2 is running on node dancer Instance raccdb1_3 is running on node vixen Instance raccdb1_4 is running on node dasher [RAC]> srvctl status service -d raccdb1 Service crmsvc is running on nodes: vixen,dasher Service hrsvc is running on nodes: comet,dancer

9/30/13&

18&


Agenda

!  Introduction





!  Administering an Oracle RAC-based CDB !  Summary and Q&A


Manage Many as One with Multitenant Backup databases as one; recover at pluggable database level

One Backup

Point-in-time recovery At pluggable database level

9/30/13&

19&


Manage Many as One with Multitenant Backup databases as one; recover at pluggable database level

vixen srvpool: frontoffice comet srvpool: backup

dancer srvpool: backup dasher srvpool: backoffice Oracle GI for a cluster Oracle GI for a cluster




raccdb1

Raccdb1_1

raccdb1_4 raccdb1_3

raccdb1_2

Backup

Point-in-time recovery At pluggable database level


Multitenant for Simplified Upgrades Apply changes once, all pluggable databases updated

Upgrade in-place

9/30/13&

20&


Multitenant for Patching Flexible choice when patching & upgrading databases


Standardize on Oracle RAC and Oracle Multitenant The new standard for Oracle Database Consolidation

Oracle GI

Oracle RAC One Node

Consolidation

Agi

lity

Oracle GI

Oracle RAC

Online (rolling) Patch and PSU Application

9/30/13&

21&


Agenda

!  Introduction








Benefit Capability Enabled

Minimize CapEx •  More applications per server

Minimize OpEx •  Manage many as one •  Standardized procedures & service levels •  Cloning for development / testing

Maximize Agility •  Rapid provisioning •  Portability through “pluggability” •  Scalability with RAC

Ease of Adoption •  Applications run unchanged

Key Benefits

9/30/13&

22&

Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Insert Information Protection Policy Classification from Slide 12 of the corporate presentation template 43

Graphic Section Divider


Oracle Multitenant meets Oracle RAC 12c OOW13 [CON8706]

Real Estate

Transcript of Oracle Multitenant meets Oracle RAC 12c OOW13 [CON8706]