The Oracle Database 12c: Interactive Quick Reference is a multimedia tool for various terms and concepts used in the Oracle Database 12c release. Built as a multimedia web page, this diagram provides descriptions of database architectural components, as well as references to relevant documentation. Use this helpful reference as a cheat sheet for writing custom data dictionary scripts, locating views pertinent to a specific database component or category, understanding the database architecture, and more.
This essential reference includes:
- DBA Views: Key DBA static data dictionary views and dynamic performance views organized by product feature areas
- Performance Views: Dynamic performance views organized by product feature areas. Click on a view and see the details for that view.
- Architecture Views: A single diagram that illustrates the relationships between key database dictionary views. Click on a view and see the definition for that view.
- Database Architecture: A single diagram that illustrates the relationships between key database memory structures, processes, and storage. Click on the diagram to find out detailed information.
- Multitenant Architecture: A single diagram that illustrates the architecture for a multitenant container database. Click on the diagram to find out detailed information.
- Background Processes: A comprehensive list that categorizes the background processes and flags which are new in Oracle Database 12c
You can download and unzip this file to run the poster locally. Open the file poster.html file located in the OUTPUT_poster folder.
- Please note that initial loading of the poster may take 20-30 seconds. If you experience performance problems, see the Download Information section above.
- Firefox v22 or later is the recommended browser. Earlier versions may work as well.
- Browser / device support varies from device to device.
- We welcome your feedback to help us improve this tool.
This tutorial covers the steps required to plug an unplugged pluggable database (PDB) from a container database (CDB) into another CDB.
Time to Complete
Approximately 20 minutes
You can disassociate or unplug a PDB from a CDB and reassociate or plug the PDB into the same CDB or into another CDB. This capability is suitable for the following situations:
- You have to upgrade a PDB to the latest Oracle version, but you do not want to apply it on all PDBs. Instead of upgrading a CDB from one release to another, you can unplug a PDB from one Oracle Database release, and then plug it into a newly created CDB from a later release.
- You want to test the performance of the CDB without a particular PDB. You unplug the PDB, test the performance without the PDB and, if necessary, replug the PDB into the CDB.
- You want to maintain a collection of PDB “gold images” as unplugged PDBs.
In this tutorial, you perform a PDB unplugging operation from a CDB. Next, you perform a plugging operation of the same PDB into another CDB by using SQL*Plus.
Different plugging scenarios are allowed:
- Plug the unplugged PDB by using the data files of the unplugged PDB. The unplugged PDB is disassociated from the source CDB.
- The source data files are used with or without any copy.
- The source data files are used after being moved to another location.
- Plug the unplugged PDB as a clone to:
- Allow developers and testers to rapidly and repeatedly provision a well-known starting state
- Support self-paced learning
- Provide a new way to deliver a brand-new application
Before starting this tutorial, you should:
- Install Oracle Database 12c.
- Create two CDBs with two PDBs in the first CDB.
The environment used in the development of this tutorial is as follows:
- ORACLE_HOME: /u01/app/oracle/product/12.1.0
- TNS Listener port: 1521
- Container databases:
- SID: cdb1
- SID: cdb2
- Pluggable databases (in cdb1):
This tutorial covers the steps to perform basic tasks on container databases (CDBs) and pluggable databases (PDBs).
Time to Complete
Approximately 45 minutes
This tutorial shows you how to:
- Connect to a CDB and to a PDB.
- Create a PDB from the seed PDB.
- Manage CDBs and PDBs.
- Start a CDB, understand the different open modes of PDBs, and shut down a CDB.
- Open and close PDBs.
- Change the name of a PDB.
- Manage the storage in a CDB and its PDBs.
- Manage permanent tablespaces.
- Manage temporary tablespaces.
- Manage the security in PDBs.
- Create common and local users.
- Create common and local roles.
- Grant common and local privileges.
- Drop PDBs.
Note: For readability, formatting was applied to some columns shown in the output.
After a long wait, finally the Oracle released the commercial version of Oracle Database 12c.
Oracle Database Products are:
Contains the Grid Infrastructure Software including Oracle Clusterware, Automated Storage Management (ASM), and ASM Cluster File System. Download and install prior to installing Oracle Real Application Clusters, Oracle Real Application Clusters One Node, or other application software in a Grid Environment
Contains the Oracle Database Gateways to non-Oracle Databases. Download if you want to set up a heterogeneous data integration environment
Contains examples of how to use the Oracle Database. Download if you are new to Oracle and want to try some of the examples presented in the Documentation
Contains the Oracle Client Libraries for Linux. Download if you want the client libraries only
Major New Oracle Database 12c Features and Products
- Adaptive Execution Plans
- Application Continuity
- Automatic Data Optimization (ADO)
- Data Guard Far Sync
- Data Redaction
- Global Data Services
- Heat Map
- Multitenant (Pluggable Databases)
- Pattern Matching
- SQL Translation Framework
Download Available only to:
Solaris Sparc64 Download
Solaris x64 Download
Helping colleagues in OTN Forum I found a issue that have not been solved yet, but we must be aware of this issue before performing implementation.
When you are using policy-managed database Oracle Manage all instance automatically on demand without dba intervention. For the whole thing work well is mandatory use SCAN (IP and SCAN Listeners) and VIP (IP and Local Listeners) database use these resource to automatically register it's own services and that's way how the Oracle client will find a Oracle Instance.
When you Configure a SHARED SERVER on Policy-Managed Dababase one question arise:
SHARED SERVER don't use Parameter LOCAL_LISTENER to register database on Listener, but it use DISPATCHERS parameter.
DISPATCHERS parameter is NOT Like LOCAL_LISTENER parameter which automatically updated by Database Agent. Then you must set DISPATCHERS manually using VIP of current Node on each Instance. As explained in note How To Configure Shared Server Dispatchers For RAC Environment [ID 578524.1]. BUT this will work only if you have a ADMIN-MANAGED database because instance is fixed on that node.
Policy-managed database has not fixed a instance on specific node and also has not a specific INSTANCE_NAME, because INSTANCE_NAME can be changed automatically on demand or when you change configuration of your SERVER POOL.
The BIG QUESTION:
How configure DISPATCHERS parameter when database is POLICY-MANAGED ? Since DISPATCHERS can't be automatically configured dynamically, but the INSTANCE is dynamic and can be reloacated to any node on that server pool.
When I get the anwser I'll post here Oracle Solution. (If someone already has the answer please post here)
I saw some doubts as to which utility to use and in what situation we should use.
I searched on some sites related to Oracle and saw that the people is still a bit confused about which command we should use.
But before start there is a rule to a Clusterware Envorinment:
The “srvctl” is to be used to managed resources with the prefix ora.* resources and “crsctl” is to be used to query or start/stop resources with prefix ora.*, but crsctl is not supported to modify or edit resources with prefix ora.* .
See this note on MOS:
|Oracle Clusterware and Application Failover Management [ID 790189.1]|
Using crs_* or crsctl commands on resources with the prefix ora.* (resources provided by Oracle) remains unsupported.
So, if you created a resource with “srvctl” this resource should be managed only by “srvctl”. If you create a resource with “crsctl” this resource should be managed using “crsctl” command.
Let’s talk about the concept Policy-Based Cluster.
Oracle Clusterware 11g release 2 (11.2) introduces a different method of managing nodes and resources used by a database called policy-based management.
With Oracle Clusterware 11g release 2 (11.2) and later, resources managed by Oracle Clusterware are contained in logical groups of servers called server pools. Resources are hosted on a shared infrastructure and are contained within server pools. The resources are restricted with respect to their hardware resource (such as CPU and memory) consumption by policies, behaving as if they were deployed in a single-system environment.
- Enables dynamic capacity assignment when needed to provide server capacity in accordance with the priorities you set with policies
- Enables allocation of resources by importance, so that applications obtain the required minimum resources, whenever possible, and so that lower priority applications do not take resources from more important applications
- Ensures isolation where necessary, so that you can provide dedicated servers in a cluster for applications and databases
Applications and databases running in server pools do not share resources. Because of this, server pools isolate resources where necessary, but enable dynamic capacity assignments as required. Together with role-separated management, this capability addresses the needs of organizations that have standardized cluster environments, but allow multiple administrator groups to share the common cluster infrastructure.
This is only a concept.
Therefore Oracle divided this concept to be used for two types of configuration
Policy-Managed Database and Policy-Based Management to non-database.
A database that you define as a cluster resource. Management of the database is defined by how you configure the resource, including on which servers the database can run and how many instances of the database are necessary to support the expected workload.
To configure Policy managed database, Oracle already have pre-defined configuration for that.
So, the options are limited and specific to Database resources (such as Services,Database).
For that reason Oracle provided “srvctl add serverpool”.
$ srvctl add serverpool -h Adds a server pool to the Oracle Clusterware. Usage: srvctl add srvpool -g <pool_name> [-l <min>] [-u <max>] [-i <importance>] [-n "<server_list>"] [-f] -g <pool_name> Server pool name -l <min> Minimum size of the server pool (Default value is 0) -u <max> Maximum size of the server pool (Default value is -1 for unlimited maximum size) -i <importance> Importance of the server pool (Default value is 0) -n "<server_list>" Comma separated list of candidate server names -f Force the operation even though some resource(s) will be stopped -h Print usage
Policy-Based Management to non-database.
To configure Non-Database resources, Oracle provided another command with much more options “crsctl add serverpool”.
This allow the DBA explore all options which Policy Managed can supply.
$ crsctl add serverpool -h Usage: crsctl add serverpool <spName> [[-file <filePath>] | [-attr "<attrName>=<value>[,...]"]] [-i] where spName Add named server pool filePath Attribute file attrName Attribute name value Attribute value -i Fail if request cannot be processed immediately -f Force option
So, we NEVER should not mix the serverpool used by database resource and serverpool used by non-database resource.
Also never use “crsctl” command to change Database Server Pool wich was created by “srvctl”. Never put a database in a serverpool created by using “crsctl” command.
Server Pool to database resource must be created by using “srvctl”.
Server Pool to non-database resource must be created by using “crsctl”
Question: Is possible change ora.* resources with “crsctl”?
Yes, It’s possible but not supported by Oracle.
Hope make this clear.