Oracle Database 18c

Multitenet
Sai Kommaraju
Senior Advanced Support Engineer

Oracle SSE

Copyright © 2019, Oracle and/or its affiliates. Allrights reserved. |

Safe Harbor Statement
The following is intended to outline our general product direction. It is intended for information
purposes only, and may not be incorporated into any contract. It is not a commitment to deliver
any material, code, or functionality, and should not be relied upon in making purchasing decisions.
The development, release, and timing of any features or functionality described for Oracle’s
products remains at the sole discretion of Oracle.

Copyright © 2019, Oracle and/or its affiliates. All rights reserved. |

Multitenant

Copyright © 2019, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential –Internal 21
Multitenant Enhancements in 18c

 Refreshable PDB Switchover

 PDB Snapshot Carousel
 Usable backups of non-CDBs and relocated PDBs
 RMAN duplication of a PDB to another CDB

Copyright © 2019, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential –Internal 22
Refreshable PDB SnapClone

SnapClone
Dev / Test
Master Dev/Test version no longer in CRM CRMDev1 CRMDev2
sync
• PDB Refresh
– Incremental refresh of clone with latest data

Only changes copied and

applied Developers

Pricing Retail CRM

Changes made to
database

TIME
Production
Copyright © 2019, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential –Internal
Refreshable PDB Switchover

Server1 create pluggable database Grey

from Grey@CDB2_Link
refresh mode auto every 2 minutes;

CDB1

Server2 create pluggable database Red

from Red@CDB1_Link
refresh mode auto every 2 minutes;

CDB2

Copyright © 2019, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential –Internal
Refreshable PDB Switchover

Server1 1. alter pluggable database refresh

mode auto every 2 minutes from
Grey@dblink switchover;
2. alter pluggable database Grey
open read write;
CDB1

Server2

CDB2

Copyright © 2019, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential –Internal
Point-in-Time Recovery with SnapshotCarousel
Carousel stores archive logs along with corresponding snapshot clones

Archive Logs
• ”Flashback” to Thursday 10:17am:
1. Restore Thursday midnight’s snapshot
2. Roll forward to 10:17am from archivelog
– PDB will be “transactionally consistent” as of this time

Sunday Monday Tuesday Wednesday Thursday Friday Saturday

Copyright © 2019, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential –Internal
Point-in-Time Cloning with Snapshot Carousel

• “Hot Clone” introduced with 12.2

• Basic hot clone is transactionally consistent with source PDB
as of SCN at completion of statement

alter pluggable database Hot_Clone open;

• Snapshot Carousel enables hot clone to a specific point in time (or SCN)
– Restore most recent snapshot from carousel
– Roll forward to required point in time by performing recovery from corresponding archive log

Copyright © 2019, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential –Internal 27
Usable backups of non –CDBs and relocated PDBs

If you are creating a PDB by cloning a non-CDB, and if you want the ability to recover the new
PDB using backups of the source non-CDB, then you must execute
DBMS_PDB.EXPORTRMANBACKUP before cloning. When the source database is opened in
read-write mode, execute the procedure as the last step before cloning. This procedure
captures all backup metadata in the data dictionary.

When relocating a PDB to a different CDB, executing DBMS_PDB.EXPORTRMANBACKUP is not

necessary. Unplugging the PDB automatically exports the backup metadata.

Useful Links: https://docs.oracle.com/en/database/oracle/oracle-database/18/multi/release-

changes.html#GUID-13A96755-8407-42B0-A8B8-00E84FD8A360
https://docs.oracle.com/en/database/oracle/oracle-database/18/multi/overview-of-pdb-
creation.html#GUID-B26D56E1-B958-444F-864C-8AFDFF1566A6

Copyright © 2019, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential –Internal
RMAN duplication of a PDB to another CDB
To duplicate a PDB to an existing CDB:

• Ensure that the required prerequisites are met i.e for active database duplication and duplicating a PDB to an existing
CDB
• Review the limitations of duplicating a PDB to an existing CDB
• Choose a strategy for naming duplicate database files
• Create the directories that store the duplicate database files on the destination CDB
• Establish Oracle net connectivity between the source CDB and the destination CDB
• Start RMAN and make the following connections:
Connect AS TARGET to the root of the source CDB as a common user with the SYSDBA or SYSBACKUP privilege.
Connect AS AUXILIARY to the root of the destination CDB as a common user with the SYSDBA or SYSBACKUP
privilege.
• Ensure that the destination CDB is open in read-write mode.
• Configure RMAN channels, if necessary
The primary task of duplication is performed by RMAN channels. Configuring additional channels improves the
duplication performance.
• Duplicate the PDB by using the DUPLICATE PLUGGABLE DATABASE command.
• To use a different name for the PDB in the destination (duplicate) database,
use the PLUGGABLE DATABASE mypdb AS pdb_dup TO cdb_sales syntax.
• Delete the foreign archived redo log files that were restored to the
location specified by the remote_recovery_file_dest initialization
parameter as part of the duplication.

Copyright © 2019, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential –Internal
RMAN duplication of a PDB to another CDB

Duplicating a PDB to an existing CDB is subject to certain restrictions.

• Only active database duplication is supported.

• Only the following clauses of the DUPLICATE command are supported: NORESUME, DB_FILE_NAME_CONVERT,
SECTION SIZE, and USING COMPRESSED BACKUPSET.
• The following clauses of the DUPLICATE command are not supported: SPFILE, NO STANDBY, FARSYNC STANDBY, and
LOG_FILE_NAME_CONVERT.
• Duplicating a PDB to a CDB that is a standby database is not supported.
• Only one PDB can be duplicated at a time. Partial PDB duplication is not supported, only complete PDB duplication is
supported. For example, you cannot include or exclude specific tablespaces while duplicating a PDB.
• Duplicating a non-CDB as a PDB in an existing CDB is not supported.
• Duplicating PDBs that contain TDE-encrypted tablespaces is not supported.
Ref:
https://docs.oracle.com/en/database/oracle/oracle-database/18/bradv/rman-duplicating-databases.html#GUID-
3E8DE9F7-4A62-46D2-A0AE-7F25DCF6DEC3
https://docs.oracle.com/en/database/oracle/oracle-database/18/bradv/rman-duplicating-databases.html#GUID-
9E630E2C-3D1B-4594-B738-4B5B43E50C58
Prerequisites: https://docs.oracle.com/database/121/RCMRF/rcmsynta020.htm#RCMRF126

Copyright © 2019, Oracle and/or its affiliates. All rights reserved. | Oracle Confidential –Internal