TSPITR to another DB...possible?

Question

Scenario:
We have a backup through RMAN and we need to perform a TSPITR but are told not to recover it to the target instance just yet. Can we recover it to another instance? Like a Test/DEV/STAGING area?
All the documentation from 11g says you can do it for the database, but does not mention that you can also do it for a subset like tablespaces. Is this possible? Any help or advice?
Version is 11.1.0.7 on Win2003, SP4 64Bit server, 2 Node RAC using RMAN Catalog.

Answer 1

OK, So I finally got things working as they should be. Only thing I did was I deleted the old backups, took a fresh new one and things started to work accordingly. Not sure why it would not work with the previous backup, but oh well. But I have a question about the script I used and how to use the storage parameters to point them to ASM so that all files can be created/recovered/deleted from the ASM disk cause currently, it creates some on the ASM and some on the local disk. Only thing on the local disk should be temp files which get deleted after...I wouldl like to store everything on the ASM disk in a directory that I suggest.
Here is my code
run{
set AUXILIARY INSTANCE PARAMETER FILE TO 'C:\EDBTEST2_backup\oradata\auxdest\initoraaux.ora';
set newname for datafile 1 to "+DATA";
set newname for datafile 2 to "+DATA";
set newname for datafile 3 to "+DATA";
set newname for datafile 4 to "+DATA";
TRANSPORT TABLESPACE RAMANS_RMAN_TEST
TABLESPACE DESTINATION 'C:\EDBTEST2_backup\oradata\auxdest\TTS'
DATAPUMP DIRECTORY DATA_PUMP_DIR
DUMP FILE 'expdp_RAMANS_RMAN_TEST.dmp'
IMPORT SCRIPT 'impdp_RAMANS_RMAN_TEST.sql'
EXPORT LOG 'RAMANS_RMAN_TEST.log'
until time "to_date('30-MAR-2010 16:25:00','DD-MON-YYYY HH24:MI:SS')"
AUXILIARY DESTINATION 'C:\EDBTEST2_backup\oradata\auxdest';
}How do I get:
TABLESPACE DESTINATION 'C:\EDBTEST2_backup\oradata\auxdest\TTS'
to actually point to a location on the ASM disk.
I read on a ASKTOM article to include the DATAPUMP DIRECTORY DATA_PUMP_DIR which points to the ASM. For my test I pointed the directory DATA_PUMP_DIR locally to see where it would store the files. After the recovery completed, look at the output of where the files were recovered to and kept, which is not correct according to the ASKTOM article...and Tom is never wrong, LOL
This is the datafile that got recovered
(This file is small but in a real world scenario, my files may be many gig's and my local disk will not be able to store them, hence why I want them to be pointed to the ASM. But it seems like its being called from the OS side, which means the OS does not see the ASM...true/false?)
C:\EDBTEST2_backup\oradata\auxdest\TTS>dir
Volume in drive C has no label.
Volume Serial Number is 00CB-7314
Directory of C:\EDBTEST2_backup\oradata\auxdest\TTS
03/31/2010  12:24 PM    <DIR>          .
03/31/2010  12:24 PM    <DIR>          ..
03/31/2010  12:24 PM             2,108 impdp_RAMANS_RMAN_TEST.sql
03/31/2010  12:24 PM        10,493,952 RAMANS_RMAN_TEST.284.715018095
03/31/2010  11:31 AM    <DIR>          RUN1
               2 File(s)     10,496,060 bytes
               3 Dir(s)  42,569,873,920 bytes free
This is the Dump file that got created in the ORACLE Directory
(If this pointed to the ASM, it would have created it there)
D:\DATA_PUMP_DIR>dir
Volume in drive D is Oracle
Volume Serial Number is 4611-C2C9
Directory of D:\DATA_PUMP_DIR
03/31/2010  12:51 PM    <DIR>          .
03/31/2010  12:51 PM    <DIR>          ..
03/31/2010  12:24 PM            86,016 EXPDP_RAMANS_RMAN_TEST.DMP
03/31/2010  01:06 PM             1,024 import.log
03/31/2010  12:24 PM             1,541 RAMANS_RMAN_TEST.log
               3 File(s)         88,581 bytes
               2 Dir(s)     278,368,256 bytes freeHas someone ran into this? Can someone please help me out?!?!?! Desperate to figure this out.