oracle database 12c : multitenant
DESCRIPTION
Présentation des nouveautés Oracle Database Multitenant 12c. http://www.digicomp.ch/fr/oracleTRANSCRIPT
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 1
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 2
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. Release timing for
Oracle Database 12c is planned for Calendar Year 2013.
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 3
Oracle Database 12c
Jean-Philippe Breysse
Oracle Suisse
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 4
Major Database Focus Areas
ENGINEERED
SYSTEMS
BIG
DATA
SOCIAL
BLOG
SMART
METER
101100101001
001001101010
101011100101
010100100101
CLOUD
COMPUTING
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 5
Private Database Cloud Architectures Using Oracle Database 11g
Dedicated Databases
share servers and OS
Virtual Machines
share servers
Schema Consolidation
share servers, OS and database
Increasing Consolidation
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 6
Private Database Cloud Architectures Using Oracle Database 12c
Dedicated Databases
share servers and OS
Virtual Machines
share servers
Pluggable Databases
share servers, OS and database
Increasing Consolidation
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 7
Isolation and multitenancy
Fast provisioning and cloning
Secure and highly available
No application changes
Manage many as one
Greater resource utilization
Performant and scalable
Lower IT costs
Consolidating Databases on Clouds Key requirements…
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 8
Oracle Database Architecture Requires memory, processes and database files
System Resources
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 9
New Multitenant Architecture Memory and processes required at container level only
System Resources
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 10
New Multitenant Architecture Memory and processes required at container level only
System Resources
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 11
OLTP benchmark comparison
Only 3GB of memory vs. 20GB memory used for 50 databases
Pluggable databases scaled to over 250 while separate database instances maxed at 50
Pluggable vs Separate Databases Highly Efficient: 6x Less H/W Resource, 5x more Scalable
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 12
Consolidating Databases Step1: Upgrade databases in-place
Upgrade in Place
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 13
Consolidating Databases Step2: Plug-in upgraded databases
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 14
Managing Shared Resources Resource management for consolidated databases
High Priority
Medium Priority
Low Priority
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 15
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
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 16
Common Users and Privileges
A common user can be granted privileges locally in a PDB (or root)
and therefore differently in each container
A common user can, alternatively, be granted a system privilege
commonly – the grant is made in root and every PDB, present and future
You can create a common role
A common role can be granted to a common user commonly
Authorization is checked in the container where the SQL is attempted
considering only the privileges that the user has in that container
Best practice: Don’t create objects in common user’s schema
Authorization is checked in the same way as in pre-12.1
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 17
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)
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 18
Services
Single SGA per
CDB Instance
Expand Cluster to Support Flexible Consolidation Model
Node1
CDB Instance 1
Node2
CDB Instance 2
Node3
CDB Instance 3
Improved Agility With Changing Workloads
Multitenant Container Database (CDB)
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 19
Simplified Patching Apply changes once, all pluggable databases updated
Upgrade
in-place
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 20
Simplified Upgrades Flexible choice when patching & upgrading databases
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 21
Patching via Unplug/Plug
Plug compatibility
Xml manifest
Things to check
– Options
– Character set
– Parameters
– Endianness
Post-plug, run any necessary SQL patch script in PDB
– Nothing required for binary patches
This method can be used for upgrades to next patchset
Details
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 22
Manage Many Databases as One Backup databases as one; recover at pluggable database Level
One Backup
Point-in-time recovery
at pluggable database level
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 23
PDB Point-in-time Recovery (PITR)
Much simpler/streamlined than tablespace PITR, which is complicated by
difficulties in identifying which metadata to use.
PDB PITR consists of 3 simple steps from RMAN:
All datafiles are recovered in-place, undo is recovered out of place and
applied in-place during open resetlogs.
Old backups of the PDB will continue to be valid.
Recovery isolation at granularity of PDB
RMAN> restore pluggable database my_db;
RMAN> recover pluggable database my_db until SCN 411010;
RMAN> alter pluggable database my_db open resetlogs;
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 24
Manage Many Databases as One One standby database covers all pluggable databases
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 25
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
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 26
Creating Databases for Test and Development Fast, flexible copy and snapshot of pluggable databases
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 27
Multitenant for Provisioning
PDBs can be cloned from
within the same CDB
Fast cloning of PDBs
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 28
Cloning a PDB Example
create pluggable database HCMBI from HCM
Local
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 29
Multitenant Cloning with Full Copy Efficient, simple & reliable process
Orchestration entirely from SQL
– DBA skills only
– No o/s access required
Parallel Execution Servers
– Fast and efficient
Clones have unique GUIDs
Source PDB must be open read only
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 30
Multitenant Cloning with Snapshot Copy Thin provisioning of database clones in seconds
Still SQL with new “as snapshot” clause
Where not supported receive error
ORA-17517: Database cloning using storage snapshot failed
Built on copy-on-write capability of underlying file system
Storage admin’s credentials stored in secure wallet once per CDB
No subsequent requirement for intervention of storage administrator
create pluggable database DEV44
from CRM_MASTER snapshot copy
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 31
Snapshot Clone Restrictions
Local clones only
Source PDB cannot be dropped
Source PDB cannot be unplugged
Both source and cloned PDBs may be opened read-write
Supported platforms
– Sun ZFS Storage Appliance (ZFSSA)
– Oracle ASM Cluster File System (ACFS)
– NetApp ™
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 32
Provisioning & Storage Gains with Snapshots
Full Size (GB) Snap Size (KB) Relative Size Full Clone Snap Clone % savings
24 140 0.00058% 9 min, 52 sec 1 min, 52 sec 80%
216 142 0.00007% 1hr, 21 min 2 min, 11 sec 97%
1300 551 0.00004% 9hr, 7 min 5 min 55 sec 99%
Internal Tests on Sun ZFS Storage Appliance
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 33
Isolation and multitenancy
Fast provisioning and cloning
Secure and highly available
No application changes
Manage many as one
Greater resource utilization
Performant and scalable
Lower IT costs
New Multitenant Architecture Ideal for consolidating databases on Clouds
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 34
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
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 35
Q&A
Copyright © 2013, Oracle and/or its affiliates. All rights reserved. 36