Oracle Database 12c para la comunidad GeneXus - Engineered for clouds

Oracle Database 12c
Engineered for Cloud
Martín Páez
Arquitecto de Soluciones – Oracle Indirect Sales
martin.paez@oracle.com

Agenda
 Rethinking Architecture for the Database Cloud
 Multitenant Architecture
 Capabilities Enabled
 Managing Shared Resources
 Upgrading to Multitenant
 Use Cases

Agenda
 Use Cases

Pressures
Increase Agility
Reduce Costs
• Capital Costs
• Operating Costs
Non-stop operations
DBA challenges:
• Patching, upgrades
• Provisioning
Pressures Requirements
Increase Agility Performance, scalability
Reduce Costs
• Capital Costs
• Operating Costs
Reliability, availability
Non-stop operations Security, tenant isolation
DBA challenges:
• Provisioning
No application changes
Pressures Requirements Trends
Increase Agility Performance, scalability Private Cloud
Reduce Costs
• Capital Costs
• Operating Costs
Reliability, availability Massively Powerful Servers
(Exadata)
Non-stop operations Security, tenant isolation Virtualization
DBA challenges:
• Provisioning
No application changes Simplification
• Standardized Services
• Self-Service
Industry Today

Private Database Cloud Architectures
Oracle Database 11g
Dedicated Databases
share servers and OS
Virtual Machines
share servers
Schema Consolidation
share servers, OS and database
Increasing Consolidation

Private Database Cloud Architectures
Oracle Database 12c
Dedicated Databases
share servers and OS
Virtual Machines
share servers
Multitenant Database
share servers, OS and database
Increasing Consolidation

Oracle Database Architecture
Requires memory, processes and database files
System Resources

New Multitenant Architecture
Memory and processes required at multitenant container level only
System Resources

Agenda
 Use Cases

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

Multitenant Architecture
 Multitenant architecture can currently
support up to 252 PDBs
 A PDB feels and operates identically to a
non-CDB
 You cannot tell, from the viewpoint of a
connected client, if you’re using a PDB or
a non-CDB
Database
Link

Unplug / plug
Simply unplug from the old CDB…

Unplug / plug
…and plug in to the new CDB…
 Moving between CDBs is a simple case
of moving a PDB’s metadata
 An unplugged PDB carries with it lineage,
patch, encryption key info etc

Common Data Dictionary
Before 12.1: dilution over time
Database Created
Data
Dictionary
User Data
Meta
Data
Mature Database
Data
Dictionary
User Data
Meta
Data
Tables, Code, Data added
Data
Dictionary
User Data
Meta
Data

OBJ$ TAB$ SOURCE$
…
Oracle Data and User Data
OBJ$ TAB$ SOURCE$
…
EMP DEPT
…
OBJ$ TAB$ SOURCE$
…
 Multitenant fix:
Horizontally-
partitioned data
dictionary
 Only Oracle system
definition remains
 Data dictionary is
diluted by customer’s
metadata

Multitenant Architecture – Dynamics
 PDBs share common SGA and
background processes
 Foreground sessions see only
the PDB they connect to

0
0.5
1
1.5
2
2.5
3
CRM HCM ERP BI
GB
Pluggable Database
MEMORY
0
0.5
1
1.5
2
2.5
3
CRM HCM ERP BI DW
GB
Pluggable Database
MEMORY
Multitenant Scalability
 Only small increments in memory as
additional PDBs are added
0
0.5
1
1.5
2
2.5
3
CRM HCM ERP
GB
Pluggable Database
MEMORY

Files in the CDB
 Each PDB has its own set of tablespaces
including SYSTEM and SYSAUX
 PDBs share UNDO, REDO
and control files, (s)pfile
 By default the CDB has a single TEMP
tablespace but PDBs may create their
own
Namespaces

Users  Local users are the successors for
customer-created users in a non-CDB
 A local user is defined only in a PDB
 A local user can administer a PDB
 A common user is defined in the root
and is represented in every PDB
 A common user can log into any PDB
where it has “Create Session” and can
therefore administer a PDB
 The Oracle system is owned by
common users

Agenda
 Use Cases

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
One standby database covers all pluggable databases

Multitenant for Simplified Upgrades
Apply changes once, all pluggable databases updated
Upgrade
in-place

Multitenant for Patching
Flexible choice when patching & upgrading databases

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)

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)

GOLD
SILVER
BRONZE
RAC, Data Guard, Daily Incrementals
Data Guard, Daily Incrementals
Weekly Full Backups
PDB migrates through SLAs as it becomes more mission critical
Unprecedented Agility with Pluggable Portability

Multitenant for Provisioning
 PDBs can be cloned from
remote CDBs
 PDBs can be cloned from
within the same CDB
Fast cloning of PDBs

Multitenant for Fast Provisioning
Pluggable databases can be quickly provisioned from seed
0
5
10
15
20
25
Non CDB PDB Clone PDB using
Copy-on-Write File
System
Time Taken to Provision New Database

Advantages of 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

Agenda
 Use Cases

Managing Shared Resources
Resource management in multitenant environment
High Priority
Medium Priority
Low Priority

Manage CPU
Pluggable Database Shares Guaranteed CPU Maximum CPU
HCM 2 2/4 = 50% 100%
CRM 1 1/4 = 25% 100%
ERP 1 1/4 = 25% 100%
2 Shares 1 Share 1 Share
A CDB Resource Plan uses
shares to specify how CPU is
distributed between PDBs

Agenda
 Use Cases

Upgrading to Multitenant
Step 1: Upgrade databases in-place
Upgrade in Place

Step 2: Plug-in upgraded databases

 No application changes required.
Step 3. Change applications to work with MultitenantStep 3. Change applications to work with Multitenant

Migrate using Replication
① Provision new PDB from Seed
② Replicate using technologies such as
Oracle GoldenGate or Data Pump
New in 12.1, you ask that full database
export and full database import make
maximum use of transportable
tablespaces in the single expdb and
impdb commands.
(Backported to 11.2.0.3.)

Agenda
 Use Cases

1. Multitenant for Test and Development
Fast, flexible copy and snapshot of pluggable databases

2. Consolidation of Disparate Applications
Shared overhead of memory and processes
System Resources

RAC, Data
Guard, Daily
Incrementals
Data Guard
Daily Incrementals
Pick from standard sizes and service levels
3. Self-Service Database as a Service (DBaaS)
✔
GOLD
SILVER
BRONZE Weekly Full
Backups
✔

4. Multitenant. Perfect for SaaS.
Multitenancy implemented by the Database, not the Application

5. Multitenant. Perfect for ISVs.
Packaged apps and reference data are easily distributed

Use Cases
1. Development / Testing – start here!
2. Consolidation of Disparate Applications
3. Database as a Service (DBaaS) on Private Cloud
4. Software as a Service (SaaS)
5. ISVs: Distribution of Packaged Apps and Data
6. …many others!

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 Database 12c para la comunidad GeneXus - Engineered for clouds

Recommended

More Related Content

What's hot (20)

Viewers also liked (8)

Similar to Oracle Database 12c para la comunidad GeneXus - Engineered for clouds (20)

More from GeneXus (20)

Recently uploaded (20)

Oracle Database 12c para la comunidad GeneXus - Engineered for clouds