This document discusses connecting to a Container Database (CDB) and pluggable databases (PDBs) in Oracle Database 12c. It covers how to connect to the CDB root and PDBs using services, and how connections are unchanged from previous versions. It also discusses users, grants, and roles in a CDB, including how users can be common or local, and how roles can be common or local. It provides examples of how to create common and local users and roles.
This document discusses the creation of a multitenant container database (CDB) and pluggable databases (PDBs) in Oracle Database 12c. It covers creating a CDB using Oracle Universal Installer, Database Configuration Assistant, or manually. The manual process involves setting enable_pluggable_database to true, adding clauses to the CREATE DATABASE command, and running a script that creates the root and seed PDBs. The document also provides commands to validate if a database is a CDB and view its containers.
New features in Oracle Database 12c include the ability to restore tables and partitions using RMAN backups. A table or partition recovery using RMAN will identify required backups, construct an auxiliary database temporarily, export the table/partition to a dump file, and optionally import the table/partition back into the source database. It is also now possible to execute SQL statements directly in RMAN without using a SQL prefix. Additionally, DDL statements can now be logged to XML and log files when DDL logging is enabled. Data files can also be renamed or relocated online using the ALTER DATABASE statement in 12c.
The document discusses Oracle Database 12c Resource Manager capabilities for managing resources in Container Databases (CDBs) and Pluggable Databases (PDBs). The key points are:
1. Resource Manager can manage resources at both the CDB level, allocating resources between PDBs, and at the PDB level, allocating resources between sessions within each PDB.
2. At the CDB level, Resource Manager uses shares to define the proportion of CDB resources allocated to each PDB and limits to control each PDB's resource usage.
3. At the PDB level, Resource Manager uses resource plans to allocate resources between consumer groups, similar to how it manages resources within a non-CDB database.
The document discusses Oracle 12c's multitenant architecture which introduces the concepts of a container database (CDB) and pluggable databases (PDBs). A CDB can host multiple PDBs that appear as independent databases but share resources. PDBs can be unplugged from one CDB and plugged into another, allowing for quick provisioning and cloning of databases. The multitenant architecture provides benefits like consolidation of databases, rapid provisioning and cloning using SQL, and easier patching and upgrades.
Kellyn Pot’Vin is a senior technical consultant and Oracle ACE Director who has authored books and leads various database technology groups. Oracle Multitenant was released in 2013 and allows databases called pluggable databases (PDBs) to be contained within a single container database (CDB), sharing resources. PDBs can be easily migrated, cloned, and provisioned. Monitoring and administration of CDBs and PDBs uses new database views with the CON_ID identifier to distinguish containers and pluggables.
Using oracle12c pluggable databases to archiveSecure-24
The document discusses using Oracle 12c pluggable databases to consolidate archive log data from multiple older Oracle databases. It describes the pre-Oracle 12c configuration with 7 separate archive databases from 2008-2014 totaling 14TB. It then covers setting up an Oracle 12c container database with pluggable databases for each year to address issues with the prior configuration like limited memory, unsupported older database versions, and lack of planning for old data. Methods covered for moving data between the old and new databases include Cloud Control provisioning, DBMS_PDB, and Datapump export/import.
This document provides an overview of Oracle 12c Pluggable Databases (PDBs). Key points include:
- PDBs allow multiple databases to be consolidated within a single container database (CDB), providing benefits like faster provisioning and upgrades by doing them once per CDB.
- Each PDB acts as an independent database with its own data dictionary but shares resources like redo logs at the CDB level. PDBs can be unplugged from one CDB and plugged into another.
- Hands-on labs demonstrate how to create, open, clone, and migrate PDBs between CDBs. The document also compares characteristics of CDBs and PDBs and shows how a non-C
This document discusses the creation of a multitenant container database (CDB) and pluggable databases (PDBs) in Oracle Database 12c. It covers creating a CDB using Oracle Universal Installer, Database Configuration Assistant, or manually. The manual process involves setting enable_pluggable_database to true, adding clauses to the CREATE DATABASE command, and running a script that creates the root and seed PDBs. The document also provides commands to validate if a database is a CDB and view its containers.
New features in Oracle Database 12c include the ability to restore tables and partitions using RMAN backups. A table or partition recovery using RMAN will identify required backups, construct an auxiliary database temporarily, export the table/partition to a dump file, and optionally import the table/partition back into the source database. It is also now possible to execute SQL statements directly in RMAN without using a SQL prefix. Additionally, DDL statements can now be logged to XML and log files when DDL logging is enabled. Data files can also be renamed or relocated online using the ALTER DATABASE statement in 12c.
The document discusses Oracle Database 12c Resource Manager capabilities for managing resources in Container Databases (CDBs) and Pluggable Databases (PDBs). The key points are:
1. Resource Manager can manage resources at both the CDB level, allocating resources between PDBs, and at the PDB level, allocating resources between sessions within each PDB.
2. At the CDB level, Resource Manager uses shares to define the proportion of CDB resources allocated to each PDB and limits to control each PDB's resource usage.
3. At the PDB level, Resource Manager uses resource plans to allocate resources between consumer groups, similar to how it manages resources within a non-CDB database.
The document discusses Oracle 12c's multitenant architecture which introduces the concepts of a container database (CDB) and pluggable databases (PDBs). A CDB can host multiple PDBs that appear as independent databases but share resources. PDBs can be unplugged from one CDB and plugged into another, allowing for quick provisioning and cloning of databases. The multitenant architecture provides benefits like consolidation of databases, rapid provisioning and cloning using SQL, and easier patching and upgrades.
Kellyn Pot’Vin is a senior technical consultant and Oracle ACE Director who has authored books and leads various database technology groups. Oracle Multitenant was released in 2013 and allows databases called pluggable databases (PDBs) to be contained within a single container database (CDB), sharing resources. PDBs can be easily migrated, cloned, and provisioned. Monitoring and administration of CDBs and PDBs uses new database views with the CON_ID identifier to distinguish containers and pluggables.
Using oracle12c pluggable databases to archiveSecure-24
The document discusses using Oracle 12c pluggable databases to consolidate archive log data from multiple older Oracle databases. It describes the pre-Oracle 12c configuration with 7 separate archive databases from 2008-2014 totaling 14TB. It then covers setting up an Oracle 12c container database with pluggable databases for each year to address issues with the prior configuration like limited memory, unsupported older database versions, and lack of planning for old data. Methods covered for moving data between the old and new databases include Cloud Control provisioning, DBMS_PDB, and Datapump export/import.
This document provides an overview of Oracle 12c Pluggable Databases (PDBs). Key points include:
- PDBs allow multiple databases to be consolidated within a single container database (CDB), providing benefits like faster provisioning and upgrades by doing them once per CDB.
- Each PDB acts as an independent database with its own data dictionary but shares resources like redo logs at the CDB level. PDBs can be unplugged from one CDB and plugged into another.
- Hands-on labs demonstrate how to create, open, clone, and migrate PDBs between CDBs. The document also compares characteristics of CDBs and PDBs and shows how a non-C
Oracle is planning to release Oracle Database 12c in calendar year 2013. The new release will include a multitenant architecture that allows for multiple pluggable databases to be consolidated and managed within a single container database. This new architecture enables fast provisioning of new databases, efficient cloning of pluggable databases, simplified patching and upgrades applied commonly to all pluggable databases, and other benefits that improve database consolidation on cloud platforms.
Simplify Consolidation with Oracle Database 12cMaris Elsins
This document discusses Oracle Database 12c's Multitenant architecture, which allows for more efficient consolidation of multiple pluggable databases (PDBs) within a single container database (CDB). Key benefits include more flexible provisioning of new databases, simplified cloning and upgrades done at the CDB level, and improved resource utilization through workload separation. While Multitenant is only available in the Enterprise Edition, the plug/unplug functionality can provide benefits even for single-tenant use cases.
This document provides an overview of Oracle 12c and its pluggable database feature from a presentation by Gustavo René Antúnez, an Oracle DBA at Pythian. It discusses the benefits of pluggable databases such as greater scalability and consolidation. It also covers key aspects of the multitenant architecture like common users, local users, and views that span the container and pluggable databases. The presentation concludes with a demonstration of RMAN backups in a multitenant environment.
This document provides an architectural diagram of a multitenant database. It shows that a multitenant container database (CDB) contains multiple pluggable databases (PDBs). Common objects like users and roles are defined at the CDB level while each PDB contains local users, roles, and database objects like tables. System resources like memory and processes are shared between the CDB and PDBs.
The document discusses new features in Oracle Database 12c including the introduction of a multitenant architecture. Key points include:
- 12c introduces a multitenant architecture that allows a single database to host many pluggable databases (PDBs). This improves consolidation and resource utilization.
- PDBs can be quickly provisioned from seed databases or cloned from other PDBs. Common operations can be performed at the container database level.
- Adaptive execution plans allow queries to dynamically switch plans at runtime if optimizer estimates prove inaccurate based on statistics collected during execution.
Reduce planned database down time with Oracle technologyKirill Loifman
How to design an Oracle database system to minimize planned interruptions? That depends on the requirements, goals, SLAs etc. The presentation will follow top-down approach. First we will describe major types of planned maintenance, prioritize those and then based on the system availability requirements find the best cost-effective technics to address those. A bit of planning, strategy and of course modern database and OS technics including latest Oracle 12c features.
Exploring Oracle Database 12c Multitenant best practices for your Clouddyahalom
The document discusses best practices for Oracle Database 12c Multitenant architecture. It begins by introducing the speaker and their company Brillix-DBAces. It then provides an overview of the Multitenant Container Database architecture in 12c, including the root and pluggable database containers, common vs local users/roles/privileges, and tools for working with Container Databases like SQL*Plus, DBCA, and Enterprise Manager.
Red Stack Tech Ltd is a global Oracle Technology brand specialising in the provision of Oracle software, Hardware, Managed and professional services across the entire Oracle Technology stack. Established in the mid 90’s, Red Stack Tech have developed through R&D and investment in new technologies, a brand which is highly regarded within the Oracle landscape. Red Stack Tech are able to deliver full end-to-end solutions that encompass all Oracle technologies with a strong focus on Oracle Engineered Systems, Database Management Services and Business Analytics.
Today, many businesses around the world are using an Oracle product and in many of these at the core there is an Oracle Database. Many of us who started as a Database administrator where put in this position because we were good PL/SQL programmers or good Sysadmins, but knew very little of what it took to be a DBA. In this session you will learn the core architecture of an Oracle Database in 12c as well as what it takes to administer and apply this new knowledge the day you go back to your office.
Database Consolidation using the Oracle Multitenant ArchitecturePini Dibask
The document discusses Oracle's Multitenant architecture, which allows multiple pluggable databases (PDBs) to consolidate within a single multitenant container database (CDB). It describes how Multitenant provides advantages like simplified upgrades, cloning, and migration of PDBs. The document also covers ensuring quality of service for PDBs using resource management, and how RAC supports high availability and scalability in a Multitenant environment. It concludes with a discussion of performance monitoring of workloads across PDBs.
Oracle Database 12c introduces several new features including pluggable databases (PDB) that allow multiple isolated databases to be consolidated within a single container database (CDB). It also introduces new administrative privileges (SYSBACKUP, SYSDG, SYSKM) and features such as transparent data encryption, invisible columns, object tables, and enhancements to RMAN and SQL.
RMAN has evolved since Oracle 8i and includes new features in Oracle 12c that help reduce downtime. In 12c, a container database can include pluggable databases. RMAN supports backup and recovery of container databases and individual pluggable databases. New features in 12c include the SYSBACKUP privilege which allows backups without granting full SYSDBA privileges, and support for multitenant container databases and pluggable databases.
Oracle Architecture document discusses:
1. The cost of an Oracle Enterprise Edition license is $47,500 per processor.
2. It provides an overview of key Oracle components like the instance, database, listener and cost based optimizer.
3. It demonstrates how to start an Oracle instance, check active processes, mount and open a database, and query it locally and remotely after starting the listener.
HBase 2.0 is the next stable major release for Apache HBase scheduled for early 2017. It is the biggest and most exciting milestone release from the Apache community after 1.0. HBase-2.0 contains a large number of features that is long time in the development, some of which include rewritten region assignment, perf improvements (RPC, rewritten write pipeline, etc), async clients, C++ client, offheaping memstore and other buffers, Spark integration, shading of dependencies as well as a lot of other fixes and stability improvements. We will go into technical details on some of the most important improvements in the release, as well as what are the implications for the users in terms of API and upgrade paths. Existing users of HBase/Phoenix as well as operators managing HBase clusters will benefit the most where they can learn about the new release and the long list of features. We will also briefly cover earlier 1.x release lines and compatibility and upgrade paths for existing users and conclude by giving an outlook on the next level of initiatives for the project.
This document discusses new features in Oracle WebLogic Server 12c. It begins with an introduction of the presenters. It then outlines 12 key things to know about WebLogic 12c, including an updated installer, per-domain Node Manager, server templates, dynamic clusters, unicast groups, cluster-targeted JMS, Java Mission Control for monitoring, built-in WLDF diagnostic modules, and RESTful management APIs. The document provides information on why upgrading to WebLogic 12.1.3 would be beneficial.
HBase and HDFS: Understanding FileSystem Usage in HBaseenissoz
This document discusses file system usage in HBase. It provides an overview of the three main file types in HBase: write-ahead logs (WALs), data files, and reference files. It describes durability semantics, IO fencing techniques for region server recovery, and how HBase leverages data locality through short circuit reads, checksums, and block placement hints. The document is intended help understand HBase's interactions with HDFS for tuning IO performance.
12cR2 Single-Tenant: Multitenant Features for All EditionsFranck Pachot
Multitenant architecture is available even without Oracle's multitenant option. In this session take a look at the overhead and the 12.2 new features so that you can choose among single-tenant or non-container databases. These features include agility in data movement, easy flashback, and fast upgrade.
The document discusses best practices for operating and supporting Apache HBase. It outlines tools like the HBase UI and HBCK that can be used to debug issues. The top categories of issues covered are region server stability problems, read/write performance, and inconsistencies. SmartSense is introduced as a tool that can help detect configuration issues proactively.
Ameerpet Online Training gives you an effective and proven online learning option with an extensive learning catalog and the freedom to attend from virtually anywhere. We have trained nearly 1500+ Students on all technologies.
We are offering 10% off on Oracle Training and we will arrange a free demo at your flexible timings
This document outlines the agenda for a training on Oracle RDBMS 12c new features. The training will cover 6 chapters: introduction, multitenant architecture, upgrade features, Flex Cluster, Global Data Service, and an overview of RDBMS features. The agenda provides a high-level overview of topics to be discussed in each chapter, including multitenant architecture concepts, upgrade options and tools, Flex Cluster configurations, Global Data Service components, and new features such as temporary undo and multiple indexes on the same columns.
Oracle is planning to release Oracle Database 12c in calendar year 2013. The new release will include a multitenant architecture that allows for multiple pluggable databases to be consolidated and managed within a single container database. This new architecture enables fast provisioning of new databases, efficient cloning of pluggable databases, simplified patching and upgrades applied commonly to all pluggable databases, and other benefits that improve database consolidation on cloud platforms.
Simplify Consolidation with Oracle Database 12cMaris Elsins
This document discusses Oracle Database 12c's Multitenant architecture, which allows for more efficient consolidation of multiple pluggable databases (PDBs) within a single container database (CDB). Key benefits include more flexible provisioning of new databases, simplified cloning and upgrades done at the CDB level, and improved resource utilization through workload separation. While Multitenant is only available in the Enterprise Edition, the plug/unplug functionality can provide benefits even for single-tenant use cases.
This document provides an overview of Oracle 12c and its pluggable database feature from a presentation by Gustavo René Antúnez, an Oracle DBA at Pythian. It discusses the benefits of pluggable databases such as greater scalability and consolidation. It also covers key aspects of the multitenant architecture like common users, local users, and views that span the container and pluggable databases. The presentation concludes with a demonstration of RMAN backups in a multitenant environment.
This document provides an architectural diagram of a multitenant database. It shows that a multitenant container database (CDB) contains multiple pluggable databases (PDBs). Common objects like users and roles are defined at the CDB level while each PDB contains local users, roles, and database objects like tables. System resources like memory and processes are shared between the CDB and PDBs.
The document discusses new features in Oracle Database 12c including the introduction of a multitenant architecture. Key points include:
- 12c introduces a multitenant architecture that allows a single database to host many pluggable databases (PDBs). This improves consolidation and resource utilization.
- PDBs can be quickly provisioned from seed databases or cloned from other PDBs. Common operations can be performed at the container database level.
- Adaptive execution plans allow queries to dynamically switch plans at runtime if optimizer estimates prove inaccurate based on statistics collected during execution.
Reduce planned database down time with Oracle technologyKirill Loifman
How to design an Oracle database system to minimize planned interruptions? That depends on the requirements, goals, SLAs etc. The presentation will follow top-down approach. First we will describe major types of planned maintenance, prioritize those and then based on the system availability requirements find the best cost-effective technics to address those. A bit of planning, strategy and of course modern database and OS technics including latest Oracle 12c features.
Exploring Oracle Database 12c Multitenant best practices for your Clouddyahalom
The document discusses best practices for Oracle Database 12c Multitenant architecture. It begins by introducing the speaker and their company Brillix-DBAces. It then provides an overview of the Multitenant Container Database architecture in 12c, including the root and pluggable database containers, common vs local users/roles/privileges, and tools for working with Container Databases like SQL*Plus, DBCA, and Enterprise Manager.
Red Stack Tech Ltd is a global Oracle Technology brand specialising in the provision of Oracle software, Hardware, Managed and professional services across the entire Oracle Technology stack. Established in the mid 90’s, Red Stack Tech have developed through R&D and investment in new technologies, a brand which is highly regarded within the Oracle landscape. Red Stack Tech are able to deliver full end-to-end solutions that encompass all Oracle technologies with a strong focus on Oracle Engineered Systems, Database Management Services and Business Analytics.
Today, many businesses around the world are using an Oracle product and in many of these at the core there is an Oracle Database. Many of us who started as a Database administrator where put in this position because we were good PL/SQL programmers or good Sysadmins, but knew very little of what it took to be a DBA. In this session you will learn the core architecture of an Oracle Database in 12c as well as what it takes to administer and apply this new knowledge the day you go back to your office.
Database Consolidation using the Oracle Multitenant ArchitecturePini Dibask
The document discusses Oracle's Multitenant architecture, which allows multiple pluggable databases (PDBs) to consolidate within a single multitenant container database (CDB). It describes how Multitenant provides advantages like simplified upgrades, cloning, and migration of PDBs. The document also covers ensuring quality of service for PDBs using resource management, and how RAC supports high availability and scalability in a Multitenant environment. It concludes with a discussion of performance monitoring of workloads across PDBs.
Oracle Database 12c introduces several new features including pluggable databases (PDB) that allow multiple isolated databases to be consolidated within a single container database (CDB). It also introduces new administrative privileges (SYSBACKUP, SYSDG, SYSKM) and features such as transparent data encryption, invisible columns, object tables, and enhancements to RMAN and SQL.
RMAN has evolved since Oracle 8i and includes new features in Oracle 12c that help reduce downtime. In 12c, a container database can include pluggable databases. RMAN supports backup and recovery of container databases and individual pluggable databases. New features in 12c include the SYSBACKUP privilege which allows backups without granting full SYSDBA privileges, and support for multitenant container databases and pluggable databases.
Oracle Architecture document discusses:
1. The cost of an Oracle Enterprise Edition license is $47,500 per processor.
2. It provides an overview of key Oracle components like the instance, database, listener and cost based optimizer.
3. It demonstrates how to start an Oracle instance, check active processes, mount and open a database, and query it locally and remotely after starting the listener.
HBase 2.0 is the next stable major release for Apache HBase scheduled for early 2017. It is the biggest and most exciting milestone release from the Apache community after 1.0. HBase-2.0 contains a large number of features that is long time in the development, some of which include rewritten region assignment, perf improvements (RPC, rewritten write pipeline, etc), async clients, C++ client, offheaping memstore and other buffers, Spark integration, shading of dependencies as well as a lot of other fixes and stability improvements. We will go into technical details on some of the most important improvements in the release, as well as what are the implications for the users in terms of API and upgrade paths. Existing users of HBase/Phoenix as well as operators managing HBase clusters will benefit the most where they can learn about the new release and the long list of features. We will also briefly cover earlier 1.x release lines and compatibility and upgrade paths for existing users and conclude by giving an outlook on the next level of initiatives for the project.
This document discusses new features in Oracle WebLogic Server 12c. It begins with an introduction of the presenters. It then outlines 12 key things to know about WebLogic 12c, including an updated installer, per-domain Node Manager, server templates, dynamic clusters, unicast groups, cluster-targeted JMS, Java Mission Control for monitoring, built-in WLDF diagnostic modules, and RESTful management APIs. The document provides information on why upgrading to WebLogic 12.1.3 would be beneficial.
HBase and HDFS: Understanding FileSystem Usage in HBaseenissoz
This document discusses file system usage in HBase. It provides an overview of the three main file types in HBase: write-ahead logs (WALs), data files, and reference files. It describes durability semantics, IO fencing techniques for region server recovery, and how HBase leverages data locality through short circuit reads, checksums, and block placement hints. The document is intended help understand HBase's interactions with HDFS for tuning IO performance.
12cR2 Single-Tenant: Multitenant Features for All EditionsFranck Pachot
Multitenant architecture is available even without Oracle's multitenant option. In this session take a look at the overhead and the 12.2 new features so that you can choose among single-tenant or non-container databases. These features include agility in data movement, easy flashback, and fast upgrade.
The document discusses best practices for operating and supporting Apache HBase. It outlines tools like the HBase UI and HBCK that can be used to debug issues. The top categories of issues covered are region server stability problems, read/write performance, and inconsistencies. SmartSense is introduced as a tool that can help detect configuration issues proactively.
Ameerpet Online Training gives you an effective and proven online learning option with an extensive learning catalog and the freedom to attend from virtually anywhere. We have trained nearly 1500+ Students on all technologies.
We are offering 10% off on Oracle Training and we will arrange a free demo at your flexible timings
This document outlines the agenda for a training on Oracle RDBMS 12c new features. The training will cover 6 chapters: introduction, multitenant architecture, upgrade features, Flex Cluster, Global Data Service, and an overview of RDBMS features. The agenda provides a high-level overview of topics to be discussed in each chapter, including multitenant architecture concepts, upgrade options and tools, Flex Cluster configurations, Global Data Service components, and new features such as temporary undo and multiple indexes on the same columns.
This document discusses upgrading to Oracle Database 19c and migrating to Oracle Multitenant. It provides an overview of key features such as being able to have 3 user-created PDBs without a Multitenant license in 19c. It also demonstrates how to use AutoUpgrade to perform an upgrade and migration to Multitenant with a single command. The document highlights various Multitenant concepts such as resource sharing, connecting to containers, and cloning PDBs.
Exploring Oracle Multitenant in Oracle Database 12cZohar Elkayam
This document discusses Oracle Multitenant in Oracle Database 12c. It provides an overview of the multitenant architecture including containers, benefits such as lower costs and easier provisioning, and impacts such as shared redo logs and one character set across PDBs. It also covers deployment including creating a CDB, provisioning new PDBs from the seed database, plugging in non-CDBs, and cloning PDBs.
Oracle Database 12.1.0.2 introduced several new features including approximate count distinct, full database caching, pluggable database (PDB) improvements like cloning and state management, JSON support, data redaction, SQL query row limits and offsets, invisible columns, SQL text expansion, calling PL/SQL from SQL, session level sequences, and extended data types support.
OOW 17 - database consolidation using the oracle multitenant architecturePini Dibask
This document discusses database consolidation using Oracle Multitenant. It begins with an introduction to multitenant architecture and concepts. It then covers ensuring quality of service in multitenant environments using Oracle Resource Manager. The document also discusses using RAC with multitenant databases and performance monitoring for multitenant environments.
This document discusses migrating databases to Oracle's multitenant architecture. It begins with an overview of using AutoUpgrade to upgrade databases and then plugging them into a container database (CDB). It also covers concepts of Oracle Multitenant like pluggable databases (PDBs), resource sharing, and connecting to different containers. The document provides guidance on tasks like cloning PDBs, upgrading within a CDB, and migrating non-CDBs to PDBs.
New Features for Multitenant in Oracle Database 21cMarkus Flechtner
Oracle Database 21c introduces several new features for multitenant databases:
- PDBs can now be upgraded automatically when plugged into a 21c CDB or opened, replaying the upgrade process.
- Resource management is improved with options like mandatory user profiles, per-PDB database resident connection pooling, and Oracle DB Nest for isolating PDBs using Linux namespaces and cgroups.
- Multitenant enhancements for high availability include PDBs being managed as cluster resources and improved PDB-level recovery when using Active Data Guard.
Winning Performance Challenges in Oracle MultitenantPini Dibask
Pini Dibask, a senior product manager at Quest Software, gave a presentation on winning performance challenges in Oracle Multitenant. The presentation covered Oracle Multitenant concepts, ensuring quality of service in multitenant environments through resource management, using RAC with multitenant, and performance monitoring tools. It discussed how Oracle Resource Manager can be used to allocate resources between pluggable databases at the container database level. The presentation also showed how tools from Quest such as Foglight can provide performance monitoring across multiple databases.
Collaborate 17 - Database consolidation using the oracle multitenant architec...Pini Dibask
The document provides an overview of database consolidation using Oracle Multitenant architecture. It discusses challenges with prior consolidation approaches and how Multitenant addresses these. Key concepts covered include pluggable databases, container databases, and resource management capabilities at the CDB and PDB level. The document also discusses how Multitenant supports high availability features like RAC and performance monitoring tools like AWR.
OUGN winning performnace challenges in oracle MultitenantPini Dibask
This document provides an overview and introduction to Oracle 12c Multitenant architecture. It discusses key features such as pluggable databases (PDBs), container databases (CDBs), and the benefits of consolidation. The document also covers best practices for ensuring quality of service (QoS) between PDBs using resource management. It describes using the Oracle resource manager to allocate resources at the CDB and PDB level. Lastly, it summarizes performance monitoring in multitenant environments with Automatic Workload Repository (AWR) functionality in 12c Release 1 and 2.
The document discusses new security concepts introduced in Oracle Multitenant. Key points include:
- Common users exist across all pluggable databases in a container database while local users are specific to a single pluggable database.
- Common users are created in the root container and can access all pluggable databases while local users are limited to a single database.
- The set container privilege allows common users to switch between pluggable databases without reconnecting. This privilege needs to be granted carefully.
- Data dictionary and performance views aggregate information across all pluggable databases when queried from the root container.
RMOUG 18 - Winning Performance Challenges in Oracle MultitenantPini Dibask
This document discusses winning performance challenges in Oracle Multitenant environments. It begins with introducing the speaker, Pini Dibask, who is a Product Manager for Database Tools at Quest Software. It then provides an overview of Quest Software and their database management solutions. The remainder of the document outlines the agenda, which includes introductions to database consolidation, Oracle Multitenant concepts, ensuring quality of service in multitenant environments, RAC and multitenancy, and performance monitoring for multitenant environments.
4th Modern Marketing Reckoner by MMA Global India & Group M: 60+ experts on W...Social Samosa
The Modern Marketing Reckoner (MMR) is a comprehensive resource packed with POVs from 60+ industry leaders on how AI is transforming the 4 key pillars of marketing – product, place, price and promotions.
End-to-end pipeline agility - Berlin Buzzwords 2024Lars Albertsson
We describe how we achieve high change agility in data engineering by eliminating the fear of breaking downstream data pipelines through end-to-end pipeline testing, and by using schema metaprogramming to safely eliminate boilerplate involved in changes that affect whole pipelines.
A quick poll on agility in changing pipelines from end to end indicated a huge span in capabilities. For the question "How long time does it take for all downstream pipelines to be adapted to an upstream change," the median response was 6 months, but some respondents could do it in less than a day. When quantitative data engineering differences between the best and worst are measured, the span is often 100x-1000x, sometimes even more.
A long time ago, we suffered at Spotify from fear of changing pipelines due to not knowing what the impact might be downstream. We made plans for a technical solution to test pipelines end-to-end to mitigate that fear, but the effort failed for cultural reasons. We eventually solved this challenge, but in a different context. In this presentation we will describe how we test full pipelines effectively by manipulating workflow orchestration, which enables us to make changes in pipelines without fear of breaking downstream.
Making schema changes that affect many jobs also involves a lot of toil and boilerplate. Using schema-on-read mitigates some of it, but has drawbacks since it makes it more difficult to detect errors early. We will describe how we have rejected this tradeoff by applying schema metaprogramming, eliminating boilerplate but keeping the protection of static typing, thereby further improving agility to quickly modify data pipelines without fear.
The Ipsos - AI - Monitor 2024 Report.pdfSocial Samosa
According to Ipsos AI Monitor's 2024 report, 65% Indians said that products and services using AI have profoundly changed their daily life in the past 3-5 years.
Beyond the Basics of A/B Tests: Highly Innovative Experimentation Tactics You...Aggregage
This webinar will explore cutting-edge, less familiar but powerful experimentation methodologies which address well-known limitations of standard A/B Testing. Designed for data and product leaders, this session aims to inspire the embrace of innovative approaches and provide insights into the frontiers of experimentation!
STATATHON: Unleashing the Power of Statistics in a 48-Hour Knowledge Extravag...sameer shah
"Join us for STATATHON, a dynamic 2-day event dedicated to exploring statistical knowledge and its real-world applications. From theory to practice, participants engage in intensive learning sessions, workshops, and challenges, fostering a deeper understanding of statistical methodologies and their significance in various fields."
"Financial Odyssey: Navigating Past Performance Through Diverse Analytical Lens"sameer shah
Embark on a captivating financial journey with 'Financial Odyssey,' our hackathon project. Delve deep into the past performance of two companies as we employ an array of financial statement analysis techniques. From ratio analysis to trend analysis, uncover insights crucial for informed decision-making in the dynamic world of finance."
Predictably Improve Your B2B Tech Company's Performance by Leveraging DataKiwi Creative
Harness the power of AI-backed reports, benchmarking and data analysis to predict trends and detect anomalies in your marketing efforts.
Peter Caputa, CEO at Databox, reveals how you can discover the strategies and tools to increase your growth rate (and margins!).
From metrics to track to data habits to pick up, enhance your reporting for powerful insights to improve your B2B tech company's marketing.
- - -
This is the webinar recording from the June 2024 HubSpot User Group (HUG) for B2B Technology USA.
Watch the video recording at https://youtu.be/5vjwGfPN9lw
Sign up for future HUG events at https://events.hubspot.com/b2b-technology-usa/
Orchestrating the Future: Navigating Today's Data Workflow Challenges with Ai...Kaxil Naik
Navigating today's data landscape isn't just about managing workflows; it's about strategically propelling your business forward. Apache Airflow has stood out as the benchmark in this arena, driving data orchestration forward since its early days. As we dive into the complexities of our current data-rich environment, where the sheer volume of information and its timely, accurate processing are crucial for AI and ML applications, the role of Airflow has never been more critical.
In my journey as the Senior Engineering Director and a pivotal member of Apache Airflow's Project Management Committee (PMC), I've witnessed Airflow transform data handling, making agility and insight the norm in an ever-evolving digital space. At Astronomer, our collaboration with leading AI & ML teams worldwide has not only tested but also proven Airflow's mettle in delivering data reliably and efficiently—data that now powers not just insights but core business functions.
This session is a deep dive into the essence of Airflow's success. We'll trace its evolution from a budding project to the backbone of data orchestration it is today, constantly adapting to meet the next wave of data challenges, including those brought on by Generative AI. It's this forward-thinking adaptability that keeps Airflow at the forefront of innovation, ready for whatever comes next.
The ever-growing demands of AI and ML applications have ushered in an era where sophisticated data management isn't a luxury—it's a necessity. Airflow's innate flexibility and scalability are what makes it indispensable in managing the intricate workflows of today, especially those involving Large Language Models (LLMs).
This talk isn't just a rundown of Airflow's features; it's about harnessing these capabilities to turn your data workflows into a strategic asset. Together, we'll explore how Airflow remains at the cutting edge of data orchestration, ensuring your organization is not just keeping pace but setting the pace in a data-driven future.
Session in https://budapestdata.hu/2024/04/kaxil-naik-astronomer-io/ | https://dataml24.sessionize.com/session/667627
1. ORACLE DATABASE 12C
Connection to cdb and pdb
Users, Grants & Role
(Reference – Oracle Documentation )
Check detailed contents on
http://dbaboss.com/ 1
2. How to connect CDB database
• Connecting to a Container Database (CDB)
• Connecting to the root of a container database is the same as that of any previous
database instance. On the database server you can use OS Authentication.
• $ export ORACLE_SID=cdb1
• $ sqlplus / as sysdba
• SQL*Plus: Release 12.1.0.1.0 Production on Mon Aug 26 15:29:49 2013
• Copyright (c) 1982, 2013, Oracle. All rights reserved.
• Connected to:
• Oracle Database 12c Enterprise Edition Release 12.1.0.1.0 - 64bit Production
• With the Partitioning, OLAP, Advanced Analytics and Real Application Testing
options
• You can connect to other common users in similar way.
• SQL> CONN system/password
• Connected.
Check detailed contents on
http://dbaboss.com/
2
3. • The V$SERVICES views can be used to display available
services from the database.
• COLUMN name FORMAT A30
• SELECT name, pdb
• FROM v$services
• ORDER BY name;
• NAME PDB
• ------------------------------ ------------------------------
• SYS$BACKGROUND CDB$ROOT
• SYS$USERS CDB$ROOT
• cdb1 CDB$ROOT
• cdb1XDB CDB$ROOT
• pdb1 PDB1
• pdb2 PDB2
Check detailed contents on
http://dbaboss.com/
3
4. • The lsnrctl utility allows you to display the available services from the command line.
• $ lsnrctl service
• LSNRCTL for Linux: Version 12.1.0.1.0 - Production on 20-MAY-2014 09:01:34
• Copyright (c) 1991, 2013, Oracle. All rights reserved.
• Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
• Services Summary...
• Service "cdb1" has 1 instance(s).
• Instance "cdb1", status READY, has 1 handler(s) for this service...
• Handler(s):
• "DEDICATED" established:0 refused:0 state:ready
• LOCAL SERVER
• Service "cdb1XDB" has 1 instance(s).
• Instance "cdb1", status READY, has 1 handler(s) for this service...
• Handler(s):
• "D000" established:0 refused:0 current:0 max:1022 state:ready
• DISPATCHER
• (ADDRESS=(PROTOCOL=tcp)(HOST=ol6-121.localdomain)(PORT=21196))
• Service "pdb1" has 1 instance(s).
• Instance "cdb1", status READY, has 1 handler(s) for this service...
• Handler(s):
• "DEDICATED" established:0 refused:0 state:ready
• LOCAL SERVER
• Service "pdb2" has 1 instance(s).
• Instance "cdb1", status READY, has 1 handler(s) for this service...
• Handler(s):
• "DEDICATED" established:0 refused:0 state:ready
• LOCAL SERVER
• The command completed successfully
Check detailed contents on
http://dbaboss.com/
4
5. • Connections using services are unchanged from previous versions.
• SQL> -- EZCONNECT
• SQL> CONN system/password@//localhost:1521/cdb1
• Connected.
• SQL>
• SQL> -- tnsnames.ora
• SQL> CONN system/password@cdb1
• Connected.
• SQL>
• The connection using a TNS alias requires an entry in the
"$ORACLE_HOME/network/admin/tnsnames.ora" file, such as the one shown below.
• CDB1 =
• (DESCRIPTION =
• (ADDRESS = (PROTOCOL = TCP)(HOST = your host name )(PORT = 1521))
• (CONNECT_DATA =
• (SERVER = DEDICATED)
• (SERVICE_NAME = cdb1)
• )
• )
Check detailed contents on
http://dbaboss.com/
5
6. • In Oracle Database 12c, we can still find this information from
V$INSTANCE. What if I connect to a container database and then
issue an ALTER SESSION command to move into a different
container, i.e. as PDB? Will I get the name of the PDB that I
move into from the V$INSTANCE view or do I essential to look
somewhere else? Lets take a look.
•
• Connect to the container database as normal and use the
V$INSTANCE view to see where I’m at.
•
• [oracle@home_1]$ sqlplus / as sysdba SQL> select
instance_name, version, status, con_id from v$instance;
INSTANCE_NAME VERSION STATUS CON_ID--------------
--- ----------------- ------------ ----------ora12cb 12.1.0.1.0
OPEN 0
Check detailed contents on
http://dbaboss.com/
6
7. • Lets transfer into a PDB. I have quite a few PDBs created, lets just use
PDB1.
•
• SQL> alter session set container=PDB1; Session altered.
• Look after I actually move containers? How can I tell? As an alternative of
selecting INSTANCE_NAME from V$INSTANCE; we have two new SHOW
commands that will provide us the information we are looking for. These
command are quite simple (SHOW CON_ID & SHOW CON_NAME).
•
• SQL> show con_id
• CON_ID------------------------------3
• SQL> show con_name CON_NAME-
• -----------------------------PDB1
• Now that we are confident that we are in PDB1, lets take a look at the
V$INSTANCE view again. What you will notice is that V$INSTANCE delivers
us with information relative to the container database (CDB). It only
makes sense that the V$INSTANCE would return CDB information. So, how
do we identify items related to the pluggable database (PDB) without the
SHOW commands
• New View V$PDB.
Check detailed contents on
http://dbaboss.com/
7
8. • Displaying the Current Container
• The SHOW CON_NAME and SHOW CON_ID commands in SQL*Plus display the current container name and ID respectively.
• SQL> SHOW CON_NAME
• CON_NAME
• ------------------------------
• CDB$ROOT
• SQL>
• SQL> SHOW CON_ID
• CON_ID
• ------------------------------
• 1
• SQL>
• They can also be retrieved using the SYS_CONTEXT function.
• SELECT SYS_CONTEXT('USERENV', 'CON_NAME')
• FROM dual;
• SYS_CONTEXT('USERENV','CON_NAME')
• --------------------------------------------------------------------------------
• CDB$ROOT
• SQL>
• SELECT SYS_CONTEXT('USERENV', 'CON_ID')
• FROM dual;
• SYS_CONTEXT('USERENV','CON_ID')
• --------------------------------------------------------------------------------
• 1
• SQL>
Check detailed contents on
http://dbaboss.com/
8
9. Connecting to a Pluggable Database
(PDB)
• Direct connections to pluggable databases must be made using a service. Each pluggable database automatically registers a service
with the listener. This is how any application will connect to a pluggable database, as well as administrative connections.
• SQL> -- EZCONNECT
• SQL> CONN system/password@//localhost:1521/pdb1
• Connected.
• SQL>
• SQL> -- tnsnames.ora
• SQL> CONN system/password@pdb1
• Connected.
• SQL>
• The connection using a TNS alias requires an entry in the "$ORACLE_HOME/network/admin/tnsnames.ora" file, such as the one
shown below.
• PDB1 =
• (DESCRIPTION =
• (ADDRESS = (PROTOCOL = TCP)(HOST = your host name.localdomain)(PORT = 1521))
• (CONNECT_DATA =
• (SERVER = DEDICATED)
• (SERVICE_NAME = pdb1)
• )
• )
• PDB users with the SYSDBA, SYSOPER, SYSBACKUP, or SYSDG privilege can connect to a closed PDB. All other PDB users can only
connect when the PDB is open. As with regular databases, the PDB users require the CONNECT SESSION privilege to enable
connections.
Check detailed contents on
http://dbaboss.com/
9
10. • The use of SET CONTAINER avoids the need to create a new connection from scratch.
•
• If there is an existing connection to a PDB / CDB$root, the same connection can be used to connect to desired PDB / CDB$root.
•
• – Connect to CDB
• [oracle@e12 ~]$ sqlplus system/oracle@cdb1
• CDB$ROOT@CDB1> sho con_name
• CON_NAME
• ------------------------------
• CDB$ROOT
• – Check the PID for the process created on the operating system
• [oracle@e12 ~]$ ps -ef |grep LOCAL |grep -v grep
• oracle 23271 1 0 10:23 ? 00:00:00 oraclecdb1 (LOCAL=NO)
• – Change the container to PDB1 using Set container
• CDB$ROOT@CDB1> alter session set container=pdb1;
• sho con_name
• CON_NAME
• ------------------------------
• PDB1
• – Check that the operating system PID remains the same as earlier connection is reused and a new connection has not been created
• [oracle@em12 ~]$ ps -ef |grep LOCAL |grep -v grep
• oracle 23271 1 0 10:23 ? 00:00:00 oraclecdb1 (LOCAL=NO)
Check detailed contents on
http://dbaboss.com/
10
11. • – Switch the container back to cdb$root using connect
• CDB$ROOT@CDB1> conn system/oracle@cdb1
• sho con_name
• CON_NAME
• ------------------------------
• CDB$ROOT
• – Check that a new operating system PID has been
created as a new connection has been created
• [oracle@e12 ~]$ ps -ef |grep LOCAL |grep -v grep
• oracle 23409 1 0 10:29 ? 00:00:00 oraclecdb1
(LOCAL=NO)
Check detailed contents on
http://dbaboss.com/
11
13. • Local User
• A user in a non-CDB maps to a local user in a PDB.
• • A local user is defined in the PDB’s own data dictionary—and so is not known outside of
• that PDB.
• • A local user can connect only to the PDB where it is defined.
• • A local user is specific to a particular PDB and owns a schema in this PDB.
• • According to the privileges granted, a user can work on the application data within the
• PDB or with other PDBs’ application using database links. Moreover, there cannot be any
• local users defined in the root.
• Common User
• • A common user is defined in the root’s data dictionary.
• • Only common users can be defined in the root: Creating a common user allows the CDB
• administrator to create at once a user that is replicated in each PDB.
• • A common user is known, not only where it is defined in the root, but also in every PDB
• that belongs to the CDB.
• • A common user can perform administrative tasks specific to the root or PDBs, such as
• plugging and unplugging PDBs, starting up the CDB, or opening a PDB when granted the
• proper privileges
Check detailed contents on
http://dbaboss.com/
13
15. • Local Roles
• A role in a non-CDB maps to a local role in a PDB. A local role is defined in the PDB’s own
• data dictionary—and so it is not known outside of that PDB and can only be used within its
• PDB.
• Common Roles
• Besides the local role, you can create common roles that are defined in every container. This
• way, it is easy to create at once a role that is replicated in all PDBs. It is at the creation time
• that you specify the nature of the role: local or common. Common roles as well as common
• users can only be created in the root by common users. Moreover, there cannot be any local
• roles defined in the root. All Oracle-supplied predefined roles are common roles.
• Local and Common Privileges
• The privileges are commonly referred to as local or common privileges, but to be more precise
• a privilege is either granted locally with the clause CONTAINER=CURRENT or commonly with the
• clause CONTAINER=ALL.
• The same rule applies to roles: common roles can be granted commonly or locally to common
• users or roles. Common roles may contain privileges that apply across the CDB, that is,
• commonly granted for all containers, and can also contain locally granted privileges that apply
• only to an individual PDB, whereas local roles do not contain any commonly granted privileges
Check detailed contents on
http://dbaboss.com/
15
16. Create Common Users
• When creating a common user the following requirements must all be met.
• •You must be connected to a common user with the CREATE USER privilege.
• •The current container must be the root container.
• •The username for the common user must be prefixed with "C##" or "c##" and contain only ASCII or EBCDIC
characters.
• •The username must be unique across all containers.
• •The DEFAULT TABLESPACE, TEMPORARY TABLESPACE, QUOTA and PROFILE must all reference objects that exist
in all containers.
• •You can either specify the CONTAINER=ALL clause, or omit it, as this is the default setting when the current
container is the root.
•
• The following example shows how to create common users with and without the CONTAINER clause from the
root container.
• CONN / AS SYSDBA
• -- Create the common user using the CONTAINER clause.
• CREATE USER c##test_user1 IDENTIFIED BY password1 CONTAINER=ALL;
• GRANT CREATE SESSION TO c##test_user1 CONTAINER=ALL;
• -- Create the common user using the default CONTAINER setting.
• CREATE USER c##test_user2 IDENTIFIED BY password1;
• GRANT CREATE SESSION TO c##test_user2;
Check detailed contents on
http://dbaboss.com/
16
17. Create Local Users
• When creating a local user the following requirements must all be met.
• •You must be connected to a user with the CREATE USER privilege.
• •The username for the local user must not be prefixed with "C##" or "c##".
• •The username must be unique within the PDB.
• •You can either specify the CONTAINER=CURRENT clause, or omit it, as this is the default setting when the current
container is a PDB.
•
• The following example shows how to create local users with and without the CONTAINER clause from the root container.
• CONN / AS SYSDBA
• -- Switch container while connected to a common user.
• ALTER SESSION SET CONTAINER = pdb1;
• -- Create the local user using the CONTAINER clause.
• CREATE USER test_user3 IDENTIFIED BY password1 CONTAINER=CURRENT;
• GRANT CREATE SESSION TO test_user3 CONTAINER=CURRENT;
• -- Connect to a privileged user in the PDB.
• CONN system/password@pdb1
• -- Create the local user using the default CONTAINER setting.
• CREATE USER test_user4 IDENTIFIED BY password1;
• GRANT CREATE SESSION TO test_user4;
• If a local user is to be used as a DBA user, it requires the PDB_DBA role granted locally to it.
Check detailed contents on
http://dbaboss.com/
17
18. Create Common Roles
• Similar to users described previously, roles can be common or local. All Oracle-supplied roles are common and
therefore available in the root container and all PDBs. Common roles can be created, provided the following
conditions are met.
• •You must be connected to a common user with CREATE ROLE and the SET CONTAINER privileges granted
commonly.
• •The current container must be the root container.
• •The role name for the common role must be prefixed with "C##" or "c##" and contain only ASCII or EBCDIC
characters.
• •The role name must be unique across all containers.
• •The role is created with the CONTAINER=ALL clause
•
• The following example shows how to create a common role and grant it to a common and local user.
• CONN / AS SYSDBA
• -- Create the common role.
• CREATE ROLE c##test_role1;
• GRANT CREATE SESSION TO c##test_role1;
• -- Grant it to a common user.
• GRANT c##test_role1 TO c##test_user1 CONTAINER=ALL;
• -- Grant it to a local user.
• ALTER SESSION SET CONTAINER = pdb1;
• GRANT c##test_role1 TO test_user3;
• Only common operations can be granted to common roles. When the common role is granted to a local user, the
privileges are limited to that specific user in that specific PDB.
Check detailed contents on
http://dbaboss.com/
18
19. • Create Local Roles
• Local roles are created in a similar manner to pre-12c databases. Each PDB can have roles with matching names, since the
scope of a local role is limited to the current PDB. The following conditions must be met.
• •You must be connected to a user with the CREATE ROLE privilege.
• •If you are connected to a common user, the container must be set to the local PDB.
• •The role name for the local role must not be prefixed with "C##" or "c##".
• •The role name must be unique within the PDB.
•
• The following example shows how to create local a role and grant it to a common user and a local user.
• CONN / AS SYSDBA
• -- Switch container.
• ALTER SESSION SET CONTAINER = pdb1;
• -- Alternatively, connect to a local or common user
• -- with the PDB service.
• -- CONN system/password@pdb1
• -- Create the common role.
• CREATE ROLE test_role1;
• GRANT CREATE SESSION TO test_role1;
• -- Grant it to a common user.
• GRANT test_role1 TO c##test_user1;
• -- Grant it to a local user.
• GRANT test_role1 TO test_user3;
• When a local role are granted to common user, the privileges granted via the local role are only valid when the common user
has its container set to the relevant PDB.
Check detailed contents on
http://dbaboss.com/
19
20. • Granting Roles and Privileges to Common and Local Users
• The rules for granting privileges and roles can seem a little confusing at first. Just remember, if you
connect to a PDB and only deal with local users and roles, everything feels exactly the same as pre-
12c databases. It's only when you start to consider the scope of common users and roles that things
become complicated.
• The basic difference between a local and common grant is the value used by the CONTAINER clause.
• -- Common grants.
• CONN / AS SYSDBA
• GRANT CREATE SESSION TO c##test_user1 CONTAINER=ALL;
• GRANT CREATE SESSION TO c##test_role1 CONTAINER=ALL;
• GRANT c##test_role1 TO c##test_user1 CONTAINER=ALL;
• -- Local grants.
• CONN system/password@pdb1
• GRANT CREATE SESSION TO test_user3;
• GRANT CREATE SESSION TO test_role1;
• GRANT test_role1 TO test_user3;
Check detailed contents on
http://dbaboss.com/
20
22. • In a non-CDB, all objects are local objects. Common objects are
being introduced in 12c to
• avoid having to store redundant representations of data and
metadata across a CDB and to
• simplify the process of upgrading a CDB. Shared objects exist only in
Oracle-supplied
• schemas.
• A shared object may be metadata-linked or object-linked.
• • Metadata-linked objects store metadata about dictionary objects
only in the root. Each
• PDB has a private data copy of an object pointing to a metadata link
stored in the root.
• • An object-linked object and its data resides in the root only and is
shared by all PDBs.
• Example
• The list of audit actions is in SYS.AUDIT_ACTIONS table in the root,
thereby making
• AUDIT_ACTIONS accessible in each separate container
Check detailed contents on
http://dbaboss.com/
22
24. • DBA dictionary views providing information
within PDB:
• SQL> SELECT view_name FROM dba_views
WHERE view_name like 'CDB%'
Check detailed contents on
http://dbaboss.com/
24
25. • For backwards-compatibility, DBA views show the same results in a PDB as in a non-CDB:
• DBA_OBJECTS shows the objects that exist in the PDB from which you run the query. This
• implies, in turn, that though the PDB and the root have separate data dictionaries, each data
• dictionary view in a PDB shows results fetched from both of these data dictionaries. The
• DBA_xxx views in the root shows, even in a populated CDB, only the Oracle-supplied system,
• as is seen in a freshly-created non-CDB. This is another advantage of the new architecture.
• To support the duties of the CDB administrator, a new family of data dictionary views is
• supported with names like CDB_xxx. Each DBA_xxx view has a CDB_xxx view counterpart
• with an extra column, Con_ID, that shows from which container the listed facts originate.
Query
• the CDB_xxx views from the root and from any PDB. The CDB_xxx views are useful when
• queried from the root because the results from a particular CDB_xxx view are the union of
the
• results from the DBA_xxx view counterpart over the root and all currently open PDBs. When
a
• CDB_xxx view is queried from a PDB, it shows only the information that it shows in its
• DBA_xxx view counterpart. If you connect to the root and query CDB_USERS, you get the list
of users, common and local, of each container. Now if you query DBA_USERS, you get the list
ofcommon users (you know that in the root, only common users exist). Now if you connect to
aPDB, and query CDB_USERS or DBA_USERS, you get the same list of users, common and
local, of the PDB.
• The same backward-compatibility principle applies also to each of the familiar v$views.
• Oracle Check detailed contents on
http://dbaboss.com/
25
26. Impacts
• One character set for all PDBs (Unicode recommended)
• • PDB initialization parameters but a single SPFILE
• • No PDB qualified database object names
• – SELECT * FROM HR:apps.tab1
• – Use DB Links: SELECT * FROM apps.tab1@HR
• • Oracle Data Guard at CDB level
• • Oracle Database Vault per PDB only
• • One master key per PDB to encrypt PDB data
• • Unified audit both at CDB and PDB level
• • Oracle Scheduler
• • Oracle GoldenGate
• • Oracle Streams
• • Oracle XStream both at CDB and PDB level
Check detailed contents on
http://dbaboss.com/
26
27. • There is only one character set and one single spfile for the CDB. The different
parameter values of each PDB are stored in a dictionary table.
• • There is no PDB qualified object name. To access an object in another PDB, use a
DB link.
• • Oracle Data Guard works exactly the same in a CDB as it does in non-CDBs. This
feature is not to be available on a per-PDB basis. Open of a physical standby CDB
will always open the root in READ ONLY mode and this also means that no PDB
may be open in a mode other than READ ONLY.
• • In Oracle Database Vault, each PDB has its own Database Vault metadata.
DatabaseVault constructs like realms are isolated within a PDB.
• • Each PDB has its own master key used to encrypt data in the PDB. The master
key must be transported from the source database wallet to the target database
wallet when a PDBis moved from one host to another. For column encryption,
each PDB maintains its own
• ENC$ which is not a metadata-linked object.
Check detailed contents on
http://dbaboss.com/
27