RMAN - returning to prior incarnations

I was practicing backups with my colleagues, and we shut down the database twice, reopening it both times with 'resetlogs', without backing it up in between. The database lacked the archivelog it needed for recovery the last time, so we read the docs and prepared to return to a previous incarnation.
We returned to 3 incarnations prior and restored/recovered using:
RMAN> restore database "to_date('9/2/04 23:59:59','mm/dd/yy hr24:mi:ss');
RMAN> recover database "to_date('9/2/04 23:59:59','mm/dd/yy hr24:mi:ss');
I have two questions:
1) What did returning to the prior incarnation gain for us? Seems like I could've just issued the restore/recover commands and performed an incomplete recovery.
2) Do I need to remove the archive logs from the 2 later incarnations, or is RMAN smart enough to know that they don't apply?
Thanks,
Chuck

ckd38 wrote:
I bought my Samsung Continuum the day after Thanksgiving of last year, November 26. Originally, I intended to sell the Continuum and purchase the iPhone at retail price. However, just tonight,  I stumbled upon Verizon's return page that said they were extending the 30 day return policy to phones that were purchased from November 27th on. The last day to do this is tomorrow. The problem is I bought my phone exactly ONE day before this cutoff date. Tomorrow, I plan on going to the store to see if they will make an exception and let me return it. Then, my plan now is to activate my old phone (Samsung Rogue) until the iPhone would arrive in February and get it for $199 instead of $599.
How flexible is Verizon with these kinds of things? And do you think this will work? I will be begging the store manager tomorrow to see if they wil take it back as I wont have to pay retail and just pay the subsidized price for the iPhone. It would really stink if that one day will cost me.
Any thoughts?
Also, one other question. If the "Smartphones Talk Free Promotion" happens to still be in effect for the iPhone, would I be eligible still? (I am a secondary line and the Continuum was my first smartphone). I am not sure as technically, the iPhone would be my 2nd smartphone once I return my current one (hopefully),
Thanks!
I hate to be the harbinger of bad news, but you are probably going to be burdened with the Continuum because of that one day. The store may help if you are really nice, but it is unlikely. Work the charm and charisma, though. It is the least that you could do.

