Confusion about recovery from tag

Hi All,
We had a situation where we need to restore and recover to point in time until 24th June. One of our colleagues at first restored the controlfile from 24th June backup using below script..
run
ALLOCATE CHANNEL c1 DEVICE TYPE SBT_TAPE PARMS 'ENV=(NB_ORA_SERV=masterhp003.xxxxx.com,NB_ORA_POLICY=ora_pacerprd01_pacerprd,NB_ORA_CLIENT=orasalxhp603),BLKSIZE=524288';
restore controlfile from 'TAG20130624T004158';
release channel c1;
After that he executed the below script to recover the database.
run
ALLOCATE CHANNEL c1 DEVICE TYPE SBT_TAPE PARMS 'ENV=(NB_ORA_SERV=masterhp003.xxxxx.com,NB_ORA_POLICY=ora_pacerprd01_pacerprd,NB_ORA_CLIENT=orasalxhp603),BLKSIZE=524288';
ALLOCATE CHANNEL c2 DEVICE TYPE SBT_TAPE PARMS 'ENV=(NB_ORA_SERV=masterhp003.xxxxx.com,NB_ORA_POLICY=ora_pacerprd01_pacerprd,NB_ORA_CLIENT=orasalxhp603),BLKSIZE=524288';
ALLOCATE CHANNEL c3 DEVICE TYPE SBT_TAPE PARMS 'ENV=(NB_ORA_SERV=masterhp003.thehartford.com,NB_ORA_POLICY=ora_pacerprd01_pacerprd,NB_ORA_CLIENT=orasalxhp603),BLKSIZE=524288';
ALLOCATE CHANNEL c4 DEVICE TYPE SBT_TAPE PARMS 'ENV=(NB_ORA_SERV=masterhp003.xxxxx.com,NB_ORA_POLICY=ora_pacerprd01_pacerprd,NB_ORA_CLIENT=orasalxhp603),BLKSIZE=524288';
set newname for datafile 1 TO '/asj_pacerqa/data01/pacerqa/datafile/system01.dbf';
set newname for datafile 2 TO 'asj_pacerqa/data01/pacerqa/datafile/sysaux01.dbf';
set newname for datafile 3 TO '/asj_pacerqa/data01/pacerqa/datafile/undotbs01.dbf';
set newname for datafile 4 TO '/asj_pacerqa/data01/pacerqa/datafile/users01.dbf';
set newname for datafile 5 TO '/asj_pacerqa/data01/pacerqa/datafile/base_idx_256k_0101.dbf';
set newname for datafile 6 TO '/asj_pacerqa/data01/pacerqa/datafile/base_idx_6400k_0101.dbf';
set newname for datafile 7 TO '/asj_pacerqa/data01/pacerqa/datafile/base_idx_6400k_0201.dbf';
set newname for datafile 8 TO '/asj_pacerqa/data01/pacerqa/datafile/base_idx_64k_0101.dbf';
set newname for datafile 9 TO '/asj_pacerqa/data01/pacerqa/datafile/base_idx_64k_0201.dbf';
set newname for datafile 10 TO '/asj_pacerqa/data01/pacerqa/datafile/base_tbl_256k_0101.dbf';
set newname for datafile 11 TO '/asj_pacerqa/data01/pacerqa/datafile/base_tbl_6400k_0101.dbf';
set newname for datafile 12 TO '/asj_pacerqa/data01/pacerqa/datafile/base_tbl_6400k_0201.dbf';
set newname for datafile 13 TO '/asj_pacerqa/data01/pacerqa/datafile/base_tbl_64k_0101.dbf';
set newname for datafile 14 TO '/asj_pacerqa/data01/pacerqa/datafile/base_tbl_64k_0201.dbf';
restore database from tag 'PACERPRD_LEVEL0_174_24';
switch datafile all;
recover database;
release channel c1;
release channel c2;
release channel c3;
release channel c4;
The tag 'PACERPRD_LEVEL0_174_24' was also from 24th datafile backup.
Please suggest whether the database was restored until 24th or it was restored to the current data.Please help us to understand.

If you would look up the recover database command in the online documentation,
you would notice the following
nowhere in your code you restored the controlfile, so you are using the current controlfile
nowhere in your code you are using 'set until' and you are not using the 'until clause' of the recover database command
This means you performed complete recovery, until now.
Please spend a bit of time to read the documentation and to understand what they are taking about.
Sybrand Bakker
Senior Oracle DBA

