Identify any objects in the original database that may be impacted by the tablespace point-in-time recovery. This will include any dependent objects, tables with referential integrity, and indexes and objects created after the point-in-time recovery time. The various constraints will have to be removed prior to tablespace point-in-time recovery.

Create a second, or clone, database. Using hot or cold backups, restore the datafiles to the clone database. Normally, you will only need the datafiles corresponding to the SYSTEM tablespace, the rollback segments, any temporary tablespaces, and the tablespace containing the tables to be recovered. If necessary, use archive files to roll forward the tablespaces to the desired point.

Mount the clone database using the ALTER DATABASE MOUNT CLONE DATABASE command.

Use the Export utility to export metadata about the objects in the tablespaces to be recovered.

Alter the original database to rename the datafiles to the recovered tablespace datafiles.

Input this special export. All objects in the tablespaces are effectively dropped and recreated.

Delete the remaining datafiles in the clone database.