RMAN recover

Hi all,
I have cluster database with 2 instnaces oracle 10g version.
I restored database and then trying to recover it now. But it is saying
released channel: T1
released channel: T2
released channel: T3
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 01/13/2013 06:25:09
RMAN-06053: unable to perform media recovery because of missing log
RMAN-06025: no backup of log thread 2 seq 112561 lowscn 27183166476 found to restore
RMAN-06025: no backup of log thread 2 seq 112560 lowscn 27183156285 found to restore
RMAN-06025: no backup of log thread 2 seq 112559 lowscn 27183144555 found to restore
RMAN-06025: no backup of log thread 2 seq 112558 lowscn 27183129592 found to restore
RMAN-06025: no backup of log thread 2 seq 112557 lowscn 27183110956 found to restore
RMAN-06025: no backup of log thread 1 seq 38877 lowscn 27183144574 found to restore
RMAN-06025: no backup of log thread 1 seq 38876 lowscn 27183093707 found to restore
RMAN> exit
on both the nodes i have archives redos are available.
I want to open db with noresetlogs option.
could you please suggest for this..
thanks

A couple of thoughts in no particular order.
1. What is your version number ... 10g is a marketing label not a version number.
2. Have you verified the files are where Oracle is looking? The files may be on a drive where you can see them but is that where Oracle is looking?
3. Have you opened an SR with Oracle and if not why not?
4. What went wrong that is causing you to want to restore the system and perform a reset. Please provide full details and exceptions.

