Behind the scenes of Oracle MulCtenant

Transcription

1

2 Behind the scenes of Oracle MulCtenant A new architecture for consolida2ng databases and simplifying opera2ons in the cloud Deba ChaFerjee Principal Product Manager, Oracle Database

3 Safe Harbor Statement The following is intended to outline our general product direccon. It is intended for informacon purposes only, and may not be incorporated into any contract. It is not a commitment to deliver any material, code, or funcconality, and should not be relied upon in making purchasing decisions. The development, release, and Cming of any features or funcconality described for Oracle s products remains at the sole discrecon of Oracle. Oracle ConfidenCal Internal/Restricted/Highly Restricted 3

4 Agenda Horizontal ParCConing of the Data DicConary Cloning in Oracle MulCtenant Sharing Resources in a MulCtenant Environment AggregaCng Data across PDBs Security Changes Oracle ConfidenCal Internal/Restricted/Highly Restricted 4

5 Agenda Horizontal Par22oning of the Data Dic2onary Cloning in Oracle MulCtenant Sharing Resources in a MulCtenant Environment AggregaCng Data across PDBs Security Changes Oracle ConfidenCal Internal/Restricted/Highly Restricted 5

6 MulCtenant Architecture Components of a Mul2tenant Container Database (CDB) PDBs Root CDB Pluggable Databases MulCtenant Container Database 6

7 A Pluggable Database Is a Portable Database Unplugging a PDB and plugging it in PO GL OE AP AP Simply unplug from the old CDB and plug it into the new CDB Moving between CDBs is a simple case of moving a PDB s metadata An unplugged PDB carries with it lineage, opatch, encrypcon key info etc. 7

8 Common Data DicConary Before 12.1: Oracle and user meta data intermingle over 2me Meta Data User Data Data Dictionary Meta Data User Data Data Dictionary Meta Data User Data Data Dictionary Database Created Tables, Code, Data added Mature Database

9 Oracle Data and User Data Multitenant fix: Horizontally-partitioned data dictionary Only Oracle system definition remains OBJ$ TAB$ SOURCE$ EMP DEPT Oracle and customer metadata intermingled

10 Horizontally ParCConed Data DicConary OBJ$ TAB$ SOURCE$ EMP DEPT Oracle-supplied objects such as views, PL/SQL, etc., are shared across all PDBs using object stubs In-database virtualization OBJ$ TAB$ SOURCE$

11 Objects in a Container database Metadata- Linked Sharing Oracle Supplied Object definicon e.g. PL/SQL (DBMS_SQL) Object- Linked Share data stored in root across all PDBs e.g. AWR tables (Data is stored in CDB$ROOT) Container- Data Objects that show data from root and all available PDBs PDB specific inside a PDB e.g. CDB_% views (CDB_USERS) Common- Data Show common metadata and PDB specific metadata e.g. DBA_SOURCE queried within a PDB Oracle ConfidenCal Internal/Restricted/Highly Restricted 11

12 DicConary and Performance views PDB- to- PDB privacy; overall system image The performance views have a new Con_ID column There s a new CDB_ dicconary view family with a Con_ID column These are so- called container- data objects When queried from a PDB, the results show only Con_ID for that PDB When queried from the root, the results may show all Con_ID values The containers you see depend on an afribute of the user that lists these (or says all present and future )

13 Data Dictionary Views CDB_xxx All objects in the mulctenant container database across all PDBs DBA_xxx All of the objects in a container or pluggable database ALL_xxx Objects accessible by the current user USER_xxx Objects owned by the current user SQL> SELECT view_name FROM dba_views WHERE view_name like 'CDB%'; CDB_pdbs: All PDBS within CDB CDB_tablespaces: All tablespaces within CDB CDB_users: All users within CDB (common and local) DBA dictionary views providing information within PDB: SQL> SELECT table_name FROM dict WHERE table_name like 'DBA%';

14 Performance Views When queried from a PDB, queries against v$ views will show only informacon pertaining to the PDB or the CDB as a whole. When queried from ROOT, v$ views and CDB_ views can return rows for more than one container. Rows returned from querying these views have an addiconal con_id column. These views are known as container_data views. The container_data sekng for the common user issuing the query will determine what rows are aggregated and made visible.

