RMAN Tablespace point-in-time Recovery

RMAN TABLESPACE POINT-IN-TIME RECOVERY

• Enables you to quickly recover one or more tablespaces
  to a time that is different from that of the rest of the database
• Like a table export, RMAN TSPITR enables you to recover a
  consistent data set; however, the data set is the entire
  tablespace rather than one object

RMAN does the following:

• Restores the specified tablespace backups
• Recovers the specified tablespaces
• Exports metadata from the auxiliary instance
• Points the target database control file to the newly recovered datafiles
• Imports metadata into the target database

When performing RMAN TSPITR, you cannot do the following:

• Run the target and auxiliary databases on separate computers.
  However, the target and auxiliary databases can be in a cluster
  configuration that uses shared disks.
• Recover dropped tablespaces.
• Recover a tablespace that has been dropped and re-created
  with the same name.
• Remove a datafile that has been added to a tablespace. If the
  file was added after the point to which RMAN is recovering, then
  the file will still be part of the tablespace (and will be empty)
  after RMAN TSPITR is complete.
• Issue DML statements on the auxiliary instance–the auxiliary
  instance is a temporary instance used for recovery only.
• Place any of the following objects within the recovery set:

  * Replicated master tables.
   * Partial tables. For example, if you perform RMAN TSPITR on 
      partitioned tables and spread partitions across multiple 
      tablespaces, then RMAN returns an error message during the  export phase.
  * Tables without their constraints or constraints without their tables.
  * Tables with VARRAY columns.
  * Tables with nested tables.
  * Tables with external files.
   * Snapshot logs and snapshot tables.
  * Tablespaces containing undo or rollback segments.
  * Objects owned by SYS (including rollback segments).