Similar Messages

  • Rman recover noredo vs. until cancel

    Hi,
    Oracle 11g 11.2.0.1
    What is the difference please between rman +recover noredo+ and +recover until cancel+ ?
    According to Oracle documentation, noredo can be used if the database is in noarchvielog mode and the online redo logs are lost. Does this mean it actually does not apply the archvielogs, even if available? Is this the difference from recover until cancel ?
    Also, why do I need to run recvover until cancel using backup controlfile from SQL, and cannot use RMAN, which does not understand this command?
    Thanks.

    According to Oracle documentation, noredo can be used if the database is in noarchvielog mode and the online redo logs are lost. Does this mean it >actually does not apply the archvielogs, even if available? Is this the difference from recover until cancel ?If database is in NOARCHIVE mode, there are NO archivelogs to apply!

  • RMAN recover on a different server - Verify all changes are applied

    Hey everyone,
    I have two database servers, Oracle 10g SE on linux. One is the 'primary', and we plan to switchover to the other newer server. In order to minimize the downtime from a duplicate database, or a full backup and restore/recover, I restored the database to the newer server using RMAN, and just continuously apply the archivelogs generated from the original database through RMAN> recover database;.
    My question is, at the time when we do do the switchover, how can I ensure that all changes in the database are written to the archivelogs? I understand I can do a 'alter system switch archivelog' until all groups are inactive, but will this be enough? I've noticed that when I force an archivelog switch, the previous group still has an 'ACTIVE' status, even though I thought that the ARC process had just written out all the changes from that redo log to the archivelog?
    Any help would be much appreciated. Thanks

    Dear oscrub,
    You can compare the system change numbers on both databases and you can also use the standby redo log files for synchronized data replication with the maximum availability or maximum protection protection levels.
    I you don't want to see the archivelog as ACTIVE state you need to run the following command;
    SQL> ALTER SYSTEM CHECKPOINT GLOBAL;You will manually trigger the checkpoint and the data in the redolog (active one) will be written to the database thanks to the database writer processes. With that way, you won't see the online redo log as ACTIVE state. You will see online redologs as "CURRENT" and "INACTIVE".
    I hope that addresses your questions.
    Regards.
    Ogan

  • RMAN Recover database error..

    Hi All,
    We were trying to restore and recover one of our databases. The restore went well but the recover is erroring out. Can someone please let us know what we should do to remedy this and carry on with the recovery.
    We got an error when we were trying to restore the controlfile at the begining (details below), but as you can see, it did manage to restore a copy of the controlfile successfully..
    Details below.
    C:\Users\oracle>rman target system/XXXX catalog rman/XXXX@rmancat
    Recovery Manager: Release 11.1.0.7.0 - Production on Thu Dec 2 08:31:03 2010
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: CODP (not mounted)
    connected to recovery catalog database
    RMAN> set dbid=2399577932
    executing command: SET DBID
    database name is CODP and DBID is 2399577932
    RMAN> RESTORE CONTROLFILE;
    Starting restore at 02-DEC-10
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=152 device type=DISK
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\CONTROLFILE_BKUP_CODP_C-2399577932-20101201-00
    channel ORA_DISK_1: "ORA-19870: error while restoring backup piece D:\RMAN\CODP\CONTROLFILE_BKUP_CODP_C-2399577932-20101201-00"
    "ORA-19505: failed to identify file D:\RMAN\CODP\CONTROLFILE_BKUP_CODP_C-2399577932-20101201-00"
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    failover to previous backup
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_DULUG8H9_1_1
    channel ORA_DISK_1: "ORA-19870: error while restoring backup piece D:\RMAN\CODP\BKUP_CODP_DULUG8H9_1_1"
    "ORA-19505: failed to identify file D:\RMAN\CODP\BKUP_CODP_DULUG8H9_1_1"
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 2) The system cannot find the file specified.
    failover to previous backup
    channel ORA_DISK_1: starting datafile backup set restore
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\CONTROLFILE_BKUP_CODP_C-2399577932-20101130-01
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\CONTROLFILE_BKUP_CODP_C-2399577932-20101130-01 tag=TAG20101130T204059
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
    output file name=C:\ORACLE\ORADATA\CONTROLFILE\CODP\CONTROL01.CTL
    output file name=D:\ORACLE\ORADATA\CONTROLFILE\CODP\CONTROL02.CTL
    output file name=D:\ORACLE\ORADATA\CODP\CONTROL03.CTL
    Finished restore at 02-DEC-10
    RMAN> RESTORE SPFILE FROM AUTOBACKUP;
    Starting restore at 02-DEC-10
    using channel ORA_DISK_1
    recovery area destination: D:\oracle\flash_recovery_area\
    database name (or database unique name) used for search: CODP
    channel ORA_DISK_1: no AUTOBACKUPS found in the recovery area
    channel ORA_DISK_1: looking for AUTOBACKUP on day: 20101202
    channel ORA_DISK_1: looking for AUTOBACKUP on day: 20101201
    channel ORA_DISK_1: looking for AUTOBACKUP on day: 20101130
    channel ORA_DISK_1: AUTOBACKUP found: D:\RMAN\CODP\controlfile_bkup_CODP_c-2399577932-20101130-01
    channel ORA_DISK_1: restoring spfile from AUTOBACKUP D:\RMAN\CODP\controlfile_bkup_CODP_c-2399577932-20101130-01
    channel ORA_DISK_1: SPFILE restore from AUTOBACKUP complete
    Finished restore at 02-DEC-10
    RMAN> restore database;
    Starting restore at 02-DEC-10
    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 00020 to D:\ORACLE\ORADATA\CODP\VCLLOAD_T1.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_56LU9C9M_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_56LU9C9M_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:02:45
    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 00002 to D:\ORACLE\ORADATA\CODP\UNDOTBS01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_57LU9CFQ_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_57LU9CFQ_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:03:25
    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 00009 to D:\ORACLE\ORADATA\CODP\PROD_T3_NEW_02.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_58LU9CMS_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_58LU9CMS_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:55
    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 00010 to D:\ORACLE\ORADATA\CODP\PROD_T3_NEW_03.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_59LU9CR4_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_59LU9CR4_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:55
    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 D:\ORACLE\ORADATA\CODP\SYSTEM01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5ALU9CV2_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5ALU9CV2_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:45
    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 00005 to D:\ORACLE\ORADATA\CODP\PROD_T1_NEW_01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5BLU9D0P_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5BLU9D0P_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:15
    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 00006 to D:\ORACLE\ORADATA\CODP\PROD_T2_NEW_01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5CLU9D1J_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5CLU9D1J_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:45
    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 00007 to D:\ORACLE\ORADATA\CODP\PROD_T3_NEW_01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5DLU9D4T_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5DLU9D4T_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:55
    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 00025 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_02.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5ELU9D79_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5ELU9D79_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:36
    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 00024 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5FLU9DAI_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5FLU9DAI_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:35
    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 00026 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_03.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5GLU9DDI_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5GLU9DDI_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:35
    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 00027 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_04.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5HLU9DGU_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5HLU9DGU_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:35
    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 00011 to D:\ORACLE\ORADATA\CODP\PROD_I3_16K_02.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5ILU9DJT_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5ILU9DJT_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:35
    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 00030 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_07.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5JLU9DN8_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5JLU9DN8_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:46
    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 00028 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_05.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5KLU9DOV_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5KLU9DOV_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:45
    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 00029 to D:\ORACLE\ORADATA\CODP\PREV_PR_CODP_06.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5LLU9DQO_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5LLU9DQO_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:45
    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 00003 to D:\ORACLE\ORADATA\CODP\SYSAUX01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5MLU9DSF_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5MLU9DSF_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:25
    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 00008 to D:\ORACLE\ORADATA\CODP\PROD_I2_16K_03.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5NLU9DT9_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5NLU9DT9_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:35
    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 00032 to D:\ORACLE\ORADATA\CODP\PROD_I2_16K_01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5OLU9DUN_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5OLU9DUN_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:55
    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 00033 to D:\ORACLE\ORADATA\CODP\PROD_I2_16K_02.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5PLU9E0P_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5PLU9E0P_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:05
    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 00034 to D:\ORACLE\ORADATA\CODP\PROD_I3_16K_01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_5QLU9E3F_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_5QLU9E3F_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:45
    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 00031 to D:\ORACLE\ORADATA\CODP\PROD_I1_16K_01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_8QLU9ES2_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_8QLU9ES2_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:35
    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 00004 to D:\ORACLE\ORADATA\CODP\USERS01.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_8SLU9ET9_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_8SLU9ET9_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
    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 00021 to D:\ORACLE\ORADATA\CODP\VCLLOAD_T2.DBF
    channel ORA_DISK_1: reading from backup piece D:\RMAN\CODP\BKUP_CODP_8ULU9ETF_1_1
    channel ORA_DISK_1: piece handle=D:\RMAN\CODP\BKUP_CODP_8ULU9ETF_1_1 tag=LEVEL0_TUE
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
    Finished restore at 02-DEC-10
    RMAN> recover database;
    Starting recover at 02-DEC-10
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 12/02/2010 09:08:05
    ORA-00210: cannot open the specified control file
    RMAN>Thanks

    Sorry everyone.. My bad.. I forgot to MOUNT the instance before trying to use the RECOVER DATABASE command.
    Thanks

  • What order are Archive logs restored in when RMAN recover database issued

    Ok, you have a run block that has restored your level-0 RMAN backup.
    Your base datafiles are down on disc.
    You are about to start recovery to point in time, lets say until this morning at 07:00am.
    run {   set until time "TO_DATE('2010/06/08_07:00:00','YYYY/MM/DD_HH24:MI:SS')";
    allocate channel d1 type disk;
    allocate channel d2 type disk;
    allocate channel d3 type disk;
    allocate channel d4 type disk;
    recover database;
    So the above runs, it analyses the earlies SCN required for recovery, checks for incremental backups (none here), works out the archivelog range
    required and starts to restore the archive logs. All as expected and works.
    My question: Is there a particular order that RMAN will restore the archive logs and is the restore / recover process implemented as per the run block.
    i.e Will all required archive logs based on the run block be restored and then the database recovered forward. Or is there something in RMAN that says restore these archive logs, ok now roll forwards, restore some more.
    When we were doing this the order of the archive logs coming back seemed to be random but obviously constrained by the run block. Is this an area we need to tune to get recoveries faster for situations where incrementals are not available?
    Any inputs on experience welcome. I am now drilling into the documentation for any references there.
    Thanks

    Hi there, thanks for the response I checked this and here are the numbers / time stamps on an example:
    This is from interpreting the list backup of archivelog commands.
    Backupset = 122672
    ==============
    Archive log sequence 120688 low time: 25th May 15:53:07 next time: 25th May 15:57:54
    Piece1 pieceNumber=123368 9th June 04:10:38 <-- catalogued by us.
    Piece2 pieceNumber=122673 25th May 16:05:18 <-- Original backup on production.
    Backupset = 122677
    ==============
    Archive log sequence 120683 low time: 25th May 15:27:50 Next time 25th May 15:32:24 <-- lower sequence number restored after above.
    Piece1 PieceNumber=123372 9th June 04:11:34 <-- Catalogued by us.
    Piece2 PieceNumber=122678 25th May 16:08:45 <-- Orignial backup on Production.
    So the above would show that if catalogue command you could influence the Piece numbering. Therefore the restore order if like you say piece number is the key. I will need to review production as to why they were backed up in different order completed on production. Would think they would use the backupset numbering and then piece within the set / availability.
    Question: You mention archive logs are restored and applied and deleted in batches if the volume of archivelogs is large enough to be spread over multiple backup sets. What determines the batches in terms of size / number?
    Thanks for inputs. Answers some questions.

  • Question:rman recover (error:Bad header found during inspecting archived )

    oracle9208 aix5.2
    after restore database successfully,i recover database
    i receive info in alert_sid.log
    Corrupt block seq: 0 blocknum=1.
    Bad header found during inspecting archived log
    Data in bad block - seq:184680448. bno:369098753. time:0
    beg:0 cks:260
    calculated check value: 2653
    Reread of seq=0, blocknum=1, file=/dev/rora_redo1_21, found same corrupt data
    alter database recover datafile list
    161 , 162 , 163 , 164 , 165 , 166 , 167 , 168
    Completed: alter database recover datafile list
    161 , 162 ,
    Fri Nov 6 22:37:17 2009
    alter database recover if needed
    start until time 'NOV 01 2009 21:07:53' using backup controlfile
    Media Recovery Start
    ORA-279 signalled during: alter database recover if needed
    start until time...
    then recover processes hang for a long time
    so why and how can i solve this problem??

    Dear user097815,
    I think there are a couple of syntax errors and it would be better for you to first try each one one-by-one than add them into your "run" block.
    RMAN> allocate channel for maintenance device type 'SBT_TAPE';
    using target database control file instead of recovery catalog
    allocated channel: ORA_MAINT_SBT_TAPE_1
    channel ORA_MAINT_SBT_TAPE_1: sid=910 devtype=SBT_TAPE
    channel ORA_MAINT_SBT_TAPE_1: Data Protector A.06.10/611
    RMAN> allocate auxiliary channel t1 type 'sbt_tape';
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found "auxiliary": expecting one of: "channel"
    RMAN-01007: at line 1 column 10 file: standard input
    RMAN> ALLOCATE AUXILIARY CHANNEL c1 DEVICE TYPE sbt;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00558: error encountered while parsing input commands
    RMAN-01009: syntax error: found "auxiliary": expecting one of: "channel"
    RMAN-01007: at line 1 column 10 file: standard input
    RMAN> run
    ALLOCATE AUXILIARY CHANNEL c1 DEVICE TYPE sbt;
    }Hope That Helps.
    Ogan

  • RMAN - Recover dropped tablespace

    I'm kinda new to RMAN. I took full backup using RMAN in archivelog mode database. No RMAN catalog created. I dropped a tablespace using 'including contents and datafiles'. When i try to restore and recover th edropped tablespacespace, i get the following error message.
    RMAN> restore datafile 8;
    Starting restore at 12-MAY-06
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=143 devtype=DISK
    RMAN-00571: ================================================
    RMAN-00569: === ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================
    RMAN-03002: failure of restore command at 05/12/2006 13:11:03
    RMAN-20201: datafile not found in the recovery catalog
    RMAN-06010: error while looking up datafile: 8
    RMAN> restore tablespace staging;
    Starting restore at 12-MAY-06
    using channel ORA_DISK_1
    RMAN-00571: ================================================
    RMAN-00569: ======= ERROR MESSAGE STACK FOLLOWS
    RMAN-00571: ============================================
    RMAN-03002: failure of restore command at 05/12/2006 13:20:15
    RMAN-20202: tablespace not found in the recovery catalog
    RMAN-06019: could not translate tablespace name "STAGING"
    This is the backlist from RMAN -
    =======================================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    9 Full 12.99G DISK 00:11:42 02-MAY-06
    BP Key: 9 Status: AVAILABLE Compressed: NO Tag: TAG20060502T150458
    Piece Name: /oraback/rman_bkups/DCDB_t589388698_s11_p1
    List of Datafiles in backup set 9
    File LV Type Ckp SCN Ckp Time Name
    1 Full 14757459 02-MAY-06 /oradata/DCDB/datafile/o1_mf_system_21cw54nf_.dbf
    2 Full 14757459 02-MAY-06 /oradata/DCDB/datafile/o1_mf_undotbs1_21cw54pq_.dbf
    3 Full 14757459 02-MAY-06 /oradata/DCDB/datafile/o1_mf_sysaux_21cw54nn_.dbf
    4 Full 14757459 02-MAY-06 /oradata/DCDB/datafile/o1_mf_users_21cw54q4_.dbf
    5 Full 14757459 02-MAY-06 /oradata/DCDB/datafile/o1_mf_dc_data1_21kfd05y_.dbf
    6 Full 14757459 02-MAY-06 /oradata/DCDB/datafile/o1_mf_dc_index_21kfhx45_.dbf
    7 Full 14757459 02-MAY-06 /oradata/DCDB/datafile/o1_mf_undotbs1_21mkohp6_.dbf
    8 Full 14757459 02-MAY-06
    10 Full 14757459 02-MAY-06 /oradata/DCDB/datafile/o1_mf_sysaux_21lbznyy_.dbf
    11 Full 14757459 02-MAY-06 /oradata/DCDB/datafile/o1_mf_system_21lc61wl_.dbf
    12 Full 14757459 02-MAY-06 /oradata/DCDB/datafile/o1_mf_ddb_data_21mmsbk2_.dbf
    13 Full 14757459 02-MAY-06 /oradata/DCDB/datafile/o1_mf_ddb_inde_21mmvx07_.dbf
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    10 Full 7.11M DISK 00:00:02 02-MAY-06
    BP Key: 10 Status: AVAILABLE Compressed: NO Tag: TAG20060502T150458
    Piece Name: /oraback/rman_bkups/DCDB_t589389403_s12_p1
    Control File Included: Ckp SCN: 14757761 Ckp time: 02-MAY-06
    SPFILE Included: Modification time: 02-MAY-06
    ===================================
    Thanks
    ~Ash

    RMAN-03002: failure of restore command at 05/12/2006 13:11:03RMAN-20201: datafile not found in the recovery catalogRMAN-06010: error while looking up datafile: 8
    RMAN-20202: tablespace not found in the recovery catalog
    I took full backup using RMAN in archivelog mode database. No RMAN catalog created.As you said "Recovery Catalog is not configured" but its prompting for Recovery Catalog!
    Try This % ORACLE_SID=trgt; export ORACLE_SID #trgt means your target database
    % rman TARGET / NOCATALOG
    hope it should work
    Ravi

  • Which backup RMAN recover will use?

    Hi All,
    Suppose we have RMAN backup of 2 weeks assume that we have taken incremental backup on monday to saturday and we take the full backup on sunday again we take the incremental backup on monday.
    If we execute recover command which backup oracle will use? incremental backup which is taken on monday or full backup which is taken on sunday? please help me on this?

    FROM RMAN reference http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta044.htm#sthref702:
    >
    Complete and point-in-time recovery of a database can use both incremental backups and archived logs. If RMAN has a choice between applying an incremental backup or applying redo, then it always chooses the incremental backup. Applying incremental backups is faster and captures NOLOGGING changes. If overlapping levels of incremental backup are available, then RMAN automatically chooses the one covering the longest period of time.
    RMAN also applies incremental backups to restored files that were not restored from an incremental backup

  • RMAN recover for testing

    I want to plan some test runs on migrating my Oracle DB to 11.2 from 10.2. I understand i can't use the Duplicate command since i am changing versions. I realize that i need to running the commands restore and recover i can essentially do this. Well Can i change the name of my DB like i can in the duplicate command? Also is there a way to do this with the recover catalog and change the DBID of the new DB? Thanks.

    Hello;
    See - Database Backup and Recovery Advanced User's Guide 10g Release 2 (10.2) B14191-03
    Best Regards
    mseberg

  • Why is my rman recovering process so slow?

    I backup my oracle8.1.7 for aix 4.3.3 using legato networker7.0 which uses rman script and ML1500 tape library. When I restored one of my 1G big tablespace,it took ten hours which is too long.I set Large_pool_size = 6m and dbwr_io_slaves = 4 and backup_tape_io_slaves = true and disk_asynch_io = true and tape_asynch_io = true.
    what should i do?
    thanks

    i solved the problem.It is not an oracle problem.The problem is about network between oracle server and backup server.

  • Can not recover table from rman backup

    For testing I want to recover deleted table from rman backup.
    I have make vm of oracle 11g.  the following step i have applied but could not recover the table.
    rman> backup database ;
    On sqlplus create login as scott/tiger
    create table scott.emp1(col1 varchar2(10));
    insert into emp1(col1) value('Yasir ') ;
    commit ;
    select * from emp1 ;
    it shows me one row successfully.
    Now i have login the  sys as sysdba
    sqlplus> alter system switch logfile ;
    after this i have drop the table .
    Now to recover the table i have restored database on same vm.
    rman>restore database ;
    rman> recover database ;
    rman> alter database open ;
    on sqlplus i have issued
    sqlplus> select * from scott.emp1 ;
    table or view does not exist.
    any help how to recover the deleted table from rman backup

    Hi,
    Check this test case
    SQL> create table TEST2 as select * from emp;
    Table created.
    SQL> select count(*) from TEST2;
      COUNT(*)
            15
    SQL> select TO_CHAR(SYSDATE,'DD-MON-YYYY HH24:MI:SS') from dual;
    TO_CHAR(SYSDATE,'DD-
    10-SEP-2013 10:57:05
    SQL> alter system switch logfile;
    System altered.
    SQL> drop table TEST2 purge;
    Table dropped.
    SQL> shu immediate
    [oracle@vnode MYSHELL]$ rman target /
    Recovery Manager: Release 11.2.0.2.0 - Production on Tue Sep 10 10:58:39 2013
    Copyright (c) 1982, 2009, Oracle and/or its affiliates.  All rights reserved.
    connected to target database: DDTEST (DBID=1667776968, not open)
    RMAN> run{
    set until time "to_date('2013 Sep 10 10:57','yyyy mon dd hh24:mi')";
    restore database;
    recover database;
    alter database open resetlogs;
    }2> 3> 4> 5> 6>
    media recovery complete, elapsed time: 00:00:02
    Finished recover at 10-SEP-13
    database opened
    RMAN> exit
    SQL> set lin 200 pages 100
    SQL> select count(*) from test2;
      COUNT(*)
            15
    HTH

  • Unable to recover database after rman recovery and database open resetlogs

    I am running Oracle 10.2.0.5 on OpenSUSE 9. I have been trying to upgrade the database to 11g, through dbua. I was getting stuck at one point during the Oracle Server install and the upgrade failed and I was forced to restore the database to an earlier backup.
    Below is the current place that I am stuck. As you can see I opened the database multiple times and reset the logs. Now I am afraid that my controlfile and redo log backups are out of sync and i can't get them back on track. Before when I actually got the database recovered RMAN would immediately throw:
    RMAN-06900: WARNING: unable to generate V$RMAN_STATUS or V$RMAN_OUTPUT row
    RMAN-06901: WARNING: disabling update of the V$RMAN_STATUS and V$RMAN_OUTPUT rows
    OPA-00600: ORA-00600: internal error code, arguments: ...
    The database would open with ALTER DATABASE RESETLOGS but any query on non-system tables would fail and throw:
    ORA-04045: errors during recompilation/revalidation of LCRS_DEV1.FACILITY_REF
    ORA-00600: internal error code, arguments: [17069], [0x1158ED180], [], [], [],
    I hope I have not dug myself into too deep of a hole here.
    Here is the trace from my most recent attempt.
    RMAN> startup nomount;
    connected to target database (not started)
    Oracle instance started
    Total System Global Area 3070230528 bytes
    Fixed Size 2099424 bytes
    Variable Size 301991712 bytes
    Database Buffers 2751463424 bytes
    Redo Buffers 14675968 bytes
    RMAN> list incarnation of database;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of list command at 08/02/2011 15:49:04
    ORA-01507: database not mounted
    RMAN> restore controlfile from autobackup;
    Starting restore at 02-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    recovery area destination: /opt/oracle/flash_recovery_area
    database name (or database unique name) used for search: LCRSDEV
    channel ORA_DISK_1: autobackup found in the recovery area
    channel ORA_DISK_1: autobackup found: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
    channel ORA_DISK_1: control file restore from autobackup complete
    output filename=/opt/oracle/oradata/LCRSDEV/control01.ctl
    output filename=/opt/oracle/oradata/LCRSDEV/control02.ctl
    output filename=/opt/oracle/oradata/LCRSDEV/control03.ctl
    Finished restore at 02-AUG-11
    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    RMAN> list incarnation of database;
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05
    2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11
    3 3 LCRSDEV 756543625 PARENT 92348137 18-JUL-11
    4 4 LCRSDEV 756543625 PARENT 95654931 01-AUG-11
    5 5 LCRSDEV 756543625 PARENT 95675699 01-AUG-11
    6 6 LCRSDEV 756543625 PARENT 95676699 02-AUG-11
    7 7 LCRSDEV 756543625 PARENT 95676700 02-AUG-11
    8 8 LCRSDEV 756543625 CURRENT 95676701 02-AUG-11
    RMAN> restore database until scn 95676700;
    Starting restore at 02-AUG-11
    Starting implicit crosscheck backup at 02-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    Crosschecked 6 objects
    Finished implicit crosscheck backup at 02-AUG-11
    Starting implicit crosscheck copy at 02-AUG-11
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 02-AUG-11
    searching for all files in the recovery area
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 08/02/2011 15:52:04
    RMAN-20208: UNTIL CHANGE is before RESETLOGS change
    RMAN> restore database;
    Starting restore at 02-AUG-11
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to /opt/oracle/oradata/LCRSDEV/system01.dbf
    restoring datafile 00002 to /opt/oracle/oradata/LCRSDEV/undotbs01.dbf
    restoring datafile 00003 to /opt/oracle/oradata/LCRSDEV/sysaux01.dbf
    restoring datafile 00004 to /opt/oracle/oradata/LCRSDEV/users01.dbf
    restoring datafile 00005 to /opt/oracle/oradata/LCRSDEV/LCRS_TBS.dbf
    channel ORA_DISK_1: reading from backup piece /opt/oracle/flash_recovery_area/LCRSDEV/backupset/2011_07_22/o1_mf_nnndf_TAG20110722T111922_72m8rc5x_.bkp
    channel ORA_DISK_1: restored backup piece 1
    piece handle=/opt/oracle/flash_recovery_area/LCRSDEV/backupset/2011_07_22/o1_mf_nnndf_TAG20110722T111922_72m8rc5x_.bkp tag=TAG20110722T111922
    channel ORA_DISK_1: restore complete, elapsed time: 00:23:36
    Finished restore at 02-AUG-11
    RMAN> recover database until scn 95676700;
    Starting recover at 02-AUG-11
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 08/02/2011 16:16:28
    RMAN-20208: UNTIL CHANGE is before RESETLOGS change
    RMAN> recover database;
    Starting recover at 02-AUG-11
    using channel ORA_DISK_1
    starting media recovery
    archive log thread 1 sequence 90 is already on disk as file /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_90_72ml85v3_.arc
    archive log filename=/opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jr20qc_.arc thread=1 sequence=1
    unable to find archive log
    archive log thread=1 sequence=1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 08/02/2011 16:25:04
    RMAN-06054: media recovery requesting unknown log: thread 1 seq 1 lowscn 95676701

    Thanks for the reply Hemant. I have reset the database for the controlfile that I am using as backup and now I am not able to recover until the correct SCN. I am thinking that my recovery catalog is bad. If I mount with the current controlfile I have this list of incarnations:
    List of Database Incarnations
    DB Key  Inc Key DB Name  DB ID            STATUS  Reset SCN  Reset Time
    *1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05*
    *2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11*
    *3 3 LCRSDEV 756543625 PARENT 92348137 18-JUL-11*
    *4 4 LCRSDEV 756543625 PARENT 95654931 01-AUG-11*
    *5 5 LCRSDEV 756543625 PARENT 95675699 01-AUG-11*
    *6 6 LCRSDEV 756543625 PARENT 95676699 02-AUG-11*
    *7 7 LCRSDEV 756543625 PARENT 95676700 02-AUG-11*
    *8 8 LCRSDEV 756543625 PARENT 95676701 02-AUG-11*
    *9 9 LCRSDEV 756543625 CURRENT 95676702 02-AUG-11*
    However if I restore the controlfile to the earlier version I am getting the following output from the process:
    RMAN> startup nomount;
    connected to target database (not started)
    Oracle instance started
    Total System Global Area 3070230528 bytes
    Fixed Size 2099424 bytes
    Variable Size 301991712 bytes
    Database Buffers 2751463424 bytes
    Redo Buffers 14675968 bytes
    RMAN> restore controlfile from '/opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_07_22/o1_mf_s_757164997_72m9rqw3_.bkp';
    Starting restore at 03-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
    output filename=/opt/oracle/oradata/LCRSDEV/control01.ctl
    output filename=/opt/oracle/oradata/LCRSDEV/control02.ctl
    output filename=/opt/oracle/oradata/LCRSDEV/control03.ctl
    Finished restore at 03-AUG-11
    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    RMAN> list incarnation of database;
    List of Database Incarnations
    DB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time
    1 1 LCRSDEV 756543625 PARENT 1 22-OCT-05
    2 2 LCRSDEV 756543625 PARENT 525876 20-JAN-11
    3 3 LCRSDEV 756543625 CURRENT 92348137 18-JUL-11
    RMAN> restore database until scn 92348137;
    Starting restore at 03-AUG-11
    Starting implicit crosscheck backup at 03-AUG-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    Crosschecked 1 objects
    Finished implicit crosscheck backup at 03-AUG-11
    Starting implicit crosscheck copy at 03-AUG-11
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 03-AUG-11
    searching for all files in the recovery area
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_1_73g3hn6o_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_2_73g3hnxq_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_01/o1_mf_1_1_73g0rts6_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_134_72v9gv4s_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_138_72v9p4b4_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_120_72v8wwg0_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_121_72v8x5ty_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_131_72v9cnrv_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_139_72v9q5ok_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_137_72v9n4t5_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_136_72v9l88q_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_123_72v8ytm8_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_132_72v9dcxd_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_124_72v8zkg0_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_128_72v96qm1_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_135_72v9jqmx_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_129_72v98q3r_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_125_72v91g3b_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_118_72v8v8r4_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_127_72v9626w_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_130_72v9bqtb_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_141_72vncy6g_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_122_72v8ycd4_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_126_72v94cns_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_133_72v9fb17_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_140_72vn6wgo_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_25/o1_mf_1_119_72v8v9hf_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73j3wo01_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_2_73josgf1_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jr20qc_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_2_73jh223h_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73josflf_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73jvqdqs_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_3_73josh91_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_08_02/o1_mf_1_1_73j91rh9_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_91_72mqlnx9_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_111_72mrdr5m_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_96_72mqx958_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_114_72mrgsf9_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_94_72mqs6gj_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_102_72mr3893_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_99_72mr2h6c_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_104_72mr5hfm_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_109_72mrc83z_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_98_72mr080w_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_93_72mqq36m_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_97_72mqz0mm_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_116_72mrk268_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_101_72mr31yv_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_110_72mrddhg_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_95_72mqv3hp_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_105_72mr5vq4_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_115_72mrjd2s_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_106_72mr7hnt_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_100_72mr2qfc_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_112_72mrfc5j_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_107_72mr909t_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_103_72mr4pol_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_113_72mrfsb9_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_117_72mrl5mf_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_108_72mrb13l_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_90_72ml85v3_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_22/o1_mf_1_92_72mqnxz1_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_143_72y6ww71_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_144_72ybybps_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_142_72xt10j7_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/archivelog/2011_07_26/o1_mf_1_145_72yccy5z_.arc
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_01/o1_mf_s_758043324_73g3jfxx_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_01/o1_mf_s_758035850_73fw6vrc_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758133684_73jvr5px_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758127608_73jot9x0_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758109276_73j3xfom_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_08_02/o1_mf_s_758129928_73jr2s7p_.bkp
    File Name: /opt/oracle/flash_recovery_area/LCRSDEV/autobackup/2011_07_22/o1_mf_s_757164997_72m9rqw3_.bkp
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 08/03/2011 12:53:19
    RMAN-20208: UNTIL CHANGE is before RESETLOGS change
    Edited by: K Doyle on Aug 3, 2011 10:22 AM

  • Why it automatically recover current redo log in RMAN command window?

    Firstly, I restore controlfile and datafiles from a backupset.
    Then when I recover database in RMAN command window like below:
    RMAN> recover database;
    Starting recover at 15-AUG-13
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    starting media recovery
    archive log thread 1 sequence 9 is already on disk as file /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_90sd0slz_.arc
    archive log thread 1 sequence 10 is already on disk as file
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_90sd0tsb_.arc
    archive log thread 1 sequence 11 is already on disk as file
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_90sd110b_.arc
    archive log thread 1 sequence 12 is already on disk as file
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_90sd2ksr_.arc
    archive log thread 1 sequence 13 is already on disk as file
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_90sd2mc6_.arc
    archive log thread 1 sequence 14 is already on disk as file
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_90sd2qrm_.arc
    archive log thread 1 sequence 15 is already on disk as file
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_90sd2s0w_.arc
    archive log thread 1 sequence 16 is already on disk as file /u01/app/oracle/oradata/lonion/redo03.log
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_90sd0slz_.arc thread=1 sequence=9
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_90sd0tsb_.arc thread=1 sequence=10
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_90sd110b_.arc thread=1 sequence=11
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_90sd2ksr_.arc thread=1 sequence=12
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_90sd2mc6_.arc thread=1 sequence=13
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_90sd2qrm_.arc thread=1 sequence=14
    archive log filename=/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_90sd2s0w_.arc thread=1 sequence=15
    archive log filename=/u01/app/oracle/oradata/lonion/redo03.log thread=1 sequence=16
    media recovery complete, elapsed time: 00:00:04
    Finished recover at 15-AUG-13
    RMAN>
    But, when I recover database in SQL*Plus command window like below:
    [oracle@lonion ~]$ uniread sqlplus /nolog
    [uniread] Loaded history (2178 lines)
    SQL*Plus: Release 10.2.0.1.0 - Production on Thu Aug 15 19:25:38 2013
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    SQL> conn /as sysdba
    Connected.
    SQL>
    SQL> recover database;
    ORA-00283: recovery session canceled due to errors
    ORA-01610: recovery using the BACKUP CONTROLFILE option must be done
    SQL> recover database using backup controlfile;
    ORA-00279: change 2147842454 generated at 08/15/2013 18:34:28 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_%u_.a
    rc
    ORA-00280: change 2147842454 for thread 1 is in sequence #9
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    auto
    ORA-00279: change 2147842651 generated at 08/15/2013 18:40:25 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_%u_.
    arc
    ORA-00280: change 2147842651 for thread 1 is in sequence #10
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_9_90sd
    0slz_.arc' no longer needed for this recovery
    ORA-00279: change 2147842653 generated at 08/15/2013 18:40:26 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_%u_.
    arc
    ORA-00280: change 2147842653 for thread 1 is in sequence #11
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_10_90s
    d0tsb_.arc' no longer needed for this recovery
    ORA-00279: change 2147842656 generated at 08/15/2013 18:40:32 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_%u_.
    arc
    ORA-00280: change 2147842656 for thread 1 is in sequence #12
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_11_90s
    d110b_.arc' no longer needed for this recovery
    ORA-00279: change 2147842684 generated at 08/15/2013 18:41:21 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_%u_.
    arc
    ORA-00280: change 2147842684 for thread 1 is in sequence #13
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_12_90s
    d2ksr_.arc' no longer needed for this recovery
    ORA-00279: change 2147842686 generated at 08/15/2013 18:41:23 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_%u_.
    arc
    ORA-00280: change 2147842686 for thread 1 is in sequence #14
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_13_90s
    d2mc6_.arc' no longer needed for this recovery
    ORA-00279: change 2147842689 generated at 08/15/2013 18:41:27 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_%u_.
    arc
    ORA-00280: change 2147842689 for thread 1 is in sequence #15
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_14_90s
    d2qrm_.arc' no longer needed for this recovery
    ORA-00279: change 2147842691 generated at 08/15/2013 18:41:28 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_16_%u_.
    arc
    ORA-00280: change 2147842691 for thread 1 is in sequence #16
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_15_90s
    g0or9_.arc' no longer needed for this recovery
    ORA-00279: change 2147842986 generated at 08/15/2013 19:14:29 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_17_%u_.
    arc
    ORA-00280: change 2147842986 for thread 1 is in sequence #17
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_16_90s
    g0os5_.arc' no longer needed for this recovery
    ORA-00308: cannot open archived log
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_17_%u_
    .arc'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    SQL> recover database using backup controlfile;
    ORA-00279: change 2147842986 generated at 08/15/2013 19:14:29 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_08_15/o1_mf_1_17_%u_.
    arc
    ORA-00280: change 2147842986 for thread 1 is in sequence #17
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    /u01/app/oracle/oradata/lonion/redo01.log        ---- Yon see, proceeding this process, it can't automatically apply the current redo log.
    Log applied.
    Media recovery complete.
    SQL>
    Question Coming:
    Now, my question is that 「Why it automatically recover current redo log in RMAN command window but not in SQL*Plus」?
    BTW: Please pay attention to the red font.

    It also seems not work.
    SQL> recover automatic database using backup controlfile;
    ORA-00279: change 2148632889 generated at 09/26/2013 12:45:22 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_.
    arc
    ORA-00280: change 2148632889 for thread 1 is in sequence #48
    ORA-00278: log file
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
    .arc' no longer needed for this recovery
    ORA-00308: cannot open archived log
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
    .arc'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    auto
    ORA-00308: cannot open archived log
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
    .arc'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    ORA-00308: cannot open archived log
    '/u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_
    .arc'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file
    or directory
    Additional information: 3
    SQL>
    It must specify the redo log.
    SQL> recover database using backup controlfile;
    ORA-00279: change 2148632889 generated at 09/26/2013 12:45:22 needed for thread
    1
    ORA-00289: suggestion :
    /u01/app/oracle/flash_recovery_area/LONION/archivelog/2013_09_26/o1_mf_1_48_%u_.
    arc
    ORA-00280: change 2148632889 for thread 1 is in sequence #48
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    /u01/app/oracle/oradata/lonion/redo02.log
    Log applied.
    Media recovery complete.
    SQL>

  • Recover Database in RMAN vs SQL*PLUS

    Hello,
    Oracle 11.2.0.1, Oracle Linux 5.5 UEK.
    I recently did a "recover database" in sql*plus, but an attempt to open the database gave ORA-01113, complaining the system tablespace requried more recovery. Then I used RMAN (nocatalog) and after the same "recover database" command I was able to open the database.
    It seems there are differences between SQL*PLUS and RMAN "recover database" command. I have not been able to locate the chapter in the Oracle documentation that explains the difference. I have some ideas, but...
    Thanks.
    h3. Solution Summary:
    The recover command in RMAN compared to SQL*Plus implements a more user friendly processing logic based on the current detected scenario. For instance, a RMAN recover database command may actually perform a "recover database using backup controlfile until cancel" and automatically apply all archived and online redo logs if available. The same can be achieved with the recover command in SQL*plus, but will have to be done manually.
    Edited by: Dude on Jan 7, 2011 12:30 PM

    Dude wrote:
    I did not remove any datafiles or redo logs. it is the same restore operation as before, and again RMAN "recovery database" succeeds, whereas SQL recover has trouble. This tells me something is different between the two methods. For one, RMAN does not requrie to specify "using backup controlfile".
    Maybe someting about "resetlogs" that that RMAN recover can handle and SQL recover not?No,problem is there.If you using rman execute RECOVER DATABASE it also will apply online logs(if available) also and as result you will get complete recovery however you must open database with resetlogs option due to you recovered database using backup controlfile.So also you can recover and open database applying this online logs.After executing RECOVER DATABASE USING BACKUP CONTROLFILE you have to pass full path of online log then press ENTER so log will apply and you can open database with RESETLOGS.See below
    C:\Documents and Settings\chinar>rman target sys/sm
    Recovery Manager: Release 10.2.0.1.0 - Production on Fri Jan 7 17:47:49 2011
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    connected to target database (not started)
    RMAN> startup nomount;
    Oracle instance started
    Total System Global Area     138412032 bytes
    Fixed Size                     1247708 bytes
    Variable Size                 71304740 bytes
    Database Buffers              58720256 bytes
    Redo Buffers                   7139328 bytes
    RMAN> restore controlfile from 'D:\oracle\product\10.2.0\flash_recovery_area\T\B
    ACKUPSET\2011_01_07\O1_MF_NCSNF_TAG20110107T171001_6LG48JR5_.BKP'
    2> ;
    Starting restore at 07-JAN-11
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=157 devtype=DISK
    channel ORA_DISK_1: restoring control file
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
    output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL01.CTL
    output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL02.CTL
    output filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\CONTROL03.CTL
    Finished restore at 07-JAN-11
    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    RMAN> restore database;
    Starting restore at 07-JAN-11
    Starting implicit crosscheck backup at 07-JAN-11
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=156 devtype=DISK
    Crosschecked 1 objects
    Finished implicit crosscheck backup at 07-JAN-11
    Starting implicit crosscheck copy at 07-JAN-11
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 07-JAN-11
    searching for all files in the recovery area
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\T\BACKUPSET\2011_01_07\O
    1_MF_NCSNF_TAG20110107T171001_6LG48JR5_.BKP
    using channel ORA_DISK_1
    channel ORA_DISK_1: starting datafile backupset restore
    channel ORA_DISK_1: specifying datafile(s) to restore from backup set
    restoring datafile 00001 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\SYSTEM01.DBF
    restoring datafile 00002 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\UNDOTBS01.DBF
    restoring datafile 00003 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\SYSAUX01.DBF
    restoring datafile 00004 to D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\USERS01.DBF
    channel ORA_DISK_1: reading from backup piece D:\ORACLE\PRODUCT\10.2.0\FLASH_REC
    OVERY_AREA\T\BACKUPSET\2011_01_07\O1_MF_NNNDF_TAG20110107T171001_6LG45BXS_.BKP
    channel ORA_DISK_1: restored backup piece 1
    piece handle=D:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\T\BACKUPSET\2011_01_07
    \O1_MF_NNNDF_TAG20110107T171001_6LG45BXS_.BKP tag=TAG20110107T171001
    channel ORA_DISK_1: restore complete, elapsed time: 00:01:04
    Finished restore at 07-JAN-11
    RMAN> recover database;
    Starting recover at 07-JAN-11
    using channel ORA_DISK_1
    starting media recovery
    archive log thread 1 sequence 7 is already on disk as file D:\ORACLE\PRODUCT\10.
    2.0\ORADATA\T\REDO02.LOG
    archive log filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG thread=1 sequ
    ence=7
    media recovery complete, elapsed time: 00:00:03
    Finished recover at 07-JAN-11
    RMAN> exit
    Recovery Manager complete.
    C:\Documents and Settings\chinar>sqlplus sys/sm as sysdba
    SQL*Plus: Release 10.2.0.1.0 - Production on Fri Jan 7 17:51:31 2011
    Copyright (c) 1982, 2005, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
    With the Partitioning, OLAP and Data Mining options
    SQL> alter database open;
    alter database open
    ERROR at line 1:
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    SQL> alter database open resetlogs;
    Database altered.
    SQL> And above you see lines as
    archive log thread 1 sequence 7 is already on disk as file D:\ORACLE\PRODUCT\10.
    *2.0\ORADATA\T\REDO02.LOG*
    archive log filename=D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG thread=1 sequ
    ence=7
    It means RMAN apply these.So you can apply these using SQLPLUS ALSO.In additionally you can see that from alert log as
    alter database recover if needed
    start until cancel using backup controlfile
    Media Recovery Start
    parallel recovery started with 2 processes
    ORA-279 signalled during: alter database recover if needed
    start until cancel using backup controlfile
    Fri Jan 07 17:50:34 2011
    alter database recover logfile 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG'
    Fri Jan 07 17:50:34 2011
    Media Recovery Log D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG
    Fri Jan 07 17:50:34 2011
    Incomplete recovery applied all redo ever generated.
    Recovery completed through change 665263
    Completed: alter database recover logfile 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\T\REDO02.LOG'And finally you see clearly that even if you execute RECOVER DATABASE from RMAN it actually execute RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE (from alert.log start  until cancel using backup controlfile)
    And these is not any difference.
    Hope that help you and you got answer.

  • RAC instance, trying to recover UNDO datafile, RMAN gives RMAN-06054

    Hello all,
    This has been a troublesome instance..a quick bit of background. This was created awhile back by someone else, I inherited this 3 mode RAC clusterof instance1.
    I'm exporting out of one database (10G) into this instance1 (11G). When I was about to start the import..I found this instance wouldn't start. Turned out no backup had been going on of this empty instance. I backed up the archive logs to tape to free up the FRA..and things fired up.
    I began the import, and found a bunch of errors...basically tellling me that I couldn't access one of the undo tablespaces...datafile problems.
    I went to look and saw:
    SQL> select a.file_name, a.file_id, b.status, a.tablespace_name
         2 from dba_data_files a, v$datafile b
         3 where a.file_id = b.file#
         4 order by a.file_name;
         FILE_NAME FILE_ID STATUS TABLESPACE_NAME
         +DATADG/instance1/datafile/sysaux.270.696702269              2 ONLINE                SYSAUX
         +DATADG/instance1/datafile/system.263.696702253              1 SYSTEM                SYSTEM
         +DATADG/instance1/datafile/undotbs1.257.696702279            3 ONLINE                UNDOTBS1
         +DATADG/instance1/datafile/undotbs2.266.696702305            4 ONLINE                UNDOTBS2
         +DATADG/instance1/datafile/undotbs3.269.696702313            5 RECOVER               UNDOTBS3
         +DATADG/instance1/datafile/users.268.696702321               6 ONLINE                USERS
         +DATADG/instance1/l_data_01_01                              11 ONLINE                L_DATA_01
         +DATADG/instance1/s_data_01_01                               7 ONLINE                S_DATA_01
         +DATADG/instance1/s_data_01_02                               8 ONLINE                S_DATA_01
         +INDEXDG/instance1/l_index_01_01                            12 ONLINE                L_INDEX_01
         +INDEXDG/instance1/s_index_01_01                             9 ONLINE                S_INDEX_01
         FILE_NAME FILE_ID STATUS TABLESPACE_NAME
         +INDEXDG/instance1/s_index_01_02                            10 ONLINE                S_INDEX_01
    There is is, file #5.
    So, I went into RMAN to try to restore/recover:
    RMAN> restore datafile 5;
    Starting restore at 06-APR-10
    allocated channel: ORA_SBT_TAPE_1
    channel ORA_SBT_TAPE_1: SID=222 instance=instance1 device type=SBT_TAPE
    channel ORA_SBT_TAPE_1: NMO v4.5.0.0
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=222 instance=instance1 device type=DISK
    creating datafile file number=5 name=+DATADG/instance1/datafile/undotbs3.269.696702313
    restore not done; all files read only, offline, or already restored
    Finished restore at 06-APR-10
    RMAN> recover datafile 5;
    Starting recover at 06-APR-10
    using channel ORA_SBT_TAPE_1
    using channel ORA_DISK_1
    starting media recovery
    RMAN-06560: WARNING: backup set with key 343546 will be read 2 times
    available space of 8315779 kb needed to avoid reading the backup set multiple times
    unable to find archived log
    archived log thread=1 sequence=1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 04/06/2010 14:33:07
    RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 1 and starting SCN of 16016
    This is all on ASM, and am a bit of a newb with that. I bascially have no data I'm worried about losing, I just need to get everything 'on the air' so I can import successfully, and let users on this instance. I've set up the backups in GRID now....so, it will be backed up on the future, but what is the quickest, most efficient way to get this UNDO tablespace datafile recovered?
    Thank you,
    cayenne

    Hemant K Chitale wrote:
    SET UNTIL SEQUENCE 27wouldn't work if the Recovery requires Sequence 1 and it is missing.
    Hemant K ChitaleOops...meant to have start and set until both to "1"
    However, I see what you mean. It seems I cannot find the file on tape.
    Since the RAC instance hasn't yet had any data put into it, I'm thinking it might be best to just blow it away, and recreate everything.
    Trouble is, I'm a bit new at RAC and ASM. I was thinking the best route might be to use DBCA to remove the database...? Would this not take care of removing all the datafiles from all the ASM instances on the RAC..as well as all the other directories, etc on all 3x nodes?
    I've already used the dbca to create templates of this instance, so recreation shouldn't be too difficult (although it will be my first RAC creation)...
    Thank you in advance for the advice so far,
    cayenne

Maybe you are looking for

  • Lenovo G40-70 : Dual boot windows 8.1 and fedora 22

    Buenas tardes Estimados, recurrí al foro porque no puedo ingresar a mi partición de W 8,1 que trae instalada de fábrica la laptop, por motivo que instalé Fedora 22  (en otra partición)Quizas mi error fue instalar Fedora en modo legacy,y cambiar la bi

  • Can't Install WAAS in WAVE 574

    Hi, When I turn on WAVE 574, it said "No system disk/ disk error" (something like that). So I assume, there is no OS installed in the disk. I downloaded WAAS 4.4.1 rescue CD, and after a while, It said, "Can't determine boot device! Platform initiali

  • Configuring an attribute of image asset editor dropdown

    Hi, I need to make a custom attribute to be a dropdown. I was able to create the new attribute for Image (DAM) but when I am not able to make it as dropdown valued(Yes/No). Can someone please thow light on this. Thanks

  • How to open local file link in IE ?

    I know, this question is not APEX-related per se, but I was not able to google the fix to this problem. In my application, users can open a file open dialog and retrieve a complete file path that is later stored in the DB. Of course, Firefox's javasc

  • No inspection lot

    Hi, I am PP consultant. I have created production order & realese it. But inspection lot did not created. I have maintain inspection inspection type in QM view. How to solve problem.