Limitations of Tablespace point-in-time Recovery

•If you have dropped a tablespace then TSPITR can't be used to recover that tablespace.

•You cannot recover a renamed tablespace to a point in time before it was renamed.

•You cannot recover tables without their associated constraints, or constraints
without the associated tables.

•Tablespaces containing undo or rollback segments cannot be recovered.

•Tablespaces that contain objects owned by SYS can't be recovered.

•In case of partitioning table which spread over multiple tablespaces in that case a single tablespace(only a partition/subset of partition) can't be recovered. You must recover all of the tablespace where partitioning table resides.

•If a tablespace is recovered by TSPITR statistics are not gathered of recovered objects. Therefore you must manually gather statistics of the recovered objects.

•Tablespace containing tables with VARRAY columns, nested tables, or external files can't be recovered with TSPITR.

•The tablespace containing replicated master tables, snapshot logs, snapshot tables can't be recovered with TSPITR.

•If a datafile was added after the point to which RMAN is recovering, an empty datafile by the same name will be included in the tablespace after RMAN TSPITR.