Oracle Database Multitenant Architecture 12.1

Ahmed Baraka
A free video tutorial from Ahmed Baraka
Snr. Database Administrator
4.6 instructor rating • 8 courses • 5,117 students

Lecture description

By the end of this lecture, you should be able to:
  • Describe the difference between the CDB and PDB
  • Describe the Multitenant Architecture components
  • Describe the difference between the shared undo and the local undo configuration
  • Describe the difference between the local users and common users
  • Understand the impact of implementing a multitenant configuration

Learn more from the full course

Oracle 12c Multitenant Architecture Administration

Learn how to build and manage an Oracle 12c Multitenant Architecture database.

10:18:37 of on-demand video • Updated April 2021

  • Describe the Oracle 12c multitenant architecture
  • Create multitenant container database
  • Create a pluggable database using different methods
  • Create and manage common and local user accounts
  • Manage PDB lockdown profiles
  • Perform backup and recovery
  • Perform PITR and flashback
  • Use the Resource Manager in a container database
  • Use Data Pump utility with PDBs
  • Manage the applications and application containers
English [Auto] Hi everyone in this lecture I will talk about the Oracle Database multitenant architecture. It really is. Twelve point one. By the end of this lecture you should be able to describe the difference between the CVB and PKB. Describe the multi-tenant architecture components. Describe the difference between that shared undo and the local and do configuration. Describe the difference between local users and the common users and understand the impact of implementing a multitenant configuration in how you live in the multi-tenant architecture is composed of two main components the instance and the multitenant container database the instance of structure is similar to the NCDC architecture. It has that is the area which resides in the memory of the server and a group of that background processes like the Pieman Essman the writer and so on. Every CD must have exactly one CD root container. It is also called the root the root stores. Oracle supplied meta data like the Data Dictionary of this system objects and the source code of that Oracle supplied the IL sequel packages. The route is not meant to create user data in it. Although technically you can do that in the physical level. The route has the same data files that you see in the traditional Nancy D-B database. It has the table it spaces system says auxilary undo data files the temporary table of spaces and you can create permanent user table spaces the control files online retailer acquires parameter file and there they do archived files belonging to the CD but not to any specific PDP. At the end of recreating a CD be it is not necessary to have pluggable databases created on the top of it. Normally after creating the CD B you create one or more DBMS to store the application data and code in them. Putting Zambelli may create a PDB to support a specific human resources or sales application or you may create a PDB to support a development or testing application in the physical level. PDB does have only data files beside the table of spaces that hold the application data. PDP is must have the system and this is auxilary table of spaces in release it will have Point 1. You cannot create undo table spaces in the Gibbie's release will have Boinne too. You can't configure the CVB to allow creating undo tablespace in the PDP is. Those are the new terms that we came across so far in Oracle multitenant architecture. The content of databases or CVB is a multitenant container database that houses Xiu or more pluggable databases. If you don't configure them multitenant option in your database we called the database then NCGUB. This is the only available architecture in Oracle databases before 12 see a pluggable database or PDB is a portable collection of schemas schema objects and none schema objects. It appears to the client as an NCGUB did Abbey's. Here I am getting into the structure of the multitenant architecture in more details. In the instance Levu there isn't much new to talk about. It's a structure is nearly the same as the instance of structure in the NCGUB database. But as you have seen Elya the most dramatic changes are in the database Livre every CD B must have one and only one root container in the code Libelle the root has the name See B do not assign a root. This is the root container name and you can change it the route start all the system dictionary tables the Oracle supplied packages and the articles supplied system users like this and system they use that data should not go in. If you want to manage it don't log files archive and read or log files or the control files you must log into the container. You cannot manage them by logging on to any other container. Observe here that the online array to log files are generated for the entire CGP. You cannot define online Riddel requires dedicated to a specific PDB every CVB database comes with a special type of PDB called ceed technically this PDB has the name PDB dollar sign ceed the C PDB is a system supplied template PDP. It is solely used to create new user PCBs. You cannot add or modify objects in the container. It is only used as a template to create new PDB as the PDB is hold. The application data and its database code each PDB appears as a whole database to its users with multiple schemas subjects table spaces dictionary views and so on. By Design anyone connected to a PDB cannot distinguish it from a stand alone. Nancy D-B database or the commands used in the previous Oracle database versions are supported. However that fact could be different. For example if ADP is connected to a PDB and issue the command shutdown it closes the PDB but it will not actually shut down the instance. Still the DBI will see exactly what he would see if he shuts down. A stand alone Nancy D-B the Debby's. Please be aware that this chart is not demonstrating the undo tablespace is because I'm going to talk about it in a little a slight in the previous slide you have learnt about two more multitenant terms. The root container and the seed PDB. I have already described them and am listing them over here only for reference regarding the undo tablespace. You have the option to create it in the root and let all that PDB is used that undo tablespace and. Twelve point one. This is the only available configuration. In this case the undo tablespace in the root is shared by all. The PDP is in the see the this configuration has a big advantage. It doesn't allow you to perform point in time recovery for a specific PCB with the shared undo configuration. If you need to perform point in time recovery you can only do it for the entire Sigsbee also as you will learn later in the course. The shared undo configuration applies availability constraints when you want to clone PDB as it will Boinne to. We have the choice to run the CVB in a local undo mode if local undo is on each placable database has its own undo tablespace this is a big improvement in release twelve point two because this configuration allows point in time recovery in the PDP level and more efficient. Flashback pluggable database. It is highly recommended to use the local undo configuration in any D-B database. This is a summary of all the concepts that have been mentioned so far in this lecture at. I don't have to state them again. I just listed them here to refresh those concepts in your mind. Please go through them and make sure you understand all of them before you proceed with the lecture. Articulate C introduces a new concept called local users and common users a local user is defined in a PDB and it is not known outside of that PDB a local user can connect only to the PDB where it is defined. If it has the required as a local user can work on the application data within the PDB local users cannot be defined in that local user within a PDB. Is it pretty much like a user in an NCGUB database a common user is defined in the root. But it is known in the road as well as in all that PDB is that belongs to the root. Even when you create a new PDB then you PTB will recognize the existing common users some administrative operations like creating a PDB and unplugging a PDB must be performed by a common user local users cannot perform those tasks system is an example of a common user that is created by Oracle. With every new OCB you can create your own Coman user if you need to. This is a summary of the local and common users concepts that I have talked about in the last two sleights. Later in the course you will gain more detailed information about the local and Coman users. For now this information is fair enough over here. I am listing the major impact of the multitenant on the traditional Nancy D-B database autokey data. God works the same in the CDB level as it does in Nancy Digby's. When you open a physical standby database you open the root container in read only mode and this. This allows all that PDB is from opening in a mode other than the read only mode. The gov't option cannot be used in the PDB live in if all local database vote is being used. It is isolated within a PDP. Each PDB has its own database vault me today. All the coolest dreams is is then supported an Oracle database that will see Nancy D-B configuration but it cannot be used with CD because you need to take those facts into your considerations when you plan to migrate to SCDP database. In this lecture you should have learnt the following. Describe the difference between that CD B and PTB. The shared undo and the local undo configuration the local users and common users describe the multi-tenant architecture components and understand the impact of implementing a multitenant configuration in the next lecture. I will talk about the Oracle Database multitenant architecture and release 12. to see over it.