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>

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

  • 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

  • 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.
    """

  • Confuse about Configuring Oracle Warehouse Builder

    newbie here... i am abit confuse on how to configure the Oracle Warehouse builder...
    I have 2 database... 1 source and 1 new one...
    I understand that i have to install the Runtime Repository in the database computer and the Target Schema through the client's computer...
    so all this while... i am just confuse about what to install into the source database and what to install into the new database...
    Please help...

    Location is a logical entity in your OWB design that can be either a database schema, a flat file location, an SAP application location etc. Once you complete your design and are ready to deploy the design into the runtime environment, you will have to 'register' the locations by providing the physical details of your location to OWB (user name/password, database, hostname etc.).
    I am a bit confused by your configuration - are the source and the target in two separate schemas or in the same schema? Your posts are somewhat contradictory.
    If they are in two different schemas, you should:
    1. Create a source module pointing to a source schema (you can then import data object structures from the source schema - i.e. you don't have to create source tables manually in OWB, but you can import them into the module automatically). This module will have a source location (for example SRC_LOC).
    2. Create a target module where all your target objects will be (i.e. where the data will be loaded). This module will have a different location (TGT_LOC). In your target module you will also create the mappings.
    3. When deploying, you will register SRC_LOC with the physical details of your source schema, while the target location will be registered with the physical details of the target schema. The code generated by OWB during deployment will make sure that the data is extracted from the source schema and inserted into the target schema (either by generating and using DB links or by qualifying the schemas in the extraction queries if source and target are in the same database instance).
    On the other hand, if both source and target objects are in the same db schema, you can have all your objects in the same target module and you will only have to register the location of this target module when deploying (LOC_TGT).
    That said, there can be a variety of reasons why there is no data in the target after you run the extract mapping that have nothing to do with locations, such as logical errors in the mapping (an inappropriate filter or a wrong join), insufficient privileges etc. I suggest you take a look in the runtime audit browser that should contain the error messages relative to your mapping.
    Regards:
    Igor

  • 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).

  • Problem in Converting Database into Archivelog mode (Oracle 10G)

    Hi Team,
    I come across a strange problem in the ORACLE 10G Server.
    I am converting database mode from NoArchivelog to Archivelog mode through RMAN in 10G.
    Now When I execute these following commands through RMAN prompt it works properly as shown below?
    C:\>rman
    Recovery Manager: Release 10.2.0.1.0 - Production on Thu Nov 30 18:01:08 2006
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    RMAN> connect target /
    connected to target database: RAVI (DBID=4025722893, not open)
    RMAN> shutdown immediate;
    using target database control file instead of recovery catalog
    database dismounted
    Oracle instance shut down
    RMAN> STARTUP MOUNT;
    connected to target database (not started)
    Oracle instance started
    database mounted
    Total System Global Area 167772160 bytes
    Fixed Size 1247876 bytes
    Variable Size 79693180 bytes
    Database Buffers 79691776 bytes
    Redo Buffers 7139328 bytes
    RMAN> SQL 'ALTER DATABASE ARCHIVELOG';
    sql statement: ALTER DATABASE ARCHIVELOG
    RMAN> ALTER DATABASE OPEN;
    database opened
    RMAN>
    But this same script when i writes in the backup.ora file & pass to Rman prompt it fails,
    File backup.ora contains...
    run
    SHUTDOWN IMMEDIATE;
    STARTUP MOUNT;
    SQL 'ALTER DATABASE ARCHIVELOG';
    ALTER DATABASE OPEN;
    passed to RMAN as follows...
    C:\OracleCode\BACKUP>"C:\oracle\product\10.2.0\db_1\bin\RMAN.EXE" target /"connect target SYSTEM/sreedhar@RAVI" log="C:\ORACLE~2\LOGS\backup_log.log" append cmdfile="C:\ORACLE~2\BACKUP\backup.ora"
    RMAN> 2> 3> 4> 5> 6> 7> 8>
    then it fails giving the following errors...
    using target database control file instead of recovery catalog
    database closed
    database dismounted
    Oracle instance shut down
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of startup command at 11/30/2006 18:05:59
    ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
    Recovery Manager complete.
    The same thing is working in the Oracle 9i but not in the Oracle 10G.
    Can Anybody plz help me in this?
    Regards,
    S.Tiwari
    .

    export ORACLE_SID=<SID>
    rman target /cmdfile="C:\ORACLE~2\BACKUP\backup.ora"
    it will connect to the default SID, there's no such thing as a default SID, what do you mean?
    But what if there are more that one SID available & I
    want to connect to SID other than the default SID.just specify the desired SID prior starting rman.
    more over the same string is working with 9i but not
    with 10G.maybe due to a bug?
    to summarize, you have two options it you would like to start up the instance:
    either you specify the SID prior starting rman and use os authentication
    or
    you register the instance statically and use oracle authentication.
    regards,
    -ap

  • 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

  • Confused about schema..

    I'm currently working on a project using VB 2010 Express and Oracle 11g XE. On my Oracle My SQL Developer, I am currently logged on as 'user X' and I created three tables. All of which are just listed on the 'tables' tree. Does it mean that 'user X' is like a schema when compared to MySQL?
    I have already integrated my database to my vb project and is working fine ATM. I'm just really confused about schemas in Oracle 11g XE.

    I'm just really confused about schemas in Oracle 11g XE.http://docs.oracle.com/cd/E11882_01/server.112/e25789/intro.htm#CEGJFFFD

  • I'm a bit confused about standby log files

    Hi all,
    I'm a bit confused about something and wondering if someone can explain.
    I have a Primary database that ships logs to a Logical Standby database.
    Everything appears to be working properly. If I check the v$archived_log table in the Primary and compare it to the dba_logstdby_log view in the Logical Standby, I'm seeing that logs are being applied.
    On the logical standby, I have the following configured for log_archive_dest_n parameters:
    *.log_archive_dest_1='LOCATION=/u01/oracle/archivedlogs/ORADB1
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=PNX8A_GMD'
    *.log_archive_dest_2='LOCATION=/u02/oracle/archivedlogs/ORADB1
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=PNX8A_GMD'
    *.log_archive_dest_3='LOCATION=/u03/oracle/archivedlogs/ORADB1
    VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=PNX8A_GMD'
    *.log_archive_dest_4='SERVICE=PNX8A_WDC ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=PNX8A_WDC'
    *.log_archive_dest_5='LOCATION=/u01/oracle/standbylogs/ORADB1
    VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=PNX8A_GMD'
    *.log_archive_dest_6='LOCATION=/u02/oracle/standbylogs/ORADB1
    VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=PNX8A_GMD'
    *.log_archive_dest_7='LOCATION=/u03/oracle/standbylogs/ORADB1
    VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=PNX8A_GMD'
    Here is my confusion now. Before converting from a Physical standby database to a Logical Standby database, I was under the impression that I needed the standby logs (i.e. log_archive_dest_5, 6 and 7 above) because a Physical Standby database would receive the redo from the primary and write it into the standby logs before applying the redo in the standby logs to the Physical standby database.
    I've now converted to a Logical Standby database. What's happening is that the standby logs are accumulating in the directory pointed to by log_archive_dest_6 above (/u02/oracle/standbylogs/ORADB1). They do not appear to be getting cleaned up by the database.
    In the Logical Standby database I do have STANDBY_FILE_MANAGEMENT parameter set to AUTO. Can anyone explain to me why standby log files would continue to accumulate and how I can get the Logical Standby database to remove them after they are no longer needed on the LSB db?
    Thanks in advance.
    John S

    JSebastian wrote:
    I assume you mean in your question, why on the standby database I am using three standby log locations (i.e. log_archive_dest_5, 6, and 7)?
    If that is your question, my answer is that I just figured more than one location would be safer but I could be wrong about this. Can you tell me if only one location should be sufficient for the standby logs? The more I think of this, that is probably correct because I assume that Log Transport services will re-request the log from the Primary database if there is some kind of error at the standby location with the standby log. Is this correct?As simple configure as below. Why more multiple destinations for standby?
    check notes Step by Step Guide on How to Create Logical Standby [ID 738643.1]
    >
    LOG_ARCHIVE_DEST_1='LOCATION=/arch1/boston VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=boston'
    LOG_ARCHIVE_DEST_2='SERVICE=chicago LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=chicago'
    LOG_ARCHIVE_DEST_3='LOCATION=/arch2/boston/ VALID_FOR=(STANDBY_LOGFILES,STANDBY_ROLE) DB_UNIQUE_NAME=boston'
    The following table describes the archival processing defined by the initialization parameters shown in Example 4-2.
         When the Boston Database Is Running in the Primary Role      When the Boston Database Is Running in the Logical Standby Role
    LOG_ARCHIVE_DEST_1      Directs archival of redo data generated by the primary database from the local online redo log files to the local archived redo log files in /arch1/boston/.      Directs archival of redo data generated by the logical standby database from the local online redo log files to the local archived redo log files in /arch1/boston/.
    LOG_ARCHIVE_DEST_2      Directs transmission of redo data to the remote logical standby database chicago.      Is ignored; LOG_ARCHIVE_DEST_2 is valid only when boston is running in the primary role.
    LOG_ARCHIVE_DEST_3      Is ignored; LOG_ARCHIVE_DEST_3 is valid only when boston is running in the standby role.      Directs archival of redo data received from the primary database to the local archived redo log files in /arch2/boston/.
    >
    Source:-
    http://docs.oracle.com/cd/B19306_01/server.102/b14239/create_ls.htm

  • Swamped and confused about products

    Hi guys,
    I am new to Oracle middleware products. After looking at a few articles, I am swamped and confused about those products, WebCenter (WC), Content Server (CS), Universal Content Management (UCM).
    1. WC has a built-in content database, part of Oracle database. CS also stores contents into Oracle database. Then what are differences between two types of content storage? Can I build WebCenter with Content Server as the content storage?
    2. WebCenter provides management functions on content. So does UCM. Users could contribute, review and release contents to web via both. Then what are differences between two types of content management? What more does UMC provide than the built-in content management in WC.
    3. Content Server needs a third-party web server (port:80) to publish its content. WebCenter Suite seems use Oracle HTTP Server (port:7777) to render web pages. Is it possible to integrate those two on one web server? Why is Oracle HTTP Server using a weird port?
    4. JDeveloper has the built-in OC4J container. But how can JDeveloper access or interact with Content Server or WC content database? Site Studio can access Content Server directly but only provides very limited portlet or ajax components. If I want to store web pages, static or dynamic, into WC and/or CS, which tool should I use?
    Can anybody help me with them? Or please point me to the right direction. I really appreciate it.
    thanks,
    Chen

    Plug it in and use the Transfer Purchases function, either from the resulting dialog box or from the File menu. If you need to authorize the computer, choose it from the Store menu.
    (65603)

  • Confused about color vs. b/w photos for printing...and more

    I reading confusing things about exporting a PDF for printing with both color and black and white images used in the same document.
    If I export to PDF and do a soft-proof and it looks okay, is that sufficient? If so, what's confusing about that, since this is my first print project, which Simulation Profile do I use? Is there a chart somewhere that compares U.S. Web Coated (SWOP) v2 to let's say 80 lb Gloss book with Aqueous coating (C2S)?
    I don't know what any of this means. So, is there a good article on this site, elsewhere, or an online printer who can help a rookie like me ensure I end up with a decent product?
    UPrinting.com advertises a "Free Project Review" that includes the following:
    Our team will run your file through a 30-point inspection, covering technical issues including:
    Artwork dimensions
    Bleed setup
    Low resolution images
    Elements that are not within the safe zone
    Image clipping
    Font sizes
    Un-embedded fonts
    Folding setup
    Page scaling
    Line weights
    Proper text spacing (compressed/expanded)
    Narrow borders that are at risk of being cut
    Compliance with USPS Mailing Guidelines
    Bindery setup for multi-page artwork
    What should I do? Is this trustworthy as long as I get a contract proof? Is there a "Go To" online printer that everyone loves (not sure you can recommend that here) or should I seek out a local printer?
    I'm using CS4 and have a file that's (maybe) ready to go but am looking at a learning curve of days if not weeks if I have to figure it all out myself.
    Thanks everyone.
    Paul

    InDesign puts grayscale and B&W (bitmap mode) art on the Black plate, where it belongs, so if you soft proof using the CMYK profile for your expected output conditions your preview will be accurate for the grayscale and B&W images as they will appear in print. presuming your monitor is calibrated and profiled so that you can trust what you see.
    Aqueous coating is applied AFTER the printing to protect, and possible enhance the glossiness of, the page (but not all coatings are glossy). This is not the same thing as printing on coated paper, which has a glossy surface and high ink holdout (and improves detail reproduction and usually will geive better color). You should be using whatever profile the printer has specified.

  • Confused about update method in JComponents

    Hello,
    I'm a bit confused about the update method in JComponents. What I remember from applets was that the update method was called whenever something changed such as a window being dragged across it or something.
    I've written a class that extends a JPanel and overwrites the paint method. Any components I add to it aren't drawn. I can add JComponent.update() methods to my paint() method but this is very inefficient as I'm having repaint() called by a thread 15 times a second. I tried to put the update methods in the JPanels update() but that doesn't work, in fact update isn't called at all. What does update do ?

    Let me take another crack at it...
    1) Grab the 9.2.0.8 patchset for the Oracle database (i.e. patch 4547809 on Metalink assuming you're using 32-bit Windows). Install this to upgrade your Oracle client to 9.2.0.8. Installation instructions are in the README.
    2) Grab the 9.2.0.8 Oracle ODBC driver, which you already appear to have, and follow the installation instructions in the README you're looking at.
    Justin

  • Confused about the 11g R2 Forms Server and using SSL

    All,
    I just installed the 11g R2 Forms Server software without configuring it.
    I then ran the config.sh script to configure it which creates a weblogic server domain.
    I'm a bit confused now. If I run opmnctl status command I get the following:
    Processes in Instance: frmrep_inst_1
    --------------------------------------------------------------+---------
    ias-component | process-type | pid | status
    --------------------------------------------------------------+---------
    emagent_frmrep_inst_1 | EMAGENT | 28279 | Alive
    RptSvr_eiaorapptest_frmrep_ins | ReportsServerComp~ | 28124 | Alive
    ohs1 | OHS | 27831 | Alive
    This looks to me like there is an Oracle Http Server installed.
    Is the Oracle Http Server answering web calls when I run forms or is the Weg Logic Server answering the call?
    Also, the Oracle Forms Installation Documentation talks about securing your environment with Oracle Identity Manager but we are not using Oracle Identity Manager. I want to use SSL but I'm not sure how to secure the environment with SSL. Do I need to configure the WebLogic server to use SSL or the OHS?
    Any help would be greatly appreciated.
    Cheers

    Fusion Middleware 11.1.x does include HTTP Server (OHS) and also requires WLS. Both HTTP Server and WLS are http listeners, amongst other things. So whether WLS handles a request or HTTP Server does it will be entirely up to you and/or the end-user.
    OHS has a listener which by default (in FMw) listens for requests on port 8888. On the other hand WLS_FORMS is preconfigured to listen on port 9001.
    This means that if your URL looks like the following, WLS_FORMS will directly answer the client:
    <blockquote>http://server:9001/forms/frmservlet?form=abc</blockquote>
    If the URL looks like the following, the HTTP Server will reply:
    <blockquote>http://server:8888/forms/frmservlet?form=abc</blockquote>
    The request path when using OHS as the listener to call Oracle Forms would look like this:
    <blockquote>CLIENT --- OHS --- WLS_FORMS --- FORMS SERVLET --- FORMS RUNTIME (frmweb.exe) --- DATABASE</blockquote>
    The request path when using WLS_FORMS as the listener to call Oracle Forms would look like this:
    <blockquote>CLIENT --- WLS_FORMS --- FORMS SERVLET --- FORMS RUNTIME (frmweb.exe) --- DATABASE</blockquote>
    Although removing OHS from the path would seem to be better because it is one less server to administer and less system resources consumed, generally it would be argued that the advantages of having it will outweigh the disadvantages.
    There are numerous advantages to use OHS in front of WLS, but the most obvious should be that OHS can be set up so that you have one and only one entry point into your FMw environment. In other words, even though for example Forms WLS listens on 9001 and Reports on 9002 and some other app on 9999, all requests can be routed through a single OHS port (e.g. 8888). This gives added security since only one port would need to be open assuming a firewall was in place. This configuration is also helpful when calling one application from another. For example when calling Reports from Forms. If you use OHS, references to other WLS managed servers can be called with a relative reference rather than a fully qualified one.
    Regarding whether or not SSL needs to be enabled at any particular point in the path is entirely up to you. You can enable SSL from the client all the way back to the db or any where in between. It is fairly common to see SSL between the client and OHS then no SSL to WLS. But if security is a great concern then you may want to consider SSL from front to back. However, keep in mind that SSL comes at a price. Performance will degrade slightly when SSL is enabled.
    Also, OAM (Oracle Access Manager) has nothing to do with SSL. SSL refers to traffic encryption. OAM is for authentication - single sign on.
    Consider reviewing the Forms Deployment Guide as well as the other Fusion Middleware documents referenced within it.
    <blockquote>http://docs.oracle.com/cd/E24269_01/index.htm</blockquote>
    Finally, and most important, this topic really has nothing to do with Oracle Forms. This is more about how a web server or its environment works.

Maybe you are looking for

  • How do I delete duplicates in numbers

    how do i delete duplicates in numbers

  • Strange results from JDBC  Query using a VARRAY

    Here's one for you experts: I have a 9i release 2 db set up, to which I connect via the JDBC thin driver. I have a JavaServer Pages application that needs to read a VARRAY from a table and then use the contents of the VARRAY. Here's the code in the J

  • CS 3.3 with Fireworks and Acrobat 9 Just Announced

    I just saw this. Those of us who have been waiting for Fireworks (or are about to fire some off) it's here. CS 3.3 also includes Acrobat 9. www.adobe.com

  • Do I have Adobe Flash Player? Installed it-cant find it

    DO I HAVE ADOBE FLASH PLAYER? INSTALLED IT-CANT FIND IT-TRIED TO DOWNLOAD VIDEOS TO "FLASH PLAYER" BUT COULD NOT DO IT-VIDEOS DISAPPEARED INTO CYBERSPACE. THIS SOUNDS LIKE IT IS NOT WORTH THE TROUBLE.WHY SO DIFFICULT TO ACCESS ADOBE FLASH PLAYER?   [

  • CHARM - how to assign

    Hi, I have configured ChaRM in our solman system, and setup STMS. I get some warning on the check, but no errors. Now I can create the change request either by going to crmd_order or thru service desk. My question is - how do I assign reporter, chang