Oracle DBA 12c Training Day1 Review

With the launch of Oracle Database 12c Administration Workshop by Oracle ACE, Atul Kumar and Oracle DBA Expert Rajeev, we saw amazing response from people who wanted to learn abd get trained on Oracle Database 12c.

In this post I am going to share topic we covered in Day1 of  DBA 12c training (specially for those couldn’t join as we closed registration for Oracle DBA 12c course early). In this blog series you will get insight of what we are covering in our training so you get inside view .

Day 1 of the Oracle DBA 12c Training started with Module covering – Introduction and overview of Database 12c covering  Architecture of Database 12c including Multi- Tenancy Container Architecture and detailing Container Database (CDB) & Pluggable Database (PDB), Database Instance (Memory Structure – SGA including Buffer Cache & Redo Logs )

And here is one of the slide from session:

Covering:

• What constitutes a Container Database aka CDB
• What constitutes a Pluggable Database aka PDB
• How does Oracle control the competition for resources between the pluggable databases within a container database? If multiple CDBs are active on the same node, then contentious resources include CPU, memory and I/O (both storage capacity and IOPs)

We covered in detail about SGA and Library cache management in 12c, concept of services including how database client make connection to Database Server and how to make a connection to a PDB.

Some the interesting questions and answers that we got and worth sharing :

Q1 ) How is SGA & PGA-shared among all the PDB’s?
A1 ) The SGA and PGA is shared among the PDB’s and here is a guideline to manage them.

Q2 ) How to configure and control resource consumption using resource manager?
A2 ) Oracle introduced CDB Resource plans which currently allow to throttle CPU consumption and number of parallel processes.

Q3 ) What is a seed PDB?
A3 ) The SEED pluggable database (PDB$SEED) acts as a template for creating fresh pluggable databases and we are not allowed to alter the configuration of SEED pluggable database (by default opens up in READ ONLY mode).

Q4 ) What is a root container and how does it differ from a CDB?
A4 ) The root stores Oracle-supplied metadata and common users. An example of metadata is the source code for Oracle-supplied PL/SQL packages. A common user is a database user known in every container. The root container is named CDB$ROOT.
The root along with the PDB as a whole makes up the CDB

Q5 ) What is problems does the new architecture solve?
A5 ) Oracle Multitenant  enables you to consolidate data and code without altering existing schemas or applications and there by facilitating a better consolidation.

Easier migration of data and code. Instead of upgrading a CDB from one database release to another, you can unplug a PDB from the existing CDB, and then plug it into a newly created CDB from a higher release.