Similar Messages

  • Confusion about recovery

    Hi ,
    I am new to the DBA field and I have a confusion about recovery.
    The confusion is if a database is in noarchivelog mode can a database be recovered from commited changes that were there in the redo log files ?
    If I provide the path name of the redo log files while using recover database using cancel will it work at all given that the database is in noarchivelog mode ?
    Please help to clear my doubts..

    Oracle can use the Online Redo Logs for Recovery. Normally this happens in the case of Instance Recovery (e.g. from a server crash or shutdown abort) -- where the datafiles are not restored from a prior backup.
    If you restore datafiles from a prior backup, you are doing a media recovery. In NOARCHIVELOG mode, you could not have run a backup with the database OPEN, so the backup would have been run with the database SHUTDOWN or MOUNTed. At the subsequent startup, transactions would be in the online redo logs only until LGWR does a "wrap around" and overwrites the first redo log used after the startup. It is only within this window that transactions are in the redo logs.+
    Remember that LGWR uses a "round-robin" algorithm to cycle through the online redo logs. So, if the Online Redo Log that was CURRENT at the time of the backup has been overwritten, you cannot use the Online Redo Logs for a RECOVERy+._
    You must also ensure that there are no NOLOGGING operations !!
    One thing that you might trip up on is the behaviour of CTAS. A "CREATE TABLE AS SELECT" is, by default LOGGING in an ARCHIVELOG database. However, it is automatically a Direct Path operation in a NOARCHIVELOG database ! So the blocks for such a table would be "corrupt" if you attempt a recovery from the Online Redo Log as the row inserts are not captured.
    Hemant K Chitale
    Edited by: Hemant K Chitale on Oct 10, 2011 11:43 AM
    Edited by: Hemant K Chitale on Oct 10, 2011 11:44 AM
    Edited by: Hemant K Chitale on Oct 10, 2011 4:33 PM
    Edited by: Hemant K Chitale on Oct 10, 2011 4:34 PM

  • Confused about transition from MobileMe

    Up until now I actually have been happy with MobileMe.  But I wanted to transition to iCloud since MobileMe will shut down at the end of June.
    So today, I started the transition to iCloud.  However, I am confused about how to set up all the devices we used to use on MobileMe.  Before our family shared five computers, three iPhones, one iPod Touch and 2 iPads.  Under MobileMe, we were able to all share the calendars and contacts.  Now I have no idea how to have multiple devices share calendars and contacts.  Each person in my family has their own separate Apple ID.  Is there a way that multiple Apple ID's can share on iCloud account?  If so, how do we set that up?  I have no idea how to get one machine to see the general iCloud account.
    Any help or insight would be greatly appreciated.
    Thanks in advance.

    Actually, that was changed in the iOS 5.1.1 update. You can now stop the phone from defaulting to CDMA by going into Settings>General>Roaming>International CDMA and making sure it's set to "off". While it doesn't sound as if there's any harm in setting Data Roaming to off, I don't think it matters in this circumstance.

  • Confused about advice from Verizon re:International Traveling

    I have an iphone 4S with Verizon. As I am going to be traveling in France this summer I decided to get a local French SIM card through LeFrenchMobile. I received that, called Verizon, had phone unlocked, and the French SIM card works perfectly. Then the Verizon representative told me I needed to go in and turn Data Roaming off so as not to be charged by Verizon. I explained that when abroad I will be using the French SIM card and therefore the data should not show up on my Verizon account. She told me No, there would still be charges from Verizon for data if I leave that on. So I am confused? I can understand why she would say that if I was leaving in the Verizon SIM but with that out of the phone is there any other method of them charging my data roaming abroad. Thanks in advance for any clarification.

    Actually, that was changed in the iOS 5.1.1 update. You can now stop the phone from defaulting to CDMA by going into Settings>General>Roaming>International CDMA and making sure it's set to "off". While it doesn't sound as if there's any harm in setting Data Roaming to off, I don't think it matters in this circumstance.

  • Confusion about recovery in nocatalog mode (Oracle 11.2.0.3)

    Hi All,
    Please help to understand the below scenario.
    A database is running in nocatalog mode.Now the situation is that the incremental level 0 backup of the database was taken on 4th July.. since then incremental level 1 backup was taken till today i.e 19th july and in the meantime no full backup was taken..The controlfile_record_keep_time is 7 days.Now if any user asks to restore and recover the database until 15th july will that be possible ? Will the data in the conrolfile be overwritten because controlfile_record_keep_time is 7 days and no record will be shown of 4th july backup ? Please help to understand.

    Hi Heamant,
    Blow is the output of list backup..Please help me to understand here as I was under the impression that since the control_file_record_keep_time is 3 it will keep 3 days old record and delete the old records including records of backup..
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    1       Incr 0  80.00K     DISK        00:00:00     19-JUL-13
            BP Key: 1   Status: AVAILABLE  Compressed: NO  Tag: TAG20130719T065051
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_4_821170252
      SPFILE Included: Modification time: 19-JUL-13
      SPFILE db_unique_name: THUB
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    2       Incr 0  33.27M     DISK        00:00:02     19-JUL-13
            BP Key: 2   Status: AVAILABLE  Compressed: NO  Tag: TAG20130719T065051
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_2_821170252
      Control File Included: Ckp SCN: 12633631356657   Ckp time: 19-JUL-13
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    3       Incr 0  1.21G      DISK        00:06:23     19-JUL-13
            BP Key: 3   Status: AVAILABLE  Compressed: NO  Tag: TAG20130719T065832
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_7_821170713
      List of Datafiles in backup set 3
      File LV Type Ckp SCN    Ckp Time  Name
      6    0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/ctxd01.dbf
      9    0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/odm.dbf
      10   0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/olap.dbf
      17   0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_int02.dbf
      18   0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/sysaux02.dbf
      19   0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/sysaux03.dbf
      21   0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/oim1.dbf
      22   0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/bmc01.dbf
      27   0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/users_1.dbf
      354  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/system11.dbf
      379  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/undo01.dbf
      399  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_queue01.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    4       Incr 0  33.27M     DISK        00:00:05     19-JUL-13
            BP Key: 4   Status: AVAILABLE  Compressed: NO  Tag: TAG20130719T065832
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_11_821171098
      Control File Included: Ckp SCN: 12633631356831   Ckp time: 19-JUL-13
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    5       Incr 0  80.00K     DISK        00:00:00     19-JUL-13
            BP Key: 5   Status: AVAILABLE  Compressed: NO  Tag: TAG20130719T065832
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_12_821171104
      SPFILE Included: Modification time: 19-JUL-13
      SPFILE db_unique_name: THUB
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    6       Incr 0  8.31G      DISK        00:08:21     19-JUL-13
            BP Key: 6   Status: AVAILABLE  Compressed: NO  Tag: TAG20130719T065832
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_10_821170713
      List of Datafiles in backup set 6
      File LV Type Ckp SCN    Ckp Time  Name
      1    0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/system01.dbf
      4    0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/system04.dbf
      15   0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind06.dbf
      20   0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/hig_custom_data_1.dbf
      288  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/system10.dbf
      295  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/system06.dbf
      314  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/portal01.dbf
      397  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_nolog01.dbf
      400  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_media01.dbf
      403  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind02.dbf
      405  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind04.dbf
      407  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_ref02.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    7       Incr 0  9.14G      DISK        00:08:52     19-JUL-13
            BP Key: 7   Status: AVAILABLE  Compressed: NO  Tag: TAG20130719T065832
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_8_821170713
      List of Datafiles in backup set 7
      File LV Type Ckp SCN    Ckp Time  Name
      3    0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/system03.dbf
      8    0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_queue02.dbf
      16   0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_ref03.dbf
      351  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/system07.dbf
      352  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/system09.dbf
      353  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/system08.dbf
      393  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind01.dbf
      398  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_archive01.dbf
      401  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_txn_data02.dbf
      402  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_txn_data03.dbf
      404  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind03.dbf
      406  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind05.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    8       Incr 0  9.30G      DISK        00:09:21     19-JUL-13
            BP Key: 8   Status: AVAILABLE  Compressed: NO  Tag: TAG20130719T065832
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_9_821170713
      List of Datafiles in backup set 8
      File LV Type Ckp SCN    Ckp Time  Name
      2    0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/system02.dbf
      5    0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/system05.dbf
      7    0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/owad01.dbf
      11   0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/sysaux01.dbf
      12   0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/apps_ts_tools01.dbf
      13   0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/system12.dbf
      14   0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_txn_data04.dbf
      28   0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/hig_accounting_data_1.dbf
      392  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_txn_data01.dbf
      394  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_ref01.dbf
      395  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_int01.dbf
      396  0  Incr 12633631356831 19-JUL-13 /acac_qpip/data01/thub_restore/a_summ01.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    9       Full    33.27M     DISK        00:00:03     19-JUL-13
            BP Key: 9   Status: AVAILABLE  Compressed: NO  Tag: TAG20130719T070759
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/cntrl_THUB_13_821171280
      Control File Included: Ckp SCN: 12633631356831   Ckp time: 19-JUL-13
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    10      Incr 1  80.00K     DISK        00:00:00     19-JUL-13
            BP Key: 10   Status: AVAILABLE  Compressed: NO  Tag: TAG20130719T071519
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_17_821171720
      SPFILE Included: Modification time: 19-JUL-13
      SPFILE db_unique_name: THUB
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    11      Incr 1  33.27M     DISK        00:00:02     19-JUL-13
            BP Key: 11   Status: AVAILABLE  Compressed: NO  Tag: TAG20130719T071519
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_15_821171720
      Control File Included: Ckp SCN: 12633631356831   Ckp time: 19-JUL-13
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    12      Full    33.27M     DISK        00:00:01     19-JUL-13
            BP Key: 12   Status: AVAILABLE  Compressed: NO  Tag: TAG20130719T071523
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/cntrl_THUB_20_821171723
      Control File Included: Ckp SCN: 12633631356831   Ckp time: 19-JUL-13
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    13      Incr 1  80.00K     DISK        00:00:00     20-JUL-13
            BP Key: 13   Status: AVAILABLE  Compressed: NO  Tag: TAG20130720T032324
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_24_821244206
      SPFILE Included: Modification time: 19-JUL-13
      SPFILE db_unique_name: THUB
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    14      Incr 1  33.27M     DISK        00:00:04     20-JUL-13
            BP Key: 14   Status: AVAILABLE  Compressed: NO  Tag: TAG20130720T032324
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_22_821244206
      Control File Included: Ckp SCN: 12633631527384   Ckp time: 20-JUL-13
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    15      Incr 1  1.30M      DISK        00:05:39     20-JUL-13
            BP Key: 15   Status: AVAILABLE  Compressed: NO  Tag: TAG20130720T032754
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_28_821244475
      List of Datafiles in backup set 15
      File LV Type Ckp SCN    Ckp Time  Name
      3    1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/system03.dbf
      8    1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_queue02.dbf
      16   1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_ref03.dbf
      351  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/system07.dbf
      352  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/system09.dbf
      353  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/system08.dbf
      393  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind01.dbf
      398  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_archive01.dbf
      401  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_txn_data02.dbf
      402  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_txn_data03.dbf
      404  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind03.dbf
      406  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind05.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    16      Incr 1  65.79M     DISK        00:05:41     20-JUL-13
            BP Key: 16   Status: AVAILABLE  Compressed: NO  Tag: TAG20130720T032754
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_27_821244475
      List of Datafiles in backup set 16
      File LV Type Ckp SCN    Ckp Time  Name
      6    1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/ctxd01.dbf
      9    1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/odm.dbf
      10   1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/olap.dbf
      17   1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_int02.dbf
      18   1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/sysaux02.dbf
      19   1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/sysaux03.dbf
      21   1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/oim1.dbf
      22   1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/bmc01.dbf
      27   1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/users_1.dbf
      354  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/system11.dbf
      379  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/undo01.dbf
      399  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_queue01.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    17      Incr 1  80.00K     DISK        00:00:00     20-JUL-13
            BP Key: 17   Status: AVAILABLE  Compressed: NO  Tag: TAG20130720T032754
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_32_821244821
      SPFILE Included: Modification time: 20-JUL-13
      SPFILE db_unique_name: THUB
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    18      Incr 1  33.27M     DISK        00:00:02     20-JUL-13
            BP Key: 18   Status: AVAILABLE  Compressed: NO  Tag: TAG20130720T032754
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_31_821244820
      Control File Included: Ckp SCN: 12633631529457   Ckp time: 20-JUL-13
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    19      Incr 1  17.05M     DISK        00:05:54     20-JUL-13
            BP Key: 19   Status: AVAILABLE  Compressed: NO  Tag: TAG20130720T032754
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_30_821244475
      List of Datafiles in backup set 19
      File LV Type Ckp SCN    Ckp Time  Name
      1    1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/system01.dbf
      4    1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/system04.dbf
      15   1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind06.dbf
      20   1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/hig_custom_data_1.dbf
      288  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/system10.dbf
      295  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/system06.dbf
      314  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/portal01.dbf
      397  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_nolog01.dbf
      400  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_media01.dbf
      403  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind02.dbf
      405  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind04.dbf
      407  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_ref02.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    20      Incr 1  36.15M     DISK        00:06:05     20-JUL-13
            BP Key: 20   Status: AVAILABLE  Compressed: NO  Tag: TAG20130720T032754
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_29_821244475
      List of Datafiles in backup set 20
      File LV Type Ckp SCN    Ckp Time  Name
      2    1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/system02.dbf
      5    1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/system05.dbf
      7    1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/owad01.dbf
      11   1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/sysaux01.dbf
      12   1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/apps_ts_tools01.dbf
      13   1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/system12.dbf
      14   1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_txn_data04.dbf
      28   1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/hig_accounting_data_1.dbf
      392  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_txn_data01.dbf
      394  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_ref01.dbf
      395  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_int01.dbf
      396  1  Incr 12633631529457 20-JUL-13 /acac_qpip/data01/thub_restore/a_summ01.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    21      Full    33.27M     DISK        00:00:01     20-JUL-13
            BP Key: 21   Status: AVAILABLE  Compressed: NO  Tag: TAG20130720T033407
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/cntrl_THUB_33_821244847
      Control File Included: Ckp SCN: 12633631529457   Ckp time: 20-JUL-13
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    22      Incr 1  80.00K     DISK        00:00:00     22-JUL-13
            BP Key: 22   Status: AVAILABLE  Compressed: NO  Tag: TAG20130722T214637
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_37_821483199
      SPFILE Included: Modification time: 20-JUL-13
      SPFILE db_unique_name: THUB
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    23      Incr 1  33.27M     DISK        00:00:02     22-JUL-13
            BP Key: 23   Status: AVAILABLE  Compressed: NO  Tag: TAG20130722T214637
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_35_821483199
      Control File Included: Ckp SCN: 12633631529457   Ckp time: 20-JUL-13
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    24      Full    33.27M     DISK        00:00:01     22-JUL-13
            BP Key: 24   Status: AVAILABLE  Compressed: NO  Tag: TAG20130722T214642
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/cntrl_THUB_40_821483202
      Control File Included: Ckp SCN: 12633631529457   Ckp time: 20-JUL-13
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    25      Incr 1  2.05M      DISK        00:05:10     22-JUL-13
            BP Key: 25   Status: AVAILABLE  Compressed: NO  Tag: TAG20130722T214958
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_41_821483399
      List of Datafiles in backup set 25
      File LV Type Ckp SCN    Ckp Time  Name
      6    1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/ctxd01.dbf
      9    1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/odm.dbf
      10   1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/olap.dbf
      17   1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_int02.dbf
      18   1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/sysaux02.dbf
      19   1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/sysaux03.dbf
      21   1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/oim1.dbf
      22   1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/bmc01.dbf
      27   1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/users_1.dbf
      354  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/system11.dbf
      379  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/undo01.dbf
      399  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_queue01.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    26      Incr 1  216.00K    DISK        00:05:14     22-JUL-13
            BP Key: 26   Status: AVAILABLE  Compressed: NO  Tag: TAG20130722T214958
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_42_821483399
      List of Datafiles in backup set 26
      File LV Type Ckp SCN    Ckp Time  Name
      3    1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/system03.dbf
      8    1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_queue02.dbf
      16   1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_ref03.dbf
      351  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/system07.dbf
      352  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/system09.dbf
      353  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/system08.dbf
      393  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind01.dbf
      398  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_archive01.dbf
      401  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_txn_data02.dbf
      402  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_txn_data03.dbf
      404  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind03.dbf
      406  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind05.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    27      Incr 1  80.00K     DISK        00:00:00     22-JUL-13
            BP Key: 27   Status: AVAILABLE  Compressed: NO  Tag: TAG20130722T214958
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_46_821483715
      SPFILE Included: Modification time: 20-JUL-13
      SPFILE db_unique_name: THUB
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    28      Incr 1  33.27M     DISK        00:00:01     22-JUL-13
            BP Key: 28   Status: AVAILABLE  Compressed: NO  Tag: TAG20130722T214958
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_45_821483715
      Control File Included: Ckp SCN: 12633631530437   Ckp time: 22-JUL-13
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    29      Incr 1  16.79M     DISK        00:05:23     22-JUL-13
            BP Key: 29   Status: AVAILABLE  Compressed: NO  Tag: TAG20130722T214958
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_44_821483399
      List of Datafiles in backup set 29
      File LV Type Ckp SCN    Ckp Time  Name
      1    1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/system01.dbf
      4    1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/system04.dbf
      15   1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind06.dbf
      20   1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/hig_custom_data_1.dbf
      288  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/system10.dbf
      295  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/system06.dbf
      314  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/portal01.dbf
      397  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_nolog01.dbf
      400  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_media01.dbf
      403  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind02.dbf
      405  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind04.dbf
      407  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_ref02.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    30      Incr 1  20.19M     DISK        00:05:30     22-JUL-13
            BP Key: 30   Status: AVAILABLE  Compressed: NO  Tag: TAG20130722T214958
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_43_821483399
      List of Datafiles in backup set 30
      File LV Type Ckp SCN    Ckp Time  Name
      2    1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/system02.dbf
      5    1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/system05.dbf
      7    1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/owad01.dbf
      11   1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/sysaux01.dbf
      12   1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/apps_ts_tools01.dbf
      13   1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/system12.dbf
      14   1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_txn_data04.dbf
      28   1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/hig_accounting_data_1.dbf
      392  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_txn_data01.dbf
      394  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_ref01.dbf
      395  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_int01.dbf
      396  1  Incr 12633631530437 22-JUL-13 /acac_qpip/data01/thub_restore/a_summ01.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    31      Full    33.27M     DISK        00:00:01     22-JUL-13
            BP Key: 31   Status: AVAILABLE  Compressed: NO  Tag: TAG20130722T215531
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/cntrl_THUB_47_821483731
      Control File Included: Ckp SCN: 12633631530437   Ckp time: 22-JUL-13
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    32      Full    33.27M     DISK        00:00:01     23-JUL-13
            BP Key: 32   Status: AVAILABLE  Compressed: NO  Tag: TAG20130723T185029
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/cntrl_THUB_52_821559030
      Control File Included: Ckp SCN: 12633631530437   Ckp time: 22-JUL-13
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    33      Full    33.30M     DISK        00:00:01     23-JUL-13
            BP Key: 33   Status: AVAILABLE  Compressed: NO  Tag: TAG20130723T185033
            Piece Name: /tech/oracle/product/11.2.0.3_FAH/dbs/c-448384833-20130723-00
      SPFILE Included: Modification time: 20-JUL-13
      SPFILE db_unique_name: THUB
      Control File Included: Ckp SCN: 12633631530437   Ckp time: 22-JUL-13
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    34      Full    33.27M     DISK        00:00:02     23-JUL-13
            BP Key: 34   Status: AVAILABLE  Compressed: NO  Tag: TAG20130723T185212
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/cntrl_THUB_58_821559132
      Control File Included: Ckp SCN: 12633631530437   Ckp time: 22-JUL-13
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    35      Full    33.30M     DISK        00:00:01     23-JUL-13
            BP Key: 35   Status: AVAILABLE  Compressed: NO  Tag: TAG20130723T185214
            Piece Name: /tech/oracle/product/11.2.0.3_FAH/dbs/c-448384833-20130723-01
      SPFILE Included: Modification time: 20-JUL-13
      SPFILE db_unique_name: THUB
      Control File Included: Ckp SCN: 12633631530437   Ckp time: 22-JUL-13
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    36      Incr 1  128.00K    DISK        00:05:16     23-JUL-13
            BP Key: 36   Status: AVAILABLE  Compressed: NO  Tag: TAG20130723T191635
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_61_821560596
      List of Datafiles in backup set 36
      File LV Type Ckp SCN    Ckp Time  Name
      3    1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/system03.dbf
      8    1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_queue02.dbf
      16   1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_ref03.dbf
      351  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/system07.dbf
      352  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/system09.dbf
      353  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/system08.dbf
      393  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind01.dbf
      398  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_archive01.dbf
      401  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_txn_data02.dbf
      402  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_txn_data03.dbf
      404  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind03.dbf
      406  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind05.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    37      Incr 1  4.00M      DISK        00:05:19     23-JUL-13
            BP Key: 37   Status: AVAILABLE  Compressed: NO  Tag: TAG20130723T191635
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_60_821560595
      List of Datafiles in backup set 37
      File LV Type Ckp SCN    Ckp Time  Name
      6    1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/ctxd01.dbf
      9    1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/odm.dbf
      17   1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_int02.dbf
      18   1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/sysaux02.dbf
      19   1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/sysaux03.dbf
      21   1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/oim1.dbf
      22   1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/bmc01.dbf
      23   1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/test1.dbf
      354  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/system11.dbf
      379  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/undo01.dbf
      399  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_queue01.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    38      Incr 1  16.77M     DISK        00:05:27     23-JUL-13
            BP Key: 38   Status: AVAILABLE  Compressed: NO  Tag: TAG20130723T191635
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_63_821560596
      List of Datafiles in backup set 38
      File LV Type Ckp SCN    Ckp Time  Name
      1    1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/system01.dbf
      4    1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/system04.dbf
      10   1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/olap.dbf
      15   1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind06.dbf
      20   1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/hig_custom_data_1.dbf
      288  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/system10.dbf
      295  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/system06.dbf
      314  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/portal01.dbf
      397  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_nolog01.dbf
      400  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_media01.dbf
      403  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind02.dbf
      405  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_txn_ind04.dbf
      407  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_ref02.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    39      Incr 1  21.27M     DISK        00:05:31     23-JUL-13
            BP Key: 39   Status: AVAILABLE  Compressed: NO  Tag: TAG20130723T191635
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/DB_THUB_62_821560596
      List of Datafiles in backup set 39
      File LV Type Ckp SCN    Ckp Time  Name
      2    1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/system02.dbf
      5    1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/system05.dbf
      7    1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/owad01.dbf
      11   1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/sysaux01.dbf
      12   1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/apps_ts_tools01.dbf
      13   1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/system12.dbf
      14   1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_txn_data04.dbf
      27   1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/users_1.dbf
      28   1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/hig_accounting_data_1.dbf
      392  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_txn_data01.dbf
      394  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_ref01.dbf
      395  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_int01.dbf
      396  1  Incr 12633631533042 23-JUL-13 /acac_qpip/data01/thub_restore/a_summ01.dbf
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    40      Full    33.27M     DISK        00:00:02     23-JUL-13
            BP Key: 40   Status: AVAILABLE  Compressed: NO  Tag: TAG20130723T192211
            Piece Name: /acac_qpip/data01/thub_restore/rman_bkp/cntrl_THUB_64_821560931
      Control File Included: Ckp SCN: 12633631533042   Ckp time: 23-JUL-13
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    41      Full    33.30M     DISK        00:00:01     23-JUL-13
            BP Key: 41   Status: AVAILABLE  Compressed: NO  Tag: TAG20130723T192213
            Piece Name: /tech/oracle/product/11.2.0.3_FAH/dbs/c-448384833-20130723-02
      SPFILE Included: Modification time: 23-JUL-13
      SPFILE db_unique_name: THUB
      Control File Included: Ckp SCN: 12633631533042   Ckp time: 23-JUL-13
    RMAN>

  • About Recovery ....plz help

    i am having a confusion about recovery....when i try to make recovery it says that "the pc will be set to factory state"...........it means does the recovery formates only C drive data or the entire drives data.
    This question was solved.
    View Solution.

    If the recovery type that you choose will format and partition only the Windoiws partition it will state that.
    If you choose a factory image recovery, then the entire hard disk will have the partitions deleted, then repartitioned  and formatted as appropriate in the OEM factory partition scheme as delivered.
    If you choose minimal system recover then only the C: (Windows) partition will be deleted,formatted and recreated with minimal HP software.
    ****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
    2015 Microsoft MVP - Windows Experience Consumer

  • Confused about transaction, checkpoint, normal recovery.

    After reading the documentation pdf, I start getting confused about it's description.
    Rephrased from the paragraph on the transaction pdf:
    "When database records are created, modified, or deleted, the modifications are represented in the BTree's leaf nodes. Beyond leaf node changes, database record modifications can also cause changes to other BTree nodes and structures"
    "if your writes are transaction-protected, then every time a transaction is committed the leaf nodes(and only leaf nodes) modified by that transaction are written to JE logfiles on disk."
    "Normal recovery, then is the process of recreating the entire BTree from the information available in the leaf nodes."
    According to the above description, I have following concerns:
    1. if I open a new environment and db, insert/modify/delete several million records, and without reopen the environment, then normal recovery is not run. That means, so far, the BTree is not complete? Will that affact the query efficiency? Or even worse, will that output incorrect results?
    2. if my above thinking is correct, then every time I finish commiting transactions, I need to let the checkpoint to run in order to recreate the whole BTree. If my above thinking is not correct, then, that means that, I don't need to care about anything, just call transaction.commit(), or db.sync(), and let je to care about all the details.(I hope this is true :>)
    michael.

    http://www.oracle.com/technology/documentation/berkeley-db/je/TransactionGettingStarted/chkpoint.html
    Checkpoints are normally performed by the checkpointer background thread, which is always running. Like all background threads, it is managed using the je.properties file. Currently, the only checkpointer property that you may want to manage is je.checkpointer.bytesInterval. This property identifies how much JE's log files can grow before a checkpoint is run. Its value is specified in bytes. Decreasing this value causes the checkpointer thread to run checkpoints more frequently. This will improve the time that it takes to run recovery, but it also increases the system resources (notably, I/O) required by JE.
    """

  • If I download a video from my video camera to a new (current 1/12) iMac 21 inch, how can I burn it to a DVD using the computer itself. Is this possible? Do I need to buy additional software. Two salespeople at the Apple were a little confused about this.

    If I download a video from my video camera to a new (current 1/12) iMac 21 inch, how can I burn it to a DVD using the computer itself. Is this possible? Do I need to buy additional software. Two salespeople at the Apple were a little confused about this. Thank you.

    The DVD recorder I'm referring to is one I've use for years. It is not attached to my aging iMac in any way. I simply play the video from my camcorder (mini-dv tape based Canon HV20)  into the DVD recorder and create a DVD that can be played in any DVD player. I can only do minimum editing so what goes in is what I get. This has been fine for creating dupes of the various things I shoot.
    If I buy a new iMac (21 inch), I'd like to be able to download the video to the iMac through iMovie, work with it to whatever degree I wish, and burn it to a DVD that can also be played in any DVD player -- or to use as a master to dupe copies.
    What I'm understanding from you and others is that this would be possible if Apple had included iDVD in the software that comes with the iMac, or if I purchase the iLife Family Pack, or buy the correct version of Toast. I'm hoping I can persuade Apple to sell me an iMac with iDVD installed.
    Essentially I want to move from a basic process of creating DVD copies to the more sophisticated process of creating one from an iMac.
    Thank you again for your help and wisdom.

  • Can I get a data recovery from Apple if my iMac was in the hard drive replacement programme and I wasn't notified about it?

    Basically my iMac just crashed and I searched on Google for replacing my hard drive and came across the iMac 1TB Seagate Hard Drive Replacement Program at http://www.apple.com/support/imac-harddrive/
    Which is that Apple is asking all 2009 - 2011 iMac users to return their iMac for a free hard drive replacement because it currently has a fault in it. After entering in my serial number, I see that my iMac is elegible for a replacement.
    I did register my iMac with Apple, but I didn't receive any email about this program and I lost all my recent data because of the faulty hard drive. I never had an issue before with the drive so this just happened out of the blue.
    Is it possible to get a free data recovery from Apple for this? I find that it was a lack of communication that I lost most of my data.

    I completely understand that it's my responsibility to back up my data but I have it set to every 2nd month, not on a weekly or daily basis to back up the data.
    Apple might not be in data recovery business but could they not acquire a third party to do this?
    This is what happened:
    It was on sleep overnight and when I tried waking it, it was lagging badly. So I shut it down and restarted it. I phoned into techincal support to find out whats wrong, but they were giving me advice to reset the params etc. But i think it made it worse because it didnt want to get passed the white start up screen.
    So I phoned back to ask if it's a usual issue with my version of iMac and the man replied that it isn't common and that I should run the disk utility to check the hard drives health.
    I installed Mountain Lion on a USB and started the disk utility. Then it highlighted in red that it's a hardware fault and cannot be repaired by the disk utility. Therefore the hard drive has a serious fault with it.
    That's when I Google'd for a replacement drive and came across the program. The techincal guy didn't even tell me about it or anything.
    If I knew about this sooner, I would have taken it in for a replacement.

  • Confused about tags on old pictures

    I imported some old pictures & it tells me that there are tags on them & asks if I wish to import them with the tags.  I say yes & they are imported.  I don't see any tags.  Was I being asked about some generic tag that I can't see or is there some way to see the tags that I'm unaware of?  Is ther some way to display this tag information in PSE 7?  Are these tags if different usable in PSE just like those created by PSE?

    I think that I now know just what the problems that I have been having are coming from.  I have a new PC with Windows 7 64 bit.  Prior to getting this machine I made a backup to an external hard drive.  I now have PSE 7 installed & working OK.
    My mistake was that I was trying to import my old pictures from holders on the external drive rather than trying to restore my catalogs from the back up.  Windows 7 is now aware of where my picture are but they are physically located on an external drive when they should be on my new machines "C'' drive rather than being stored externally.
    I thinks that the reason that I has getting the Tags meta data displayed under imported tags rather than having my original tag structure being restored.  Is this a correct assumption?  If This is correct do I fix things by doing the following or is there a better way?
    Select all picture & tellthe program  to delete from catalog but not from hard drive.  Then tell the program to restore my
    catalog from the external drive.  Once this has been done & confirming that indeed the tag file structure has been restored I then select all picture in the catalogue & move them all from the external drive to the correct location.
    Thanks in advance

  • I'm confused about the apple ID transition from my aol screen name. Does it continue to use my aol email as my apple ID, converting it somehow or do I need to provide a new email address or just create a new username for the apple ID?

    I'm confused about the transition to an apple ID that doesn't use my aol email to sign in. The instructions are vague and ambiguous. Any help would be appreciated.

    OK, so if your current Apple ID using your AOL Username (like johndoe), then you need to log onto Manage your Apple ID and EDIT that AOL Username to a valid email address: Apple - My Apple ID
    If you have an AOL email address (like [email protected]), and you are not using that as another Apple ID, you can change the AOL Username Apple ID to that. Otherwise, you can change it to any valid email address (which you will have to verify when you change to it).
    Hope that clears it up. Post back if it doesn't!
    Cheers,
    GB

  • Confused about standby redo log groups

    hi masters,
    i am little bit confuse about creating redo log group for standby database,as per document number of standby redo group depends on following equation.
    (maximum number of logfiles for each thread + 1) * maximum number of threads
    but i dont know where to fing threads? actually i would like to know about thread in deep.
    how to find current thread?
    thanks and regards
    VD

    is it really possible that we can install standby and primary on same host??
    yes its possible and i have done it many times within the same machine.
    For yours confusion about spfile ,i agree document recommend you to use spfile which is for DG broker handling if you go with DG borker in future only.
    There is no concern spfile using is an integral step for primary and standby database implementation you can go with pfile but good is use spfile.Anyhow you always keep pfile on that basis you created spfile,i said you make an entry within pfile then mount yours standby database with this pfile or you can create spfile from this pfile after adding these parameter within pfile,i said cause you might be adding this parmeter from SQL prompt.
    1. logs are not getting transfered(even i configure listener using net manager)
    2.logs are not getting archived at standby diectory.
    3.'ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION' NEVER COMPLETE ITS RECOVERY
    4. when tried to open database it always note it 'always' said system datafile is not from sufficiently old backup.
    5.i tried 'alter database recover managed standby database camncel' also.Read yours alert log file and paste the latest log here..
    Khurram

  • Confuse about the document

    Hi,all . From the document ,i had confused about the following .
    Automatic Undo Management in Oracle RAC
    url >> http://docs.oracle.com/cd/B19306_01/rac.102/b28759/adminrac.htm#CHDGAIFJ
    Oracle automatically manages undo segments within a specific undo tablespace that is assigned to an instance. Only the instance assigned to the undo tablespace can modify the contents of that tablespace. However, each instance can read the undo data blocks created by any instance. Also, when performing transaction recovery, any instance can update any undo tablespace, as long as that undo tablespace is not currently being used by another instance for undo generation or transaction recovery
    what's the meaning of above that is bold ?

    Say you're running a 2-node RAC and node 2 dies. The services which were running on node 2 now get re-located to node 1. It is then possible that node 1 will perform transaction rollback/recovery and, when it does so, it will need to be able to read from node 2's undo tablespace (and maybe update the undo segment headers in node 2's undo tablespace, too).

  • Recovery from failure question

    In order to use two racks of servers (in our case located in separate buildings) and make sure that primary and backup (backup count 1) of each partition are allocated to nodes in different racks I have understood that there is a "machine id" that can be assigned to each node.
         As far as I understand it the cluster will (when configured this way) survive failure of one rack (as long as no more failures occur before the other rack is online again), ie it will execute in a lower "safely mode". I have two questions about this:
         1. Lets say that one rack looses connection with the rest of the network long enough for the cluster to consider the other rack to be down. This will happen with both racks. What happens when the racks once again can communicate? Will they automatically sort out the "split brain" situation?
         2. Lets assume that one of the racks A is hit by a power spike that causes the switch and all the servers except one to rebooted. This will totally cut the failed rack off from the other rack while the switch re-boots and the nodes in rack B will consider all nodes in rack A to be down. After the switch is re-booted the nodes one still working server in rack A will be able to communicate with the nodes in rack B again. My question is then if Coherent in this situation will try to creating backups for all partitions of rack B in the nodes on the single available server in rack A? If this is the case the nodes in that server will most likely quickly run out of heap. What will happen in this situation? Will coherence retry - rebalancing when more nodes join the cluster or will the cluster crash?
         Best Regards
         Magnus

    The second answer makes me a bit confused - two     > follow-up questions:
         >
         > 2A - If I use machine id 0 for N servers in rack A
         > and machine id 1 for N servers in rack B I had the
         > impression that primary and backup could NEVER end up
         > in the same rack (even after failures - ie the system
         > would run with only primaries if all nodes with say
         > machine id 1 went down) - is this not the way it
         > works?
         Never is not exactly true. Only if it is theoretically possible to fit all the data in distinct nodes. But e.g. if you have two boxes, with the cluster nodes on one of the boxes not providing enough capacity to hold an entire copy of the data-set, the two copies still have to exist, then inevitably some of the duplicate data will end up on the nodes on the larger box, since they cannot fit into the smaller one. Also be aware that data distribution is done with the granularity of partitions. You cannot distribute a single partition to two nodes, so too uneven partitioning of the data-set can lead to problems.
         > 2B - My concern was that in the case of failures (or
         > as I stated my question during recovery from
         > failures) the number of physical servers (and
         > therefore nodes!) with machine id say zero and one
         > may be different (it seems quite hard to make sure
         > that this cant happen!) and in this case (say for
         > instance that only one out of N servers with machine
         > id zero comes up immediately, the other N - 1 comes
         > up much later because they were forced to do a disk
         > check or required operator intervention to start
         > after a failure) the memory of the single server
         > (heap space of its nodes) will not be enough to
         > accommodate backups for all the primaries on all the
         > N servers with the other machine id.
         >
         While and immediately after you are losing nodes (when their death is detected) partition backups will be attempted to be promoted to primary copies. This might cause OutOfMemoryErrors in those nodes. I do not know if Coherence is able to recover from that (theoretically it should be possible to drop the newly created object references to get back to the state before the attempt to promote the partition backup to a primary partition).
         So during nodes dying you can either temporarily or permanently lose access to data for which primaries were on boxes which died and the reconstruction from the backup caused OutOfMemoryError. If the Coherence JVM is not able to recover from that OutOfMemoryError then you might lose other primaries which reside on this cluster node and have a ripple effect because of this.
         You can reduce the risk of such events by having more than two racks if multiple nodes in racks can fail together, and also sizing the cluster JVMs to have lower memory utilization due to cached data. This way a rack failure will cause for one less primaries lost and for two, more free memory to reconstruct data in. You can read the Production Checklist for some information on sizing the cluster.
         Whatever happens, I don't expect that you will lose data due to OutOfMemory errors when you do not lose a cluster node. So after that blackout on one of the racks, and after the cluster reached a quiescent state as far as redistribution of partitions is concerned, you will not lose data just because you added back a node (I expect a copy of a backup is not dropped before the safe reception of the backup at the transfer destination is acknowledged).
         If there are not enough cluster nodes running on one of the racks to accommodate the entire data-set, your data will not be balanced in a way that copies of the same data are fully on different, but they will still reside on separate cluster nodes. When more nodes are started then gradually they will be rebalanced to hold more data on separate racks.
         Best regards,
         Robert

  • Confusion about applet

    sir
    i have confusion about applet that if an applet compile successfully but on running it shows a exception message about "main"that no such method exist.help me out please

    The full text of the error message would make it easier for us to see what is wrong BUT it sounds like you are trying to run the Applet as an applicaiton from the comand line rather than through an HTML tag in an HTML page loaded into your browser!
    Though you can make Applets run as applications it not normal to do so.

Maybe you are looking for

  • Why does my "Doteasy" e-mail format change when sent using Mozilla?

    Up until recently I have been using Internet Explorer as a browser both at work and at home. I recently switched to Mozilla Firefox only at home and have been happy overall. When I access my work e-mail account from home ("Doteasy.com") I am unable t

  • Emailed jpeg files turn into .dat files

    why can't I open jpeg files that i email myself on my iphone 3Gs?

  • Create a Blank Text file if it does not exist in a Given Directory

    Hi, I would like to check if text file in a given folder exists or not if not then create a blank text file in a given directory. I was checking File system task, it has options to create directory and move files, copy files but not creating files. H

  • Virus on my macbook

    I went to school the other day and the computers there detected a virus on my flash drive. I came home got Norton and scanned the computer. It found about 3 instances of some form of "hacktool." At the same time my computer had been running really sl

  • Movie using much more space than file size

    Hello. I published a movie in imovie to the media gallery in HD. It is a long video, so I knew it would take up a lot of space. It is listed as 5 GB in my imovie project folder. However, when I "show package contents" of the movie, the actual size of