15 Agenda Horizontal ParCConing of the Data DicConary Cloning in Oracle Mul2tenant Sharing Resources in a MulCtenant Environment AggregaCng Data across PDBs Security Changes Oracle ConfidenCal Internal/Restricted/Highly Restricted 15

16 MulCtenant 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 GL OE AP PO PDBs can be cloned from remote CDBs PDBs can be cloned from non- CDBs Thinly provision snapshot clones in seconds 16

17 Cloning and creacng PDBs Rich and rapid provisioning capability delivered with the ease of SQL Provision a new PDB create pluggable database PDB3 admin user PDB_Admin identified by p roles = (DBA)! Provision a remote full clone create pluggable database PDB2 from PDB1@CDB2! Thinly provision a local snapshot clone create pluggable database PDB2 from PDB1 snapshot copy!

18 TradiConal File System Full copy duplicates all data blocks my_file my_file_copy File is colleccon of data blocks And headers Copy duplicates header & data blocks EffecCve & simple, but expensive! cp my_file my_file_copy

19 Copy- on- Write Basics Much more efficient storage of substan2ally similar files my_file my_file_copy File is colleccon of data blocks And headers Copy file requires only copy of header Much more efficient storage Minimal IO to create copy Only copy block when changed cp my_file my_file_copy

20 Provisioning & Storage Gains with Snapshots Internal Tests on Sun ZFS Storage Appliance Full Size (GB) Full Clone 24 9 min, 52 sec 216 1hr, 21 min hr, 7 min

21 Provisioning & Storage Gains with Snapshots Internal Tests on Sun ZFS Storage Appliance Full Size (GB) Snap Size (KB) Rela2ve Size Full Clone Snap Clone % Savings % 9 min, 52 sec 1 min, 52 sec 80% % 1hr, 21 min 2 min, 11 sec 97% % 9hr, 7 min 5 min 55 sec 99%

22 Cloning a on- premise non- CDB to a PDB in cloud Seed GL OE 1. Convert a non- CDB upgraded to directly as a PDB using a database link 2. The data files for clone the are copied over from the source using the database link over SQL Net 3. Once pluggable database is created you will need to run noncdb_to_pdb.sql 4. No need to generate the XML manifest file. GL OE

23 Convert schema based consolidacon to a PDB in cloud AP GL Schema GL OE AR Customers have implemented schema based consolidacon The subset clone using USER_TABLESPACES clause migrate these schemas into individual pluggable databases 23

24 AddiConal Plauorm Support for Cloning New Features in Support snapshot clones on local, NFS or clustered filesystem with dnfs enabled File system agnoscc snapshot clones of pluggable databases Set inicalizacon parameter clonedb=true; Source should be READ- ONLY What? Why? How? Copyright 2014, Oracle and/or its affiliates. All rights reserved.

25 DEMO 1. Create a PDB over database link 2. Create a snapshot clone Oracle ConfidenCal Internal/Restricted/Highly Restricted 25

26 Agenda Horizontal ParCConing of the Data DicConary Cloning in Oracle MulCtenant Sharing Resources in a Mul2tenant Environment Security Changes AggregaCng Data across PDBs Oracle ConfidenCal Internal/Restricted/Highly Restricted 26

27 Managing Shared Resources Resource management in a mul2tenant environment GL OE AP High Priority Medium Priority Low Priority 27

28 Managing Resources Between PDBs Using Resource Manager, you can control CPU Exadata I/O Sessions Parallel execucon servers Simple- yet- powerful policies configured in terms of: A number of shares allocated to each PDB A cap (a.k.a. maximum uclizacon limit) may be applied to each PDB

29 AllocaCng Resources in DB 12c No Resource AllocaCon Gives maximum flexibility for each PDB Allows any PDB to consume all available resource Risky as one PDB can run away with all resources. Specify a minimum allocacon Ensures all PDBs get a specific share of the resources Allows any PDB to consume any unused resources Kicks in at 100% resource uclizacon. Assumes that not all PDBs will use its allocated resources Specify a minimum and maximum Ensures all PDBs get a specific share of the resources Prevents a PDB from taking more than the maximum value assigned. May result in unused capacity

