Before you perform restore and recovery operations, you must be aware of the limitations.
If you are using any version of Oracle from 11.2.0.4 to 12.1.0.1, the restore operation will be in hung state when you run the renamedg command. You can apply the Oracle patch 195447733 to fix this issue.
The following restore and recovery operations are not supported:
- Restore and recovery of tablespaces of the root container database (CDB)
- Restore of temporary tablespaces and temporary tablespaces associated with PDBs
- Restore and recovery of tablespaces from multiple PDBs simultaneously
- Restore of log backups
- Restore of backups to a different location
- Restore with recovery of tablespace and PDBs up to a specific SCN and date
- Restore of redo log files in any configuration other than Data Guard standby or Active Data Guard standby databases
- Restore of SPFILE and Password file
- When you perform a restore operation on a database that was re-created using the preexisting database name on the same host, was managed by SnapCenter, and had valid backups, the restore operation overwrites the newly created database files even though the DBIDs are different.
This can be avoided by performing either of following actions:
- Discover the SnapCenter resources after the database is re-created
- Create a backup of the re-created database