Requirements of Tablespace Point-in-time Recovery

•You must have the backups of all datafiles of the recovery and auxiliary tablepspace set and your desired TSPITR time is after the time of the backups for those datafiles.

•You must have control file backup before the TSPITR time.

•The control file backup must be a binary one. That is ALTER DATABASE BACKUP CONTROLFILE TO '';

•Ensure that all files constituting the recovery set tablespaces are in the recovery set on the auxiliary database; otherwise, the export phase during tablespace transport fails.

•Enough disk space must be available on the auxiliary host to accommodate the auxiliary database.

•Provide enough real memory to start the auxiliary instance.

•If the tablespace to be recovered has been renamed, ensure that the target SCN for TSPITR is after the time when the file was renamed. You cannot TSPITR a renamed tablespace to a point in time earlier than the rename. However, you can perform a DBPITR to an SCN before the rename. In this case, the tablespace reverts to its name as of the target SCN.