30 Manage CPU A CDB Resource Plan uses shares to specify how CPU is distributed between PDBs 2 Shares 1 Share 1 Share 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%

31 Manage CPU A CDB Resource Plan uses utilization limits to limit the CPU usage for a PDB. With utilization limits, your CPU may be underutilized. 2 Shares 1 Share 50% 1 Share 50% Pluggable Database Shares Guaranteed CPU U2liza2on Limit Maximum CPU HCM 2 2/4 = 50% 100% CRM 1 1/4 = 25% 50% 50% ERP 1 1/4 = 25% 50% 50%

32 Manage CPU Configure a default directive: the default shares and utilization limit for PDBs. With a default directive, you don t need to modify the resource plan for each PDB plug and unplug 2 Shares Default Default Pluggable Database Shares Guaranteed CPU U2liza2on Limit Maximum CPU (Default direccve) 1 50% HCM 2 2/4 = 50% 100% CRM default (1) 1/4 = 25% default (50%) 50% ERP default (1) 1/4 = 25% default (50%) 50%

33 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 PDB s parallel operations. PDB Shares Parallel Server Percentage Parallel Degree Limit ETL BI DW

34 Sekng up Resource Manager in Oracle Enterprise Manager Extremely simple to manage the CDB resource plans using Enterprise Manager UI

35 Agenda Horizontal ParCConing of the Data DicConary Cloning in Oracle MulCtenant Sharing Resources in a MulCtenant Environment Aggrega2ng Data across PDBs Security Changes Oracle ConfidenCal Internal/Restricted/Highly Restricted 35

36 CONTAINERS Clause New Features in With the containers clause data can be aggregated from idenccal tables/views across many PDBs from the root container Provide a way to aggregate user created data from mulcple PDBs in the same container select ENAME from containers(scof.emp) Where CON_ID in (45, 49); What? Why? How? Copyright 2014, Oracle and/or its affiliates. All rights reserved.

37 Example My Toy Company (1) Oracle ConfidenCal Internal/Restricted/Highly Restricted 37

38 Example My Toy Company (2) DOLLS SALES_DATA ROBOTS SALES_DATA Oracle ConfidenCal Internal/Restricted/Highly Restricted 38

39 Example My Toy Company (3) Can I write a single query to aggregate data from both PDBs? Oracle ConfidenCal Internal/Restricted/Highly Restricted 39

40 Agenda Horizontal ParCConing of the Data DicConary Cloning in Oracle MulCtenant Sharing Resources in a MulCtenant Environment AggregaCng Data across PDBs Security Concepts Oracle ConfidenCal Internal/Restricted/Highly Restricted 40

41 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

42 Common Users and Privileges Authoriza2on is checked in the same way as as pre A common user can be granted privileges locally in a PDB (or root) and therefore differently in each container A common user can, alternacvely, 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 AuthorizaCon is checked in the container where the SQL is afempted considering only the privileges that the user has in that container

43 GranCng the Sysdba privilege in a PDB You can grant any system privilege to a either local, or a common user When a user authorizes AS SYSDBA in a PDB, the effect is contained to within that PDB NOTE: you cannot delete objects like Sys.DBMS_Sql in a PDB This does not enable the user to get to another container Gekng to a new container depends only on the privileges that the user has in the new container

44 Services and Sessions The five facts have the same result as pre Listener locacon, listener port, service name, username, password Now a service has a new property: the inical PDB A session is created in essencally the same as before A local user can connect to a PDB only by using network authenccacon A local user can create a session only in the PDB where it is defined, subject, to having Create Session there A common user can create a session in any PDB where it has Create Session

45 Another way to choose the current container For admin tasks or conneccon pooling alter session set container = PDB_01 Of course, only a common user can do this because only a common can be known in both the present container and the descnacon container This requires the new Set Container system privilege in the descnacon container

46 Oracle ConfidenCal Internal/Restricted/Highly Restricted 46

47