Oracle Multitenant meets Oracle RAC - IOUG 2014 Version

The Oracle Multitenant
Option meets Oracle RAC
Deba Chatterjee
Principal Product Manager, Oracle Multitenant
Markus Michalewicz
Director of Product Management, Oracle RAC

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

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
Consolidation
Agility

Agenda
 Introduction
 Summary and Q&A

Oracle Multitenant Architecture
Components of a Multitenant Container Database (CDB)
Pluggable Databases (PDBs)
PDBs
Root
CDB

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

Oracle Real Application Clusters (RAC) 12c
 Overview
– Clustered database deployments for
high availability, performance, and agility
– Oracle's premier shared disk
database clustering technology
– Choice of administrator-managed or
policy-managed deployments
 Benefits
– Runs all database workloads
– Foundation for database clouds
– Scale out and scale up on-demand
– Highest availability for the database
– Flexible workload management

Oracle Multitenant on Oracle RAC
Consider a Single Instance (SI), non-CDB
Server
Database Instance
Services
Server
Database Instance
CRM
North
CRM
South
Services CRM
Reporting

Then consider 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

Finally, picture a CDB RAC Database
Node2
CDB Instance 2
Node1
CDB Instance 1
CDB
Services

The simplest way of converting a SI PDB to RAC: unplug/plug
Node2
CDB Instance 2
Node1
CDB Instance 1
CDB

Agenda
 Introduction
 Summary and Q&A

HRg1wc
Why Use Services?
Because the default service should not be used for client connections
 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 PDBs 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

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: backofficecomet srvpool: frontoffice
dancer srvpool: frontofficedasher srvpool: frontoffice
Oracle GI for a cluster Oracle GI for a cluster
Oracle GI for a clusterOracle GI for a cluster
Oracle RAC Oracle RAC
Oracle RACOracle 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 Server Pool
Minimum and Importance properties
dasher srvpool: frontoffice
Oracle GI for a cluster
Oracle RAC
raccdb1_4
1st
vixen srvpool: frontoffice
Oracle RAC
raccdb1_3
2nd
comet srvpool: backoffice
Oracle RAC
raccdb1_1
4th
dancer srvpool: backoffice
Oracle RAC
raccdb1_2
3rd

Oracle RAC
raccdb1_2
dancer srvpool: frontoffice
Oracle RAC
raccdb1_2
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 transactional

Oracle RAC
raccdb1_2
Oracle RAC
raccdb1_2
Oracle RAC
raccdb1_1
comet srvpool: frontoffice
Oracle RAC
raccdb1_1
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 transactional

Agenda
 Introduction
 Summary and Q&A

Improved Agility With Changing Workloads
Dynamic Provisioning
dancer srvpool: backofficedasher srvpool: frontoffice
Oracle GI | HUB Oracle GI | HUB
Oracle GI | HUB
Oracle RAC
raccdb1
raccdb1_3
raccdb1_4 raccdb1_2
[GRID]> srvctl modify serverpool
–serverpool backoffice –max 1
[RAC]> srvctl config serverpool
Server pool name: frontoffice
Importance: 10, Min: 2, Max 4
Server pool name: backoffice
Importance: 5, Min: 1, Max 1
[RAC]> srvctl status service –db
Service crmsrv is running on nodes dasher,dancer,vixen
Service hrsvc is not running
Oracle GI | HUB
Oracle RAC
raccdb1_1
 Add Servers Just-In Time to meet demand
– Server Pools sized via Min and Max properties
– Dynamically controlled by QoS Management
– Planned control via Clusterware or QoSM Policies
Oracle GI | HUB
Oracle RAC
raccdb1_2

Facilitating Policy-Managed Dynamic Database Services
HRg1wc
HR PDB
CRM PDB
CRMSVC
vixen srvpool: backofficecomet 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

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: frontofficecomet srvpool: backup
dancer srvpool: backupdasher srvpool: backoffice
raccdb1
raccdb1_1
raccdb1_4 raccdb1_3
raccdb1_2
backup

Oracle RAC
raccdb1_3
Stopping a PDB once it was opened r/w or r/o using services
vixen srvpool: frontofficecomet srvpool: frontoffice
raccdb1
raccdb1_1Raccdb1_2
 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

Agenda
 Introduction
 Summary and Q&A

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

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: frontofficecomet srvpool: backoffice
OS OL 6.4 OS OL 6.4
OS OL 6.4OS 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
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
Server pool name: Generic
Server pool name: frontoffice

Create Pluggable Databases
Create HR PDB on running instances
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

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

Agenda
 Introduction
 Summary and Q&A

Utilize Nodes in the Cluster to Support Flexible Consolidation Model
Services
Single SGA per
CDB Instance
Node1
CDB Instance 1
Node2
CDB Instance 2
Multitenant Container Database (CDB)

Utilize Nodes in the Cluster to Support Flexible Consolidation Model
Services
Single SGA per
CDB Instance
Node1
CDB Instance 1
Node2
CDB Instance 2
Node3
CDB Instance 3
Multitenant Container Database (CDB)

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

Manage Many as One with Multitenant
Backup databases as one; recover at pluggable database level
vixen srvpool: frontofficecomet srvpool: backup
dancer srvpool: backupdasher srvpool: backoffice
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

Multitenant for Patching
Flexible choice when patching & upgrading databases

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

Agenda
 Introduction
 Summary and Q&A

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

Oracle Multitenant meets Oracle RAC - IOUG 2014 Version

Recommended

More Related Content

What's hot (20)

Viewers also liked (18)

Similar to Oracle Multitenant meets Oracle RAC - IOUG 2014 Version (20)

More from Markus Michalewicz (20)

Recently uploaded (20)

Oracle Multitenant meets Oracle RAC - IOUG 2014 Version