Cancel media recovery

Hai all,
In note id , 232240.1 - Performing Switchover in a Data Guard Configuration
Convert the physical standby to the new primary:
If you are on verion 9.0.1 then you should first cancel managed recovery prior
to issuing the above command. If you are on 9.2.0 and have started managed
recovery with the "through all switchover" clause then you should also cancel
managed recovery before issuing the above command.
also cancel
managed recovery before issuing the above command.>>>>>>>>
How can I cancel this ?
Kai

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
sbs

Similar Messages

  • SQL*Plus auto accept CANCEL during recovery

    I am scripting out to do an incomplete recovery with a backup controlfile.
    How do I get SQL*Plus to automatically accept "CANCEL"
    when I get to this point: Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    and then move on to "alter database open resetlogs"
    SQL> recover database until cancel;
    ORA-00279: change 794271 generated at 12/22/2006 12:09:07 needed for thread 1
    ORA-00289: suggestion :
    /opt/oracle/flash_recovery_area/DDB/archivelog/1_4_609804799.dbf
    ORA-00280: change 794271 for thread 1 is in sequence #4
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    CANCEL
    Media recovery cancelled.
    SQL> ALTER DATABASE OPEN RESETLOGS;

    You can't - that's the whole point behind incomplete media recovery - how does sqlplus know when you want to cancel

  • Can't Cancel the Process Of Media Recovery Creation and Start A New One

    help me cancel the process of media recovery creation and start it all over again because i found that i need four disks to make the recovery creation. i made the first disk but i need to get another three disks for the process to be completed. It says that "media recovery creation has not been completed", so i want to cancel the whole opeation and start from the beginning later when i am ready for it. How can i do that, any steps or instructions to solve this issue would be appreciated.
    Computer: HP Pavilion dv6-6120se
    OS: Windows 7 home premium x64
    This question was solved.
    View Solution.

    You can only create one set of recovery discs. So once the process is completed, you will not be able to create another.
    -------------How do I give Kudos? | How do I mark a post as Solved? --------------------------------------------------------

  • Oracle Media Recovery Not Started

    Hi,
    Need help
    I've just performed system copy in HP-UX & Oracle as database using backup restore method.
    I'm using online backup for this system copy. Control file has been created successfully. Now I'm trying to start the media recover using below cmd
    "recover database using backup controlfile until cancel"
    After applying this command system is not starting the media recovery. From alert log file I can see the msg Media Recovery Start but oracle is not giving any further message, it is stuck on the below screen.
    aigas:oraaeq 2> sqlplus /nolog
    SQL*Plus: Release 10.2.0.2.0 - Production on Thu May 13 08:42:39 2010
    Copyright (c) 1982, 2005, Oracle.  All Rights Reserved.
    SQL> conn /as sysdba
    Connected to an idle instance.
    SQL> startup mount
    ORACLE instance started.
    Total System Global Area 5284823040 bytes
    Fixed Size                  2051424 bytes
    Variable Size            2650800800 bytes
    Database Buffers         2617245696 bytes
    Redo Buffers               14725120 bytes
    Database mounted.
    SQL>
    SQL> recover database using backup controlfile until cancel;
    output of tail -f alert.log file **********
    parallel_threads_per_cpu = 1
      optimizer_index_cost_adj = 20
      query_rewrite_enabled    = FALSE
      optimpeek_user_binds   = FALSE
      pga_aggregate_target     = 3469486325
      workarea_size_policy     = AUTO
      statistics_level         = typical
      optimizermjc_enabled   = FALSE
      bloomfilter_enabled    = FALSE
    PMON started with pid=2, OS id=5447
    PSP0 started with pid=3, OS id=5449
    MMAN started with pid=4, OS id=5451
    DBW0 started with pid=5, OS id=5453
    DBW1 started with pid=6, OS id=5455
    LGWR started with pid=7, OS id=5457
    CKPT started with pid=8, OS id=5459
    SMON started with pid=9, OS id=5461
    RECO started with pid=10, OS id=5463
    CJQ0 started with pid=11, OS id=5465
    MMON started with pid=12, OS id=5467
    MMNL started with pid=13, OS id=5469
    Thu May 13 09:17:26 2010
    ALTER DATABASE   MOUNT
    Thu May 13 09:17:30 2010
    Setting recovery target incarnation to 1
    Thu May 13 09:17:30 2010
    Successful mount of redo thread 1, with mount id 680883430
    Thu May 13 09:17:30 2010
    Database mounted in Exclusive Mode
    Completed: ALTER DATABASE   MOUNT
    Thu May 13 09:18:19 2010
    ALTER DATABASE RECOVER  database using backup controlfile
    Thu May 13 09:18:19 2010
    Media Recovery Start
    We have mounted two nfs file system which are part of oracle file system
    Regards,
    Neehir Bhatt

    Hi Neehir,
    How did you create the control file ?
    Did you use start the DB with source SID and generated a control file trace  and then excutede the control file trace sql with the SID change in ordrer to create actual control files with ORACLE_SID reset to actual DBSID. .
    Also i use:
    recover database until cancel using backup controlfile;
    and not :
    "recover database using backup controlfile until cancel"
    Not sure though if that should make difference because if yours was erroneous oracle should have let you known.
    What message comes when you try
    alter database open
    Regards.
    Ruchit.

  • Cancel based recovery

    dear dba's,
    i'm using oracle 11gR2 in windows 2003 sever S2.
    could anyone tell me
    1. what is CANCEL BASED RECOVERY
    2. pls give the commands with an explanation
    3. In which suituation we must use this type of recovery.
    Thanks & Regards,
    John Marshal.A

    +1. what is CANCEL BASED RECOVERY+
    It is an incomplete recovery option , at particular time you want to recover yours database for an audit purpose or to avoid any logical error by users in past , but flashback technology now been dominant to cancel based reocovery.
    +2. pls give the commands with an explanation+
    +3. In which suituation we must use this type of recovery.+
    When yours controlfile does not know when so far yours recover could be go on and on by "recover database using backup controlfile until cancel" yours restored controlfile from backup typically does not know how far i need redo if you are doing manual recovery while RMAN does not need cancel based recovery it will keep applying log until it finds and bumped out with an error RMAN-06054: media recovery requesting unknown archived log for ..... .
    Situation could be manual recovery in general when you do not define time.scn based recovery using until clause.
    Copied from my blog but need to be a bit changes thats why pasting here.
    Scenario 1
    I lost all data file but my control file is intact at the same location where it was , before lost datafiles i have backed up the data files, controlfile and archive logs.
    If you are just restoring the data files and not control files then you may know how much archive log sequence required for yours recovery after the backup taken using archived log repository.
    RMAN> backup database;
    Starting backup at 02-OCT-09
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=128 device type=DISK
    channel ORA_DISK_1: starting full datafile backup set
    channel ORA_DISK_1: specifying datafile(s) in backup set
    input datafile file number=00001 name=/u01/app/oracle/oradata/his/system01.dbf
    input datafile file number=00002 name=/u01/app/oracle/oradata/his/sysaux01.dbf
    input datafile file number=00003 name=/u01/app/oracle/oradata/his/undotbs01.dbf
    input datafile file number=00004 name=/u01/app/oracle/oradata/his/users01.dbf
    channel ORA_DISK_1: starting piece 1 at 02-OCT-09
    channel ORA_DISK_1: finished piece 1 at 02-OCT-09
    piece handle=/u01/app/oracle/flash_recovery_area/HIS/backupset/2009_10_02/o1_mf_nnndf_TAG20091002T112226_5dc712wg_.bkp tag=TAG20091002T112226 comment=NONE
    channel ORA_DISK_1: backup set complete, elapsed time: 00:00:45
    Finished backup at 02-OCT-09
    Starting Control File and SPFILE Autobackup at 02-OCT-09
    piece handle=/u01/app/oracle/flash_recovery_area/HIS/autobackup/2009_10_02/o1_mf_s_699189791_5dc72j13_.bkp comment=NONE
    Finished Control File and SPFILE Autobackup at 02-OCT-09
    RMAN> sql 'alter system archive log current';
    using target database control file instead of recovery catalog
    sql statement: alter system archive log current
    RMAN> sql 'alter system archive log current';
    sql statement: alter system archive log current
    RMAN> sql 'alter system archive log current';
    sql statement: alter system archive log current
    RMAN> exit
    Recovery Manager complete.
    [oracle@khurram his]$ sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.6.0 - Production on Fri Oct 2 11:24:04 2009
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> select name,sequence#
      2    from v$archived_log
      3   where status='A'
      4  /
    NAME                                                                                 SEQUENCE#
    /u01/app/oracle/product/11.1.0/db_1/dbs/arch1_2_699187272.dbf                           2
    /u01/app/oracle/flash_recovery_area/HIS/archivelog/2009_10_02/o1_mf_1_2_5dc73qw2_.arc   2
    /u01/app/oracle/product/11.1.0/db_1/dbs/arch1_3_699187272.dbf                           3
    /u01/app/oracle/flash_recovery_area/HIS/archivelog/2009_10_02/o1_mf_1_3_5dc73vgm_.arc   3
    /u01/app/oracle/product/11.1.0/db_1/dbs/arch1_4_699187272.dbf                           4
    /u01/app/oracle/flash_recovery_area/HIS/archivelog/2009_10_02/o1_mf_1_4_5dc740d7_.arc   4
    6 rows selected.You may know if yours control file intact (not lost or restored from backup), you may know how much recovery will go so far by knowing archived logs repository (conrolfile).From above v$archived_log archveilog repository you are seeing that after backup there are sequence required for the archive logs are 2,3 and 4 for recovering the restored backup which you have taken as above.
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    [oracle@khurram his]$ cd /u01/app/oracle/oradata/his/*.dbf
    bash: cd: /u01/app/oracle/oradata/his/sysaux01.dbf: Not a directory
    [oracle@khurram his]$ rm -rf  /u01/app/oracle/oradata/his/*.dbf
    [oracle@khurram his]$ sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.6.0 - Production on Fri Oct 2 11:28:01 2009
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> shutdown abort
    ORACLE instance shut down.
    SQL> startup mount
    ORACLE instance started.
    Total System Global Area 1620115456 bytes
    Fixed Size                  2144864 bytes
    Variable Size             922748320 bytes
    Database Buffers          687865856 bytes
    Redo Buffers                7356416 bytes
    Database mounted.
    SQL> exit
    Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    [oracle@khurram his]$ rman target /
    Recovery Manager: Release 11.1.0.6.0 - Production on Fri Oct 2 11:29:30 2009
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    connected to target database: HIS (DBID=3219691467, not open)
    RMAN> restore database;
    Starting restore at 02-OCT-09
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=154 device type=DISK
    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 /u01/app/oracle/oradata/his/system01.dbf
    channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/his/sysaux01.dbf
    channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/his/undotbs01.dbf
    channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/his/users01.dbf
    channel ORA_DISK_1: reading from backup piece /u01/app/oracle/flash_recovery_area/HIS/backupset/2009_10_02/o1_mf_nnndf_TAG20091002T112226_5dc712wg_.bkp
    channel ORA_DISK_1: piece handle=/u01/app/oracle/flash_recovery_area/HIS/backupset/2009_10_02/o1_mf_nnndf_TAG20091002T112226_5dc712wg_.bkp tag=TAG20091002T112226
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:35
    Finished restore at 02-OCT-09
    RMAN> recover database;
    Starting recover at 02-OCT-09
    using channel ORA_DISK_1
    starting media recovery
    archived log for thread 1 with sequence 2 is already on disk as file /u01/app/oracle/flash_recovery_area/HIS/archivelog/2009_10_02/o1_mf_1_2_5dc73qw2_.arc
    archived log for thread 1 with sequence 3 is already on disk as file /u01/app/oracle/flash_recovery_area/HIS/archivelog/2009_10_02/o1_mf_1_3_5dc73vgm_.arc
    archived log for thread 1 with sequence 4 is already on disk as file /u01/app/oracle/flash_recovery_area/HIS/archivelog/2009_10_02/o1_mf_1_4_5dc740d7_.arc
    archived log file name=/u01/app/oracle/flash_recovery_area/HIS/archivelog/2009_10_02/o1_mf_1_2_5dc73qw2_.arc thread=1 sequence=2
    media recovery complete, elapsed time: 00:00:01
    Finished recover at 02-OCT-09
    as you can see that 2,3,4 were required during recovery process.Scenario 2
    I lost all data file as well control file , i have backed up the data files, controlfile and archive logs.
    Its like a disastre you lost alls data file and as well controlfile , if you backed the controlfile then remember during controlfile backup it will have file type flag 4 that tells Oracle it is a backup control file. The Stop SCN for alls data file marked to 0xffff.ffffffff (infinity).File type flag in the backup control file tells to oracle that it cannot rely on its redo thread,which means recovering will go on and on , controlfile will not aware how much should i go for redo it will never stop if you are able to supply redo.
    It will always ask you more subsequent redo if you already supplied to it during process that's why it let you open the database in reset logs.
    Lets see after restoring the controlfile and datafiles , you will see SQL tool recovery mechanism ask you recover database using backup controlfile which shows that controlfile does not know where to end the applying redo chain.
    Here an excerpt which shows that restored controlfile does not know till how long the redo should be applied, its the RMAN robustness which does not ask you manually to supply redo, RMAN search the alls redo from archivelogs and if possible you have redo within redo logs.But if you are not with RMAN i.e recovering by SQL then you have to cancel recovery at some end.
    RMAN> shutdown abort
    Oracle instance shut down
    RMAN> exit
    Recovery Manager complete.
    [oracle@khurram ~]$ rm -rf /u01/app/oracle/oradata/his/*
    [oracle@khurram ~]$ rman target /
    Recovery Manager: Release 11.1.0.6.0 - Production on Fri Oct 2 09:32:37 2009
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    connected to target database (not started)
    RMAN> startup nomount
    Oracle instance started
    Total System Global Area    1620115456 bytes
    Fixed Size                     2144864 bytes
    Variable Size                922748320 bytes
    Database Buffers             687865856 bytes
    Redo Buffers                   7356416 bytes
    RMAN> restore controlfile from autobackup;
    Starting restore at 02-OCT-09
    using target database control file instead of recovery catalog
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=153 device type=DISK
    recovery area destination: /u01/app/oracle/flash_recovery_area
    database name (or database unique name) used for search: HIS
    channel ORA_DISK_1: AUTOBACKUP /u01/app/oracle/flash_recovery_area/HIS/autobackup/2009_10_02/o1_mf_s_699182899_5dc0c49t_.bkp found in the recovery area
    AUTOBACKUP search with format "%F" not attempted because DBID was not set
    channel ORA_DISK_1: restoring control file from AUTOBACKUP /u01/app/oracle/flash_recovery_area/HIS/autobackup/2009_10_02/o1_mf_s_699182899_5dc0c49t_.bkp
    channel ORA_DISK_1: control file restore from AUTOBACKUP complete
    output file name=/u01/app/oracle/oradata/his/control01.ctl
    output file name=/u01/app/oracle/oradata/his/control02.ctl
    output file name=/u01/app/oracle/oradata/his/control03.ctl
    Finished restore at 02-OCT-09
    RMAN> alter database mount;
    database mounted
    released channel: ORA_DISK_1
    RMAN> restore database;
    Starting restore at 02-OCT-09
    Starting implicit crosscheck backup at 02-OCT-09
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=153 device type=DISK
    Crosschecked 1 objects
    Finished implicit crosscheck backup at 02-OCT-09
    Starting implicit crosscheck copy at 02-OCT-09
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 02-OCT-09
    searching for all files in the recovery area
    cataloging files...
    cataloging done
    List of Cataloged Files
    =======================
    File Name: /u01/app/oracle/flash_recovery_area/HIS/autobackup/2009_10_02/o1_mf_s_699182899_5dc0c49t_.bkp
    File Name: /u01/app/oracle/flash_recovery_area/HIS/archivelog/2009_10_02/o1_mf_1_5_5dc0d1m8_.arc
    File Name: /u01/app/oracle/flash_recovery_area/HIS/archivelog/2009_10_02/o1_mf_1_3_5dc0cx6p_.arc
    File Name: /u01/app/oracle/flash_recovery_area/HIS/archivelog/2009_10_02/o1_mf_1_4_5dc0czx3_.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 /u01/app/oracle/oradata/his/system01.dbf
    channel ORA_DISK_1: restoring datafile 00002 to /u01/app/oracle/oradata/his/sysaux01.dbf
    channel ORA_DISK_1: restoring datafile 00003 to /u01/app/oracle/oradata/his/undotbs01.dbf
    channel ORA_DISK_1: restoring datafile 00004 to /u01/app/oracle/oradata/his/users01.dbf
    channel ORA_DISK_1: reading from backup piece /u01/app/oracle/flash_recovery_area/HIS/backupset/2009_10_02/o1_mf_nnndf_TAG20091002T092724_5dc09dlc_.bkp
    channel ORA_DISK_1: piece handle=/u01/app/oracle/flash_recovery_area/HIS/backupset/2009_10_02/o1_mf_nnndf_TAG20091002T092724_5dc09dlc_.bkp tag=TAG20091002T092724
    channel ORA_DISK_1: restored backup piece 1
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:45
    Finished restore at 02-OCT-09
    [oracle@khurram ~]$ sqlplus / as sysdba
    SQL*Plus: Release 11.1.0.6.0 - Production on Fri Oct 2 09:34:51 2009
    Copyright (c) 1982, 2007, Oracle.  All rights reserved.
    Connected to:
    Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production
    With the Partitioning, OLAP, Data Mining and Real Application Testing options
    SQL> recover database using backup contorlfile until cancel
    Keep applying log as you can and you have and cancel at an end when alls logs are supplied to recovery process.

  • RMAN Restore Error - media recovery requesting unknown log: thread 1 seq 7

    Im using RMAN to copy a database to another server. The new server is IDENTICAL to the old one. By identical I mean it has the same sever name, ip address, operating system, Oracle version and directory structure.
    The new server already has the instance created, (same name as the old server instance, paths etc)
    The backup files have been manually restored to the new server, same locations as they were on the old one. ( RMAN did an automatic controlfile backup and also the archivelogs on the old server ).
    Ive restored the control file on the new server from the RMAN backup pieces.
    Ive catalogued the RMAN backup pieces on the new server.
    I know the last sequence available in the archivelogs backup by running on the new server :
    list backup of archivelog all;
    List of Backup Sets
    ===================
    BS Key Size Device Type Elapsed Time Completion Time
    5 14.43M DISK 00:00:03 11-MAY-11
    BP Key: 9 Status: AVAILABLE Compressed: NO Tag: TAG20110511T163502
    Piece Name: C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\BACKUPSET\
    011_05_11\O1_MF_ANNNN_TAG20110511T163502_6WOC5833_.BKP
    List of Archived Logs in backup set 5
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 2 550217 10-MAY-11 556559 11-MAY-11
    1 3 556559 11-MAY-11 559776 11-MAY-11
    1 4 559776 11-MAY-11 560093 11-MAY-11
    1 5 560093 11-MAY-11 560794 11-MAY-11
    BS Key Size Device Type Elapsed Time Completion Time
    7 15.50K DISK 00:00:01 11-MAY-11
    BP Key: 10 Status: AVAILABLE Compressed: NO Tag: TAG20110511T163653
    Piece Name: C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\BACKUPSET\
    011_05_11\O1_MF_ANNNN_TAG20110511T163653_6WOC8PMP_.BKP
    List of Archived Logs in backup set 7
    Thrd Seq Low SCN Low Time Next SCN Next Time
    1 6 560794 11-MAY-11 560851 11-MAY-11
    So far its all going swimmingly well.
    Now I want to restore the datafiles and recover. So I ran :
    RMAN run { restore database; recover database; alter database open resetlogs; }
    This gave me the output below which goes great but I get a final error, I think the error is because its looking for an archive log thats not in the backup set, but it should be. However, I think SCN 560851 is for a log that hadnt been created yet on the old server when the backup was ran ?
    How do I address resolving the error ? Its worth pointing out log, "archive log filename=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\ARCHIVELOG
    \2011_05_11\O1_MF_1_6_6WOK1X4W_.ARC recid=10 stamp=750881741" isnt on the old server either which is why its not in the backup set.
    I can do a alter database open reset logs but Id prefer to know why its failing.
    Any help would be much appreciated.
    RMAN> run { restore database; recover database; alter database open resetlogs; }
    Starting restore at 11-MAY-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 C:\ORACLE\PRODUCT\10.2.0\ORADATA\SAT\SYSTEM01.DBF
    restoring datafile 00002 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\SAT\UNDOTBS01.DBF
    restoring datafile 00003 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\SAT\SYSAUX01.DBF
    restoring datafile 00004 to C:\ORACLE\PRODUCT\10.2.0\ORADATA\SAT\USERS01.DBF
    channel ORA_DISK_1: reading from backup piece C:\ORACLE\PRODUCT\10.2.0\FLASH_REC
    OVERY_AREA\SAT\BACKUPSET\2011_05_11\O1_MF_NNNDF_TAG20110511T163507_6WOC5CM7_.BKP
    channel ORA_DISK_1: restored backup piece 1
    piece handle=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\BACKUPSET\2011_05_
    11\O1_MF_NNNDF_TAG20110511T163507_6WOC5CM7_.BKP tag=TAG20110511T163507
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:55
    Finished restore at 11-MAY-11
    Starting recover at 11-MAY-11
    using channel ORA_DISK_1
    starting media recovery
    channel ORA_DISK_1: starting archive log restore to default destination
    channel ORA_DISK_1: restoring archive log
    archive log thread=1 sequence=6
    channel ORA_DISK_1: reading from backup piece C:\ORACLE\PRODUCT\10.2.0\FLASH_REC
    OVERY_AREA\SAT\BACKUPSET\2011_05_11\O1_MF_ANNNN_TAG20110511T163653_6WOC8PMP_.BKP
    channel ORA_DISK_1: restored backup piece 1
    piece handle=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\BACKUPSET\2011_05_
    11\O1_MF_ANNNN_TAG20110511T163653_6WOC8PMP_.BKP tag=TAG20110511T163653
    channel ORA_DISK_1: restore complete, elapsed time: 00:00:01
    archive log filename=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\ARCHIVELOG
    \2011_05_11\O1_MF_1_6_6WOK1X4W_.ARC thread=1 sequence=6
    channel default: deleting archive log(s)
    archive log filename=C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\SAT\ARCHIVELOG
    \2011_05_11\O1_MF_1_6_6WOK1X4W_.ARC recid=10 stamp=750881741
    unable to find archive log
    archive log thread=1 sequence=7
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of recover command at 05/11/2011 18:15:42
    RMAN-06054: media recovery requesting unknown log: thread 1 seq 7 lowscn 560851
    RMAN>
    Edited by: user12173666 on 11-May-2011 10:28

    You need to do incomplete recovery i.e. to ask RMAN to restore/recover to some specific point in time. This is usually done with some UNTIL clause or SET UNTIL statement. Example in your case:
    SET UNTIL SEQUENCE 7;See http://download.oracle.com/docs/cd/B19306_01/backup.102/b14194/rcmsynta065.htm#RCMRF160.

  • How to do media recovery from cold backup?????????/

    Hi
    i take cold backup of my 9i database ....
    in case my database is up .....
    how will i recover my database if i lose a single database file and i want to recover it from cold backup......
    Thanks in advance
    Gagan

    Here you go
    These are the steps:
    1. Restore the lost file from a backup.
    2. If the database is down, mount it.
         SVRMGR> STARTUP MOUNT PFILE=<location_of_pfile>;
    3. Issue the following query:
    SVRMGR> SELECT V1.GROUP#, MEMBER, SEQUENCE#,
    FIRST_CHANGE#
    FROM V$LOG V1, V$LOGFILE V2
    WHERE V1.GROUP# = V2.GROUP# ;
    This will list all your online redolog files and their respective
    sequence and first change numbers.
    4. If the database is in NOARCHIVELOG mode, issue the query:
         SVRMGR> SELECT FILE#, CHANGE# FROM V$RECOVER_FILE;
    If the CHANGE# is GREATER than the minimum FIRST_CHANGE# of your logs,
    the datafile can be recovered. Just keep in mind that all the logs to
    applied will be online logs, and move on to step 5.
    If the CHANGE# is LESS than the minimum FIRST_CHANGE# of your logs, the
    file cannot be recovered. Your options at this point would be to restore
    the most recent full backup (and thus lose all changes to the database
    since) or recreate the tablespace as explained in scenario a.
    5. Recover the datafile:
    SVRMGR> RECOVER DATAFILE '<full_path_file_name>'
    6. Confirm each of the logs that you are prompted for until you receive the
    message "Media recovery complete". If you are prompted for a non-existing
    archived log, Oracle probably needs one or more of the online logs to
    proceed with the recovery. Compare the sequence number referenced in the
    ORA-280 message with the sequence numbers of your online logs. Then enter
    the full path name of one of the members of the redo group whose sequence
    number matches the one you are being asked for. Keep entering online logs
    as requested until you receive the message "Media recovery complete"
    7. If the database is at mount point, open it.

  • Media Recovery Waiting for thread 1 sequence (in transit)

    I have rebuilt our standby database using an rman duplicate since it was missing many archive logs.
    Following the duplicate, the standby is now almost in sync with the primary. Logs are shipping across but are not being applied in a timely manner. How long should it take for an archive log from the primary to be applied to the standby?
    I need to know this so that a proper script can be set up to check the primary and standby. At the moment they are never exactly in sync - always one sequence number behind the primary.
    Why is the standby is not applying in a timely manner?
    From the alert log:
    Media Recovery Waiting for thread 1 sequence 11278 (in transit)
    The log seems to be "in transit" for a long time
    PRIMARY:
    SQL> select max (sequence#) current_seq from v$log;
    CURRENT_SEQ
    11278
    SB:
    SQL> select MAX (SEQUENCE#), APPLIED FROM V$ARCHIVED_LOG where APPLIED ='YES' GROUP BY APPLIED;
    MAX(SEQUENCE#) APP
    11277 YES
    ALERT LOG:
    RFS[2]: Archived Log: '/backup/prod/log_1_11277_704816194.dbf'
    Primary database is in MAXIMUM PERFORMANCE mode
    Mon Nov 1 15:22:01 2010
    Media Recovery Log /backup/prod/log_1_11272_704816194.dbf
    Mon Nov 1 15:26:49 2010
    Media Recovery Log /backup/prod/log_1_11273_704816194.dbf
    Mon Nov 1 15:29:54 2010
    Media Recovery Log /backup/prod/log_1_11274_704816194.dbf
    Mon Nov 1 15:34:18 2010
    Media Recovery Log /backup/prod/log_1_11275_704816194.dbf
    Mon Nov 1 15:36:42 2010
    Media Recovery Log /backup/prod/log_1_11276_704816194.dbf
    Mon Nov 1 15:39:43 2010
    Media Recovery Log /backup/prod/log_1_11277_704816194.dbf
    Mon Nov 1 15:42:34 2010
    Media Recovery Waiting for thread 1 sequence 11278 (in transit)
    I should add that I understand that for the Primary and Standby to be out by one log is not cause for concern (they are applying). Its just that I wanted to script a check that would compare them both, and and the moment they are never equal - when I understand that they should be and that the logs should be applied almost immediately.
    Edited by: Dan A on Nov 1, 2010 4:36 PM

    How long should it take for an archive log from the primary to be applied to the standby?depends on network speed also.
    make sure the archives are shipped to standby location.
    PRIMARY:
    SQL> select max (sequence#) current_seq from v$log;
    CURRENT_SEQ
    11278(this is log not archivelog ) ..... :)SB:
    SQL> select MAX (SEQUENCE#), APPLIED FROM V$ARCHIVED_LOG where APPLIED ='YES' GROUP BY APPLIED;
    MAX(SEQUENCE#) APP
    11277 YES
    Hi check is MRP started or not?
    primary database you need not check current sequence, check last generated sequence..not current sequence.
    current sequence is redo log which has been not yet archived
    I think everything is perfect here.. no issues.
    Hope you understood, let me know if not clear , thanks.

  • RMAN-06054: media recovery requesting unknown archived log

    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 05/16/2013 09:03:43
    RMAN-05501: aborting duplication of target database
    RMAN-03015: error occurred in stored script Memory Script
    RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 34751 and starting SCN of 8923445274I am receiving the error above on performing RMAN Active cloning, please advise how to resolve this

    In addition to what was said, I can think of two other possibilities for RMAN-6054 during duplicate: bugs such as 12625205 (also see 8554110); duplicate was run earlier without removing the old restored files (Note 1549172.1). In the first case, just specify SCN or find the actual log file and speficy log sequence, instead of time. In the latter case, remove the old restored files or speficy noresume.
    Edited by: user11989003 on May 29, 2013 10:17 AM

  • Media Recovery Log    DATAGUARD

    hi all ,
    i have installed 10.2.0.2 databases and configure dataguard. everything works fine but i have 1 problem.
    imagine that server 1 is primary ;
    when i check on server 1 ; (primary DB)
    SQL> archive log list;
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination            /u01/app/oracle/archive/SID
    Oldest online log sequence 215
    Next log sequence to archive 218
    Current log sequence 218
    server 2 ( Standby server )
    SQL> archive log list;
    Database log mode Archive Mode
    Automatic archival Enabled
    Archive destination            dgsby_Stan
    Oldest online log sequence 216
    Next log sequence to archive 0
    Current log sequence 218
    on the alert_log of stanby server , it locate the archived logs from primary on */u01/app/oracle/product/10g/dbs/* not on */u01/app/oracle/archive/SID*
    Primary database is in MAXIMUM AVAILABILITY mode
    Standby controlfile consistent with primary
    RFS[6]: Successfully opened standby log 5: '/u02/app/oracle/oradata/SID/stdby_log01_1.log'
    Mon Dec 19 13:16:28 2011
    Media Recovery Log /u01/app/oracle/product/10g/dbs/dgsby_Stan1_217_767463156.dbf
    Media Recovery Waiting for thread 1 sequence 218 (in transit)
    Mon Dec 19 13:16:31 2011
    Recovery of Online Redo Log: Thread 1 Group 5 Seq 218 Reading mem 0
    Mem# 0 errs 0: /u02/app/oracle/oradata/SID/stdby_log01_1.log
    if i do switchover i faced with same reverse situation ; ( old primary acts like the old standby and old standby acts like old primary db )
    i have already set log_archive_dest_1 on both server.
    i want both standby and primary db locates the archive logs on */u01/app/oracle/archive/SID* not on */u01/app/oracle/product/10g/dbs/*
    what do i have to correct this situation ???
    thanks

    here is the output from standby ;
    SQL>
    SQL> show parameter standby_archive_dest
    NAME TYPE VALUE
    standby_archive_dest string /u01/app/oracle/archive/TELE
    SQL>
    SQL> show parameter log_archive_dest_1
    NAME TYPE VALUE
    log_archive_dest_1 string location="/u01/app/oracle/arch
    ive/SID", valid_for=(ONLINE_L
    OGFILE,ALL_ROLES)
    log_archive_dest_10 string
    SQL> show parameter log_archive_dest
    NAME TYPE VALUE
    log_archive_dest string
    log_archive_dest_1 string location="/u01/app/oracle/arch
    ive/SID", valid_for=(ONLINE_L
    OGFILE,ALL_ROLES)
    log_archive_dest_10 string
    log_archive_dest_2 string location="dgsby_Stan", valid_
    for=(STANDBY_LOGFILE,STANDBY_R
    OLE)
    log_archive_dest_3 string
    log_archive_dest_4 string
    log_archive_dest_5 string
    NAME TYPE VALUE
    log_archive_dest_6 string
    log_archive_dest_7 string
    log_archive_dest_8 string
    log_archive_dest_9 string
    log_archive_dest_state_1 string ENABLE
    log_archive_dest_state_10 string enable
    log_archive_dest_state_2 string ENABLE
    log_archive_dest_state_3 string ENABLE
    log_archive_dest_state_4 string enable
    log_archive_dest_state_5 string enable
    log_archive_dest_state_6 string enable
    NAME TYPE VALUE
    log_archive_dest_state_7 string enable
    log_archive_dest_state_8 string enable
    log_archive_dest_state_9 string enable

  • What is Media Recovery Log ..? Physical Standby Database

    Hello All,
    In my physical stdby database alert log I could see the below message, I'm not sure what id Media Recovery Log and why it is dumping ORACLE_HOME Directory..?
    Could any one please help on this..? I need to house keep ORACLE_HOME directory.
    Oracle 11gR2 / RHEL5
    RFS[164]: No standby redo logfiles available for thread 2
    RFS[164]: Opened log for thread 2 sequence 1995 dbid 287450012 branch 760028574
    Fri Nov 11 19:39:05 2011
    Media Recovery Log /u01/app/oracle/product/11.2.0/db_1/dbs/arch2_1992_760028574.dbf
    Media Recovery Log /u01/app/oracle/product/11.2.0/db_1/dbs/arch2_1993_760028574.dbf
    Media Recovery Waiting for thread 1 sequence 5568 (in transit)
    Fri Nov 11 19:39:53 2011
    Archived Log entry 948 added for thread 2 sequence 1994 rlc 760028574 ID 0x1122a1
    FYI : The primary and standby database are in sync.

    Hello;
    The alert log is providing you with information. If you want more run this query :
    select process,status,client_process,sequence# from v$managed_standby;You should see processes like ARCH, RFS and MRP0.
    MRP will tell you if its applying log(s), waiting for a log, or if it thinks there's a gap.
    PROCESS   STATUS       CLIENT_P  SEQUENCE#
    ARCH      CONNECTED    ARCH              0
    ARCH      CONNECTED    ARCH              0
    ARCH      CONNECTED    ARCH              0
    ARCH      CONNECTED    ARCH              0
    ARCH      CONNECTED    ARCH              0
    ARCH      CONNECTED    ARCH              0
    ARCH      CONNECTED    ARCH              0
    ARCH      CONNECTED    ARCH              0
    MRP0      APPLYING_LOG N/A            5051
    RFS       IDLE         N/A               0
    RFS       IDLE         UNKNOWN           0There's a tiny amount of information about this under "9.3.1 Adding a Datafile or Creating a Tablespace" in Oracle document E10700-02.
    If you find this helpful please click the "helpful" button.
    Best Regards
    mseberg

  • "needs media recovery" after a successful recovery ???

    RMAN novice here....
    Oracle 9.2.0.1.0 on Redhat Linux (Itanium)
    Running in NOarchivelog mode
    In RMAN, I backed up a set of datafiles in read only mode taking this approach....
    sql "alter tablespace foo read only";
    configure channel 1 device type disk format 'backupdisk/mybackuparea/foo.dbf.bck';
    backup datafile 'dbdisk/mydb/foo.dbf';
    sql "alter tablespace foo read write;
    Everything seemed to go fine.
    After some time, I wanted to restore/recover. This is what I did (again, in RMAN"...
    sql "alter fablespace foo offline";
    restore datafile 'dbdisk/mydb/foo.dbf';
    recover datafile 'dbdisk/mydb/foo.dbf' noredo;
    sql "alter tablespace foo online";
    My first stab at it, without the "noredo" failed. But with the "noredo" I got
    "Starting recover at ...."
    A set of channel assignment statements
    "Finished recover at ..."
    Looks to have run OK.
    But then, when I try to put the tablesopace back online...
    "failure of sql command on default channel at...."
    "failure during parse/execution of SQL statement: alter tablespace foo online"
    "file 1 needs media recovery"
    "data file 1: 'dbdisk/mydb/foo.dbf'"
    What gives?
    Thanks for any help

    I've read the books and googled this to death.
    Looks like I'm screwed.
    At this point, I don't even care about the datafile or the tablespace it contained. I just want my database back.
    I dropped the tablespace and it's datafile (and it's data too). I'll have to repopulate from scratch.
    Lesson learned
    This is what I want to do.....
    I want to do a 1x/wk backup of a schema (not the whole DB, I don't have enough disk space for that, just 1 of the schemas). I've designed the thing such that each schema has it;s own tablespaces (no overlap) and each tablespace maps to a single datafile.
    I would have liked to do some sort of online backup of the schema (read/write while backup is happening), but I'll settle for read only. If Oracle can't hack that, then I'll take the tablespaces offline.
    The schema contains hundreds of millions of records, and the load preocess involves several times that number of data manipulation statements (deletes, updates, inserts). I'd rather not use archivelog mode because I don't have the disk space for it. And, given the volume and nature of the data I'm loading (hundreds of millions of records, created from the data in large raw data files), and how it's being loaded (precompiled C/SQL programs), I would never have need to "rerun" the enormous archives for any reason.
    So...
    1) backup a single schema (an exclusive set of tablespaces/datafiles)
    2) as "online" as possible
    3) in noarchivelog mode.
    The only thing that I've seen that can do this is EXPORT/IMPORT. I tried that, but extrapolating IMPORT performance, even with all the streamlining recommendations, would take over 3 days. For this reason, IMPORT is not a viable option.
    -dave

  • Media Recovery failed with error 1111

    Hi,
    on 10g R2 on Unix I have :
    Media Recovery Start
    Managed Standby Recovery not using Real Time Apply
    Fri Jun 24 10:56:52 2011
    Media Recovery failed with error 1111
    From alert.log :
    Errors in file /data01/oracle/mydb/admin/bdump/hhhh_17637.trc:
    ORA-01111: name for data file 523 is unknown - rename to correct file
    ORA-01110: data file 523: '/oracle/product/10g/db_1/dbs/UNNAMED00523'
    ORA-01157: cannot identify/lock data file 523 - see DBWR trace file
    ORA-01111: name for data file 523 is unknown - rename to correct file
    ORA-01110: data file 523: /oracle/product/10g/db_1/dbs/UNNAMED00523'
    Any idea ?
    Thanks.

    here is one test case, i ran into same issue. and reolved as below.
    When Standby_file_management is set to “MANUAL” , if any data files added on primary database, These changes certainly won’t be altered in standby database.
    After starting MRP process, it dies and terminated with the following errors.
    Errors from Alert log file:-
    Errors in file /oracle/app/oracle/admin/CC/bdump/cc_mrp0_22294.trc:
    ORA-01111: name for data file 536 is unknown - rename to correct file
    ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
    ORA-01157: cannot identify/lock data file 536 - see DBWR trace file
    ORA-01111: name for data file 536 is unknown - rename to correct file
    ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
    Errors from Trace file:-
    MRP0: Background Media Recovery terminated with error 1111
    ORA-01111: name for data file 536 is unknown - rename to correct file
    ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
    ORA-01157: cannot identify/lock data file 536 - see DBWR trace file
    ORA-01111: name for data file 536 is unknown - rename to correct file
    ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
    ORA-01111: name for data file 536 is unknown - rename to correct file
    ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
    ORA-01157: cannot identify/lock data file 536 - see DBWR trace file
    ORA-01111: name for data file 536 is unknown - rename to correct file
    ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
    ARCH: Connecting to console port...
    Check out from SQL, Which files need to be recovered on standby database?
    SQL> select * from v$recover_file where error like '%FILE%';
    FILE# ONLINE  ONLINE_ ERROR                   CHANGE# TIME
    +536 ONLINE ONLINE FILE MISSING 0+
    SQL>
    On Primary check out for actual naming convention:-
    SQL>  select file#,name from v$datafile where file#=536;
    FILE# NAME
    +536 DATA/c/datafile/undotbs9.595.750444337
    SQL>
    On Standby check datafile name:-
    SQL> select file#,name from v$datafile where file#=536;
    FILE# NAME
    +536 /oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536+
    SQL>
    Make sure still standby_file_management is set to “MANUAL”, After performing media recovery again can be enabled to “AUTO”.
    Rename datafile from standby database:-
    SQL> alter database create datafile '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536' as 'DATA3/cc/datafile/undotbs9_595_750444337';+
    Database altered.
    Start the MRP Now:-
    SQL> alter database recover managed standby database disconnect from session;
    Database altered.
    After creating the file, MRP will start applying archives on standby database.

  • Media recovery issue

    Hello
    Why is media recovery is faster than, normal DML,DDL,etc?
    In production database, It took 1 hour to rebuild indexes and move some objects to diffrent tablespace.
    However, When I apply the archivelog of these changes to standby, it took about 20 minutes.
    What is reason for this?
    Cheers

    Media Recovery / Physical Standby operations are faster because they actually only write the final results.
    For example, in the index rebuild case, the operations doing the SQL are
    a. read table, get column values from table
    b. sort values
    c. if allocated pga/sort_area is insufficient, overflow to disk
    d. run final sort pass, if necessary
    e. write sorted results to the index segment
    (recursive SQLs to allocate extents, update the data dictionary for the index definition also have to be applied, each of these also having to read the existing extent maps and data dictionary before updating them).
    However, when you run media recovery
    1. Oracle does not have to read the table
    2. There is no sort operation
    3. Writes to temp are avoided (as Temp operations are nologging and there is nothing in the redo to "replay" against the tempfiles)
    4. The index blocks are "updated" directly

  • Media Recovery

    I am running Oracle 10g on windows 2003 R2.
    1) My UNDO TBS require media recovery, but the data file is in place for the mentioned location.
    Error encountered ORA - 01113 - needs media recovery.
    How can i do media recovery.
    2) My PROD1 TBS was full and i wanted to resize the datafile. i got error on the client admin console and connection was lost.
    When i try to connect again to the instance i get ORA- 12638 - credential fail error.
    Am not able to connect to the instance from client admin console, but i am already connect thru SQL Plus on the DB Server.
    Please adivse how can i resolve this.
    Regards

    I get following error when i try to recover undo tbs
    datafile.
    SQL> recover datafile
    'e:\oracle\oradata\ptmn\undotbs.dbf';
    ORA-00603: ORACLE server session terminated by fatal
    errorCheck your alert.log see if there any additional errors.
    Check if the datafile is still online,
    select * from dba_data_files
    where file_id=2Do you have any active transaction in the database ?
    select * from v$transactionIf there's no active undo segment, it's might be easier just create a new undo tablespace, change your default undo tablespace to new one and offline drop the old one.

Maybe you are looking for