Purpose of auxiliary instance in TSPITR

Need help!
I've read Database Backup and Recovery User's Guide 11g but I can't uderstand why we need auxiliary instance to perform tspitr.
We can do complete recovery of tablespace within same instance, why it's impossible for tspitr?
Here Re: Question on recovery Hemant K Chitale says: "+You cannot recover a tablespace to an SCN that is lower than the rest of the database.+". Can anyone help me to uderstand why?
In this message Re: scn of datafile after recovery is shown that when we turn tablespace offline, its SCN becomes lower than SCN of other tablespaces after a while, and when we turn it online "+it will not apply redo it will just adopt current SCN+".
Edited by: jonny.engineer on 23.04.2013 21:39

We can do complete recovery of tablespace within same instance, why it's impossible for tspitr?A TSIPTR is an Incomplete Recovery. Oracle will not allow you to run a database such that at, say, shutdown and startup, the datafiles are at different SCNs. All the datafiles must be consistent to the same point in time. (TSPITR makes a consistent database -- the auxiliary instance -- and then uses Transportable Tablespace to copy the tablespace and plug it back to the original database. At this point, the Checkpoint SCN of the datafiles of the transported tablespace get's reset to be consistent with the rest of the database).
Here Re: Question on recovery Hemant K Chitale says: "You cannot recover a tablespace to an SCN that is lower than the rest of the database.". Can anyone help me to uderstand why?See my answer above. A database cannot have datafiles that are of different points in time (SCNs). The exception is when transportable tablespaced is used -- in this case the Checkpoint SCNs of the transported datafiles are reset to be consistent with the database.
In this message Re: scn of datafile after recovery is shown that when we turn tablespace offline, its SCN becomes lower than SCN of other tablespaces after a while, and when we turn it online "it will not apply redo it will just adopt current SCN".That is a tablespace that belongs to the database. Activity against the tablespace is halted once the OFFLINE is done. The database knows that the datafiles are frozen and have no changes. Therefore, it is easy for the database to reset the Checkpoint SCNs when the ONLINE is done.
Hemant K Chitale

