Oracle Database 12c : Multitenant

Technology

digicomp-academy-suisse-romande-sa
of 36
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Description
Présentation des nouveautés Oracle Database Multitenant 12c.

http://www.digicomp.ch/fr/oracle
Text
  • 1.1Copyright © 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.2Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 3. Oracle Database 12c Jean-Philippe Breysse Oracle Suisse3Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 4. Major Database Focus Areas SOCIALBLOG101100101001 001001101010 101011100101 010100100101SMART METERBIG DATA 4Copyright © 2013, Oracle and/or its affiliates. All rights reserved.ENGINEERED SYSTEMSCLOUD COMPUTING
  • 5. Private Database Cloud Architectures Using Oracle Database 11g Virtual MachinesDedicated Databasesshare serversshare servers and OS Increasing Consolidation5Copyright © 2013, Oracle and/or its affiliates. All rights reserved.Schema Consolidationshare servers, OS and database
  • 6. Private Database Cloud Architectures Using Oracle Database 12c Virtual MachinesDedicated DatabasesPluggable Databasesshare serversshare servers and OSshare servers, OS and databaseIncreasing Consolidation6Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 7. Consolidating Databases on Clouds Key requirements… No application changes Isolation and multitenancyFast provisioning and cloning Secure and highly available Lower IT costs Manage many as one Greater resource utilization Performant and scalable7Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 8. Oracle Database Architecture Requires memory, processes and database files System Resources8Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 9. New Multitenant Architecture Memory and processes required at container level only System Resources9Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 10. New Multitenant Architecture Memory and processes required at container level only System Resources10Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 11. Pluggable vs Separate Databases Highly Efficient: 6x Less H/W Resource, 5x more Scalable 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 5011Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 12. Consolidating Databases Step1: Upgrade databases in-placeUpgrade in Place12Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 13. Consolidating Databases Step2: Plug-in upgraded databases13Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 14. Managing Shared Resources Resource management for consolidated databasesLow Priority Medium PriorityHigh Priority14Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 15. Users Local users are the successors forcustomer-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 rootand is represented in every PDB  A common user can log into any PDBwhere it has “Create Session” and can therefore administer a PDB  The Oracle system is owned bycommon users 15Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 16. Common Users and Privileges Authorization is checked in the same way as in pre-12.1  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 privilegecommonly – 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 attemptedconsidering only the privileges that the user has in that container  Best practice: Don’t create objects in common user’s schema16Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 17. Improved Agility With Changing Workloads Expand Cluster to Support Flexible Consolidation Model Services CDB Instance 1CDB Instance 2Single SGA per CDB Instance Node1Multitenant Container Database (CDB)17Copyright © 2013, Oracle and/or its affiliates. All rights reserved.Node2
  • 18. Improved Agility With Changing Workloads Expand Cluster to Support Flexible Consolidation Model Services CDB Instance 1CDB Instance 3CDB Instance 2Single SGA per CDB Instance Node1Node3Multitenant Container Database (CDB)18Copyright © 2013, Oracle and/or its affiliates. All rights reserved.Node2
  • 19. Simplified Patching Apply changes once, all pluggable databases updatedUpgrade in-place19Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 20. Simplified Upgrades Flexible choice when patching & upgrading databases20Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 21. Patching via Unplug/Plug Details  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 patchset21Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 22. Manage Many Databases as One Backup databases as one; recover at pluggable database LevelOne BackupPoint-in-time recovery at pluggable database level22Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 23. PDB Point-in-time Recovery (PITR) Recovery isolation at granularity of PDB  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:RMAN> restore pluggable database my_db; RMAN> recover pluggable database my_db until SCN 411010; RMAN> alter pluggable database my_db open resetlogs;  All datafiles are recovered in-place, undo is recovered out of place andapplied in-place during open resetlogs.  Old backups of the PDB will continue to be valid.23Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 24. Manage Many Databases as One One standby database covers all pluggable databases24Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 25. Fast Provisioning Pluggable databases can be quickly provisioned from seed Time Taken to Provision New Database 25 20 15 10 5 0 Non CDB25Copyright © 2013, Oracle and/or its affiliates. All rights reserved.PDBClone PDB using Copy-on-Write File System
  • 26. Creating Databases for Test and Development Fast, flexible copy and snapshot of pluggable databases26Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 27. Multitenant for Provisioning Fast cloning of PDBs  PDBs can be cloned from within the same CDB27Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 28. Cloning a PDB Example Local create pluggable database HCMBI from HCM28Copyright © 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 only29Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 30. Multitenant Cloning with Snapshot Copy Thin provisioning of database clones in secondscreate pluggable database DEV44 from CRM_MASTER snapshot copy  Still SQL with new “as snapshot” clause  Where not supported receive errorORA-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 30Copyright © 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 ™31Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 32. Provisioning & Storage Gains with Snapshots Internal Tests on Sun ZFS Storage ApplianceFull Size (GB) Snap Size (KB)Relative SizeFull CloneSnap Clone% savings240.00058%9 min, 52 sec1 min, 52 sec80%2161420.00007%1hr, 21 min2 min, 11 sec97%1300321405510.00004%9hr, 7 min5 min 55 sec99%Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 33. New Multitenant Architecture Ideal for consolidating databases on Clouds No application changes Isolation and multitenancyFast provisioning and cloning Secure and highly available Lower IT costs Manage many as one Greater resource utilization Performant and scalable33Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 34. Manage Many as One with Multitenant Backup databases as one; recover at pluggable database levelOne BackupPoint-in-time recovery At pluggable database level34Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 35. Q&A35Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • 36. 36Copyright © 2013, Oracle and/or its affiliates. All rights reserved.
  • Comments
    Top