Originally posted by qzheng
A table was truncated by a batch job and we need to restore the data. We have cold backup and the database is in archive log mode. We don't need any roll forward as the data in the table is stable until the batch job changed it.

We are trying to restore the backup to a test server, open the database, export the table, and import the table to production. Since the table is small and the tablespace where it resides is also small, we want to just restore a partial database.

The question is what files need to be restored from the cold backup? The RBS and TEMP are both very large and we are thinking to skip them and, after the database is open create new RBS and TEMP tablespace. So I guess I need the control files, SYSTEM tablespace file, USER tablespace file, and the affected TABLESPACE.

But how about the online redo log files? Do I need to restore them too? Since the test server mount points are all different, how do I tell the control files that redo log files are changed?

Thanks
Yep you can do tablespace point in time recovery (TSPITR). you can save lot of time by doing this. Steps are.

1. Find out the name of tablespace on which the truncated object was there. And find out the corresponding datafiles.
2. Restore the system tablespace datafiles and datafiles of interest (the ones you found from step one).
3. Take trace of controlfile from production and edit it to suit the new location and names of datafiles and redologs.
4. open the test db in nomount state and run the controlfile creation script prepared in step 3.
5. in mount state do the following for all those datafiles which you have not restored.

alter database datafiles <> offline drop;

Execute this command for all datafiles that are not in system and tablespace of interest.
6. recover the database untill point in a point in time where your table is with required data.
7. Open the database with resetlogs.

Try this out and let me know the result.