{ "date": "2016-11-08T18:58:48", "slug": "oracle-12cr2-multitenant-local-undo", "link": "https://www.dbi-services.com/blog/oracle-12cr2-multitenant-local-undo/", "title": { "rendered": "Oracle 12cR2 multitenant: Local UNDO" }, "content": { "rendered": "

By Franck Pachot

\n

.
\nPluggable Databases are supposed to be isolated, containing the whole of user data and metadata. This is the definition of dictionary separation coming with multitenant architecture: only system data and metadata are at CDB level. User data and metadata are in separate tablespaces belonging to the PDB. And this is what makes the unplug/plug available: because PDB tablespaces contain everything, you can transport their datafiles from one CDB to another.
\nHowever, if they are so isolated, can you explain why

\n\n


\nThere is something that is not contained in your PDB but is at CDB level, and which contains user data. The UNDO tablespace is shared:

\n

\"CaptureLocalUndo001\"

\n

You cannot flashback a PDB because doing so requires to rollback the ongoing transactions at the time you flashback. Information was in UNDO tablespace at that time, but is not there anymore.

\n

It’s the same idea with Point-In-Time recovery of PDB. You need to restore the UNDO tablespace to get those UNDO records from the Point-In-Time. But you cannot restore it in place because it’s shared with other PDBs that need current information. This is why you need an auxiliary instance for PDBPITR in 12.1

\n

To clone a PDB cannot be done with ongoing transactions because their UNDO is not in the PDB. This is why it can be done only when the PDB is read-only.

\n

12.2 Local UNDO

\n

In 12.2 you can choose to have one UNDO tablespace per PDB, in local undo mode, which is the default in DBCA:

\n

\"CaptureLocalUndo000\"

\n

With local undo PDBs are truly isolated even when opened with ongoing transactions:

\n

\"CaptureLocalUndo002\"

\n

Look at the ‘RB segs’ column from RMAN report schema:
\n
\n[oracle@OPC122 ~]$ rman target /
\n 
\nRecovery Manager: Release 12.2.0.1.0 - Production on Tue Nov 8 18:53:46 2016
\n 
\nCopyright (c) 1982, 2016, Oracle and/or its affiliates. All rights reserved.
\n 
\nconnected to target database: CDB1 (DBID=901060295)
\n 
\nRMAN> report schema;
\n 
\nusing target database control file instead of recovery catalog
\nReport of database schema for database with db_unique_name CDB1
\n 
\nList of Permanent Datafiles
\n===========================
\nFile Size(MB) Tablespace RB segs Datafile Name
\n---- -------- -------------------- ------- ------------------------
\n1 880 SYSTEM YES /u02/app/oracle/oradata/CDB1/system01.dbf
\n3 710 SYSAUX NO /u02/app/oracle/oradata/CDB1/sysaux01.dbf
\n4 215 UNDOTBS1 YES /u02/app/oracle/oradata/CDB1/undotbs01.dbf
\n5 270 PDB$SEED:SYSTEM NO /u02/app/oracle/oradata/CDB1/pdbseed/system01.dbf
\n6 560 PDB$SEED:SYSAUX NO /u02/app/oracle/oradata/CDB1/pdbseed/sysaux01.dbf
\n7 5 USERS NO /u02/app/oracle/oradata/CDB1/users01.dbf
\n8 180 PDB$SEED:UNDOTBS1 NO /u02/app/oracle/oradata/CDB1/pdbseed/undotbs01.dbf
\n9 270 PDB1:SYSTEM YES /u02/app/oracle/oradata/CDB1/PDB1/system01.dbf
\n10 590 PDB1:SYSAUX NO /u02/app/oracle/oradata/CDB1/PDB1/sysaux01.dbf
\n11 180 PDB1:UNDOTBS1 YES /u02/app/oracle/oradata/CDB1/PDB1/undotbs01.dbf
\n12 5 PDB1:USERS NO /u02/app/oracle/oradata/CDB1/PDB1/users01.dbf
\n 
\nList of Temporary Files
\n=======================
\nFile Size(MB) Tablespace Maxsize(MB) Tempfile Name
\n---- -------- -------------------- ----------- --------------------
\n1 33 TEMP 32767 /u04/app/oracle/oradata/temp/temp01.dbf
\n2 64 PDB$SEED:TEMP 32767 /u04/app/oracle/oradata/temp/temp012016-10-04_11-34-07-330-AM.dbf
\n3 100 PDB1:TEMP 100 /u04/app/oracle/oradata/CDB1/PDB1/temp012016-10-04_11-34-07-330-AM.dbf
\n

\n

You have an UNDO tablespace in ROOT, in PDB$SEED and in each user PDB.

\n

If you have a database in shared undo mode, you can move to local undo mode while in ‘startup migrate’. PDBs when opened will have an UNDO tablespace created. You can also create an UNDO tablespace in PDB$SEED.

\n

Yes, in 12.2, you can open the PDB$SEED read/write for this purpose:

\n


\n18:55:59 SQL> alter pluggable database PDB$SEED open read write force;
\n 
\nPluggable database altered.
\n 
\n18:56:18 SQL> show pdbs;
\n 
\n CON_ID CON_NAME OPEN MODE RESTRICTED
\n---------- ------------------------------ ---------- ----------
\n 2 PDB$SEED READ WRITE NO
\n 3 PDB1 READ WRITE NO
\n18:56:23 SQL> alter pluggable database PDB$SEED open read only force;
\n 
\nPluggable database altered.
\n
\nBut remember this is only allowed for local undo migration.

\n

The recommandation is to run in local undo mode, even in Single-Tenant.

\n

More about it in the 12cR2 Multitenant book:
\n\"\"

\n", "protected": false } }