Similar Messages

  • Error when connecting to auxiliary instance

    Hi,
    I have set up an auxiliary database to do a DUPLICATE. The auxiliary instance is started in NOMOUNT mode.
    When i try to connect from RMAN i get the following error:
    RMAN>connect auxiliary sys/<password>@<sid>
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-04006: error from auxiliary database: ORA-00600: internal error code, arguments: [15435], [SYS], [X$DBMS_BACKUP_RESTORE], [], [], [], [], []
    ORA-04031: unable to allocate 1040 bytes of shared memory ("shared pool","X$DBMS_BACKUP_RESTORE","PL/SQL DIANA","PAR.C:parapt:Page")
    RMAN-04015: error setting target database character set to WE8MSWIN1252
    Environment is 10.2 on Windows
    any clues??
    Regards
    Rolf

    Hi all and thanks for your response,
    RMAN client is 10.1.0.3.0. Auxiliary instance is 10.2.0.3 (same as target).
    I modified auxiliary init.ora with:
    SHARED_POOL_SIZE=64M
    I had created the auxiliary instance as said in the manual (I think), using orapwd, oradim, creating a init.ora file, etc.
    I don't remember that SHARED_POOL_SIZE was mandatory for the init.file of the auxiliary instance...
    However, i restarted the instance (nomount), and now I can connect the auxiliary instance from RMAN :)
    However; i was going to create a duplicate database useing the DUPLICATE command. Everything went smoothly, all datafiles restored to correct path, but when RMAN finaly was trying to CREATE CONTROLFILE... I hit this error:
    SQL-setning: CREATE CONTROLFILE REUSE SET DATABASE "W558DUP" RESETLOGS NOARCHIVELOG
    MAXLOGFILES 16
    MAXLOGMEMBERS 3
    MAXDATAFILES 200
    MAXINSTANCES 8
    MAXLOGHISTORY 77312
    LOGFILE
    GROUP 1 ( 'D:\ORACLE\ORADATA\W558DUP\REDO01.LOG' ) SIZE 16 M REUSE,
    GROUP 2 ( 'D:\ORACLE\ORADATA\W558DUP\REDO02.LOG' ) SIZE 16 M REUSE,
    GROUP 3 ( 'D:\ORACLE\ORADATA\W558DUP\REDO03.LOG' ) SIZE 16 M REUSE,
    GROUP 4 ( 'D:\ORACLE\ORADATA\W558DUP\REDO04.LOG' ) SIZE 16 M REUSE,
    GROUP 5 ( 'D:\ORACLE\ORADATA\W558DUP\REDO05.LOG' ) SIZE 16 M REUSE
    DATAFILE
    'D:\ORACLE\ORADATA\W558DUP\SYSTEM01.DBF'
    CHARACTER SET WE8MSWIN1252
    frigitt kanal: TSM
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 08/25/2008 04:20:19
    RMAN-06136: ORACLE error from auxiliary database: ORA-01503: CREATE CONTROLFILE
    failed
    ORA-00600: internal error code, arguments: [kccscf_1], [9], [77312], [65535], []
    RMAN>
    I find Bug 4877360 (*'Create controlfile command in 10.2 compatibility mode results in an ORA-600 [kccscf_1]*') on metalink, confirmed in 10.2.0.3 (my version) and fixed in 10.2.0.4, and there is a patch (Patch 4877360)
    but not for Windows as far as i can see...
    I also tried the CREATE CONTROLFILE ( referencing all datafiles) from sql*plus but got the same error.
    My auxiliary init.ora files contain the COMPATIBLE=10.2.0.3.0 parameter.
    Could I set compatibility to, say 10.1 (since the bug reference the 10.2 compatibility mode) ??
    Regards
    Rolf

  • Help required understanding the purpose of having instance Init blocks

    I want to know exactly what the purpose of having instance initialization blocks in Java. As in static init blocks, we can execute some commands before creating an instance of a class.
    And also in instance init blocks, we are executing some commands which we can do in a constructor. So I’m little bit confused of the purpose of having this concept instance init blocks without writing it in the constructor itself.
    Really appreciate if anyone can explain this ASAP as I am still a beginner who is studying for SCJP exam.
    Thanks in advance.

    The instance initialization blocks are always executed before the constructor code is executed. This may be used for some activity which is common to all constructors (in case constructors are overloaded).

  • RMAN-05520: database name mismatch, auxiliary instance has ORADB

    Hi,
    i am using Oracle 10g (10.2.0.1.0) in RHEL 5 server. i am trying to duplicate my primary database(ORADB) to standby database with name DEVDB in different server. I have taken an RMAN backup and transferred to standby server and now i am trying to duplicate with the below commands
    [oracle@rhel5 data]$ rman target / auxiliary sys/oracle@DEVDB
    Recovery Manager: Release 10.2.0.1.0 - Production on Sat Mar 9 16:11:52 2013
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    connected to target database: ORADB (DBID=2542358497, not open)
    connected to auxiliary database: ORADB (not mounted)
    RMAN>
    RMAN>
    RMAN> duplicate target database to DEVDB
    2> ;
    Starting Duplicate Db at 09-MAR-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: sid=151 devtype=DISK
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 03/09/2013 16:14:02
    RMAN-05520: database name mismatch, auxiliary instance has ORADB, command specified DEVDB
    My primary db pfile has
    *.db_name='ORADB'
    *.db_unique_name='ORADB'
    My standby db has
    *.db_name='ORADB'
    *.db_unique_name='DEVDB'
    Regards,
    007

    Hello again;
    Agreed. You have at least two issues.
    Generally I change the SID
    export ORACLE_SID=DEVDB
    Then I start NOMOUNT using an INIT file.
    Then this should be correct
    connected to target database: ORADB (DBID=2542358497, not open)
    connected to auxiliary database: ORADB (not mounted)h2. Later
    I think I was wrong I would like to change my answer. I looked back and found my old notes and things are not as I stated above.
    I used an INIT file ( standby side ) for cloning as follows :
    db_name=RECOVER2
    instance_name=RECOVER2
    control_files=("/u01/app/oracle/oradata/RECOVER2/control01.ctl", "/u01/app/oracle/flash_recovery_area/RECOVER2/control02.ctl")
    db_recovery_file_dest=/u01/app/oracle/flash_recovery_area
    db_recovery_file_dest_size=4070572032
    compatible=11.2.0.0.0
    core_dump_dest='/u01/app/oracle/diag/rdbms/recover2/RECOVER2/cdump'
    db_block_size=8192
    audit_file_dest=/u01/app/oracle/admin/RECOVER2/adump
    undo_tablespace=UNDOTBS1
    undo_management = AUTO
    undo_retention=10800So for the duplicate I don't set DB_UNIQUE_NAME
    I Backed up the target database as shown here with the ‘backup current controlfile for standby format’ command:
    RMAN RUN {
    allocate channel d1 type disk;
    backup format '/u01/backups/RECOVER2/df_t%t_s%s_p%p' database;
    sql 'alter system archive log current';
    backup format '/u01/backups/RECOVER2/al_t%t_s%s_p%p' archivelog all;
    backup current controlfile for standby format '/u01/backups/RECOVER2/sb_t%t_s%s_p%p';
    release channel d1;
    }I did a startup the standby as follows : ( Notice you are correct about the SID and I was incorrect )
    export ORACLE_SID=RECOVER2
    /home/oracle:SRECOVER2 >sysplus "/ as sysdba"
    Connected to an idle instance.
    SQL> startup nomount pfile='/u01/app/oracle/admin/RECOVER2/pfile/initRECOVER2.ora';I started RMAN like this :
    /home/oracle:SRECOVER2 >export ORACLE_SID=RECOVER2
    rman target sys/password@recover2 auxiliary /
    Recovery Manager: Release 11.2.0.1.0 - Production on Fri Sep 10 13:35:29 2010
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: RECOVER2 (DBID=3806912436)
    connected to auxiliary database: RECOVER2 (not mounted)So you connect to the Primary, but the auxiliary should show "not mounted"
    Finally I issue the duplicate command
    RMAN> run {
    2> allocate channel C1 device type disk;
    3> allocate auxiliary channel C2 device type disk;
    4> duplicate target database for standby nofilenamecheck;
    5> }Best Regards
    mseberg
    Edited by: mseberg on Mar 9, 2013 10:39 AM

  • Thread: Cannot connect to auxiliary instance posted by William Wong

    I am experiencing the same issue and I am able to get the suggestion to work connecting to both the target and auxiliary databases on the auxiliary server, but I don't know where to go from there. Do I go back to the target server and continue from there?
    This is on 2 identical linux boxes running Oracle 10.2.0.6.

    Your problem I think is that the listener on the auxiliary server is likely to have the status of this service (shown with lsnrctl servcies) as BLOCKED.
    What you need to do is, on that server, edit the listener.ora and add a static SID_LIST section to the file, so that the listener will report that service as status UNKNOWN. That is, there will be two statuses listed for the same service, one BLOCKED because that's coming from dynamic registration and one UNKNOWN because that's what the SID_LIST says.
    An example listener.ora would look like:
    LISTENER =
      (DESCRIPTION_LIST =
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
        (DESCRIPTION =
          (ADDRESS = (PROTOCOL = TCP)(HOST = PLPC358)(PORT = 1521))
    SID_LIST_LISTENER =
      (SID_LIST =
        (SID_DESC =
          (GLOBAL_DBNAME = TESTDB)
          (ORACLE_HOME = c:\oracle\10g\db_1)
          (SID_NAME = TESTDB)
      )You will have to make sure that on the server where you're running RMAN (effectively, the client for this occasion), the auxiliary instance is listed in the tnsnames.ora with a SID=TESTDB sort of line, rather than a SERVICE=TESTDB. If you try to connect via 'service=' aliases, you'll be trying to connect via the BLOCKED "socket" on the auxialiary instance. If you connect via a "sid=" alias, you'll be connecting via the UNKNOWN socket, and that's what you want.
    Message was edited by:
    Catfive Lander
    I should have read your earlier post more carefully. I see you already have the UNKNOWN instance listed on the auxialiary server, so I think you're half-way there. I think you just need to make sure the tnsnames.ora used by your RMAN machine refers to SID= not SERVICE=

  • Unable to connect to Auxiliary instance using connect string

    Hi All
    I am trying to setup Data guard on 11G Release 2 OS : OEL 5.4. I have to connect to the auxiliary instance using rman. But i am getting following error.
    >
    [oracle@vm4dg ~]$ rman
    Recovery Manager: Release 11.2.0.1.0 - Production on Mon Apr 29 19:25:13 2013
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    RMAN> connect auxiliary sys/orcl123@melbourne
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-04006: error from auxiliary database: ORA-01031: insufficient privileges
    >
    I have tried the solutions like all service name in listener.ora to be in upper/lower case.
    Thanks
    Ankur

    Here's what you asked for
    On primary
    >
    [oracle@oel54gen ~]$ rman target sys/orcl123@London auxiliary sys/orcl123@melbourne
    Recovery Manager: Release 11.2.0.1.0 - Production on Mon Apr 29 19:50:09 2013
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    connected to target database: LONDON (DBID=3149285088)
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00554: initialization of internal recovery manager package failed
    RMAN-04006: error from auxiliary database: ORA-01031: insufficient privileges
    >
    for sqlplus on primary
    >
    [oracle@oel54gen ~]$ sqlplus "sys/orcl123@melbourne as sysdba"
    SQL*Plus: Release 11.2.0.1.0 Production on Mon Apr 29 19:52:13 2013
    Copyright (c) 1982, 2009, Oracle. All rights reserved.
    ERROR:
    ORA-01031: insufficient privileges
    Enter user-name:
    >
    for sqlplus on Standby
    >
    [oracle@vm4dg dbs]$ sqlplus "sys/orcl123@london as sysdba"
    SQL*Plus: Release 11.2.0.1.0 Production on Mon Apr 29 19:53:42 2013
    Copyright (c) 1982, 2009, Oracle. All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
    With the Partitioning, Automatic Storage Management, OLAP, Data Mining
    and Real Application Testing options
    SQL>
    >
    One more thing is that i have two oracle homes on each machine. And listener are running from grid home
    Thanks
    Ankur

  • Purpose of Auxiliary Channels?

    I am having difficulty understanding the purpose of auxiliary channels. I have used busses to run multiple tracks through the same reverb, etc. What's the difference between the two and when do I use one over the other?

    Brian Battles wrote:
    How do you send a track through an Auxiliary channel? I see the only choices are Output or Bus. Methinks I am still misunderstanding how an Aux works.
    Think of Aux channels as "extra channels through which you can route audio." The 3 uses for an Aux channel are:
    1. as an auxiliary channel for Send effects, like reverb and delay
    2. as a bus for audio before the main output bus (for sub-mixes)
    3. as an audio conduit for ReWire-based applications like Ableton Live or Reason
    Taking the first 2 uses, which are arguably the most common, we can do the following:
    1. To use the Aux channel for a Send effect, create an Aux channel, assign a Bus number to it (let's use Bus 1 for this example), then throw in a Send effect in one the Insert slots (reverb for example). On an audio or instrument track, you can assign Bus 1 to one of the Send slots and dial in the amount of the the reverb you want.
    2. To use the Aux as a sub-mix bus, similarly, you create an Aux channel, assign a Bus number (Bus 2 this time, for example) and call up an appropriate bus plugin (such as a compressor or limiter). Then on tracks you want to feed into this "sub-mix" bus, you'd select Bus 2 for the Output.
    As you see, you either send a signal to a bus via the Send slot/knob or via the Output slot.
    As you mention, Aux channels also have Send slots as well as an assignable Output, which makes further routing of sends and outputs possible. This opens up tremendous possibilities for audio routing.
    I can make a track into an Aux track, but how does that differ from making it, say, an Audio track?
    An Aux track can't record audio or play software instruments, so it should be treated as a channel through which you route audio coming from audio or instrument channel strips.
    Hope I was clear and didn't confuse you further. I might tend to over-explain.
    -droo

  • Auxiliary instance connection time out

    Hi Experts,
    I am creating a duplicate DB on oracle 10.2.0 on XP on a remote host.
    first host (suman)is source and the second host(sumanr) is target means duplicate. in 2nd host i have installed the oracle software, created the pswd file, pfile, the instance and started in nomount. In 1st host DB is opened and running, now I am trying to connect to the 2nd host instance but getting following error..
    RMAN> connect target
    connected to target database: ORCL (DBID=1255758361)
    RMAN> connect auxiliary sys/oracle@stby
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-04006: error from auxiliary database: ORA-12170: TNS:Connect timeout occurredthe host string 'stby' is to connect to the 2nd host DB.
    I have not mentioned any time out parameter in sqlnet.ora
    Any help will be appreciated
    Rgds

    Always try to clone from Aux instance. as
    rman target sys/****@orcl auxiliary /
    Error:     ORA-12170 (ORA-12170)
    Text:     TNS:Connect timeout occurred
    Cause:     The server shut down because connection establishment with a
         client failed to complete within the allotted time interval. This
         may be a result of network/system delays; or this may indicate
         that a malicious client is trying to cause a Denial of Service
         attack on the server.
    Action:     If the error occurred because of a slow network/system,
         reconfigure the SQLNET.INBOUND_CONNECT_TIMEOUT parameter in
         sqlnet.ora to a larger value. If a malicious client is suspected,
         use the address in sqlnet.log to identify the source and restrict
         access. Note that logged addresses may not be reliable as they can
         be forged (e.g. in TCP/IP).

  • Unable to create auxiliary instance for duplication

    Hi Forum,
    I'm struggling with a problem:
    I'm running a 10g database (10.2) on Windows 2003 server (same problem on Windows XP, though) and plan to duplicate the database to the same server, into the same OraHome. I'm logged on as the local administrator and I'm a member or ORA_DBA user group on that machine.
    As I want to duplicate to the same machine / Ora home I need to create a new Oracle_SID (testdb in my example).
    I added the new Database SID to the listener.ora file using the NetManager and used SID as opposed to SERVICE_NAME to reference the new database because no service for that new database exists.
    I also added an entry to TNSNAMES.ora, although I guess that this is not required for the process.
    I have a password file for the existing database but not for the new database. This to me seemed to be correct as I want to log on using OS-credentials.
    Next, I want to start the instance in NOMOUNT mode. To achieve that, I fire up a command line and write:
    set oracle_sid=testdb
    sqlplus /nologsql> connect / as sysdba
    sql> ERROR:
    TNS-12560: TNS:protocol adapter error
    What am I missing?

    This Windows service is needed to allow automatic database startup/shutdown controlled by the OS. It's a kind of a shell, in which Oracle maintains all database activities on windows, in fact executable 'oracle.exe' is invoked. When you stop this service, database is also shutdown, but the opposite is not true. It is mandatory to have the service running, otherwise you see ORA-12560, a little bit misleading error message.
    You find more information in the platform guide:
    http://download.oracle.com/docs/cd/B19306_01/win.102/b14304/toc.htm
    Werner

  • Auxiliary channel allocation in TSPITR with RMAN-managed instance

    Hi,
    I'm trying do perform TSPITR with RMAN-managed auxiliary instance. All backups are stored on tape. I need to send MML environment values while allocating auxiliary channel to connect to correct NetWorker server and send other NetWorker parameters.
    Unfortunately I have issues with sending these params - I can't send them from recover RUN block, as auxiliary instance does not exists at the time when I'm starting to execute script. (example from test env using disk channels)
    RMAN> RUN
    2> {
    3> ALLOCATE CHANNEL c1 DEVICE TYPE disk;
    4> ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE disk;
    5> SET NEWNAME FOR DATAFILE 1 TO '/u01/backup/tspitr/10gdb2/system01.f';
    6> SET NEWNAME FOR DATAFILE 2 TO '/u01/backup/tspitr/10gdb2/undo01.f';
    7> SET NEWNAME FOR DATAFILE 7 TO '/u01/backup/tspitr/10gdb2/hr_bak01.f';
    8> SET AUXILIARY INSTANCE PARAMETER FILE TO '/home/oracle/params_auxinit.ora';
    9> RECOVER TABLESPACE hr_test UNTIL TIME "SYSDATE - 1/4"
    10> AUXILIARY DESTINATION '/u01/backup/tspitr/10gdb2';
    11> RELEASE CHANNEL c1;
    12> RELEASE CHANNEL aux1;
    13> }
    allocated channel: c1
    channel c1: sid=141 devtype=DISK
    released channel: c1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of allocate command at 04/07/2010 17:21:53
    RMAN-06174: not connected to auxiliary databaseI know I can do it using configure, but is there any way to set this on session level?
    10.2.0.4, RHEL
    Thanks,
    Lukasz

    What can be done here, is to CONFIGURE AUXILIARY CHANNEL to set appropriate params for auxiliary instance (without allocating channels manually).
    I just wanted to know, if I can do it just for this one session (without permanent modification). What I can do, is:
    CONFIGURE AUXILIARY CHANNEL DEVICE TYPE sbt_tape PARMS 'mml settings';
    CONFIGURE CHANNEL DEVICE TYPE sbt_tape PARMS 'mml settings';
    CONFIGURE DEFAULT DEVICE TYPE TO sbt_tape;
    RUN
    (new names, auxiliary parameter file)
    RECOVER TABLESPACE ...
    CONFIGURE AUXILIARY CHANNEL DEVICE TYPE sbt_tape CLEAR;
    CONFIGURE CHANNEL DEVICE TYPE sbt_tape CLEAR;
    CONFIGURE DEFAULT DEVICE TYPE CLEAR;I just wanted more 'elegant' solution.
    Update:
    Due to bug no. 4768353 there is no possibility to use automatic channel allocation in auxiliary instance. Problem resolved by using own customized auxiliary instance started before recovery process. Channels have been allocated manually using ALLOCATE AUXILIARY CHANNEL c1 DEVICE TYPE sbt... on already running aux.
    Thanks,
    Lukasz
    Edited by: Łukasz Mastalerz on Apr 19, 2010 6:47 PM

  • TSPITR - Recover a Dropped Tablespace aborting due dependency over XDB.

    I found an issue using TSPITR to Recover a Dropped Tablespace when XML DB (XDB) is installed on a different tablespace from "SYSAUX".
    During execution of TSPITR RMAN use Data Pump to export/import Tablespace Metadata as Data Pump has dependency over XDB views and related objects and XDB is installed on a set of tablespace not included on dummy database then EXPDP fails.
    Errors raised ORA-39123, ORA-00376, ORA-01110.
    I didn't found any limitation about XDB location on documentation or MoS.
    This looks like a Oracle Bug.
    See this:
    XDB installed on TABLESPACE XDB.
    SQL> select owner,tablespace_name
        from dba_segments
        where owner='XDB'
         GROUP BY owner,tablespace_name ;
    OWNER                          TABLESPACE_NAME
    XDB                            XDBDropping Tablespace SOE.
    SQL> select to_char(sysdate,'dd-mm-yyyy hh24:mi:ss') actual_date from dual;
    ACTUAL_DATE
    17-12-2012 11:57:44
    SQL> drop tablespace SOE including contents and datafiles;
    Tablespace dropped.Restoring Dropped Tablespace.
    RMAN> list backup tag TAG20121217T112226;
    List of Backup Sets
    ===================
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    69      Full    995.61M    DISK        00:02:41     17-12-2012 11:25:07
            BP Key: 69   Status: AVAILABLE  Compressed: YES  Tag: TAG20121217T112226
            Piece Name: +DG_16M/prod/backupset/2012_12_17/nnndf0_tag20121217t112226_0.286.802264947
      List of Datafiles in backup set 69
      File LV Type Ckp SCN    Ckp Time            Name
      1       Full 1628648    17-12-2012 11:22:26 +DS8000_DG/prod/datafile/system.349.799325249
      2       Full 1628648    17-12-2012 11:22:26 +DS8000_DG/prod/datafile/sysaux.348.799325249
      3       Full 1628648    17-12-2012 11:22:26 +DS8000_DG/prod/datafile/undotbs1.347.799325251
      4       Full 1628648    17-12-2012 11:22:26 +DS8000_DG/prod/datafile/users.335.799325251
      5       Full 1628648    17-12-2012 11:22:26 +DS8000_DG/prod/datafile/audit_aux.287.799330083
      6       Full 1628648    17-12-2012 11:22:26
      7       Full 1628648    17-12-2012 11:22:26 +DS8000_DG/prod/datafile/xdb.311.801410833
    RMAN>
    run{
    SET NEWNAME FOR DATAFILE 6 TO "+DS8000_DG";
    RECOVER TABLESPACE SOE
    UNTIL TIME "to_date('17-12-2012 11:55:00','dd/mm/yyyy hh24:mi:ss')"
    AUXILIARY DESTINATION '/u01/app/oracle/flash_recovery_area01/stage_area_tspitr';
    executing command: SET NEWNAME
    Starting recover at 17-12-2012 12:01:29
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=18 device type=DISK
    RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point-in-time
    List of tablespaces expected to have UNDO segments
    Tablespace SYSTEM
    Tablespace UNDOTBS1
    Creating automatic instance, with SID='FCox'
    initialization parameters used for automatic instance:
    db_name=PROD
    db_unique_name=FCox_tspitr_PROD
    compatible=11.2.0.0.0
    db_block_size=8192
    db_files=200
    sga_target=280M
    processes=50
    db_create_file_dest=/u01/app/oracle/flash_recovery_area01/stage_area_tspitr
    log_archive_dest_1='location=/u01/app/oracle/flash_recovery_area01/stage_area_tspitr'
    #No auxiliary parameter file used
    starting up automatic instance PROD
    Oracle instance started
    Total System Global Area     292278272 bytes
    Fixed Size                     2220880 bytes
    Variable Size                109055152 bytes
    Database Buffers             176160768 bytes
    Redo Buffers                   4841472 bytes
    Automatic instance created
    List of tablespaces that have been dropped from the target database:
    Tablespace SOE
    contents of Memory Script:
    # set requested point in time
    set until  time "to_date('17-12-2012 11:55:00','dd/mm/yyyy hh24:mi:ss')";
    # restore the controlfile
    restore clone controlfile;
    # mount the controlfile
    sql clone 'alter database mount clone database';
    # archive current online log
    sql 'alter system archive log current';
    # avoid unnecessary autobackups for structural changes during TSPITR
    sql 'begin dbms_backup_restore.AutoBackupFlag(FALSE); end;';
    executing Memory Script
    executing command: SET until clause
    Starting restore at 17-12-2012 12:01:46
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=16 device type=DISK
    channel ORA_AUX_DISK_1: starting datafile backup set restore
    channel ORA_AUX_DISK_1: restoring control file
    channel ORA_AUX_DISK_1: reading from backup piece +DG_16M/prod/autobackup/2012_12_17/s_802265113.276.802265115
    channel ORA_AUX_DISK_1: piece handle=+DG_16M/prod/autobackup/2012_12_17/s_802265113.276.802265115 tag=TAG20121217T112513
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:05
    output file name=/u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/controlfile/o1_mf_8dy9ghpz_.ctl
    Finished restore at 17-12-2012 12:01:52
    sql statement: alter database mount clone database
    sql statement: alter system archive log current
    sql statement: begin dbms_backup_restore.AutoBackupFlag(FALSE); end;
    contents of Memory Script:
    # set requested point in time
    set until  time "to_date('17-12-2012 11:55:00','dd/mm/yyyy hh24:mi:ss')";
    # set destinations for recovery set and auxiliary set datafiles
    set newname for clone datafile  1 to new;
    set newname for clone datafile  3 to new;
    set newname for clone datafile  2 to new;
    set newname for clone tempfile  1 to new;
    set newname for datafile  6 to
    "+DS8000_DG";
    # switch all tempfiles
    switch clone tempfile all;
    # restore the tablespaces in the recovery set and the auxiliary set
    restore clone datafile  1, 3, 2, 6;
    switch clone datafile all;
    executing Memory Script
    executing command: SET until clause
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    renamed tempfile 1 to /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_temp_%u_.tmp in control file
    Starting restore at 17-12-2012 12:01:58
    using channel ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: starting datafile backup set restore
    channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_AUX_DISK_1: restoring datafile 00001 to /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_system_%u_.dbf
    channel ORA_AUX_DISK_1: restoring datafile 00003 to /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_undotbs1_%u_.dbf
    channel ORA_AUX_DISK_1: restoring datafile 00002 to /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_sysaux_%u_.dbf
    channel ORA_AUX_DISK_1: restoring datafile 00006 to +DS8000_DG
    channel ORA_AUX_DISK_1: reading from backup piece +DG_16M/prod/backupset/2012_12_17/nnndf0_tag20121217t112226_0.286.802264947
    channel ORA_AUX_DISK_1: piece handle=+DG_16M/prod/backupset/2012_12_17/nnndf0_tag20121217t112226_0.286.802264947 tag=TAG20121217T112226
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:09:15
    Finished restore at 17-12-2012 12:11:13
    datafile 6 switched to datafile copy
    input datafile copy RECID=5 STAMP=802267873 file name=+DS8000_DG/prod/datafile/soe.487.802267321
    datafile 1 switched to datafile copy
    input datafile copy RECID=6 STAMP=802267873 file name=/u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_system_8dy9gs09_.dbf
    datafile 3 switched to datafile copy
    input datafile copy RECID=7 STAMP=802267873 file name=/u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_undotbs1_8dy9ov17_.dbf
    datafile 2 switched to datafile copy
    input datafile copy RECID=8 STAMP=802267873 file name=/u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_sysaux_8dy9hxsc_.dbf
    contents of Memory Script:
    # set requested point in time
    set until  time "to_date('17-12-2012 11:55:00','dd/mm/yyyy hh24:mi:ss')";
    # online the datafiles restored or switched
    sql clone "alter database datafile  1 online";
    sql clone "alter database datafile  3 online";
    sql clone "alter database datafile  2 online";
    sql clone "alter database datafile  6 online";
    # recover and open resetlogs
    recover clone database tablespace  "SOE", "SYSTEM", "UNDOTBS1", "SYSAUX" delete archivelog;
    alter clone database open resetlogs;
    executing Memory Script
    executing command: SET until clause
    sql statement: alter database datafile  1 online
    sql statement: alter database datafile  3 online
    sql statement: alter database datafile  2 online
    sql statement: alter database datafile  6 online
    Starting recover at 17-12-2012 12:11:14
    using channel ORA_AUX_DISK_1
    starting media recovery
    archived log for thread 1 with sequence 15 is already on disk as file +DG_16M/prod/archivelog/2012_12_17/thread_1_seq_15.277.802267317
    channel ORA_AUX_DISK_1: starting archived log restore to default destination
    channel ORA_AUX_DISK_1: restoring archived log
    archived log thread=1 sequence=14
    channel ORA_AUX_DISK_1: reading from backup piece +DG_16M/prod/backupset/2012_12_17/annnf0_tag20121217t112512_0.264.802265113
    channel ORA_AUX_DISK_1: piece handle=+DG_16M/prod/backupset/2012_12_17/annnf0_tag20121217t112512_0.264.802265113 tag=TAG20121217T112512
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
    archived log file name=/u01/app/oracle/flash_recovery_area01/stage_area_tspitr/1_14_801941068.dbf thread=1 sequence=14
    channel clone_default: deleting archived log(s)
    archived log file name=/u01/app/oracle/flash_recovery_area01/stage_area_tspitr/1_14_801941068.dbf RECID=141 STAMP=802267877
    archived log file name=+DG_16M/prod/archivelog/2012_12_17/thread_1_seq_15.277.802267317 thread=1 sequence=15
    media recovery complete, elapsed time: 00:00:01
    Finished recover at 17-12-2012 12:11:19
    database opened
    contents of Memory Script:
    # make read only the tablespace that will be exported
    sql clone 'alter tablespace  SOE read only';
    # create directory for datapump import
    sql "create or replace directory TSPITR_DIROBJ_DPDIR as ''
    /u01/app/oracle/flash_recovery_area01/stage_area_tspitr''";
    # create directory for datapump export
    sql clone "create or replace directory TSPITR_DIROBJ_DPDIR as ''
    /u01/app/oracle/flash_recovery_area01/stage_area_tspitr''";
    executing Memory Script
    sql statement: alter tablespace  SOE read only
    sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/u01/app/oracle/flash_recovery_area01/stage_area_tspitr''
    sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/u01/app/oracle/flash_recovery_area01/stage_area_tspitr''
    Performing export of metadata...
       EXPDP> Starting "SYS"."TSPITR_EXP_FCox":
       EXPDP> ORA-39123: Data Pump transportable tablespace job aborted
    ORA-00376: file 7 cannot be read at this time
    ORA-01110: data file 7: '+DS8000_DG/prod/datafile/xdb.311.801410833'
    Removing automatic instance
    shutting down automatic instance
    database closed
    database dismounted
    Oracle instance shut down
    Automatic instance removed
    auxiliary instance file /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_temp_8dyb0qok_.tmp deleted
    auxiliary instance file /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/onlinelog/o1_mf_3_8dyb0kfp_.log deleted
    auxiliary instance file /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/onlinelog/o1_mf_2_8dyb0fm9_.log deleted
    auxiliary instance file /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/onlinelog/o1_mf_1_8dyb07xv_.log deleted
    auxiliary instance file /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_sysaux_8dy9hxsc_.dbf deleted
    auxiliary instance file /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_undotbs1_8dy9ov17_.dbf deleted
    auxiliary instance file /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/datafile/o1_mf_system_8dy9gs09_.dbf deleted
    auxiliary instance file /u01/app/oracle/flash_recovery_area01/stage_area_tspitr/PROD/controlfile/o1_mf_8dy9ghpz_.ctl deleted
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 12/17/2012 12:12:19
    RMAN-06962: Error received during export of metadata
    RMAN-06965: Datapump job has stopped
    RMAN-06960:    EXPDP> Job "SYS"."TSPITR_EXP_FCox" stopped due to fatal error at 12:12:02
    RMAN>If I drop tablespace SOE and XDB on Target database and try to restore both (SOE,XDB) export will succeeds but during IMPORT Metadata RMAN will faill due XDB dependency.
    In my view, they (mean Oracle) need find way to include XDB Tablespace at DUMMY database only to export (EXPDP) Metadata purposes.
    If someone get a workaround for this error will be grateful.
    P.S: This is not a Production environment and will soon open a SR on Oracle Support.

    Hi Michael,
    I did not find solution to use TSPITR to recover dropped tablespace if XML DB is installed in a non-default tablespace (i.e outside of SYSAUX).
    As far I could understand, the only way to perform this RESTORE is using the old fashion. By creating clone database excluding all unnecessary tablespace, exporting and importing metadata from desired tablespace manually.
    Since Oracle has not solved the issue I created my own workaround.
    @All
    If someone is able to use TSPITR to restore dropped tablespace when XDB is installed in a non-default tablespace, please let me know!!!
    The procedure below is supported on All Oracle Version since 10.1 until 11.2.
    I DON'T RECOMMEND to create AUXILIARY (clone) database using the same server from TARGET because you can damage the TARGET database.
    On this example I'm using same server.
    See this example:
    ### ON TARGET DATABASE
    SQL> select count(1) SEG_COUNT from dba_segments where tablespace_name='SOE';
      SEG_COUNT
            32
    SQL> ! date
    Wed Dec 19 15:08:11 GMT-02:00 2012
    SQL> drop tablespace soe including contents and datafiles;
    Tablespace dropped.
    ### CHECK TABLESPACE TO BE EXCLUDED FROM RESTORE
    SQL> select tablespace_name
        from dba_tablespaces
         where tablespace_name not in ('SYSTEM','SYSAUX','UNDOTBS1','SOE','XDB','TEMP');
    TABLESPACE_NAME
    USERS
    AUDIT_AUX
    ### CHECK BACKUP ON TARGET DATABASE
    RMAN> list backup completed between "sysdate-1" and "sysdate";
    List of Backup Sets
    ===================
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    95      Full    986.56M    DISK        00:03:18     19-12-2012 14:41:59
            BP Key: 95   Status: AVAILABLE  Compressed: YES  Tag: TAG20121219T143840
            Piece Name: /fra/PROD/backupset/2012_12_19/o1_mf_nnndf_TAG20121219T143840_8f3vdn3q_.bkp
      List of Datafiles in backup set 95
      File LV Type Ckp SCN    Ckp Time            Name
      1       Full 1675258    19-12-2012 14:38:42 +DS8000_DG/prod/datafile/system.349.799325249
      2       Full 1675258    19-12-2012 14:38:42 +DS8000_DG/prod/datafile/sysaux.348.799325249
      3       Full 1675258    19-12-2012 14:38:42 +DS8000_DG/prod/datafile/undotbs1.347.799325251
      4       Full 1675258    19-12-2012 14:38:42 +DS8000_DG/prod/datafile/users.335.799325251
      5       Full 1675258    19-12-2012 14:38:42 +DS8000_DG/prod/datafile/audit_aux.287.799330083
      6       Full 1675258    19-12-2012 14:38:42
      7       Full 1675258    19-12-2012 14:38:42 +DS8000_DG/prod/datafile/xdb.311.801410833
    BS Key  Size       Device Type Elapsed Time Completion Time
    96      1.16M      DISK        00:00:00     19-12-2012 14:42:08
            BP Key: 96   Status: AVAILABLE  Compressed: YES  Tag: TAG20121219T144208
            Piece Name: /fra/PROD/backupset/2012_12_19/o1_mf_annnn_TAG20121219T144208_8f3vm0k3_.bkp
      List of Archived Logs in backup set 96
      Thrd Seq     Low SCN    Low Time            Next SCN   Next Time
      1    8       1675198    19-12-2012 14:38:25 1675365    19-12-2012 14:42:07
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    97      Full    7.52M      DISK        00:00:02     19-12-2012 14:42:11
            BP Key: 97   Status: AVAILABLE  Compressed: NO  Tag: TAG20121219T144209
            Piece Name: /fra/PROD/autobackup/2012_12_19/o1_mf_s_802449729_8f3vm2cc_.bkp
      SPFILE Included: Modification time: 19-12-2012 14:36:30
      SPFILE db_unique_name: PROD
      Control File Included: Ckp SCN: 1675376      Ckp time: 19-12-2012 14:42:09
    RMAN>
    ### PREPARING ENV
    cp $ORACLE_HOME/dbs/orapwprod $ORACLE_HOME/dbs/orapwtspitr
    cd $ORACLE_HOME/dbs
    ## Creating INIT from TSPITR Instance
    vi inittspitr.ora
    DB_NAME=prod
    DB_UNIQUE_NAME=tspitr
    CONTROL_FILES=/stage_area_tspitr/PROD/controlfile/control01.ctl
    REMOTE_LOGIN_PASSWORDFILE=exclusive
    COMPATIBLE =11.2.0
    DB_BLOCK_SIZE=8192
    memory_target=700M
    streams_pool_size=100M
    ### creating stage area to deploy database
    mkdir -p  /fra/stage_area_tspitr/PROD
    cd /fra/stage_area_tspitr/PROD
    mkdir controlfile datafile onlinelog
    #### RESTORING DATABASE TSPITR
    export ORACLE_SID=tspitr
    $ rman target /
    RMAN> startup nomount
    Oracle instance started
    Total System Global Area     730714112 bytes
    Fixed Size                     2225088 bytes
    Variable Size                553651264 bytes
    Database Buffers             167772160 bytes
    Redo Buffers                   7065600 bytes
    RMAN> restore controlfile from '/fra/PROD/autobackup/2012_12_19/o1_mf_s_802449729_8f3vm2cc_.bkp';
    Starting restore at 19-12-2012 15:16:27
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=146 device type=DISK
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
    output file name=/fra/stage_area_tspitr/PROD/controlfile/control01.ctl
    Finished restore at 19-12-2012 15:16:31
    RMAN> startup mount
    database is already started
    database mounted
    released channel: ORA_DISK_1
    ### REPORT SCHEMA TO GET DATAFILE NUMBER TO BE RESTORED
    RMAN> report schema;
    RMAN-06139: WARNING: control file is not current for REPORT SCHEMA
    Report of database schema for database with db_unique_name TSPITR
    List of Permanent Datafiles
    ===========================
    File Size(MB) Tablespace           RB segs Datafile Name
    1    700      SYSTEM               ***     +DS8000_DG/prod/datafile/system.349.799325249
    2    600      SYSAUX               ***     +DS8000_DG/prod/datafile/sysaux.348.799325249
    3    200      UNDOTBS1             ***     +DS8000_DG/prod/datafile/undotbs1.347.799325251
    4    5        USERS                ***     +DS8000_DG/prod/datafile/users.335.799325251
    5    100      AUDIT_AUX            ***     +DS8000_DG/prod/datafile/audit_aux.287.799330083
    6    0        SOE                  ***     +DS8000_DG/tspitr/datafile/soe.368.802445265
    7    100      XDB                  ***     +DS8000_DG/prod/datafile/xdb.311.801410833
    List of Temporary Files
    =======================
    File Size(MB) Tablespace           Maxsize(MB) Tempfile Name
    1    385      TEMP                 32767       +DS8000_DG/prod/tempfile/temp.300.799325437
    RMAN>
    ### GET LOGFILE NAME to RENAME to new location.
    $ sqlplus / as sysdba
    SQL> select member from v$logfile;
    MEMBER
    +DS8000_DG/prod/onlinelog/group_1.330.802352807
    +DS8000_DG/prod/onlinelog/group_2.331.802352815
    +DS8000_DG/prod/onlinelog/group_3.321.802352821
    run {
    set newname for datafile 1 to '/fra/stage_area_tspitr/PROD/datafile/datafiles_%U';
    set newname for datafile 2 to '/fra/stage_area_tspitr/PROD/datafile/datafiles_%U';
    set newname for datafile 3 to '/fra/stage_area_tspitr/PROD/datafile/datafiles_%U';
    set newname for datafile 7 to '/fra/stage_area_tspitr/PROD/datafile/datafiles_%U';
    set newname for datafile 6 to "+DS8000_DG";
    restore datafile 1,2,3,7,6 from tag 'TAG20121219T143840' ;
    switch datafile 1;
    switch datafile 2;
    switch datafile 3;
    switch datafile 7;
    switch datafile 6;
    switch tempfile all;
    set until time "to_date('19-12-2012 14:42:00','dd-mm-yyyy hh24:mi:ss')";
    recover database SKIP TABLESPACE  "USERS", "AUDIT_AUX" delete archivelog;
    ## Renaming ONLINELOG
    sql "alter database rename file ''+DS8000_DG/prod/onlinelog/group_1.330.802352807'' to ''/fra/stage_area_tspitr/PROD/onlinelog/group1.rdo''";
    sql "alter database rename file ''+DS8000_DG/prod/onlinelog/group_2.331.802352815'' to ''/fra/stage_area_tspitr/PROD/onlinelog/group2.rdo''";
    sql "alter database rename file ''+DS8000_DG/prod/onlinelog/group_3.321.802352821'' to ''/fra/stage_area_tspitr/PROD/onlinelog/group3.rdo''";
    alter database open resetlogs;
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    Starting restore at 19-12-2012 15:32:13
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00001 to /fra/stage_area_tspitr/PROD/datafile/datafiles_data_D-PROD_TS-SYSTEM_FNO-1
    channel ORA_DISK_1: restoring datafile 00002 to /fra/stage_area_tspitr/PROD/datafile/datafiles_data_D-PROD_TS-SYSAUX_FNO-2
    channel ORA_DISK_1: restoring datafile 00003 to /fra/stage_area_tspitr/PROD/datafile/datafiles_data_D-PROD_TS-UNDOTBS1_FNO-3
    channel ORA_DISK_1: restoring datafile 00007 to /fra/stage_area_tspitr/PROD/datafile/datafiles_data_D-PROD_TS-XDB_FNO-7
    channel ORA_DISK_1: restoring datafile 00006 to +DS8000_DG
    channel ORA_DISK_1: reading from backup piece /fra/PROD/backupset/2012_12_19/o1_mf_nnndf_TAG20121219T143840_8f3vdn3q_.bkp
    channel ORA_DISK_1: piece handle=/fra/PROD/backupset/2012_12_19/o1_mf_nnndf_TAG20121219T143840_8f3vdn3q_.bkp tag=TAG20121219T143840
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:12:35
    Finished restore at 19-12-2012 15:44:48
    datafile 1 switched to datafile copy
    input datafile copy RECID=6 STAMP=802453489 file name=/fra/stage_area_tspitr/PROD/datafile/datafiles_data_D-PROD_TS-SYSTEM_FNO-1
    datafile 2 switched to datafile copy
    input datafile copy RECID=8 STAMP=802453489 file name=/fra/stage_area_tspitr/PROD/datafile/datafiles_data_D-PROD_TS-SYSAUX_FNO-2
    datafile 3 switched to datafile copy
    input datafile copy RECID=10 STAMP=802453489 file name=/fra/stage_area_tspitr/PROD/datafile/datafiles_data_D-PROD_TS-UNDOTBS1_FNO-3
    datafile 7 switched to datafile copy
    input datafile copy RECID=12 STAMP=802453489 file name=/fra/stage_area_tspitr/PROD/datafile/datafiles_data_D-PROD_TS-XDB_FNO-7
    datafile 6 switched to datafile copy
    input datafile copy RECID=14 STAMP=802453489 file name=+DS8000_DG/tspitr/datafile/soe.304.802452733
    renamed tempfile 1 to /fra/stage_area_tspitr/PROD/datafile/datafiles_data_D-PROD_TS-TEMP_FNO-1 in control file
    executing command: SET until clause
    Starting recover at 19-12-2012 15:44:49
    using channel ORA_DISK_1
    Executing: alter database datafile 4 offline
    Executing: alter database datafile 5 offline
    starting media recovery
    archived log for thread 1 with sequence 8 is already on disk as file +DS8000_DG/prod/onlinelog/group_2.331.802352815
    archived log file name=+DS8000_DG/prod/onlinelog/group_2.331.802352815 thread=1 sequence=8
    media recovery complete, elapsed time: 00:00:02
    Finished recover at 19-12-2012 15:44:55
    sql statement: alter database rename file ''+DS8000_DG/prod/onlinelog/group_1.330.802352807'' to ''/fra/stage_area_tspitr/PROD/onlinelog/group1.rdo''
    sql statement: alter database rename file ''+DS8000_DG/prod/onlinelog/group_2.331.802352815'' to ''/fra/stage_area_tspitr/PROD/onlinelog/group2.rdo''
    sql statement: alter database rename file ''+DS8000_DG/prod/onlinelog/group_3.321.802352821'' to ''/fra/stage_area_tspitr/PROD/onlinelog/group3.rdo''
    database opened
    ## Exporting Tablespace Metadata
    RMAN >
    run {
    sql 'alter tablespace  SOE read only';
    # create directory for datapump export
    sql  "create or replace directory TSPITR_DIROBJ_DPDIR as ''/fra/stage_area_tspitr''";
    # grant on directory to SYSTEM
    sql "grant read,write on directory TSPITR_DIROBJ_DPDIR to system";
    # exporting metadata
    host "expdp system/oracle@localhost:1521/tspitr DIRECTORY=TSPITR_DIROBJ_DPDIR DUMPFILE=exp_transport_soe.dmp TRANSPORT_FULL_CHECK=Y TRANSPORT_TABLESPACES=SOE";
    using target database control file instead of recovery catalog
    sql statement: alter tablespace  SOE read only
    sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/fra/stage_area_tspitr''
    sql statement: grant read,write on directory TSPITR_DIROBJ_DPDIR to system
    Export: Release 11.2.0.3.0 - Production on Wed Dec 19 15:53:02 2012
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, Automatic Storage Management, Oracle Label Security, OLAP,
    Data Mining, Oracle Database Vault and Real Application Testing options
    Starting "SYSTEM"."SYS_EXPORT_TRANSPORTABLE_01":  system/********@localhost:1521/tspitr DIRECTORY=TSPITR_DIROBJ_DPDIR DUMPFILE=exp_transport_soe.dmp TRANSPORT_FULL_CHECK=Y TRANSPORT_TABLESPACES=SOE
    Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
    Processing object type TRANSPORTABLE_EXPORT/TABLE
    Processing object type TRANSPORTABLE_EXPORT/INDEX/INDEX
    Processing object type TRANSPORTABLE_EXPORT/INDEX/FUNCTIONAL_INDEX/INDEX
    Processing object type TRANSPORTABLE_EXPORT/CONSTRAINT/CONSTRAINT
    Processing object type TRANSPORTABLE_EXPORT/INDEX_STATISTICS
    Processing object type TRANSPORTABLE_EXPORT/INDEX/STATISTICS/FUNCTIONAL_INDEX/INDEX_STATISTICS
    Processing object type TRANSPORTABLE_EXPORT/CONSTRAINT/REF_CONSTRAINT
    Processing object type TRANSPORTABLE_EXPORT/TABLE_STATISTICS
    Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PLUGTS_BLK
    Master table "SYSTEM"."SYS_EXPORT_TRANSPORTABLE_01" successfully loaded/unloaded
    Dump file set for SYSTEM.SYS_EXPORT_TRANSPORTABLE_01 is:
      /fra/stage_area_tspitr/exp_transport_soe.dmp
    Datafiles required for transportable tablespace SOE:
      +DS8000_DG/tspitr/datafile/soe.304.802452733
    Job "SYSTEM"."SYS_EXPORT_TRANSPORTABLE_01" successfully completed at 15:54:28
    host command complete
    ## Stop Database and destroy it to make sure that Datafile 6 will not be used by this database;
    RMAN>
    run {
    shutdown immediate;
    ## removing controlfile and SYSTEM Tablespace to make sure that database will not be opened
    host "rm -f /fra/stage_area_tspitr/PROD/controlfile/control01.ctl /fra/stage_area_tspitr/PROD/datafile/datafiles_data_D-PROD_TS-SYSTEM_FNO-1";
    database closed
    database dismounted
    Oracle instance shut down
    host command complete
    ## TARGET Database
    ## Plugging Tablespace on TARGET database.
    $ export ORACLE_SID=prod
    $ rman target /
    run {
    # create directory for datapump import
    sql "create or replace directory TSPITR_DIROBJ_DPDIR as ''/fra/stage_area_tspitr''";
    # grant on directory to SYSTEM
    sql "grant read,write on directory TSPITR_DIROBJ_DPDIR to system";
    host "impdp system/oracle@localhost:1521/prod DIRECTORY=TSPITR_DIROBJ_DPDIR DUMPFILE=exp_transport_soe.dmp TRANSPORT_DATAFILES=''+DS8000_DG/tspitr/datafile/soe.304.802452733''";
    sql "alter tablespace soe read write";
    sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/fra/stage_area_tspitr''
    sql statement: grant read,write on directory TSPITR_DIROBJ_DPDIR to system
    Import: Release 11.2.0.3.0 - Production on Wed Dec 19 16:09:30 2012
    Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.
    Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, Automatic Storage Management, Oracle Label Security, OLAP,
    Data Mining, Oracle Database Vault and Real Application Testing options
    Master table "SYSTEM"."SYS_IMPORT_TRANSPORTABLE_01" successfully loaded/unloaded
    Starting "SYSTEM"."SYS_IMPORT_TRANSPORTABLE_01":  system/********@localhost:1521/prod DIRECTORY=TSPITR_DIROBJ_DPDIR DUMPFILE=exp_transport_soe.dmp TRANSPORT_DATAFILES=+DS8000_DG/tspitr/datafile/soe.304.802452733
    Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
    Processing object type TRANSPORTABLE_EXPORT/TABLE
    Processing object type TRANSPORTABLE_EXPORT/INDEX/INDEX
    Processing object type TRANSPORTABLE_EXPORT/INDEX/FUNCTIONAL_INDEX/INDEX
    Processing object type TRANSPORTABLE_EXPORT/CONSTRAINT/CONSTRAINT
    Processing object type TRANSPORTABLE_EXPORT/INDEX_STATISTICS
    Processing object type TRANSPORTABLE_EXPORT/INDEX/STATISTICS/FUNCTIONAL_INDEX/INDEX_STATISTICS
    Processing object type TRANSPORTABLE_EXPORT/CONSTRAINT/REF_CONSTRAINT
    Processing object type TRANSPORTABLE_EXPORT/TABLE_STATISTICS
    Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PLUGTS_BLK
    Job "SYSTEM"."SYS_IMPORT_TRANSPORTABLE_01" successfully completed at 16:10:03
    host command complete
    sql statement: alter tablespace soe read write
    ### Recompiling Invalid Objects and Checking objects from  tablespace SOE
    $ sqlplus / as sysdba
    SQL>  @$ORACLE_HOME/rdbms/admin/utlrp.sql
    TIMESTAMP
    COMP_TIMESTAMP UTLRP_BGN  2012-12-19 16:10:34
    OBJECTS WITH ERRORS
                      0
    ERRORS DURING RECOMPILATION
                              0
    Function created.
    PL/SQL procedure successfully completed.
    Function dropped.
    PL/SQL procedure successfully completed.
    SQL> select count(1) SEG_COUNT from dba_segments where tablespace_name='SOE';
      SEG_COUNT
            32
    SQL> SELECT COUNT(1) OBJ_INVALID FROM DBA_OBJECTS WHERE STATUS != 'VALID';
    OBJ_INVALID
              0
    ## PERFORM A FULL BACKUP AFTER RESTORE TABLESPACE.Regards,
    Levi Pereira

  • Restore using TSPITR Results  Dead lock error

    This is the step is followed but i am getting deadlock error .please give your valuable suggestion .
    Product Used:oracle 11g in linux environmnet
    1)Before taking backup get SCN number for restore.
    Command applied: Select current_scn from v$database;
    2)running Full backup of database
    Command applied:
    configure controlfile autobackup on;
    backup database;
    CROSSCHECK BACKUP;
    exit;
    3)Running level 0 incremental backup
    Command applied:
    BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 0 TAG ='WEEKLY' TABLESPACE TEST;
    exit;
    3) Running level 1 incremental backup
    Command applied:
    BACKUP AS COMPRESSED BACKUPSET INCREMENTAL LEVEL 1 TAG ='DAILY' TABLESPACE TEST;
    4)Before Restore(TSPITR) following procedure are applied under sysdba privilege
    Command applied:
    SQL 'exec dbms_backup_restore.manageauxinstance ('TSPITR',1)';
    5)TSPITR Restore command
    Command applied:
    run
    SQL 'ALTER TABLESPACE TEST OFFLINE'
    RECOVER TABLESPACE TEST UNTIL SCN 1791053 AUXILIARY DESTINATION '/opt/oracle/base/flash_recovery_area';
    SQL 'ALTER TABLESPACE TEST ONLINE';
    and i tried with this option also(the same error i was getting)
    Command applied:
    run
    SQL 'ALTER TABLESPACE TEST OFFLINE';
    SET UNTIL SCN 1912813;
    RESTORE TABLESPACE TEST ;
    RECOVER TABLESPACE TEST UNTIL SCN 1912813 AUXILIARY DESTINATION '/opt/oracle/base/flash_recovery_area';
    SQL 'ALTER TABLESPACE TEST ONLINE';
    The follwing error i get for above mentioned restore command
    Recovery Manager: Release 11.2.0.1.0 - Production on Tue Aug 17 18:11:18 2010
    Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
    connected to target database: NEW10 (DBID=2860680927)
    RMAN> run
    2> {
    3> SQL 'ALTER TABLESPACE TEST OFFLINE';
    4> RECOVER TABLESPACE TEST UNTIL SCN 1791053 AUXILIARY DESTINATION '/opt/oracle/base/flash_recovery_area';
    5> SQL 'ALTER TABLESPACE TEST ONLINE';
    6> }
    7>
    using target database control file instead of recovery catalog
    sql statement: ALTER TABLESPACE TEST OFFLINE
    Starting recover at 17-AUG-10
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=404 device type=DISK
    RMAN-05026: WARNING: presuming following set of tablespaces applies to specified point-in-time
    List of tablespaces expected to have UNDO segments
    Tablespace SYSTEM
    Tablespace UNDOTBS1
    Creating automatic instance, with SID='BkAq'
    initialization parameters used for automatic instance:
    db_name=NEW10
    db_unique_name=BkAq_tspitr_NEW10
    compatible=11.2.0.0.0
    db_block_size=8192
    db_files=200
    sga_target=280M
    processes=50
    db_create_file_dest=/opt/oracle/base/flash_recovery_area
    log_archive_dest_1='location=/opt/oracle/base/flash_recovery_area'
    #No auxiliary parameter file used
    starting up automatic instance NEW10
    Oracle instance started
    Total System Global Area 292933632 bytes
    Fixed Size 1336092 bytes
    Variable Size 100666596 bytes
    Database Buffers 184549376 bytes
    Redo Buffers 6381568 bytes
    Automatic instance created
    Running TRANSPORT_SET_CHECK on recovery set tablespaces
    TRANSPORT_SET_CHECK completed successfully
    contents of Memory Script:
    # set requested point in time
    set until scn 1791053;
    # restore the controlfile
    restore clone controlfile;
    # mount the controlfile
    sql clone 'alter database mount clone database';
    # archive current online log
    sql 'alter system archive log current';
    # avoid unnecessary autobackups for structural changes during TSPITR
    sql 'begin dbms_backup_restore.AutoBackupFlag(FALSE); end;';
    executing Memory Script
    executing command: SET until clause
    Starting restore at 17-AUG-10
    allocated channel: ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: SID=59 device type=DISK
    channel ORA_AUX_DISK_1: starting datafile backup set restore
    channel ORA_AUX_DISK_1: restoring control file
    channel ORA_AUX_DISK_1: reading from backup piece /opt/oracle/base/flash_recovery_area/NEW10/autobackup/2010_08_17/o1_mf_s_727280767_66nmo8x7_.bkp
    channel ORA_AUX_DISK_1: piece handle=/opt/oracle/base/flash_recovery_area/NEW10/autobackup/2010_08_17/o1_mf_s_727280767_66nmo8x7_.bkp tag=TAG20100817T142607
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
    output file name=/opt/oracle/base/flash_recovery_area/NEW10/controlfile/o1_mf_66o0wsh8_.ctl
    Finished restore at 17-AUG-10
    sql statement: alter database mount clone database
    sql statement: alter system archive log current
    sql statement: begin dbms_backup_restore.AutoBackupFlag(FALSE); end;
    contents of Memory Script:
    # set requested point in time
    set until scn 1791053;
    # set destinations for recovery set and auxiliary set datafiles
    set newname for clone datafile 1 to new;
    set newname for clone datafile 8 to new;
    set newname for clone datafile 3 to new;
    set newname for clone datafile 2 to new;
    set newname for clone datafile 9 to new;
    set newname for clone tempfile 1 to new;
    set newname for datafile 7 to
    "/opt/oracle/base/oradata/NEW10/test01.dbf";
    # switch all tempfiles
    switch clone tempfile all;
    # restore the tablespaces in the recovery set and the auxiliary set
    restore clone datafile 1, 8, 3, 2, 9, 7;
    switch clone datafile all;
    executing Memory Script
    executing command: SET until clause
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    executing command: SET NEWNAME
    renamed tempfile 1 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_temp_%u_.tmp in control file
    Starting restore at 17-AUG-10
    using channel ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: starting datafile backup set restore
    channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_AUX_DISK_1: restoring datafile 00001 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_%u_.dbf
    channel ORA_AUX_DISK_1: restoring datafile 00008 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_%u_.dbf
    channel ORA_AUX_DISK_1: restoring datafile 00003 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_undotbs1_%u_.dbf
    channel ORA_AUX_DISK_1: restoring datafile 00002 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_%u_.dbf
    channel ORA_AUX_DISK_1: restoring datafile 00009 to /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_%u_.dbf
    channel ORA_AUX_DISK_1: reading from backup piece /opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnndf_TAG20100817T140128_66nl7174_.bkp
    channel ORA_AUX_DISK_1: piece handle=/opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnndf_TAG20100817T140128_66nl7174_.bkp tag=TAG20100817T140128
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:02:45
    channel ORA_AUX_DISK_1: starting datafile backup set restore
    channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_AUX_DISK_1: restoring datafile 00007 to /opt/oracle/base/oradata/NEW10/test01.dbf
    channel ORA_AUX_DISK_1: reading from backup piece /opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnnd0_WEEKLY_66nl9m8k_.bkp
    channel ORA_AUX_DISK_1: piece handle=/opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnnd0_WEEKLY_66nl9m8k_.bkp tag=WEEKLY
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:06:55
    Finished restore at 17-AUG-10
    datafile 1 switched to datafile copy
    input datafile copy RECID=6 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_66o0x1sf_.dbf
    datafile 8 switched to datafile copy
    input datafile copy RECID=7 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_66o0x1r9_.dbf
    datafile 3 switched to datafile copy
    input datafile copy RECID=8 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_undotbs1_66o0x1vr_.dbf
    datafile 2 switched to datafile copy
    input datafile copy RECID=9 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_66o0x1vj_.dbf
    datafile 9 switched to datafile copy
    input datafile copy RECID=10 STAMP=727294911 file name=/opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_66o0x1rs_.dbf
    contents of Memory Script:
    # set requested point in time
    set until scn 1791053;
    # online the datafiles restored or switched
    sql clone "alter database datafile 1 online";
    sql clone "alter database datafile 8 online";
    sql clone "alter database datafile 3 online";
    sql clone "alter database datafile 2 online";
    sql clone "alter database datafile 9 online";
    sql clone "alter database datafile 7 online";
    # recover and open resetlogs
    recover clone database tablespace "TEST", "SYSTEM", "UNDOTBS1", "SYSAUX" delete archivelog;
    alter clone database open resetlogs;
    executing Memory Script
    executing command: SET until clause
    sql statement: alter database datafile 1 online
    sql statement: alter database datafile 8 online
    sql statement: alter database datafile 3 online
    sql statement: alter database datafile 2 online
    sql statement: alter database datafile 9 online
    sql statement: alter database datafile 7 online
    Starting recover at 17-AUG-10
    using channel ORA_AUX_DISK_1
    channel ORA_AUX_DISK_1: starting incremental datafile backup set restore
    channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
    destination for restore of datafile 00007: /opt/oracle/base/oradata/NEW10/test01.dbf
    channel ORA_AUX_DISK_1: reading from backup piece /opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnnd1_DAILY_66nmf6qs_.bkp
    channel ORA_AUX_DISK_1: piece handle=/opt/oracle/base/flash_recovery_area/NEW10/backupset/2010_08_17/o1_mf_nnnd1_DAILY_66nmf6qs_.bkp tag=DAILY
    channel ORA_AUX_DISK_1: restored backup piece 1
    channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
    starting media recovery
    archived log for thread 1 with sequence 39 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_39_66nmc1dg_.arc
    archived log for thread 1 with sequence 40 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_40_66nmcfw4_.arc
    archived log for thread 1 with sequence 41 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_41_66nmcwcf_.arc
    archived log for thread 1 with sequence 42 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_42_66nmddbw_.arc
    archived log for thread 1 with sequence 43 is already on disk as file /opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_43_66o0wyys_.arc
    archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_39_66nmc1dg_.arc thread=1 sequence=39
    archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_40_66nmcfw4_.arc thread=1 sequence=40
    archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_41_66nmcwcf_.arc thread=1 sequence=41
    archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_42_66nmddbw_.arc thread=1 sequence=42
    archived log file name=/opt/oracle/base/flash_recovery_area/NEW10/archivelog/2010_08_17/o1_mf_1_43_66o0wyys_.arc thread=1 sequence=43
    media recovery complete, elapsed time: 00:00:50
    Finished recover at 17-AUG-10
    database opened
    contents of Memory Script:
    # make read only the tablespace that will be exported
    sql clone 'alter tablespace TEST read only';
    # create directory for datapump import
    sql "create or replace directory TSPITR_DIROBJ_DPDIR as ''
    /opt/oracle/base/flash_recovery_area''";
    # create directory for datapump export
    sql clone "create or replace directory TSPITR_DIROBJ_DPDIR as ''
    /opt/oracle/base/flash_recovery_area''";
    executing Memory Script
    sql statement: alter tablespace TEST read only
    sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/opt/oracle/base/flash_recovery_area''
    sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''/opt/oracle/base/flash_recovery_area''
    Performing export of metadata...
    EXPDP> Starting "SYS"."TSPITR_EXP_BkAq":
    EXPDP> Processing object type TRANSPORTABLE_EXPORT/PLUGTS_BLK
    EXPDP> Processing object type TRANSPORTABLE_EXPORT/TABLE
    EXPDP> Processing object type TRANSPORTABLE_EXPORT/GRANT/OWNER_GRANT/OBJECT_GRANT
    EXPDP> Processing object type TRANSPORTABLE_EXPORT/INDEX
    EXPDP> Processing object type TRANSPORTABLE_EXPORT/CONSTRAINT/CONSTRAINT
    EXPDP> Processing object type TRANSPORTABLE_EXPORT/INDEX_STATISTICS
    EXPDP> Processing object type TRANSPORTABLE_EXPORT/TRIGGER
    EXPDP> Processing object type TRANSPORTABLE_EXPORT/TABLE_STATISTICS
    EXPDP> Processing object type TRANSPORTABLE_EXPORT/POST_INSTANCE/PLUGTS_BLK
    EXPDP> Master table "SYS"."TSPITR_EXP_BkAq" successfully loaded/unloaded
    EXPDP> ******************************************************************************
    EXPDP> Dump file set for SYS.TSPITR_EXP_BkAq is:
    EXPDP> /opt/oracle/base/flash_recovery_area/tspitr_BkAq_82690.dmp
    EXPDP> ******************************************************************************
    EXPDP> Datafiles required for transportable tablespace TEST:
    EXPDP> /opt/oracle/base/oradata/NEW10/test01.dbf
    EXPDP> Job "SYS"."TSPITR_EXP_BkAq" successfully completed at 18:25:02
    Export completed
    contents of Memory Script:
    # shutdown clone before import
    shutdown clone immediate
    # drop target tablespaces before importing them back
    sql 'drop tablespace TEST including contents keep datafiles';
    executing Memory Script
    database closed
    database dismounted
    Oracle instance shut down
    sql statement: drop tablespace TEST including contents keep datafiles
    Removing automatic instance
    shutting down automatic instance
    target database instance not started
    Automatic instance removed
    auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_temp_66o1k480_.tmp deleted
    auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/onlinelog/o1_mf_3_66o1k0mg_.log deleted
    auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/onlinelog/o1_mf_2_66o1jyt4_.log deleted
    auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/onlinelog/o1_mf_1_66o1jx3w_.log deleted
    auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_66o0x1rs_.dbf deleted
    auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_sysaux_66o0x1vj_.dbf deleted
    auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_undotbs1_66o0x1vr_.dbf deleted
    auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_66o0x1r9_.dbf deleted
    auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/datafile/o1_mf_system_66o0x1sf_.dbf deleted
    auxiliary instance file /opt/oracle/base/flash_recovery_area/NEW10/controlfile/o1_mf_66o0wsh8_.ctl deleted
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 08/17/2010 18:25:36
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-03009: failure of sql command on default channel at 08/17/2010 18:25:25
    RMAN-11003: failure during parse/execution of SQL statement: drop tablespace TEST including contents keep datafiles
    ORA-00604: error occurred at recursive SQL level 1
    ORA-00060: deadlock detected while waiting for resource
    Recovery Manager complete.
    please give your valuable suggestion .It should be more helpful for us.
    Edited by: user10750009 on Aug 20, 2010 1:07 AM
    Edited by: user10750009 on Aug 20, 2010 1:15 AM

    I want TSPITR ,during this operation i faced this deadlock error.
    Before that we faced roll backsegment error for that we applied follwing workaround .
    If i applied follwing workaround before every backup and restore .i didn't get any error .all things went successful.
    spool /tmp/Createtest.log
    connect / as sysdba
    REM Perform startup in case we are still down
    ALTER SYSTEM SET PROCESSES=500 SCOPE=SPFILE;
    SHUT IMMEDIATE;
    STARTUP MOUNT EXCLUSIVE;
    ALTER DATABASE ARCHIVELOG;
    ARCHIVE LOG START;
    ALTER DATABASE OPEN;
    connECT / as sysdba;
    alter system set undo_management = MANUAL scope=spfile;
    shutdown immediate;
    startup;
    Connect / as sysdba;
    DROP TABLE TEST123;
    create table test123 (t1 number, t2 varchar2(10));
    begin
    for i in 1.. 300000 loop
    insert into test values (i,'AAAAAAAAAA');
    end loop;
    end;
    delete test123;
    commit;
    alter system set undo_management = auto scope=spfile;
    shutdown immediate ;
    startup ;
    The above workaround we applied before creating tablespace and datafile ,after that we face some dead lock error while restore TSPITR .Did you need any more information
    Edited by: user10750009 on Aug 20, 2010 1:12 AM

  • Restore just one table into new instance

    Hello
    We need to know the content of a table 10 days ago. To not affect the database (80GB) itself, our idea was
    a) to setup an auxiliary instance
    b) to restore/recover the instance into the aux
    c) voilà: table can be accessed.
    Is there maybe a more simpler (and not that space consuming) way via
    a) transportable tablespace
    b) "transportable table"
    c) table restore into aux
    d) ???
    btw: RMAN settings are fine, Backup is on tape, restore/recover is possible... :-)
    Thanks for your suggestions Casi

    It would be easier to answer such questions,if you wouldn't hide your database version. Because of 'Transportable Tablespaces' it seems to be higher than Oracle 6.
    TSPITR (Tablespace Point-in-Time Recovery) seems to be the most appropriate way, it uses transportable tablespaces in the background. No need to restore a whole database in such a case.
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/rcmtspit.htm#i1014116
    Werner

  • TSPITR using backups from standby

    Hi,
    I would like to ask for your opinion/advice regarding the following
    scenario. We have a primary 10.2.0.3 RAC database which has a physical
    standby database, both sites being managed through dataguard. Every
    night full RMAN backups are taken for the primary and standby
    databases. Between the primary and standby sites we do not have any
    shared storage like NFS or SAMBA (because of the problems mentioned
    into Note:413098.1).
    Now, as far as I know, backups of datafiles/archives taken from the
    standby can be used on primary, am I right? So, what I would like to
    achieve is to perform a TSPITR of one particular tablespace by taking
    a backup control file from the primary but using datafile copies and
    archives from the standby. And of course, because I don't want to load
    too much the primary, the auxiliary instance should be located on the
    standby machine. Is this possible? Has anybody tried this before?
    Many thanks!
    talek.

    if you are on 10.2.0.3, check this document and make use of Incrementally Updated Backups: Rolling Forward Image Copy Backup
    http://download-east.oracle.com/docs/cd/B19306_01/backup.102/b14192/bkup004.htm
    You can restore datafiles backedup from physical standby
    can restore archivelogs created on physical standby
    but can not use control file from standby to recover on primary
    You should be able to use bakcup from a physical standby and recover any tablespace in Point In Time on priamry prvovided you have a backup/datafile copy before and archives untill that time.

  • TSPITR to another DB...possible?

    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.

    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.

Maybe you are looking for

  • Credit Limit based on customer and material?

    Hello Gurus, I've 2 diff types of goods.. 1) fast moving/ selling goods 2) slow moving goods. For a particular customer, I've assigned certain credit limit of say 10,000 EUR via FD32. My question is, for the slow moving goods or one particular materi

  • Caching in SAP Wdget foundation

    Hi, Can i do caching in SAP Widget Foundation...? or How to develop a data caching widget..? Thanks in advance John Edited by: john paul on Apr 22, 2009 8:00 AM

  • Possible to edit without the main.fla file?

    About 10 days ago I purchased a flash template for my photography business. At the time I knew zilch about flash and actionscript, so I wasn't totally aware of what to look for before purchasing it. Here is what it looks like dcpphotographer.com My p

  • Why Free Hand software stopped?

    I'm a senior graphic designer and I work in a cosmetics company. I work using many Graphic software like (Adobe photoshop, InDesign, Audition, Illustrator and 3Ds max, 3D Maya ... etc.) on Mac OS and Windows. My problem that I was work using (Macrome

  • Non system or disc error

    when I start my hp compaq 6230 I get the message "fixed disc parameter task or Bios error.  System Halted. The only other message I get after startup is "non system disc or disc error. Replace and strike any key" The only function key that works is F