Multitenant Best Practices - Aioug

Oracle
MulAtenant Best PracAces

Deba Cha(erjee
Senior Principal Product Manager

Giridhar Ravipa;
Principal Member of Technical Sta

November 21, 2015

Copyright 2015, Oracle and/or its aliates. All rights reserved. |
Safe Harbor Statement

The following is intended to outline our general product direcAon. It is intended for
informaAon purposes only, and may not be incorporated into any contract. It is not a
commitment to deliver any material, code, or funcAonality, and should not be relied upon
in making purchasing decisions. The development, release, and Aming of any features or
funcAonality described for Oracles products remains at the sole discreAon of Oracle.
12/3/15
Oracle Database Architecture

Requires memory, processes and database les
System Resources
GL
OE
AP
New MulAtenant Architecture

Memory and processes required at container level only
System Resources
GL
GL
OE
OE
AP
AP
Oracle MulAtenant
New architecture for consolida;ng databases and simplifying opera;ons

Pricing

PDB$SEED

Self-contained PDB for each applica;on
Retail

PDBs
Portability (via pluggability)

Rapid provisioning (via clones)
ApplicaAons run unchanged
Common opera;ons performed at Root level
CDB$ROOT
MulAtenant Container
Manage many as one (upgrade, backups, HA)

Granular control when appropriate

Shared memory and background processes
More applicaAons per server

12/3/15
Oracle Data and User Data
Before 12.1: Oracle and user data intermingle over ;me
New database contains

Oracle meta-data only
Populate database with
user data
OBJ$
TAB$
DEPT
EMP
SOURCE$

Meta-Data
PDB
Root
Oracle and customer

meta-data intermingled
Portability challenge!
MulAtenant x:
Horizontally-par--oned
data dic-onary
User Data
Only Oracle-supplied
meta-data remains in root
Planning & ConsolidaAon Target
Are You Too Busy to Plan ?
Copyright 2015, Oracle and/or its aliates. All rights reserved. | Oracle CondenAal Internal/Restricted/Highly Restricted
Planning(1/2)
IdenAfy Who are my candidates ?
Dene consolidaAon criteria
SLAs Performance and/or
availability
Workload
Line of Business
Character set and/or Time zone
PosiAons you to more easily dene
a DBaaS Service Catalog
How do I size my server ?

Consider
Aggregate compute resource
requirements (CPU, Memory, IO,
Network, Storage)
Workload and targeted
consolidaAon density
EsAmate and Validate
10
Planning (2/2)
Dene Management
Policies
Where/when to
Manage Many as One
SLAs and HA soluAon
Provisioning policies
DB Resource
Management Policies
Evaluate PDB
Candidate
UncertainAes
Deploy as Single
Tenant
PosiAon the PDB for
MulAtenant
Clone and unplug/
plug features
available
Analyze the Workloads

IdenAfy compaAbility
and conicts
IdenAfy
oversubscripAon
opportuniAes
11
Cigna Health CON6379: Oracle Mul;tenant Customer Success Story (class of 2014)

Post Consolida;on
Server Congs
10x reducAon
3x reducAon
Servers
Oracle Versions
OS Versions
Hardware Type
HA SoluAon
Physical Servers
Databases
DB Character Set
3 1
8 1
1 Standard Version
1 Standard HA SoluAon
50% reducAon
7x reducAon
1 Standard Character Set
TacAcal View of MulAtenant

Theme
Provisioning
Provisioning
CreaAng a CDB and Snapshot clones
DBaaS
Provisioning, Self-Service, Adopt to

changing workloads
Security,
IsolaAon
Conguring MulAtenant security for

various use cases
Resource
Manager
Shares, caps, dynamic capabiliAes
RAC
PDB/Node Anity, portability, scale

out
Performance
Manage Performance
High
Availability
Performance
MulAtenant
DBaaS
Security
Resource
Management
Provisioning & Cloning
MulAtenant for Provisioning

Fast cloning of PDBs
GL-1
GL-2
AP-1
AP-2
PO-1
PDBs can be cloned from

within the same CDB
remote CDBs
GL
OE
AP
PO

non-CDBs
Thinly provision snapshot
clones in seconds
15
MulAtenant Cloning Types and Plaoorms

FLAVORS
Subset Clone
Remote Clone
over DB link
Full Clones
MulAtenant Cloning
Metadata
Only clone
TYPES
Supported on all plaoorms
File System AgnosAc

(CloneDB=TRUE)
Source in Read-only if child
exists
Exadata Sparse clones
Snapshot clones
ACFS
Copy-on-write - Source
opened in read write aser
clone is created
SNAPSHOT CLONE SYNTAX - CREATE PLUGGABLE

DATABASE PDB2 FROM PDB1 SNAPSHOT COPY;
ZFSSA
Netapp
EMC
16
Deployment
CDB Crea;on and Congura;on

Use DBCA
Standardize
GUI or Silent Mode

Customize CDB OpAons
CustomizaAon of Database
OpAons in a MulAtenant
Setup(1616554.1)
12/3/15
Character set
AL32UTF8
Use OMF
OperaAons
e.g. Patching schedule
Deployment - ConguraAons
Size your SGA the Divide by 2 rule of
thumb
Congure Huge Pages if SGA > 30GB
AcAve process count should be ~5 x
physical core
Set SGA_TARGET to 60% of physical
memory
Let Oracle Manage the Memory Pools
AutomaAc PGA memory management

20% of SGA
12/3/15
Set SGA_MAX_SIZE to a high value

Set DB_FILES, PROCESSES to anAcipate growth
We use GLOBAL UNDO, size your undo
tablespace with consideraAon
Redo
o Minimum 4GB and size to switch max <=
10-20 mins
o 3-4 redo groups
Archive
o Calibrate retenAon/deleAon policies for
backups/archive logs
Monitor temp usage
Initialization Parameters & Miscelleneous

For MulAtenant, there are two
groups of parameters:
Evaluate and adjust any parameter

that aects applicaAon
performance
Those that can be modied within a PDB

Those that can only be set on the CDB level
In order to nd the possible

parameters you need to run:
SELECT NAME FROM V$SYSTEM_PARAMETER WHERE
ISPDB_MODIFIABLE='TRUE' ORDER BY NAME;
OPEN_CURSORS
OPTIMIZER se|ngs
CURSOR_SHARING
Evaluate as consolidaAon density increases
Congure clone quotas and storage limits
PDB level parameters persist across Dont modify PDB$SEED

database restarts and also across
Create and customize your own SEED
unplug/plug and clone.
Management
Review AutoTask scheduling
Opera;onal
Size SYSAUX appropriately
Monitor free space in CDB and in all PDBs
Ensure 10GB free before upgrade to 12.1.0.2
Look for ORA-1652 temp extent allocaAon
errors in the mmon slaves trace les
Monitor the Audit Directory

Audit can be dened in the context of the CDB
or PDB
Monitor and purge the audit desAnaAon
$ORACLE_HOME/rdbms/admin/catcon.pl
Execute SQL*Plus scripts or SQL statements in
a non-CDB
all or subset of PDBs in a CDB
12/3/15
By default, all 3 auto tasks start at the same

Ame in all PDBs.
Stagger the schedule to manage performance
Enable gather stats and disable segment
advisor and auto sql tuning advisor if they are
not needed.
Dene an DBRM policy to limit CPU
Archive Logging
Pre-ConsolidaAon: Evaluate and Size Aggregate
Redo Rate
Size Archive Log Dest and Monitor Purging
Policies
Calibrate disk quota for FAST RECOVER AREA
per consolidaAon density, le sizes and target
recovery window
Resource Management
Managing Shared Resources

Resource management in a mul;tenant environment
GL
High Priority
OE
AP
Medium Priority
Low Priority
22
Resource AllocaAon Strategy

Default Resource
AllocaAon
Same allocaAon for all PDBs

Specify a share and each one gets the same minimum at 100% uAlizaAon
Each PDB can use up to 100% CPU
Specify a minimum
allocaAon
Ensures all PDBs get a specic share of the resources

Allows any PDB to consume any unused resources
Kicks in at 100% resource uAlizaAon.
Specify a minimum
and maximum
Ensures all PDBs get a specic share of the resources

Prevents a PDB from taking more than the maximum value assigned.
May result in unused capacity
Manage CPU
A CDB Resource Plan uses
shares to specify how CPU is
distributed between PDBs
GL
OE
AP
2 Shares
1 Share
1 Share
Pluggable Database
Shares
Guaranteed CPU
Maximum CPU
GL
2/4 = 50%
100%
OE
1/4 = 25%
100%
AP
1/4 = 25%
100%
Manage CPU
GL
OE
AP
2 Shares
1 Share
50%
1 Share
50%
A CDB Resource Plan uses

utilization limits to limit the
CPU usage for a PDB.
With utilization limits, your
CPU may be under-utilized.
Pluggable Database
Shares
Guaranteed CPU U;liza;on Limit
Maximum CPU
GL
2/4 = 50%
100%
OE
1/4 = 25%
50%
50%
AP
1/4 = 25%
50%
50%
Manage CPU
Configure a default directive: the
default shares and utilization limit
for PDBs.
GL
OE
AP
2 Shares
Default
Default
Pluggable Database
Shares
Maximum CPU
(Default DirecAve)
GL
2/4 = 50%
OE
Default (1)
1/4 = 25%
Default (50%)
50%
AP
Default (1)
1/4 = 25%
Default (50%)
50%
50%
100%
Manage CPU
With a default directive, you dont
need to modify the resource plan
for each PDB plug and unplug
GL
OE
AP
PO
2 Shares
Default
Default
Default
Pluggable Database
Shares
Maximum CPU
(Default DirecAve)
GL
2/5 = 40%
OE
Default (1)
1/5 = 20%
Default (50%)
50%
AP
Default (1)
1/5 = 20%
Default (50%)
50%
PO
Default (1)
1/5 = 20%
Default (50%)
50%
50%
100%
Parallel Statement Queuing in PDBs

Specifies the probability
that this PDB will get to
launch the next parallel
operation
Limit the total number

of parallel servers the
PDB can use at a
time.
Limit the DOP of

the PDBs parallel
operations.
PDB
Shares
Parallel Server Percentage
Parallel Degree Limit
GL
50
OE
50
AP
50
16
(P)DBaaS
Unprecedented Agility with Portable Pluggability

PDB migrates through SLAs as it becomes more mission cri;cal
GOLD
RAC, Data Guard
SILVER
RAC
BRONZE
Backups
30
Deployment
PDB Provisioning in PDBaaS
A central CDB with a catalog and a PDB templates
CDB1 BI SERVICE 125/250 PDBS 50%
CDB2 FINANCE 75 / 125 - PDBS - 60%
CDB3 SCHEMA 200 / 250 PDBS 80%
PDB TEMPLATES
BI
FINANCE
DATABASE OF DATABASES
FINANCE POD 60% u;lized
PROVISION A BI PDB
CATALOG
FORWARDS
REQUEST TO BI
POD TO
PROVISION A PDB
BI POD 50% u;lized
SCHEMA POD 80% u;lized
Oracle CondenAal Internal/Restricted/Highly Restricted
Security
Management
Common Users
Understand, dene and Generalize your
common user & local user policies
Dene the role separaAon between local and
common users
Avoid GRANT session to common user globally
New PDBs plugged in inherit common user
Enforce local grant session to the common user
Standardize on common user prex

Avoids plug in violaAons if the common user is
unknown to the CDB
12/3/15
Do not create objects in the common

users schema
Do not change privileges on Oracle
supplied common users
Grant the privilege within the targeted PDBs
Validate impact of common users prior to

unplug/plug operaAons
conicts are not captured in PDB
compaAbility checks
Management
Security Prac;ces - Ager Clone Trigger
PDB Cloning
Production
DEPT LAST_NAME
SSN
Non-Production
SALARY
10
AGUILAR
203-33-3234
40,000
20
BENSON
543-44-2737
30,000
10
CHANDRA
323-22-2943
60,000
30
DONNER
270-24-4023
50,000
DEPT
LAST_NAME
SSN
10
SMITH
11123-1111
40,000
10
JOHNSON
222-34-1345
60,000
Aser Clone Trigger allows to execute PL/SQL on the target

Useful to mask sensiAve informaAon on the target
Trigger code removed aser cloning is successful
12/3/15
SALARY
Q&A
35
Key Benets
Benet
Capability Enabled
Minimize CapEx
More applicaAons per server
Minimize OpEx
Manage many as one (reduced patching!)

Standardized procedures & service levels
Enable self-service provisioning
Maximize Agility
Easy
Snapshot cloning for development and tesAng

Portability through pluggability
Scalability with RAC
To Adopt: ApplicaAons run unchanged
To Use: Interface is SQL
12/3/15
Upgrade and Plugin as PDB

Upgrade or use exisAng 12.1 non-cdb
PDB$
SEED
Start database read-only

Create XML descripAon le
exec DBMS_PDB.DESCRIBE('PDB1.xml');
PDB1
CDB
Shutdown database
PDB1
xml
Run PDB compaAbility check

Plugin database
create pluggable database PDB1
using ('PDB1.xml') nocopy tempfile reuse;
DB1
Read Only
Convert to PDB
start ?/rdbms/admin/noncdb_to_pdb.sql
Create Pluggable Database

Crea;ng from scratch
SQL> create pluggable database PDB1 admin user admin identified by password;
Plugging a New PDB

SQL> create pluggable database PDB1 using /tmp/pdb1.xml;
Using le_name_convert
SQL> create pluggable database PDB1 using /tmp/pdb1.xml
file_name_convert = (/u01/oradata/cdb1, /u01/oradata/cdb2);
40
Create Pluggable Database

Unplugging and plugging a Pluggable database
At the source
SQL> alter pluggable database PDB1 close;
SQL> alter pluggable database PDB1 unplug into /tmp/pdb1.xml;
SQL> drop pluggable database PDB1 keep datafiles;
At the target
SQL> create pluggable database PDB1 using /tmp/pdb1.xml;
41
Cloning Pluggable Database

Full clone from another PDB.
SQL> create pluggable database PDB1 from PDB2;
Snapshot clone of a PDB

SQL> create pluggable database PDB1 from PDB2 snapshot copy;
Subset clone using USER_TABLESPACES clause

SQL> create pluggable database PDB1 from PDB2
user_tablespaces = (tbs1,tbs2);
42

Metadata only clone
SQL> create pluggable database PDB1 from PDB2 nodata;
Remote clone of a PDB

SQL> create pluggable database PDB1 from PDB2@CDB2_link;
Remote snapshot clone of PDB where CDBs share the same storage
SQL> create pluggable database PDB1 from PDB2@CDB2_LINK
snapshot copy;
43

Storage Agnos;c clone
SQL> Alter system set clonedb=TRUE scope=spfile;
-- Restart database and source stays in read-only
SQL> create pluggable database PDB1 from PDB2 snapshot copy;
Closing a pluggable database

SQL>
alter pluggable database PDB1 close <<immediate>>;
Dropping a pluggable database

SQL> drop pluggable database PDB1 including datafiles / Keep datafiles;
44

Multitenant Best Practices - Aioug

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Multitenant Best Practices - Aioug

Uploaded by

Copyright:

Available Formats

Oracle

MulAtenant Best PracAces

Safe Harbor Statement

Copyright 2015, Oracle and/or its aliates. All rights reserved. |

Oracle Database Architecture

Copyright 2015, Oracle and/or its aliates. All rights reserved. |

New MulAtenant Architecture

Copyright 2015, Oracle and/or its aliates. All rights reserved. |

New architecture for consolida;ng databases and simplifying opera;ons

Self-contained PDB for each applica;on

Portability (via pluggability)

Common opera;ons performed at Root level

Manage many as one (upgrade, backups, HA)

Copyright 2015, Oracle and/or its aliates. All rights reserved. |

Oracle Data and User Data

Before 12.1: Oracle and user data intermingle over ;me

New database contains

Oracle and customer

Planning & ConsolidaAon Target

Copyright 2015, Oracle and/or its aliates. All rights reserved. |

Are You Too Busy to Plan ?

How do I size my server ?

Analyze the Workloads

TacAcal View of MulAtenant

CreaAng a CDB and Snapshot clones

Provisioning, Self-Service, Adopt to

Conguring MulAtenant security for

Shares, caps, dynamic capabiliAes

PDB/Node Anity, portability, scale

Copyright 2015, Oracle and/or its aliates. All rights reserved. |

Provisioning & Cloning

Copyright 2015, Oracle and/or its aliates. All rights reserved. |

MulAtenant for Provisioning

PDBs can be cloned from

PDBs can be cloned from

Copyright 2015, Oracle and/or its aliates. All rights reserved. |

MulAtenant Cloning Types and Plaoorms

Supported on all plaoorms

File System AgnosAc

SNAPSHOT CLONE SYNTAX - CREATE PLUGGABLE

GUI or Silent Mode

AutomaAc PGA memory management

Set SGA_MAX_SIZE to a high value

Copyright 2015, Oracle and/or its aliates. All rights reserved. |

Initialization Parameters & Miscelleneous

Evaluate and adjust any parameter

Those that can be modied within a PDB

In order to nd the possible

Congure clone quotas and storage limits

PDB level parameters persist across Dont modify PDB$SEED

Review AutoTask scheduling

Monitor the Audit Directory

By default, all 3 auto tasks start at the same

Copyright 2015, Oracle and/or its aliates. All rights reserved. |

Copyright 2015, Oracle and/or its aliates. All rights reserved. |

Managing Shared Resources

Copyright 2015, Oracle and/or its aliates. All rights reserved. |

Resource AllocaAon Strategy

Same allocaAon for all PDBs

Ensures all PDBs get a specic share of the resources

Ensures all PDBs get a specic share of the resources

Copyright 2015, Oracle and/or its aliates. All rights reserved. |

Copyright 2015, Oracle and/or its aliates. All rights reserved. |