Similar Messages

  • Loadpsp, rman returns a TNS ORA-12560: TNS:protocol adapter error

    loadpsp, rman returns a TNS ORA-12560: TNS:protocol adapter error.
    also the enterprsie manager is also not running. please help

    What platform are you running?
    Do you have ORACLE_HOME and ORACLE_SID env. variables defined? and if they are, are they correct?
    does your PATH env. variable references the correct Oracle home directory?
    If Windows, is the service for the database instance running?
    can you connect using SQL*Plus?

  • Firefox 4.0 has disabled Trendmico Toolbar and 2 other items. How can I return to prior Firefox application?

    I installed new Firefox 4.0 and it automatically disabled Trend Micro tool bar 3.1.1110, Trend Micro NSC Firefox Extension 6.5.0.1234 and HP Smart Web Printing 4.6.0 since they wer "not compatible.
    How can I return to my previous application of Firefox?

    Did you try the add-on compatibility reporter? https://addons.mozilla.org/en-US/firefox/addon/15003/
    Firefox 4.0 beta 1 installs to a separate directory, so unless you uninstalled it, your previous Firefox install should be there. Just find it in the start menu and run it, allowing it to set itself back as the default browser.
    If you did uninstall it, just install it again: [[Installing Firefox]].
    You can but don't have to uninstall 4.0 via Add/Remove Programs

  • Prevent automatic updates & return to prior version

    i do not like or want to new version of firefox
    i want to return to the old view
    i do not want to have any further automatic updates - only by request and approval
    more INFO:
    visual disruptions do not work for me AT ALL

    You should send any feedback about these changes to http://input.mozilla.org/feedback since putting the feedback here is useless. Firefox developers collect data submitted through there then present it at the weekly Firefox meeting.
    There was a previous way by going through the Options menu but after disabling it through there, when you would go to Help > About Firefox, it would update regardless of that setting.
    You can set these prefs in <code>about:config</code> to disable automatic updating:<br>
    app.update.auto - false<br>
    app.update.enabled - false<br>
    app.update.silent - false<br>
    If you really wish to downgrade, you can do that through the [[Install an older version of Firefox]] link.<br>
    However, I recommend you try to use these add-ons to help customize 29. <br>
    Here are a few suggestions for restoring the old design. I hope you’ll find one that works for you:
    *Use the [https://addons.mozilla.org/en-US/firefox/addon/classicthemerestorer/ Classic Theme Restorer] to bring back the old design. Learn more here: [[How to make the new Firefox look like the old Firefox]]
    *Use the [https://addons.mozilla.org/en-US/firefox/addon/the-addon-bar/ Add-on Bar Restored] to bring back the add-on bar. Learn more here: [[What happened to the Add-on Bar?]]

  • Photos on ipad organized/dated.  when synched to computer they became jumbled/ with dates missing. How is it corrected/returned to prior format?

    Photos on ipad organized/dated.  When synched with computer they became jumbled
    /dated missing.  Now labeled "10impt".  How is it corrected?

    Photos on ipad organized/dated.  When synched with computer they became jumbled
    /dated missing.  Now labeled "10impt".  How is it corrected?

  • RMAN and database incarnations

    In experimenting with RMAN, I got our team into a situation where a test database would not restore and recover. I performed an incomplete recovery, opened resetlogs, and without performing a backup, did the same thing again.
    In any case, we started reading up on how to return to a previous database incarnation. We're not using a Recovery Catalog w RMAN, but 10g has been enhanced so that the control file now tracks db incarnations.
    We set the db incarnation back 2 previous, and then performed:
    RMAN> restore database until "to_date('9/2/04 23:59:59','mm/dd/yy hr24:mi:ss');
    RMAN> recover database until "to_date('9/2/04 23:59:59','mm/dd/yy hr24:mi:ss');
    and all seems well.
    I have 2 questions:
    1) Was the return back 2 incarnations really necessary? It seems like the database would've considered the 2 lines above an incomplete recovery and restore/recovered anyway.
    2) Do I need to manually remove the archive logs created for incarnations 3 & 4, or will RMAN know that they are not applicaable? And how does it know they're inapplicable, if so? The incarnation?
    Thanks for reading this looong question,
    Chuck

    In experimenting with RMAN, I got our team into a situation where a test database would not restore and recover. I performed an incomplete recovery, opened resetlogs, and without performing a backup, did the same thing again.
    In any case, we started reading up on how to return to a previous database incarnation. We're not using a Recovery Catalog w RMAN, but 10g has been enhanced so that the control file now tracks db incarnations.
    We set the db incarnation back 2 previous, and then performed:
    RMAN> restore database until "to_date('9/2/04 23:59:59','mm/dd/yy hr24:mi:ss');
    RMAN> recover database until "to_date('9/2/04 23:59:59','mm/dd/yy hr24:mi:ss');
    and all seems well.
    I have 2 questions:
    1) Was the return back 2 incarnations really necessary? It seems like the database would've considered the 2 lines above an incomplete recovery and restore/recovered anyway.
    2) Do I need to manually remove the archive logs created for incarnations 3 & 4, or will RMAN know that they are not applicaable? And how does it know they're inapplicable, if so? The incarnation?
    Thanks for reading this looong question,
    Chuck

  • Relationship between current incarnation & Backups/ RMAN-20011

    Hi
    I have
    the following situation in RMAN:
    Incarnations:
    >
    RMAN> list incarnation;
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    133 146 TESTDB 2528045035 PARENT 1 05-SEP-10
    133 134 TESTDB 2528045035 CURRENT 972274 02-MAR-11
    133 548 TESTDB 2528045035 ORPHAN 996374 02-MAR-11
    133 646 TESTDB 2528045035 ORPHAN 996490 04-MAR-11
    133 460 TESTDB 2528045035 ORPHAN 997986 02-MAR-11
    >
    Backups:
    >
    RMAN> list backup;
    List of Backup Sets
    ===================
    BS Key Size Device Type Elapsed Time Completion Time
    176 56.57M DISK 00:00:42 02-MAR-11
    BP Key: 177 Status: AVAILABLE Compressed: NO Tag: TAG20110302T100444
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/01m66vht_1_1
    List of Archived Logs in backup set 176
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 2 977121 02-MAR-11 988286 02-MAR-11
    1 3 988286 02-MAR-11 994189 02-MAR-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    187 Incr 0 999.72M DISK 00:15:42 02-MAR-11
    BP Key: 190 Status: AVAILABLE Compressed: NO Tag: TAG20110302T100531
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/02m66vjc_1_1
    List of Datafiles in backup set 187
    File LV Type Ckp SCN Ckp Time Name
    1 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/system01.dbf
    2 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/sysaux01.dbf
    3 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/undotbs01.dbf
    4 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/users01.dbf
    BS Key Size Device Type Elapsed Time Completion Time
    201 4.48M DISK 00:00:01 02-MAR-11
    BP Key: 206 Status: AVAILABLE Compressed: NO Tag: TAG20110302T102124
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/03m670h5_1_1
    List of Archived Logs in backup set 201
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 4 994189 02-MAR-11 996336 02-MAR-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    214 Full 9.36M DISK 00:00:10 02-MAR-11
    BP Key: 216 Status: AVAILABLE Compressed: NO Tag: TAG20110302T102129
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-00
    SPFILE Included: Modification time: 02-MAR-11
    SPFILE db_unique_name: TESTDB
    Control File Included: Ckp SCN: 996373 Ckp time: 02-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    244 757.50K DISK 00:00:01 02-MAR-11
    BP Key: 247 Status: AVAILABLE Compressed: NO Tag: TAG20110302T103137
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/05m67149_1_1
    List of Archived Logs in backup set 244
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 5 996336 02-MAR-11 997210 02-MAR-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    261 Incr 0 1001.02M DISK 00:13:29 02-MAR-11
    BP Key: 263 Status: AVAILABLE Compressed: NO Tag: TAG20110302T103138
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/06m6714b_1_1
    List of Datafiles in backup set 261
    File LV Type Ckp SCN Ckp Time Name
    1 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/system01.dbf
    2 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/sysaux01.dbf
    3 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/undotbs01.dbf
    4 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/users01.dbf
    BS Key Size Device Type Elapsed Time Completion Time
    279 742.00K DISK 00:00:01 02-MAR-11
    BP Key: 284 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104517
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/07m671tt_1_1
    List of Archived Logs in backup set 279
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 6 997210 02-MAR-11 997953 02-MAR-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    297 Full 9.36M DISK 00:00:10 02-MAR-11
    BP Key: 299 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104519
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-01
    SPFILE Included: Modification time: 02-MAR-11
    SPFILE db_unique_name: TESTDB
    Control File Included: Ckp SCN: 997985 Ckp time: 02-MAR-11
    BS Key  Size       Device Type Elapsed Time Completion Time
    *342 438.00K DISK 00:00:00 02-MAR-11*
    BP Key: 345   Status: AVAILABLE  Compressed: NO  Tag: TAG20110302T104935
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/09m67260_1_1
    List of Archived Logs in backup set 342
    Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
    *1 7 997953 02-MAR-11 998260 02-MAR-11*
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    *364 Incr 0 1001.65M DISK 00:14:34 02-MAR-11*
    BP Key: 366   Status: AVAILABLE  Compressed: NO  Tag: TAG20110302T104937
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1
    List of Datafiles in backup set 364
    File LV Type Ckp SCN    Ckp Time  Name
    *1 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/system01.dbf*
    *2 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/sysaux01.dbf*
    *3 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/undotbs01.dbf*
    *4 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/users01.dbf*
    BS Key  Size       Device Type Elapsed Time Completion Time
    *387 7.58M DISK 00:00:02 02-MAR-11*
    BP Key: 392   Status: AVAILABLE  Compressed: NO  Tag: TAG20110302T110421
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0bm6731m_1_1
    List of Archived Logs in backup set 387
    Thrd Seq     Low SCN    Low Time  Next SCN   Next Time
    *1 8 998260 02-MAR-11 1000465 02-MAR-11*
    BS Key  Type LV Size       Device Type Elapsed Time Completion Time
    *410 Full 9.36M DISK 00:00:10 02-MAR-11*
    BP Key: 412   Status: AVAILABLE  Compressed: NO  Tag: TAG20110302T110425
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02
    SPFILE Included: Modification time: 02-MAR-11
    SPFILE db_unique_name: TESTDB
    Control File Included: Ckp SCN: 1000507      Ckp time: 02-MAR-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    483 Full 9.36M DISK 00:00:05 02-MAR-11
    BP Key: 484 Status: AVAILABLE Compressed: NO Tag: TAG20110302T113759
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-03
    SPFILE Included: Modification time: 02-MAR-11
    SPFILE db_unique_name: TESTDB
    Control File Included: Ckp SCN: 998081 Ckp time: 02-MAR-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    571 Full 9.36M DISK 00:00:04 02-MAR-11
    BP Key: 572 Status: AVAILABLE Compressed: NO Tag: TAG20110302T121754
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-04
    SPFILE Included: Modification time: 02-MAR-11
    SPFILE db_unique_name: TESTDB
    Control File Included: Ckp SCN: 996489 Ckp time: 02-MAR-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    667 Full 9.36M DISK 00:00:18 04-MAR-11
    BP Key: 668 Status: AVAILABLE Compressed: NO Tag: TAG20110304T132050
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110304-00
    SPFILE Included: Modification time: 04-MAR-11
    SPFILE db_unique_name: TESTDB
    Control File Included: Ckp SCN: 996596 Ckp time: 04-MAR-11
    RMAN>
    >
    I want rebuild the Database with the Backup (bold text).
    And I get the error after executed the following script:
    >
    RMAN> RUN
    2> {
    3> # STARTUP NOMOUNT;
    4> # RESTORE SPFILE TO '/u01/app/oracle/product/11.2.0.2/db_1/dbs/spfileTESTDB.ora' from TAG "TAG20110302T063849";
    5> # SHUTDOWN IMMEDIATE;
    6> STARTUP NOMOUNT;
    7> RESTORE CONTROLFILE FROM TAG "TAG20110302T110425";
    8> STARTUP MOUNT;
    9> SET UNTIL SCN 1000507;
    10> RESTORE DATABASE;
    11> RECOVER DATABASE;
    12> ALTER DATABASE OPEN RESETLOGS;
    13> }
    database is already started
    Starting restore at 04-MAR-11
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: reading from backup piece /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02
    channel ORA_DISK_1: piece handle=/opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02 tag=TAG20110302T110425
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
    output file name=/CDATA/TESTDB/control01.ctl
    output file name=/CFLASH/TESTDB/control02.ctl
    Finished restore at 04-MAR-11
    database is already started
    database mounted
    released channel: ORA_DISK_1
    executing command: SET until clause
    Starting restore at 04-MAR-11
    Starting implicit crosscheck backup at 04-MAR-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=136 device type=DISK
    Crosschecked 11 objects
    Finished implicit crosscheck backup at 04-MAR-11
    Starting implicit crosscheck copy at 04-MAR-11
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 04-MAR-11
    searching for all files in the recovery area
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /CFLASH/TESTDB/archivelog/2011_03_04/o1_mf_1_1_6q1k25xs_.arc
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    channel ORA_DISK_1: restoring datafile 00001 to /CDATA/TESTDB/system01.dbf
    channel ORA_DISK_1: restoring datafile 00002 to /CDATA/TESTDB/sysaux01.dbf
    channel ORA_DISK_1: restoring datafile 00003 to /CDATA/TESTDB/undotbs01.dbf
    channel ORA_DISK_1: restoring datafile 00004 to /CDATA/TESTDB/users01.dbf
    channel ORA_DISK_1: reading from backup piece /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1
    channel ORA_DISK_1: piece handle=/opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1 tag=TAG20110302T104937
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:13:45
    Finished restore at 04-MAR-11
    Starting recover at 04-MAR-11
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 03/04/2011 13:47:17
    RMAN-06004: ORACLE error from recovery catalog database: RMAN-20011: target database incarnation is not current in recovery catalog
    >
    How can I know the right incarnation to reset current?
    Please , help
    reagards
    hqr200475
    Edited by: hqt200475 on 04.03.2011 06:19

    Hi Werner,
    I tried some experiments to find out the Relationship between current incarnations & Backups !
    Here is a listing 2 hours before with the incarnation 460:
    >
    RMAN> list incarnation;
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    133 146 TESTDB 2528045035 PARENT 1 05-SEP-10
    133 134 TESTDB 2528045035 PARENT 972274 02-MAR-11
    133 548 TESTDB 2528045035 ORPHAN 996374 02-MAR-11
    133 646 TESTDB 2528045035 ORPHAN 996490 04-MAR-11
    133 460 TESTDB 2528045035 CURRENT 997986 02-MAR-11
    RMAN> list backup;
    List of Backup Sets
    ===================
    BS Key Size Device Type Elapsed Time Completion Time
    176 56.57M DISK 00:00:42 02-MAR-11
    BP Key: 177 Status: AVAILABLE Compressed: NO Tag: TAG20110302T100444
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/01m66vht_1_1
    List of Archived Logs in backup set 176
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 2 977121 02-MAR-11 988286 02-MAR-11
    1 3 988286 02-MAR-11 994189 02-MAR-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    187 Incr 0 999.72M DISK 00:15:42 02-MAR-11
    BP Key: 190 Status: AVAILABLE Compressed: NO Tag: TAG20110302T100531
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/02m66vjc_1_1
    List of Datafiles in backup set 187
    File LV Type Ckp SCN Ckp Time Name
    1 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/system01.dbf
    2 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/sysaux01.dbf
    3 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/undotbs01.dbf
    4 0 Incr 994637 02-MAR-11 /CDATA/TESTDB/users01.dbf
    BS Key Size Device Type Elapsed Time Completion Time
    201 4.48M DISK 00:00:01 02-MAR-11
    BP Key: 206 Status: AVAILABLE Compressed: NO Tag: TAG20110302T102124
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/03m670h5_1_1
    List of Archived Logs in backup set 201
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 4 994189 02-MAR-11 996336 02-MAR-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    214 Full 9.36M DISK 00:00:10 02-MAR-11
    BP Key: 216 Status: AVAILABLE Compressed: NO Tag: TAG20110302T102129
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-00
    SPFILE Included: Modification time: 02-MAR-11
    SPFILE db_unique_name: TESTDB
    Control File Included: Ckp SCN: 996373 Ckp time: 02-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    244 757.50K DISK 00:00:01 02-MAR-11
    BP Key: 247 Status: AVAILABLE Compressed: NO Tag: TAG20110302T103137
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/05m67149_1_1
    List of Archived Logs in backup set 244
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 5 996336 02-MAR-11 997210 02-MAR-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    261 Incr 0 1001.02M DISK 00:13:29 02-MAR-11
    BP Key: 263 Status: AVAILABLE Compressed: NO Tag: TAG20110302T103138
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/06m6714b_1_1
    List of Datafiles in backup set 261
    File LV Type Ckp SCN Ckp Time Name
    1 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/system01.dbf
    2 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/sysaux01.dbf
    3 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/undotbs01.dbf
    4 0 Incr 997238 02-MAR-11 /CDATA/TESTDB/users01.dbf
    BS Key Size Device Type Elapsed Time Completion Time
    279 742.00K DISK 00:00:01 02-MAR-11
    BP Key: 284 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104517
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/07m671tt_1_1
    List of Archived Logs in backup set 279
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 6 997210 02-MAR-11 997953 02-MAR-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    297 Full 9.36M DISK 00:00:10 02-MAR-11
    BP Key: 299 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104519
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-01
    SPFILE Included: Modification time: 02-MAR-11
    SPFILE db_unique_name: TESTDB
    Control File Included: Ckp SCN: 997985 Ckp time: 02-MAR-11
    BS Key Size Device Type Elapsed Time Completion Time
    342 438.00K DISK 00:00:00 02-MAR-11
    BP Key: 345 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104935
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/09m67260_1_1
    List of Archived Logs in backup set 342
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 7 997953 02-MAR-11 998260 02-MAR-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    364 Incr 0 1001.65M DISK 00:14:34 02-MAR-11
    BP Key: 366 Status: AVAILABLE Compressed: NO Tag: TAG20110302T104937
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0am67261_1_1
    List of Datafiles in backup set 364
    File LV Type Ckp SCN Ckp Time Name
    1 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/system01.dbf
    2 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/sysaux01.dbf
    3 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/undotbs01.dbf
    4 0 Incr 998289 02-MAR-11 /CDATA/TESTDB/users01.dbf
    BS Key Size Device Type Elapsed Time Completion Time
    387 7.58M DISK 00:00:02 02-MAR-11
    BP Key: 392 Status: AVAILABLE Compressed: NO Tag: TAG20110302T110421
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/DATA/0bm6731m_1_1
    List of Archived Logs in backup set 387
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 8 998260 02-MAR-11 1000465 02-MAR-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    410 Full 9.36M DISK 00:00:10 02-MAR-11
    BP Key: 412 Status: AVAILABLE Compressed: NO Tag: TAG20110302T110425
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-02
    SPFILE Included: Modification time: 02-MAR-11
    SPFILE db_unique_name: TESTDB
    Control File Included: Ckp SCN: 1000507 Ckp time: 02-MAR-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    483 Full 9.36M DISK 00:00:05 02-MAR-11
    BP Key: 484 Status: AVAILABLE Compressed: NO Tag: TAG20110302T113759
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-03
    SPFILE Included: Modification time: 02-MAR-11
    SPFILE db_unique_name: TESTDB
    Control File Included: Ckp SCN: 998081 Ckp time: 02-MAR-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    571 Full 9.36M DISK 00:00:04 02-MAR-11
    BP Key: 572 Status: AVAILABLE Compressed: NO Tag: TAG20110302T121754
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110302-04
    SPFILE Included: Modification time: 02-MAR-11
    SPFILE db_unique_name: TESTDB
    Control File Included: Ckp SCN: 996489 Ckp time: 02-MAR-11
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    667 Full 9.36M DISK 00:00:18 04-MAR-11
    BP Key: 668 Status: AVAILABLE Compressed: NO Tag: TAG20110304T132050
    Piece Name: /opt/BACKUP/11.2.0.2/RMAN/TESTDB/CONTROLFILES/c-2528045035-20110304-00
    SPFILE Included: Modification time: 04-MAR-11
    SPFILE db_unique_name: TESTDB
    Control File Included: Ckp SCN: 996596 Ckp time: 04-MAR-11
    RMAN> @TESTDB_rr.rman
    RMAN> RUN
    2> {
    3> # STARTUP NOMOUNT;
    4> # RESTORE SPFILE TO '/u01/app/oracle/product/11.2.0.2/db_1/dbs/spfileTESTDB.ora' from TAG "TAG20110302T063849";
    5> # SHUTDOWN IMMEDIATE;
    6> STARTUP NOMOUNT;
    7> RESTORE CONTROLFILE FROM TAG "TAG20110302T110425";
    8> STARTUP MOUNT;
    9> SET UNTIL SCN 1000507;
    10> RESTORE DATABASE;
    11> RECOVER DATABASE;
    12> ALTER DATABASE OPEN RESETLOGS;
    13> }
    database is already started
    Starting restore at 04-MAR-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=12 device type=DISK
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 03/04/2011 13:29:58
    RMAN-06026: some targets not found - aborting restore
    RMAN-06024: no backup or copy of the control file found to restore
    RMAN> **end-of-file**
    RMAN> list incarnation;
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    133 146 TESTDB 2528045035 PARENT 1 05-SEP-10
    133 134 TESTDB 2528045035 PARENT 972274 02-MAR-11
    133 548 TESTDB 2528045035 ORPHAN 996374 02-MAR-11
    133 646 TESTDB 2528045035 ORPHAN 996490 04-MAR-11
    133 460 TESTDB 2528045035 CURRENT 997986 02-MAR-11
    >
    regards
    hqt200475

  • RMAN INCARNATIONS

    HI,
    in RMAN ( 8i) restore log I have this erroe :
    RMAN> run
    2> {
    3> set until time "TO_DATE( '26/04/2007 13:00:00', 'MM/DD/YYYY
    4> HH24:MI:SS' )";
    8> }
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: set
    RMAN-06004: ORACLE error from recovery catalog database: RMAN-20003: target database incarnation not found in recovery catalog
    How should I do to find available incarnations with DATE TIME ?
    Many thanks.

    The goal it is marked for your backup is going far beyond of the available backups. Was this database cloned? On the other hand there is no backup available to meet the criteria you have set at the beginning.
    Post the output of the command:
    LIST INCARNATION OF DATABASE;
    and
    LIST BACKUP;

  • Problem with time based rman recovery

    Hi and happy boxing day:
    I am following by the letter the instructions in Sybex FundamentalsII book p.348 regarding an rman time based recovery. Here is the syntax:
    RMAN> run {
    2> allocate channel ch1 type disk;
    3> set until time 'DEC 26 2007 10:30:00';
    4> restore database;
    5> recover database;
    6> sql 'alter database open resetlogs';
    7> }
    and here is the error:
    allocated channel: ch1
    channel ch1: sid=11 devtype=DISK
    executing command: SET until clause
    released channel: ch1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of set command at 12/26/2007 11:06:45
    ORA-01858: a non-numeric character was found where a numeric was expected
    Is this a format issue? Any tips please!
    Thanks,
    DA

    You can only register a database once if you are using a recovery catalog, so whoever or whatever told you to re-register is simply getting their terminology in a knot!
    There **is** a sort-of "re-register" command which does sometimes need to be issued after a resetlogs: it's called a RESET command. See http://tinyurl.com/29t5lr for details. A "reset" is, effectively, a "re-register".
    One of the details you will see is that you only need to do a manual reset if it was **you** that issued a resetlogs, outside of RMAN. If you get RMAN to do the resetlogs, however, then there's no need to also issue the reset command, because RMAN already knows about it (and has already updated its own metadata accordingly).
    The other thing you'll notice from the documentation is that if you aren't using a recovery catalog then the concept of issuing a reset is entirely redundant. That's because you can't recover to a prior incarnation of the database without a catalog: it's one of the main reasons for wanting to run in catalog mode in the first place. No catalog = no ability to step through incarnations = no need to inform RMAN that you're in a new incarnation.

  • ORA-19909 orphan incarnation

    Gurus -
    I need your help....I'm creating a development database for user testing. I put PROD in hotbackup mode, copy the db and arch files to development server. After creating the controlfile for the dev database attempt to recover database until cancel using backup controlfile and get the error message ora-19909. I did an alter database backup controfile to trace. used the generated controlfile from the trace file attempted to do the recover database until cancel using backup controlfile and got the same message (ora-19909).
    Only thing that change since the last refresh was an additional of a datafile in PROD. We have used this same method for 2 years with out error, what could be wrong and how to resolve this??

    882424 wrote:
    Gurus -
    I need your help....I'm creating a development database for user testing. I put PROD in hotbackup mode, copy the db and arch files to development server. After creating the controlfile for the dev database attempt to recover database until cancel using backup controlfile and get the error message ora-19909. I did an alter database backup controfile to trace. used the generated controlfile from the trace file attempted to do the recover database until cancel using backup controlfile and got the same message (ora-19909).
    Only thing that change since the last refresh was an additional of a datafile in PROD. We have used this same method for 2 years with out error, what could be wrong and how to resolve this??
    19909, 00000, "datafile %s belongs to an orphan incarnation"
    // *Cause: Either the specified datafile was restored from a backup that was
    //         taken during a period of time that has already been discarded by
    //         a RESETLOGS operation, or Oracle cannot identify which database
    //         incarnation the file belongs to.  The alert log contains more
    //         information.
    // *Action: Restore a backup of this file that belongs to either the current
    //          or a prior incarnation of the database.  If you are using RMAN
    //          to restore, RMAN will automatically select a correct backup.you are doing something wrong; either error of commission or error of omission;
    but since we can't see exactly what you did specific solution is not possible

  • RESTORE VALIDATE possible prior to an OPEN RESETLOGS?

    Is it possible to perform a RESTORE VALIDATE to a point in time prior to an OPEN RESETLOGS?
    RMAN> list incarnation;
    List of Database Incarnations
    DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
    1       1       AA02     2787653425       PARENT  1          29.FEB.2008 15:56:3
    3
    2       2       AA02     2787653425       CURRENT 182455     29.FEB.2008 16:55:5
    5
    RMAN> run
    2> {
    3> set until time = "to_date('29.FEB.2008 16:00:00','DD.MON.YYYY HH24:MI:SS')";
    4> restore database validate;
    5> }
    executing command: SET until clause
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of set command at 06/11/2009 11:13:35
    RMAN-20207: UNTIL TIME or RECOVERY WINDOW is before RESETLOGS timeUsing the RESET DATABASE TO INCARNATION clause it should be possible to perform the RESTORE however that is not the intention (yet), only to RESTORE VALIDATE.

    That's what I'm finding... I don't want to have to restart the database to reset the incarnation to have to test restore a backup prior to open resetlogs (no catalog only controlfile used).
    "If RMAN is connected NOCATALOG, then you can only specify TO INCARNATION if the database is mounted and the control file contains a record of the prior incarnation. If you do not run RESET DATABASE, RMAN recovers to the last incarnation recorded in the control file."
    http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta050.htm
    Yet another reason to have a RMAN catalog.

  • Need inputs on RMAN Backup n Recovery for multiple restore of clean backup

    I will explain my scenario below:
    We have the requirement of performance testing of our proposed production platform, for this i am asked to take RMAN backup of clean position (Say Day0 or baseline backup) and restore it multiple times for few rounds of testing. My question is after 1st restore (with set until time of day0 position) if i open the database with resetlogs, would i be able to restore same clean backup again? I am using control file in the environment instead of RMAN catalog database. What i can do to make this scenario work? I am already in preperation of setting rman catalog database.
    Please suggest me the best way forward...
    Many Thanks
    Nukesh

    Hi Asif,
    I tried to make it work but seems there are still issue with my recovery, can you have a look and point out the shortcommings. i am totally lost here
    RMAN> list incarnation;
    using target database control file instead of recovery catalog
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    1 1 MYTEST 2433328848 PARENT 1 19-DEC-06
    2 2 MYTEST 2433328848 PARENT 564488 04-NOV-10
    3 3 MYTEST 2433328848 CURRENT 693719 06-NOV-10
    RMAN> exit
    TEST1DB-> rman target sys@MYTEST1
    Recovery Manager: Release 10.2.0.3.0 - Production on Sun Nov 7 11:43:01 2010
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    target database Password:
    connected to target database: MYTEST (DBID=2433328848, not open)
    RMAN> reset database to incarnation 2;
    using target database control file instead of recovery catalog
    database reset to incarnation 2
    RMAN> run {
    2> restore database until scn 10000;
    3> recover database until scn 10000;
    4> alter database open resetlogs;
    5> };
    Starting restore at 07-NOV-10
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=191 instance=MYTEST1 devtype=DISK
    allocated channel: ORA_DISK_2
    channel ORA_DISK_2: sid=190 instance=MYTEST1 devtype=DISK
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 11/07/2010 11:45:18
    RMAN-20208: UNTIL CHANGE is before RESETLOGS change
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found ";": expecting one of: "allocate, alter, backup, beginline, blockrecover, catalog, change, c onnect, copy, convert, create, crosscheck, configure, duplicate, debug, delete, drop, exit, endinline, flashback, host, {, l ibrary, list, mount, open, print, quit, recover, register, release, replace, report, renormalize, reset, restore, resync, rm an, run, rpctest, set, setlimit, sql, switch, spool, startup, shutdown, send, show, test, transport, upgrade, unregister, va lidate"
    RMAN-01007: at line 0 column 2 file: standard input
    RMAN>
    RMAN> show all;
    RMAN configuration parameters are:
    CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
    CONFIGURE BACKUP OPTIMIZATION OFF; # default
    CONFIGURE DEFAULT DEVICE TYPE TO DISK;
    CONFIGURE CONTROLFILE AUTOBACKUP ON;
    CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '/rmanbackup/MYTEST/ora_cf%F';
    CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
    CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
    CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/rmanbackup/MYTEST/ora_df%t_s%s_s%p';
    CONFIGURE MAXSETSIZE TO UNLIMITED; # default
    CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
    CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
    CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
    CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10g/dbs/snapcf_MYTEST1.f'; # default
    RMAN> exit
    SQL> select name from v$database;
    NAME
    MYTEST
    SQL> show parameter CONTROL_FILE_RECORD_KEEP_TIME
    NAME TYPE VALUE
    control_file_record_keep_time integer 7
    SQL>

  • RMAN Active Database error

    Hello Team,
    I was doing ACTIVE DATABASE CLONING WHEN I NOTICED THIS ERROR:-
    released channel: t15
    released channel: t16
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 10/10/2012 18:50:41
    RMAN-05501: aborting duplication of target database
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-11003: failure during parse/execution of SQL statement: alter database recover logfile '/dupp3db/arch/dup3_1_145_794494895.arc'
    ORA-10877: error signaled in parallel recovery slave
    I went through a notr in metalink ( ID 1098638.1), but didn't able to resolve it not able to undetstand. Please suggest

    rman> list incarnation;
    rman> RESET DATABASE TO INCARNATION <x>;
    *X is the correct incarnation                                                                                                                                                                                                   

  • RMAN error while allocating channels

    Hi
    We are trying to backup Oracle 11gr2 database using RMAN. The MML is provided by the vendor and we have linked the library with libobk.so. The server OS is Solaris 10 64 bit on AMD64 architecture.
    When we try to run backup the RMAN returns with the error
    "failed to load media management library".
    sbttest returns with the following error
    "ld.so.1: sbttest: fatal: /oracle/app/oracle/product/11.2.0/dbhome_1/lib/libobk.so: wrong ELF data format: ELFDATA2MSB"
    Can anyone help us in resolving the issue.
    Thanks in advance
    Dinesh Sakhuja
    Edited by: user13711883 on 24 Feb, 2012 4:50 AM

    Wrong forum.
    {forum:id=74}

  • About database incarnations in catalog versus non-catalog

    Hi all
    Listing out the incarnations of my target database when not connected to the recovery catalog :
    RMAN> list incarnation of database testdb;
    using target database control file instead of recovery catalog
    List of Database Incarnations
    DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
    1       1       TESTDB   2539541829       PARENT  1          11-JUL-11
    2       2       TESTDB   2539541829       PARENT  591584     12-JUL-11
    3       3       TESTDB   2539541829       PARENT  2061948    19-JUL-11
    4       4       TESTDB   2539541829       ORPHAN  1345130669 13-MAY-13
    5       5       TESTDB   2539541829       CURRENT 1345130669 15-MAY-13And listing out the incarnations when connected to the catalog:
    RMAN> list incarnation of database testdb;
    List of Database Incarnations
    DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
    1178485 1178523 TESTDB   2539541829       PARENT  1          11-JUL-11
    1178485 1178524 TESTDB   2539541829       PARENT  591584     12-JUL-11
    1178485 1178525 TESTDB   2539541829       PARENT  2061948    19-JUL-11
    1178485 1178526 TESTDB   2539541829       ORPHAN  1345130669 13-MAY-13
    1178485 1178486 TESTDB   2539541829       CURRENT 1345130669 15-MAY-13Why are INC KEY numbers not matching? Is this a bug or is it expected behaviour?
    Please help me shed some light on this..
    Thanks.

    Hi,
    Manual said:
    DB Key- When combined with the Inc Key, the unique key by which RMAN identifies the database incarnation in the recovery catalog. Use this key to unregister a database from a recovery catalog, that is, delete all the rows associated with that database from the recovery catalog.
    INC Key- When combined with DB Key, the unique key by which RMAN identifies the database incarnation in the recovery catalog. Use this key in RESET DATABASE TO INCARNATION when recovering the database to a time before the most recent RESETLOGS.
    <<http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsynta027.htm#CHDGGAFF>>
    recovery-catalog and control file-catalog is a catalog of different, So not match.
    Regards,

Maybe you are looking for

  • Class architecture question

    I am coming from a c++ world into objective-c++/cocoa. I work for a company that sells static libraries to be used by other developers. Distributed with these libraries are, of course, the header files. Currently, I am tasked with adding cocoa suppor

  • The Origin of Random iChat video failu

    I hope this topic gets a lot of response and reply from as many people as we can get involved. If you are like me you have been using iChat more of less happily for some months and then suddenly all **** breaks loose and you cannot initiate chats wit

  • Static input help for DATS type

    Hello, I'd like to link static input help for screen field of DATS type. If I click on help linked to this screen field I get CONVT_NO_NUMBER error: 'Unable to interpret "=2" as a number.' My steps: - In Screen Painter I selected desired screen field

  • Display traditional chinese

    Hi I am now trying to use the JavaTV RI 1.1 which is just released. The RI uses a XML file as it's SI source and parse the file to create standard object which is specified in the JavaTV API for application to read SI. One of the main difference betw

  • Getting Kicked off of My Own WiFi Network

    I've been having trouble for awhile now that I will be kicked off of my own wifi network. It will then not recognize the password (which is saved to app, 1Password) for several minutes, saying its incorrect, before finally reconnecting. I don't know