Performing Incomplete Recovery - RMAN Recipes for Oracle Database 12c - page 388

Here is a small snippet of the output produced:
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
After the PDB has been restored and recovered to the specified point, you must open the PDB with the OPEN
RESETLOGS clause
ALTER PLUGGABLE DATABASE salespdb OPEN RESETLOGS;
If successful, you should see this message:
Statement processed
The OPEN RESETLOGS in this situation only applies to the PDB. This syntax is required to open the PDB and create
a new incarnation of it. It does not reset the online logs for the root container database nor create a new incarnation
for the root container database. You can check on the incarnation status of the PDB by querying:
select pdb_incarnation#
from v$pdb_incarnation
where status = 'CURRENT'
and con_id = <container_ID>;
How It Works
Restoring a pluggable database to a prior point in time is very similar to restoring a non-pluggable database to a
previous point in time. The main difference is that you must use the PLUGGABLE clause and specify a specific PDB.
You do not have to shut down the parent root container database or any other pluggable databases in the CDB. In
other words you can perform an incomplete recovery on an individual pluggable database without impacting the
availability of any other databases within the CDB.
When performing a point in time recovery on a PDB, RMAN first restores the PDB data files from the appropriate
backup. To perform a PDB point in time recovery, RMAN requires a copy of the root container's undo tablespace as it
was for the specified point in time in the past. To accomplish this RMAN creates a temporary auxiliary database which
minimally consists of the root container's undo, system, and sysaux tablespaces.
If you're using a FRA, RMAN will create the auxiliary database data files in the FRA in the <FRA>/<SID>/datafile
directory. Make sure you have enough space allocated and free in your FRA to accommodate the prior mentioned
tablespaces' data files. If you don't have enough space, an ORA-19809: limit exceeded for recovery files error
will be thrown.
If you're not using a FRA, RMAN will create the auxiliary database data files in the location specified by the
AUXILIARY DESTINATION clause. Again, you need to ensure you have enough disk space in auxiliary destination to
allow for the restoration of the auxiliary database.
After RMAN is finished with the PDB point in time recovery, the auxiliary instance is shutdown. Also, when the
PDB is opened for use RMAN removes any data files that were restored for the auxiliary database.