RMAN-06054: media recovery requesting unknown log: thread 1 seq 300 lowscn

Got it dropped and recretaed - dont know why didnt work
Edited by: user3489571 on 14-Apr-2010 18:46

The ALTER DATABASE REGISTER LOGFILE command in SQLPlus is for Standby and Streams implementation.
You should be using the CATALOG command in RMAN.

Similar Messages

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

  • 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

  • Standby media recovery waiting for inactive thread

    Hi,
    Please let me know any idea on this scenario. Thanks.
    Environment:
    Oracle 11.2.0.2
    primary: 3 node RAC
    standby: 3 node RAC
    Problem:
    there is thread 5 (not registered instance or did not show in srvctl) that generates archivelog. but the lag apply stopped because of this when the instance (of thread 5) is shutdown.
    question: somehow an instance is registered in the cluster but in srvctl only 3 instance is running. it should have 4 instance but 1 is not running. How can I remove the thread 5 so when someone startup then shutdown instance#4 it will not create archivelog that will stopped the apply of archivelog in standby.
    note: this is perf environment server so someone and "other" DBA is accessing this environment which I am not aware what are they doing with the cluster.
    looking in alert log file: - it is waiting for thread 5 sequence 510. But the instance is down so log is not shipped to standby database and this resulted to lag in other threads.
    Sat Aug 03 18:54:47 2013
    Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_1_seq_13718.1544.822333555
    Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_2_seq_17665.22678.822315375
    Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_3_seq_15465.14138.822313997
    Media Recovery Waiting for thread 5 sequence 510
       THREAD# LAST_SEQ_RECEIVED LAST_SEQ_APPLIED
             1             13745            13717
             2             17728            17664
             3             15527            15464
             5               509              509
    what I did is:
    1. primary (asm copy to file system)
    2. scp primary to standby
    3. standby (file system copy to asm)
    4. rman target / -> catalog archivelog <thread 5 sequence 510)
    5. then looking into alert log file; it performed media recovery
    Sat Aug 03 23:03:13 2013
    Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_1_seq_13718.1544.822333555
    Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_2_seq_17665.22678.822315375
    Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_3_seq_15465.14138.822313997
    Media Recovery Waiting for thread 5 sequence 510
    Sat Aug 03 23:15:21 2013
    Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_5_seq_510
    Sat Aug 03 23:15:32 2013
    Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_3_seq_15466.10925.822316315
    Sat Aug 03 23:17:18 2013
    Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_2_seq_17666.853.822333143
    Sat Aug 03 23:18:39 2013
    Media Recovery Log +FLASH/dgjmspl/archivelog/2013_08_01/thread_3_seq_15467.834.822333553
    Sat Aug 03 23:20:54 2013

    in Standby, thread 4 and 5 are both UNUSED, and size is incorrect (not equal to other redo log). I want to recreate it but cannot drop redo log. I follow Doc ID 740675.1.
    any idea what are the missing steps? thanks.
    ORA-01624: needed for crash recovery of instance UNNAMED_INSTANCE_5 (thread 5)
    select group#,thread#,archived,status,bytes from v$log;
    primary DB:
        GROUP#    THREAD# ARC STATUS                BYTES
             1          1 YES INACTIVE         1073741824
             2          1 YES INACTIVE         1073741824
             3          2 NO  CURRENT          1073741824
             4          2 YES INACTIVE         1073741824
             5          3 YES INACTIVE         1073741824
             6          3 YES INACTIVE         1073741824
             7          2 YES INACTIVE         1073741824
             8          1 NO  CURRENT          1073741824
             9          3 NO  CURRENT          1073741824
            10          4 YES INACTIVE         1073741824
            11          4 NO  CURRENT          1073741824
        GROUP#    THREAD# ARC STATUS                BYTES
            12          4 YES INACTIVE         1073741824
            13          5 YES INACTIVE         1073741824
            14          5 YES INACTIVE         1073741824
            15          5 NO  CURRENT          1073741824
    standby DB:
        GROUP#    THREAD# ARC STATUS                BYTES
             1          1 YES INACTIVE         1073741824
             2          1 YES INACTIVE         1073741824
             3          2 NO  CURRENT          1073741824
             4          2 YES INACTIVE         1073741824
             5          3 YES INACTIVE         1073741824
             6          3 YES INACTIVE         1073741824
             7          2 YES INACTIVE         1073741824
             8          1 NO  CURRENT          1073741824
             9          3 NO  CURRENT          1073741824
            10          4 YES INACTIVE         1073741824
            11          4 NO  CURRENT          1073741824
        GROUP#    THREAD# ARC STATUS                BYTES
            12          4 YES INACTIVE         1073741824
            13          5 YES INACTIVE         1073741824
            14          5 YES INACTIVE         1073741824
            15          5 NO  CURRENT          1073741824

  • Error :  RMAN-06054

    Hi,
    I get the error "Error : RMAN-06054" when I try to recover a full database backup.
    The backup command used was:
    BACKUP DATABASE PLUS ARCHIVELOG;
    In my tests, when I dont remove the ONLINE redo log files the recovering works OK!
    I use auto backup controlfile configuration.
    Thank you,
    Faria

    I get the same problem. I followed this guide:
    http://www.orafusion.com/art_rman3.htm
    and get the error:
    RMAN-00571: ==============================
    RMAN-00569: =ERROR MESSAGE STACK FOLLOWS =
    RMAN-00571: ===============================
    RMAN-03002: failure of recover command at 04/01/2005 14:14:43
    RMAN-06054: media recovery requesting unknown log: thread 1 scn 32230460
    How to avoid it?

  • Rman with error RMAN-06054

    first, i backup all datafiles. then i delete the datafile of system tablesapce.
    then i recover database by recovery manager. it makes these errors.i do not
    how slove it.i nees help,i will thank ereryone who help me
    RMAN-03022: compiling command: recover(4)
    RMAN-03026: error recovery releasing channel resources
    RMAN-08031: released channel: c1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: recover
    RMAN-03002: failure during compilation of command
    RMAN-03013: command type: recover(4)
    RMAN-06054: media recovery requesting unknown log: thread 1 scn 1869941
    null

    Why don't review your syntax of your recover statements? Maybe there're some surprises waiting for you.

  • RMAN Active Cloning fails with RMAN-06054: missing log file

    Version Details:
    O.S Version     HP-UX B.11.31 U ia64
    Oracle DB Version     11.2.0.3.0
         Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    Scenario :
    Using RMAN Active cloning to duplicate a RAC database from Production to Development environment.
    Problem:
    At the end of the cloning the below errors are reported;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 05/14/2013 07: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 24751 and starting SCN of 89285945274
    RMAN Script used for Active cloning:
    #!/bin/ksh
    . setdb entDBu
    start_dt=`date +%Y%m%d_%H%M`
    job=`basename $0 ".sh"`
    rman  >> ${job}_${start_dt}.log  2>&1 <<eof
    set echo on;
    connect target sys/@DCC&(_O@entDBp1
    connect auxiliary sys/@DCC&(_O@entDBuu
    run {
    allocate channel prmy1 type disk;
    allocate auxiliary channel stby1 type disk;
    duplicate target database
    to entDBu
    from active database pfile=/app/oracle/product/11.2.0.3/db/dbs/initentDBu.ora;
    show all;
    exit
    eof
    end_dt=`date +%Y%m%d_%H%M`
    mailx -s "DR RMAN Job: $job done" "[email protected]" <<eof2
    started: ${start_dt}
    finish: ${end_dt}
    eof2How to prevent the error of RMAN-06054: media recovery requesting unknown archived log for thread  with sequence   and starting SCN of  while performing the RMAN Active Cloning? I do NOT want to use UNTIL clause.

    Sivaprasad S wrote:
    Version Details:
    O.S Version     HP-UX B.11.31 U ia64
    Oracle DB Version     11.2.0.3.0
         Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    Scenario :
    Using RMAN Active cloning to duplicate a RAC database from Production to Development environment.
    Problem:
    At the end of the cloning the below errors are reported;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of Duplicate Db command at 05/14/2013 07: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 24751 and starting SCN of 89285945274RMAN Script used for Active cloning:
    #!/bin/ksh
    . setdb entDBu
    start_dt=`date +%Y%m%d_%H%M`
    job=`basename $0 ".sh"`
    rman  >> ${job}_${start_dt}.log  2>&1 <<eof
    set echo on;
    connect target sys/@DCC&(_O@entDBp1
    connect auxiliary sys/@DCC&(_O@entDBuu
    run {
    allocate channel prmy1 type disk;
    allocate auxiliary channel stby1 type disk;
    duplicate target database
    to entDBu
    from active database pfile=/app/oracle/product/11.2.0.3/db/dbs/initentDBu.ora;
    show all;
    exit
    eof
    end_dt=`date +%Y%m%d_%H%M`
    mailx -s "DR RMAN Job: $job done" "[email protected]" <<eof2
    started: ${start_dt}
    finish: ${end_dt}
    eof2How to prevent the error of RMAN-06054: media recovery requesting unknown archived log for thread  with sequence   and starting SCN of  while performing the RMAN Active Cloning? I do NOT want to use UNTIL clause.Where UNTIL clause in your script I didn't saw.
    Please try following RMAN script
    DUPLICATE TARGET DATABASE FOR STANDBY
      FROM ACTIVE DATABASE
    SPFILE
       SET "control_files"="/u01/app/oracle/oradata/stbdbcontrol01.ctl"
       SET "db_name"="prmdb"
       SET "db_unique_name"="stbdb"
       SET "db_file_name_convert"="/u01/app/oracle/oradata/prmdb","/u01/app/oracle/oradata/stbdb"
       SET "log_file_name_convert"="/u01/app/oracle/oradata/prmdb","/u01/app/oracle/oradata/stbdb"
       SET "db_recovery_file_dest"="/u01/app/oracle/fra"
       SET "diagnostic_dest"=/u01/app/oracle"
       SET "audit_file_dest"="/u01/app/oracle/admin/stbdb/adump"
    PASSWORD FILE
    NOFILENAMECHECK;
    {code}
    Please change parameters for your environment.
    Regards
    Mahir M. Quluzade                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • 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

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

  • 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

  • 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

  • Block Media Recovery and RMAN Incremental Level 1 backup

    Hi
    I have read somewhere that Block Media Recovery will not work if a database is backed up using rman incremental 1. Is this true, and if so is there a work around?
    I cannot seem to find this in oralce's documentation.
    Regards
    Me

    Hi,
    1) is Full Backup = Incremental level 0 backup?
    Yes
    2) When oralce say BMR does not work with incremental, will it work in the case I put forward. becuase Im doing an incremental 0...
    But does you have the Archive logs available.. ?? If yes then it will Support.
    3) Im my case will BMR work...that is use Incr level 0 on Sunday and then use archive logs for mon, tues etc
    Yes, I believe.
    @Hemanth .. am I right.. ?? Wait for your inputs...
    - Pavan Kumar N

  • ARC0: media recovery disabled in Alert.log? What is ist?

    Hello this is Standing in my Alert.log;
    Dump file c:\timDB\oracle\dump\bgdump\tim1ALRT.LOG
    Tue Jun 21 13:08:18 2005
    ORACLE V8.1.7.0.0 - Production vsnsta=0
    vsnsql=e vsnxtr=3
    Windows NT Version 4.0 Service Pack 6, CPU type 586
    Tue Jun 21 13:08:18 2005
    Thread 1 advanced to log sequence 5496
    Current log# 4 seq# 5496 mem# 0: C:\TIMDB\ORA_BACKUP\TIM\ORA_REDO\TIM1LOG4.RDO
    Current log# 4 seq# 5496 mem# 1: C:\TIMDB\ORA_DB\TIM\ORA_REDO2\TIM1LOG4.RDO
    Tue Jun 21 13:08:18 2005
    ARC0: media recovery disabled
    What is Wrong wiht my Oracle?

    This problem occurs because an archive process has been started but it has nothing to do because the database is in NOARCHIVELOG mode. This could be rather serious if it is expected that the database runs in ARCHIVELOG mode.
    This happens when only log_archive_start = true. Which means an archive process is started on database startup, but because the database is not actually in archivelog mode, the archiver reports the above message.
    To verify use v$database view. The LOG_MODE is NOARCHIVELOG even though log_archive_start = true.
    Put the database in archivelog mode:
    1.1. Mount the database.
    1.2. Issue the command: ALTER DATABASE ARCHIVELOG;
    Jaffar

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

Maybe you are looking for

  • Page incomplete in edit mode

    I use frames, and when attempting to edit one of the frames, the correct frame comes up but it is incomplete with about 50%missing. I suspect this may be from a far earlier version of the page. So how do I get to the current page to edit. If you go t

  • Combined Analysis related question

    Dear all, I have a requirement from my customer as follows: - Display the list of opportunities split with Estimated order taking by Type (New business, Development on existing customer, Contract Renewal) and by Sales Stage with an indication of the

  • Is IWebBrowser2 will work in future version of Windows?

    I read from many news website that Microsoft is going to discontinue Internet Explorer for future version of Windows (after Windows 10) and will be replaced by Spartan web browser. My question is how IWebBrowser2 behavior in future version of Windows

  • Using an .aspx file for a spry dataset

    I need to pull title data and associated links from this page ( http://www.isurv.com/site/custom_scripts/rss_whats_new.aspx) on to a separate site where the info is displayed as latest news. Whilst locally I can get this to work in I.E.  no data show

  • New Kanaka for Mac Builds Address Heartbleed OpenSSL Bug

    Today Novell released Versions 2.7.1.1 and 2.8.0.1 of Novell Kanaka for Mac. These new builds include OpenSSL version 1.0.1gwhich is a fix for the Heartbleed vulnerability that can expose encrypted data being transmitted between components and a web