From the 12c documentation, it is clear that a Pluggable Database does not have (a) it's own instance (b) it's own redo and archivelogs.
Also, there are a number of restrictions in RMAN when you configure a Multi-Tenanted Database and run RMAN against one of the PDBs.
Here are the documented restrictions :
What does this mean ? For most Backup scenarios, you would run Backups from the *CONTAINER* Database. You can connect to the Container Database and Backup an individual PDB.
Also, there are a number of restrictions in RMAN when you configure a Multi-Tenanted Database and run RMAN against one of the PDBs.
Here are the documented restrictions :
The following operations are not available when you connect as target directly to a PDB:
· Back up archived logs
· Delete archived logs
· Delete archived log backups
· Restore archived logs (RMAN does restore archived logs when required during media recovery.)
· Point-in-time recovery (PITR)
· TSPITR
· Table recovery
· Duplicate database
· Flashback operations
· Running Data Recovery Advisor
· Report/delete obsolete
· Register database
· Import catalog
· Reset database
· Configuring the RMAN environment (using the CONFIGURE command)
Note:
When you connect as TARGET to a PDB, you cannot connect to a recovery catalog.
.
.
