Pluggable Database Oracle 12c

Documents

dvnasns
  • Siva's Oracle DBA Blog: Migrating Database from Filesystem to ASM http://www.sivakumardba.com/2012/05/migrating-database-from-filesys... 1 of 5 11/10/2014 5:11 PM
  • Siva's Oracle DBA Blog: Migrating Database from Filesystem to ASM http://www.sivakumardba.com/2012/05/migrating-database-from-filesys... 2 of 5 11/10/2014 5:11 PM
  • Siva's Oracle DBA Blog: Migrating Database from Filesystem to ASM http://www.sivakumardba.com/2012/05/migrating-database-from-filesys... 3 of 5 11/10/2014 5:11 PM
  • Siva's Oracle DBA Blog: Migrating Database from Filesystem to ASM http://www.sivakumardba.com/2012/05/migrating-database-from-filesys... 4 of 5 11/10/2014 5:11 PM
  • Siva's Oracle DBA Blog: Migrating Database from Filesystem to ASM http://www.sivakumardba.com/2012/05/migrating-database-from-filesys... 5 of 5 11/10/2014 5:11 PM
  • srcnblgc Talk on Software Ocean || "Technology Doesn’t Kill Projects, People Do" Home Oracle Golden Gate Archive Posts Tagged ‘pluggable Database’ Multitenant : Startup and Shutdown Container Databases (CDB) and Pluggable Databases (PDB) in Oracle Database 12c Release 1 (12.1) August 27, 2014 sercanbilgic 1 comment Container Database (CDB) Startup and shutdown of the container database is the same as it has always been for regular instances. The SQL*Plus STARTUP and SHUTDOWNcommands are available when connected to the CDB as a privileged user. Some typical values are shown below. STARTUP [NOMOUNT | MOUNT | RESTRICT | UPGRADE | FORCE | READ ONLY] SHUTDOWN [IMMEDIATE | ABORT] Pluggable Database (PDB) Pluggable databases can be started and stopped using SQL*Plus commands or the ALTER PLUGGABLE DATABASE command. SQL*Plus Commands The following SQL*Plus commands are available to start and stop a pluggable database, when connected to that pluggable database as a privileged user. STARTUP FORCE; STARTUP OPEN READ WRITE [RESTRICT]; STARTUP OPEN READ ONLY [RESTRICT]; STARTUP UPGRADE; SHUTDOWN [IMMEDIATE]; Some examples are shown below. pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 1 of 15 11/10/2014 5:12 PM
  • STARTUP FORCE; SHUTDOWN IMMEDIATE; STARTUP OPEN READ WRITE RESTRICT; SHUTDOWN; STARTUP; SHUTDOWN IMMEDIATE; ALTER PLUGGABLE DATABASE The ALTER PLUGGABLE DATABASE command can be used from the CDB or the PDB. The following commands are available to open and close the current PDB when connected to the PDB as a privileged user. ALTER PLUGGABLE DATABASE OPEN READ WRITE [RESTRICTED] [FORCE]; ALTER PLUGGABLE DATABASE OPEN READ ONLY [RESTRICTED] [FORCE]; ALTER PLUGGABLE DATABASE OPEN UPGRADE [RESTRICTED]; ALTER PLUGGABLE DATABASE CLOSE [IMMEDIATE]; Some examples are shown below. ALTER PLUGGABLE DATABASE OPEN READ ONLY FORCE; ALTER PLUGGABLE DATABASE CLOSE IMMEDIATE; ALTER PLUGGABLE DATABASE OPEN READ WRITE; ALTER PLUGGABLE DATABASE CLOSE IMMEDIATE; The following commands are available to open and close one or more PDBs when connected to the CDB as a privileged user. ALTER PLUGGABLE DATABASE OPEN READ WRITE [RESTRICTED] [FORCE]; ALTER PLUGGABLE DATABASE OPEN READ ONLY [RESTRICTED] [FORCE]; ALTER PLUGGABLE DATABASE OPEN UPGRADE [RESTRICTED]; ALTER PLUGGABLE DATABASE CLOSE [IMMEDIATE]; The clause can be any of the following: One or more PDB names, specified as a comma-separated list. The ALL keyword to indicate all PDBs. The ALL EXCEPT keywords, followed by one or more PDB names in a comma-separate list, to indicate a subset of PDBs. Some examples are shown below. ALTER PLUGGABLE DATABASE pdb1, pdb2 OPEN READ ONLY FORCE; ALTER PLUGGABLE DATABASE pdb1, pdb2 CLOSE IMMEDIATE; ALTER PLUGGABLE DATABASE ALL OPEN; ALTER PLUGGABLE DATABASE ALL CLOSE IMMEDIATE; ALTER PLUGGABLE DATABASE ALL EXCEPT pdb1 OPEN; ALTER PLUGGABLE DATABASE ALL EXCEPT pdb1 CLOSE IMMEDIATE; Pluggable Database (PDB) Automatic Startup pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 2 of 15 11/10/2014 5:12 PM
  • The 12.1.0.2 patchset has introduced the ability to preserve the startup state of PDBs, so you probably shouldn’t be implementing a trigger in the manner discussed in this section. Prior to 12.1.0.2, when the CDB is started, all PDBs remain in mounted mode. There is no default mechanism to automatically start them when the CDB is started. The way to achieve this is to use a system trigger on the CDB to start some or all of the PDBs. CREATE OR REPLACE TRIGGER open_pdbs AFTER STARTUP ON DATABASE BEGIN EXECUTE IMMEDIATE 'ALTER PLUGGABLE DATABASE ALL OPEN'; END open_pdbs; / You can customise the trigger if you don’t want all of your PDBs to start. Preserve PDB Startup State (12.1.0.2 onward) The 12.1.0.2 patchset introduced the ability to preserve the startup state of PDBs through a CDB restart. This is done using the ALTER PLUGGABLE DATABASE command. We will start off by looking at the normal result of a CDB restart. Notice the PDBs are in READ WRITE mode before the restart, but in MOUNTED mode after it. SELECT name, open_mode FROM v$pdbs; NAME OPEN_MODE ------------------------------ ---------- PDB$SEED READ ONLY PDB1 READ WRITE PDB2 READ WRITE SQL> SHUTDOWN IMMEDIATE; STARTUP; SELECT name, open_mode FROM v$pdbs; NAME OPEN_MODE ------------------------------ ---------- PDB$SEED READ ONLY PDB1 MOUNTED PDB2 MOUNTED SQL> Next, we open both pluggable databases, but only save the state of PDB1. ALTER PLUGGABLE DATABASE pdb1 OPEN; ALTER PLUGGABLE DATABASE pdb2 OPEN; ALTER PLUGGABLE DATABASE pdb1 SAVE STATE; The DBA_PDB_SAVED_STATES view displays information about the saved state of containers. COLUMN con_name FORMAT A20 COLUMN instance_name FORMAT A20 SELECT con_name, instance_name, state FROM dba_pdb_saved_states; CON_NAME INSTANCE_NAME STATE pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 3 of 15 11/10/2014 5:12 PM
  • -------------------- -------------------- -------------- PDB1 cdb1 OPEN SQL> Restarting the CDB now gives us a different result. SELECT name, open_mode FROM v$pdbs; NAME OPEN_MODE ------------------------------ ---------- PDB$SEED READ ONLY PDB1 READ WRITE PDB2 READ WRITE SQL> SHUTDOWN IMMEDIATE; STARTUP; SELECT name, open_mode FROM v$pdbs; NAME OPEN_MODE ------------------------------ ---------- PDB$SEED READ ONLY PDB1 READ WRITE PDB2 MOUNTED SQL> The saved state can be discarded using the following statement. ALTER PLUGGABLE DATABASE pdb1 DISCARD STATE; COLUMN con_name FORMAT A20 COLUMN instance_name FORMAT A20 SELECT con_name, instance_name, state FROM dba_pdb_saved_states; no rows selected SQL> Here is a brief list of some of the usage notes explained in the documentation. The state is only saved and visible in the DBA_PDB_SAVED_STATES view if the container is in READ ONLY or READ WRITE mode. The ALTER PLUGGABLE DATABASE ... SAVE STATEcommand does not error when run against a container in MOUNTED mode, but nothing is recorded, as this is the default state after a CDB restart. Like other examples of the ALTER PLUGGABLE DATABASE command, PDBs can be identified individually, as a comma separated list, using the ALL or ALL EXCEPT keywords. The INSTANCES clause can be added when used in RAC environments. The clause can identify instances individually, as a comma separated list, using the ALL or ALL EXCEPT keywords. Regardless of the INSTANCES clause, the SAVE/DISCARD STATE commands only affect the current instance. For more information see: Introduction to the Multitenant Architecture Overview of the Multitenant Architecture Managing a Multitenant Environment ALTER PLUGGABLE DATABASE Using the STARTUP SQL*Plus Command on a PDB pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 4 of 15 11/10/2014 5:12 PM
  • Preserving or Discarding the Open Mode of PDBs When the CDB Restarts Categories: 12c, Database, new features in 12c, Oracle Tags: 12c, container database, new features in 12c, pluggable Database, Startup and Shutdown CDB & PDB Multitenant : Connecting to Container Databases (CDB) and Pluggable Databases (PDB) in Oracle Database 12c Release 1 (12.1) August 27, 2014 sercanbilgic 1 comment 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 Wed Aug 27 08:56:49 2014 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 SQL> You can connect to other common users in similar way. SQL> CONN system/password Connected. SQL> 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 6 rows selected. SQL> 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 27-AUG-2014 09:01:34 pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 5 of 15 11/10/2014 5:12 PM
  • 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 $ 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 = ol6-121.localdomain)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = cdb1) ) ) Displaying the Current Container The SHOW CON_NAME command in SQL*Plus displays the current container name. SQL> SHOW CON_NAME CON_NAME ------------------------------ CDB$ROOT SQL> It can also be retrieved using the SYS_CONTEXT function. pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 6 of 15 11/10/2014 5:12 PM
  • SELECT SYS_CONTEXT('USERENV', 'CON_NAME') FROM dual; SYS_CONTEXT('USERENV','CON_NAME') -------------------------------------------------------------------------------- CDB$ROOT SQL> Switching Between Containers When logged in to the CDB as an appropriately privileged user, the ALTER SESSION command can be used to switch between containers within the container database. SQL> ALTER SESSION SET container = pdb1; Session altered. SQL> SHOW CON_NAME CON_NAME ------------------------------ PDB1 SQL> ALTER SESSION SET container = cdb$root; Session altered. SQL> SHOW CON_NAME CON_NAME ------------------------------ CDB$ROOT SQL> 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 = ol6-121.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 pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 7 of 15 11/10/2014 5:12 PM
  • 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. JDBC Connections to PDBs It has already been mentioned that you must connect to a PDB using a service. This means that by default many JDBC connect strings will be broken. Valid JDBC connect strings for Oracle use the following format. # Syntax jdbc:oracle:thin:@[HOST][:PORT]:SID jdbc:oracle:thin:@[HOST][:PORT]/SERVICE # Example jdbc:oracle:thin:@ol6-121:1521:pdb1 jdbc:oracle:thin:@ol6-121:1521/pdb1 When attempting to connect to a PDB using the SID format, you will receive the following error. ORA-12505, TNS:listener does not currently know of SID given in connect descriptor Ideally, you would correct the connect string to use services instead of SIDs, but if that is a problem the USE_SID_AS_SERVICE_listener_name listener parameter can be used. Edit the “$ORACLE_HOME/network/admin/listener.ora” file, adding the following entry, with the “listener” name matching that used by your listener. USE_SID_AS_SERVICE_listener=on Reload or restart the listener. $ lsnrctl reload Now both of the following connection attempts will be successful as any SIDs will be treated as services. jdbc:oracle:thin:@ol6-121:1521:pdb1 jdbc:oracle:thin:@ol6-121:1521/pdb1 For more information see: Introduction to the Multitenant Architecture Overview of the Multitenant Architecture Managing a Multitenant Environment Connections to Containers in a CDB Categories: 12c, Database, new features in 12c, Oracle Tags: 12c, Connecting CDB with PDB, container database, new features in 12c, pluggable Database Multitenant : Migrate a Non-Container Database (CDB) to a Pluggable Database (PDB) in Oracle Database 12c Release 1 (12.1) August 27, 2014 sercanbilgic 1 comment Clone a Remote Non-CDB The 12.1.0.2 patchset introduced the ability to create a PDB as a clone of a remote non-CDB. pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 8 of 15 11/10/2014 5:12 PM
  • Using DBMS_PDB The DBMS_PDB package allows you to generate an XML metadata file from a non-CDB 12c database, effectively allowing it to be describe it the way you do when unplugging a PDB database. This allows the non-CDB to be plugged in as a PDB into an existing CDB. Note. Typically, any feature used in the PDB must be present in the root container of the destination CDB prior to the migration. The following example assumes this to be the case. Cleanly shutdown the non-CDB and start it in read-only mode. export ORACLE_SID=db12c sqlplus / as sysdba SHUTDOWN IMMEDIATE; STARTUP OPEN READ ONLY; Describe the non-DBC using the DBMS_PDB.DESCRIBE procedure. This procedure creates an XML file in the same way that the unplug operation does for a PDB. BEGIN DBMS_PDB.DESCRIBE( pdb_descr_file => '/tmp/db12c.xml'); END; / Shutdown the non-CDB database. export ORACLE_SID=db12c sqlplus / as sysdba SHUTDOWN IMMEDIATE; Connect to an existing CDB and create a new PDB using the file describing the non-CDB database. Remember to configure the FILE_NAME_CONVERT parameter to convert the existing files to the new location. export ORACLE_SID=cdb1 sqlplus / as sysdba CREATE PLUGGABLE DATABASE pdb6 USING '/tmp/db12c.xml' COPY FILE_NAME_CONVERT = ('/u01/app/oracle/oradata/db12c/', '/u01/app/oracle/oradata/cdb1/pdb6/'); Switch to the PDB container and run the “$ORACLE_HOME/rdbms/admin/noncdb_to_pdb.sql” script to clean up the new PDB, removing any items that should not be present in a PDB. You can see an example of the output produced by this script here. ALTER SESSION SET CONTAINER=pdb6; @$ORACLE_HOME/rdbms/admin/noncdb_to_pdb.sql Startup the PDB and check the open mode. ALTER SESSION SET CONTAINER=pdb6; ALTER PLUGGABLE DATABASE OPEN; SELECT name, open_mode FROM v$pdbs; NAME OPEN_MODE ------------------------------ ---------- PDB6 READ WRITE pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 9 of 15 11/10/2014 5:12 PM
  • 1 row selected. SQL> The non-CDB has now been converted to a PDB. You should backup the PDB before you start to use it. Using Data Pump (expdb, impdp) A simple option is to export the data from the non-CDB and import it into a newly created PDB directly. Provided the import is connecting using a service pointing to the relevant PDB, this is no different to any other data transfer using data pump. If the non-CDB is version 11.2.0.3 onward, you can consider using Transport Database, as described here. If the non-CDB is pre-11.2.0.3, then you can still consider using transportable tablespaces. Using Replication Another alternative is to use a replication product like Golden Gate to replicate the data from the non-container database to a pluggable database. For more information see: Introduction to the Multitenant Architecture Overview of the Multitenant Architecture Managing a Multitenant Environment Creating a PDB Using a Non-CDB DBMS_PDB Categories: 12c, Database, new features in 12c, Oracle Tags: 12c, container database, Migrate Non-Container Database to Pluggable Database, new features in 12c, pluggable Database Multitenant : Overview of Container Databases (CDB) and Pluggable Databases (PDB) August 25, 2014 sercanbilgic 1 comment Overview The multitenant option represents one of the biggest architectural changes in the history of the Oracle database. The option introduced the concepts of the Container Database (CDB) and Pluggable Database (PDB). Container Database (CDB) : On the surface this seems very similar to a conventional Oracle database, as it contains most of the working parts you will be already familiar with (controlfiles, datafiles, undo, tempfiles, redo logs etc.). It also houses the data dictionary for those objects that are owned by the root container and those that are visible to all PDBs. Pluggable Database (PDB) : Since the CDB contains most of the working parts for the database, the PDB only needs to contain information specific to itself. It does not need to worry about controlfiles, redo logs and undo etc. Instead it is just made up of datafiles and tempfiles to handle it’s own objects. This includes it’s own data dictionary, containing information about only those objects that are specific to the PDB. pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 10 of 15 11/10/2014 5:12 PM
  • This split of the data dictionary between common objects, in the root container, and PDB-specific objects, in the PDB’s data dictionary, is very important, because this separation is what gives the multitenant option its flexibility. From the perspective of the PDB, the data dictionary is the union of the root and PDB data dictionaries, so internally the PDB feels very much like a normal Oracle database. For example, the DBA_% and ALL_% views within the PDB appears the same as any non-CDB database. Creating Pluggable Databases (PDBs) Since the bulk of the working parts are already present in the root container, creating a new PDB is a comparatively quick and simple task. When creating a completely new PDP, the PDB is created as a copy of a seed PDB, so it only takes as long as the files take to copy. Instead of creating a new PDB from the seed, you can clone an existing PDB. pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 11 of 15 11/10/2014 5:12 PM
  • Unpluging and Plugging in Pluggable Databases (PDBs) One of the most powerful features of the multitenant option is the ability to unplug a PDB from a CDB and plug it back into another CDB. Not only does this allow databases to be moved easily, but it also paves the way for quick patching and upgrading to future versions. A PDB can be unplugged from a 12.1 CBD and plugged into a 12.2 CDB, effectively upgrading it in seconds. Conversion of a non-CDB database to a pluggable database involves getting a description the non-CDB database and using this to plug it into a CDB as a new PDB. Views The introduction of the multitenant option brings with it an extra layer of data dictionary views, allowing reporting across the root container and the pluggable databases (PDBs). Ignoring editions for the moment, prior releases had the following hierarchy. DBA_ : All objects in the database. | --ALL_ : Objects accessible by the current user, including those owned by the current user. | --USER_ : Objects owned by the current user. With Oracle 12c, an extra layer is added to the hierarchy. CDB_ : All objects in the root container and all PDBs. | --DBA_ : All objects in the root container or PDB, depending on the current settings. | --ALL_ : Objects accessible by the current user, including those owned by the current user. | --USER_ : Objects owned by the current user. pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 12 of 15 11/10/2014 5:12 PM
  • The views are described in the Reference Manual. For more information see: Introduction to the Multitenant Architecture Overview of the Multitenant Architecture Managing a Multitenant Environment Categories: 12c, Database, new features in 12c, Oracle Tags: 12 c new features, 12c, container database, pluggable Database RSS feed Recent Posts Oracle Fusion Distributed Order Orchestration on Oracle SuperCluster T5-8 November 4, 2014 Linux Kernel Upgrade on Exadata(manual way) October 24, 2014 Change exadata flashcache mode from WriteThrough to WriteBack October 24, 2014 A Beginner’s Guide to NoSQL October 13, 2014 Siebel Web Service Call with SOAP October 13, 2014 Using Puppet to Manage Oracle October 13, 2014 Restricted access to PL/SQL subprograms in Oracle 12c October 13, 2014 New AWR Report Format: Oracle 11.2.0.4 and 12c October 12, 2014 Using the dcli Utility September 22, 2014 Back to School: What Open UI Does for You – And What Not(GOOD BYE SIEBEL, AT LEAST FOR ME)re- blogged from siebel-essentials September 20, 2014 Transport tablespaces across platforms in Oracle Database 12c August 27, 2014 Automatic Diagnostics Repository (ADR) Enhancements in Oracle Database 12c (ADRCI) August 27, 2014 Online Move Datafile in Oracle Database 12c Release 1 (12.1) August 27, 2014 Capture Privilege Usage (DBMS_PRIVILEGE_CAPTURE) in Oracle Database 12c Release 1 (12.1) August 27, 2014 Multitenant : Startup and Shutdown Container Databases (CDB) and Pluggable Databases (PDB) in Oracle Database 12c Release 1 (12.1) August 27, 2014 Archives November 2014 (1) October 2014 (7) September 2014 (2) August 2014 (17) July 2014 (17) June 2014 (1) May 2014 (3) April 2014 (9) March 2014 (4) pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 13 of 15 11/10/2014 5:12 PM
  • February 2014 (5) January 2014 (10) December 2013 (4) November 2013 (7) October 2013 (12) September 2013 (6) August 2013 (11) July 2013 (6) June 2013 (18) May 2013 (12) April 2013 (16) April 2012 (1) Tag Cloud 12 c new features 12c 12c Release 1 adf Analyze AWR apache AWR Big Data bpel bpm cell Configuration container database correlation creating script Database Data Validation debugging LoadRunner script eclipse Exadata exalogic export finding applets with given display name flow form applet framework hadoop Hadoop Cluster how to use smart script if-else Index Installation Installing Siebel 8.2.2 Invisible Index linux list applet Load Balancing LoadRunner Load Runner Load Test LOAD UI Mappings Migration new features in 12c Open UI oracle oracle 11g pattern performace test Performance performance test Performance Tuning pick pluggable Database querying applets&screens&views Query Statistic Query Tuning RAC recording script Reverse key SCBroker siebel Siebel Base Table and EIM Table Siebel DB Siebel Schema siebel tools siebel_log smart script soa SOAP UI SQL SQL Plan tomcat unix Web Service Categories .NET (1) Framework (1) 11g (1) 12c (12) big data (6) disk partition (1) EAI (1) Exa Family (18) Exadata (3) Exalogic (15) Hadoop (5) java (2) LDAP (1) linux (1) Load Balancer (1) F5 (1) new features in 12c (10) nosql (1) Oracle (120) ADF (1) Database (69) Materialized Views (2) Query Tuning (14) SQL Server (2) pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 14 of 15 11/10/2014 5:12 PM
  • Using Hint (7) SOA (8) Pattern (2) Performance Test (12) plsql (1) restricted access (1) Siebel (44) Data Validation (1) Product Cnfigurator (1) Smart Script (1) sql (1) subprograms (1) SuperCluster (1) Uncategorized (3) Unix (6) TROUG Follow My Blog bilgic.sercan01@gmail.com Join 528 other followers Meta Register Log in Entries RSS Comments RSS Blog at WordPress.com. Top Blog at WordPress.com. The INove Theme. pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 15 of 15 11/10/2014 5:12 PM
Please download to view
20
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
Pluggable Database Oracle 12c
Text
  • Siva's Oracle DBA Blog: Migrating Database from Filesystem to ASM http://www.sivakumardba.com/2012/05/migrating-database-from-filesys... 1 of 5 11/10/2014 5:11 PM
  • Siva's Oracle DBA Blog: Migrating Database from Filesystem to ASM http://www.sivakumardba.com/2012/05/migrating-database-from-filesys... 2 of 5 11/10/2014 5:11 PM
  • Siva's Oracle DBA Blog: Migrating Database from Filesystem to ASM http://www.sivakumardba.com/2012/05/migrating-database-from-filesys... 3 of 5 11/10/2014 5:11 PM
  • Siva's Oracle DBA Blog: Migrating Database from Filesystem to ASM http://www.sivakumardba.com/2012/05/migrating-database-from-filesys... 4 of 5 11/10/2014 5:11 PM
  • Siva's Oracle DBA Blog: Migrating Database from Filesystem to ASM http://www.sivakumardba.com/2012/05/migrating-database-from-filesys... 5 of 5 11/10/2014 5:11 PM
  • srcnblgc Talk on Software Ocean || "Technology Doesn’t Kill Projects, People Do" Home Oracle Golden Gate Archive Posts Tagged ‘pluggable Database’ Multitenant : Startup and Shutdown Container Databases (CDB) and Pluggable Databases (PDB) in Oracle Database 12c Release 1 (12.1) August 27, 2014 sercanbilgic 1 comment Container Database (CDB) Startup and shutdown of the container database is the same as it has always been for regular instances. The SQL*Plus STARTUP and SHUTDOWNcommands are available when connected to the CDB as a privileged user. Some typical values are shown below. STARTUP [NOMOUNT | MOUNT | RESTRICT | UPGRADE | FORCE | READ ONLY] SHUTDOWN [IMMEDIATE | ABORT] Pluggable Database (PDB) Pluggable databases can be started and stopped using SQL*Plus commands or the ALTER PLUGGABLE DATABASE command. SQL*Plus Commands The following SQL*Plus commands are available to start and stop a pluggable database, when connected to that pluggable database as a privileged user. STARTUP FORCE; STARTUP OPEN READ WRITE [RESTRICT]; STARTUP OPEN READ ONLY [RESTRICT]; STARTUP UPGRADE; SHUTDOWN [IMMEDIATE]; Some examples are shown below. pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 1 of 15 11/10/2014 5:12 PM
  • STARTUP FORCE; SHUTDOWN IMMEDIATE; STARTUP OPEN READ WRITE RESTRICT; SHUTDOWN; STARTUP; SHUTDOWN IMMEDIATE; ALTER PLUGGABLE DATABASE The ALTER PLUGGABLE DATABASE command can be used from the CDB or the PDB. The following commands are available to open and close the current PDB when connected to the PDB as a privileged user. ALTER PLUGGABLE DATABASE OPEN READ WRITE [RESTRICTED] [FORCE]; ALTER PLUGGABLE DATABASE OPEN READ ONLY [RESTRICTED] [FORCE]; ALTER PLUGGABLE DATABASE OPEN UPGRADE [RESTRICTED]; ALTER PLUGGABLE DATABASE CLOSE [IMMEDIATE]; Some examples are shown below. ALTER PLUGGABLE DATABASE OPEN READ ONLY FORCE; ALTER PLUGGABLE DATABASE CLOSE IMMEDIATE; ALTER PLUGGABLE DATABASE OPEN READ WRITE; ALTER PLUGGABLE DATABASE CLOSE IMMEDIATE; The following commands are available to open and close one or more PDBs when connected to the CDB as a privileged user. ALTER PLUGGABLE DATABASE OPEN READ WRITE [RESTRICTED] [FORCE]; ALTER PLUGGABLE DATABASE OPEN READ ONLY [RESTRICTED] [FORCE]; ALTER PLUGGABLE DATABASE OPEN UPGRADE [RESTRICTED]; ALTER PLUGGABLE DATABASE CLOSE [IMMEDIATE]; The clause can be any of the following: One or more PDB names, specified as a comma-separated list. The ALL keyword to indicate all PDBs. The ALL EXCEPT keywords, followed by one or more PDB names in a comma-separate list, to indicate a subset of PDBs. Some examples are shown below. ALTER PLUGGABLE DATABASE pdb1, pdb2 OPEN READ ONLY FORCE; ALTER PLUGGABLE DATABASE pdb1, pdb2 CLOSE IMMEDIATE; ALTER PLUGGABLE DATABASE ALL OPEN; ALTER PLUGGABLE DATABASE ALL CLOSE IMMEDIATE; ALTER PLUGGABLE DATABASE ALL EXCEPT pdb1 OPEN; ALTER PLUGGABLE DATABASE ALL EXCEPT pdb1 CLOSE IMMEDIATE; Pluggable Database (PDB) Automatic Startup pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 2 of 15 11/10/2014 5:12 PM
  • The 12.1.0.2 patchset has introduced the ability to preserve the startup state of PDBs, so you probably shouldn’t be implementing a trigger in the manner discussed in this section. Prior to 12.1.0.2, when the CDB is started, all PDBs remain in mounted mode. There is no default mechanism to automatically start them when the CDB is started. The way to achieve this is to use a system trigger on the CDB to start some or all of the PDBs. CREATE OR REPLACE TRIGGER open_pdbs AFTER STARTUP ON DATABASE BEGIN EXECUTE IMMEDIATE 'ALTER PLUGGABLE DATABASE ALL OPEN'; END open_pdbs; / You can customise the trigger if you don’t want all of your PDBs to start. Preserve PDB Startup State (12.1.0.2 onward) The 12.1.0.2 patchset introduced the ability to preserve the startup state of PDBs through a CDB restart. This is done using the ALTER PLUGGABLE DATABASE command. We will start off by looking at the normal result of a CDB restart. Notice the PDBs are in READ WRITE mode before the restart, but in MOUNTED mode after it. SELECT name, open_mode FROM v$pdbs; NAME OPEN_MODE ------------------------------ ---------- PDB$SEED READ ONLY PDB1 READ WRITE PDB2 READ WRITE SQL> SHUTDOWN IMMEDIATE; STARTUP; SELECT name, open_mode FROM v$pdbs; NAME OPEN_MODE ------------------------------ ---------- PDB$SEED READ ONLY PDB1 MOUNTED PDB2 MOUNTED SQL> Next, we open both pluggable databases, but only save the state of PDB1. ALTER PLUGGABLE DATABASE pdb1 OPEN; ALTER PLUGGABLE DATABASE pdb2 OPEN; ALTER PLUGGABLE DATABASE pdb1 SAVE STATE; The DBA_PDB_SAVED_STATES view displays information about the saved state of containers. COLUMN con_name FORMAT A20 COLUMN instance_name FORMAT A20 SELECT con_name, instance_name, state FROM dba_pdb_saved_states; CON_NAME INSTANCE_NAME STATE pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 3 of 15 11/10/2014 5:12 PM
  • -------------------- -------------------- -------------- PDB1 cdb1 OPEN SQL> Restarting the CDB now gives us a different result. SELECT name, open_mode FROM v$pdbs; NAME OPEN_MODE ------------------------------ ---------- PDB$SEED READ ONLY PDB1 READ WRITE PDB2 READ WRITE SQL> SHUTDOWN IMMEDIATE; STARTUP; SELECT name, open_mode FROM v$pdbs; NAME OPEN_MODE ------------------------------ ---------- PDB$SEED READ ONLY PDB1 READ WRITE PDB2 MOUNTED SQL> The saved state can be discarded using the following statement. ALTER PLUGGABLE DATABASE pdb1 DISCARD STATE; COLUMN con_name FORMAT A20 COLUMN instance_name FORMAT A20 SELECT con_name, instance_name, state FROM dba_pdb_saved_states; no rows selected SQL> Here is a brief list of some of the usage notes explained in the documentation. The state is only saved and visible in the DBA_PDB_SAVED_STATES view if the container is in READ ONLY or READ WRITE mode. The ALTER PLUGGABLE DATABASE ... SAVE STATEcommand does not error when run against a container in MOUNTED mode, but nothing is recorded, as this is the default state after a CDB restart. Like other examples of the ALTER PLUGGABLE DATABASE command, PDBs can be identified individually, as a comma separated list, using the ALL or ALL EXCEPT keywords. The INSTANCES clause can be added when used in RAC environments. The clause can identify instances individually, as a comma separated list, using the ALL or ALL EXCEPT keywords. Regardless of the INSTANCES clause, the SAVE/DISCARD STATE commands only affect the current instance. For more information see: Introduction to the Multitenant Architecture Overview of the Multitenant Architecture Managing a Multitenant Environment ALTER PLUGGABLE DATABASE Using the STARTUP SQL*Plus Command on a PDB pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 4 of 15 11/10/2014 5:12 PM
  • Preserving or Discarding the Open Mode of PDBs When the CDB Restarts Categories: 12c, Database, new features in 12c, Oracle Tags: 12c, container database, new features in 12c, pluggable Database, Startup and Shutdown CDB & PDB Multitenant : Connecting to Container Databases (CDB) and Pluggable Databases (PDB) in Oracle Database 12c Release 1 (12.1) August 27, 2014 sercanbilgic 1 comment 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 Wed Aug 27 08:56:49 2014 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 SQL> You can connect to other common users in similar way. SQL> CONN system/password Connected. SQL> 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 6 rows selected. SQL> 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 27-AUG-2014 09:01:34 pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 5 of 15 11/10/2014 5:12 PM
  • 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 $ 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 = ol6-121.localdomain)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED) (SERVICE_NAME = cdb1) ) ) Displaying the Current Container The SHOW CON_NAME command in SQL*Plus displays the current container name. SQL> SHOW CON_NAME CON_NAME ------------------------------ CDB$ROOT SQL> It can also be retrieved using the SYS_CONTEXT function. pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 6 of 15 11/10/2014 5:12 PM
  • SELECT SYS_CONTEXT('USERENV', 'CON_NAME') FROM dual; SYS_CONTEXT('USERENV','CON_NAME') -------------------------------------------------------------------------------- CDB$ROOT SQL> Switching Between Containers When logged in to the CDB as an appropriately privileged user, the ALTER SESSION command can be used to switch between containers within the container database. SQL> ALTER SESSION SET container = pdb1; Session altered. SQL> SHOW CON_NAME CON_NAME ------------------------------ PDB1 SQL> ALTER SESSION SET container = cdb$root; Session altered. SQL> SHOW CON_NAME CON_NAME ------------------------------ CDB$ROOT SQL> 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 = ol6-121.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 pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 7 of 15 11/10/2014 5:12 PM
  • 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. JDBC Connections to PDBs It has already been mentioned that you must connect to a PDB using a service. This means that by default many JDBC connect strings will be broken. Valid JDBC connect strings for Oracle use the following format. # Syntax jdbc:oracle:thin:@[HOST][:PORT]:SID jdbc:oracle:thin:@[HOST][:PORT]/SERVICE # Example jdbc:oracle:thin:@ol6-121:1521:pdb1 jdbc:oracle:thin:@ol6-121:1521/pdb1 When attempting to connect to a PDB using the SID format, you will receive the following error. ORA-12505, TNS:listener does not currently know of SID given in connect descriptor Ideally, you would correct the connect string to use services instead of SIDs, but if that is a problem the USE_SID_AS_SERVICE_listener_name listener parameter can be used. Edit the “$ORACLE_HOME/network/admin/listener.ora” file, adding the following entry, with the “listener” name matching that used by your listener. USE_SID_AS_SERVICE_listener=on Reload or restart the listener. $ lsnrctl reload Now both of the following connection attempts will be successful as any SIDs will be treated as services. jdbc:oracle:thin:@ol6-121:1521:pdb1 jdbc:oracle:thin:@ol6-121:1521/pdb1 For more information see: Introduction to the Multitenant Architecture Overview of the Multitenant Architecture Managing a Multitenant Environment Connections to Containers in a CDB Categories: 12c, Database, new features in 12c, Oracle Tags: 12c, Connecting CDB with PDB, container database, new features in 12c, pluggable Database Multitenant : Migrate a Non-Container Database (CDB) to a Pluggable Database (PDB) in Oracle Database 12c Release 1 (12.1) August 27, 2014 sercanbilgic 1 comment Clone a Remote Non-CDB The 12.1.0.2 patchset introduced the ability to create a PDB as a clone of a remote non-CDB. pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 8 of 15 11/10/2014 5:12 PM
  • Using DBMS_PDB The DBMS_PDB package allows you to generate an XML metadata file from a non-CDB 12c database, effectively allowing it to be describe it the way you do when unplugging a PDB database. This allows the non-CDB to be plugged in as a PDB into an existing CDB. Note. Typically, any feature used in the PDB must be present in the root container of the destination CDB prior to the migration. The following example assumes this to be the case. Cleanly shutdown the non-CDB and start it in read-only mode. export ORACLE_SID=db12c sqlplus / as sysdba SHUTDOWN IMMEDIATE; STARTUP OPEN READ ONLY; Describe the non-DBC using the DBMS_PDB.DESCRIBE procedure. This procedure creates an XML file in the same way that the unplug operation does for a PDB. BEGIN DBMS_PDB.DESCRIBE( pdb_descr_file => '/tmp/db12c.xml'); END; / Shutdown the non-CDB database. export ORACLE_SID=db12c sqlplus / as sysdba SHUTDOWN IMMEDIATE; Connect to an existing CDB and create a new PDB using the file describing the non-CDB database. Remember to configure the FILE_NAME_CONVERT parameter to convert the existing files to the new location. export ORACLE_SID=cdb1 sqlplus / as sysdba CREATE PLUGGABLE DATABASE pdb6 USING '/tmp/db12c.xml' COPY FILE_NAME_CONVERT = ('/u01/app/oracle/oradata/db12c/', '/u01/app/oracle/oradata/cdb1/pdb6/'); Switch to the PDB container and run the “$ORACLE_HOME/rdbms/admin/noncdb_to_pdb.sql” script to clean up the new PDB, removing any items that should not be present in a PDB. You can see an example of the output produced by this script here. ALTER SESSION SET CONTAINER=pdb6; @$ORACLE_HOME/rdbms/admin/noncdb_to_pdb.sql Startup the PDB and check the open mode. ALTER SESSION SET CONTAINER=pdb6; ALTER PLUGGABLE DATABASE OPEN; SELECT name, open_mode FROM v$pdbs; NAME OPEN_MODE ------------------------------ ---------- PDB6 READ WRITE pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 9 of 15 11/10/2014 5:12 PM
  • 1 row selected. SQL> The non-CDB has now been converted to a PDB. You should backup the PDB before you start to use it. Using Data Pump (expdb, impdp) A simple option is to export the data from the non-CDB and import it into a newly created PDB directly. Provided the import is connecting using a service pointing to the relevant PDB, this is no different to any other data transfer using data pump. If the non-CDB is version 11.2.0.3 onward, you can consider using Transport Database, as described here. If the non-CDB is pre-11.2.0.3, then you can still consider using transportable tablespaces. Using Replication Another alternative is to use a replication product like Golden Gate to replicate the data from the non-container database to a pluggable database. For more information see: Introduction to the Multitenant Architecture Overview of the Multitenant Architecture Managing a Multitenant Environment Creating a PDB Using a Non-CDB DBMS_PDB Categories: 12c, Database, new features in 12c, Oracle Tags: 12c, container database, Migrate Non-Container Database to Pluggable Database, new features in 12c, pluggable Database Multitenant : Overview of Container Databases (CDB) and Pluggable Databases (PDB) August 25, 2014 sercanbilgic 1 comment Overview The multitenant option represents one of the biggest architectural changes in the history of the Oracle database. The option introduced the concepts of the Container Database (CDB) and Pluggable Database (PDB). Container Database (CDB) : On the surface this seems very similar to a conventional Oracle database, as it contains most of the working parts you will be already familiar with (controlfiles, datafiles, undo, tempfiles, redo logs etc.). It also houses the data dictionary for those objects that are owned by the root container and those that are visible to all PDBs. Pluggable Database (PDB) : Since the CDB contains most of the working parts for the database, the PDB only needs to contain information specific to itself. It does not need to worry about controlfiles, redo logs and undo etc. Instead it is just made up of datafiles and tempfiles to handle it’s own objects. This includes it’s own data dictionary, containing information about only those objects that are specific to the PDB. pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 10 of 15 11/10/2014 5:12 PM
  • This split of the data dictionary between common objects, in the root container, and PDB-specific objects, in the PDB’s data dictionary, is very important, because this separation is what gives the multitenant option its flexibility. From the perspective of the PDB, the data dictionary is the union of the root and PDB data dictionaries, so internally the PDB feels very much like a normal Oracle database. For example, the DBA_% and ALL_% views within the PDB appears the same as any non-CDB database. Creating Pluggable Databases (PDBs) Since the bulk of the working parts are already present in the root container, creating a new PDB is a comparatively quick and simple task. When creating a completely new PDP, the PDB is created as a copy of a seed PDB, so it only takes as long as the files take to copy. Instead of creating a new PDB from the seed, you can clone an existing PDB. pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 11 of 15 11/10/2014 5:12 PM
  • Unpluging and Plugging in Pluggable Databases (PDBs) One of the most powerful features of the multitenant option is the ability to unplug a PDB from a CDB and plug it back into another CDB. Not only does this allow databases to be moved easily, but it also paves the way for quick patching and upgrading to future versions. A PDB can be unplugged from a 12.1 CBD and plugged into a 12.2 CDB, effectively upgrading it in seconds. Conversion of a non-CDB database to a pluggable database involves getting a description the non-CDB database and using this to plug it into a CDB as a new PDB. Views The introduction of the multitenant option brings with it an extra layer of data dictionary views, allowing reporting across the root container and the pluggable databases (PDBs). Ignoring editions for the moment, prior releases had the following hierarchy. DBA_ : All objects in the database. | --ALL_ : Objects accessible by the current user, including those owned by the current user. | --USER_ : Objects owned by the current user. With Oracle 12c, an extra layer is added to the hierarchy. CDB_ : All objects in the root container and all PDBs. | --DBA_ : All objects in the root container or PDB, depending on the current settings. | --ALL_ : Objects accessible by the current user, including those owned by the current user. | --USER_ : Objects owned by the current user. pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 12 of 15 11/10/2014 5:12 PM
  • The views are described in the Reference Manual. For more information see: Introduction to the Multitenant Architecture Overview of the Multitenant Architecture Managing a Multitenant Environment Categories: 12c, Database, new features in 12c, Oracle Tags: 12 c new features, 12c, container database, pluggable Database RSS feed Recent Posts Oracle Fusion Distributed Order Orchestration on Oracle SuperCluster T5-8 November 4, 2014 Linux Kernel Upgrade on Exadata(manual way) October 24, 2014 Change exadata flashcache mode from WriteThrough to WriteBack October 24, 2014 A Beginner’s Guide to NoSQL October 13, 2014 Siebel Web Service Call with SOAP October 13, 2014 Using Puppet to Manage Oracle October 13, 2014 Restricted access to PL/SQL subprograms in Oracle 12c October 13, 2014 New AWR Report Format: Oracle 11.2.0.4 and 12c October 12, 2014 Using the dcli Utility September 22, 2014 Back to School: What Open UI Does for You – And What Not(GOOD BYE SIEBEL, AT LEAST FOR ME)re- blogged from siebel-essentials September 20, 2014 Transport tablespaces across platforms in Oracle Database 12c August 27, 2014 Automatic Diagnostics Repository (ADR) Enhancements in Oracle Database 12c (ADRCI) August 27, 2014 Online Move Datafile in Oracle Database 12c Release 1 (12.1) August 27, 2014 Capture Privilege Usage (DBMS_PRIVILEGE_CAPTURE) in Oracle Database 12c Release 1 (12.1) August 27, 2014 Multitenant : Startup and Shutdown Container Databases (CDB) and Pluggable Databases (PDB) in Oracle Database 12c Release 1 (12.1) August 27, 2014 Archives November 2014 (1) October 2014 (7) September 2014 (2) August 2014 (17) July 2014 (17) June 2014 (1) May 2014 (3) April 2014 (9) March 2014 (4) pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 13 of 15 11/10/2014 5:12 PM
  • February 2014 (5) January 2014 (10) December 2013 (4) November 2013 (7) October 2013 (12) September 2013 (6) August 2013 (11) July 2013 (6) June 2013 (18) May 2013 (12) April 2013 (16) April 2012 (1) Tag Cloud 12 c new features 12c 12c Release 1 adf Analyze AWR apache AWR Big Data bpel bpm cell Configuration container database correlation creating script Database Data Validation debugging LoadRunner script eclipse Exadata exalogic export finding applets with given display name flow form applet framework hadoop Hadoop Cluster how to use smart script if-else Index Installation Installing Siebel 8.2.2 Invisible Index linux list applet Load Balancing LoadRunner Load Runner Load Test LOAD UI Mappings Migration new features in 12c Open UI oracle oracle 11g pattern performace test Performance performance test Performance Tuning pick pluggable Database querying applets&screens&views Query Statistic Query Tuning RAC recording script Reverse key SCBroker siebel Siebel Base Table and EIM Table Siebel DB Siebel Schema siebel tools siebel_log smart script soa SOAP UI SQL SQL Plan tomcat unix Web Service Categories .NET (1) Framework (1) 11g (1) 12c (12) big data (6) disk partition (1) EAI (1) Exa Family (18) Exadata (3) Exalogic (15) Hadoop (5) java (2) LDAP (1) linux (1) Load Balancer (1) F5 (1) new features in 12c (10) nosql (1) Oracle (120) ADF (1) Database (69) Materialized Views (2) Query Tuning (14) SQL Server (2) pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 14 of 15 11/10/2014 5:12 PM
  • Using Hint (7) SOA (8) Pattern (2) Performance Test (12) plsql (1) restricted access (1) Siebel (44) Data Validation (1) Product Cnfigurator (1) Smart Script (1) sql (1) subprograms (1) SuperCluster (1) Uncategorized (3) Unix (6) TROUG Follow My Blog bilgic.sercan01@gmail.com Join 528 other followers Meta Register Log in Entries RSS Comments RSS Blog at WordPress.com. Top Blog at WordPress.com. The INove Theme. pluggable Database | srcnblgc http://sercanbilgic.com/tag/pluggable-database/ 15 of 15 11/10/2014 5:12 PM
Comments
Top