Thread: ORA-01153: incompatible media recovery - 2 STANBYs :-)

Thxs Guys,
Now I've 2 Standby's .......
If one is Good. 2 is even Better :-)))

Is this an answer on another topic ?? ;-)
If so, maybe close both ??

Similar Messages

  • ERROR in 9i standby - ORA-01153

    Hi,
    I am getting error while firing
    "recover standby database " command in my 9i standby.
    We are manually moving the archivelogs to standby from production, and firing the above command. All are done thru scheduled scripts .
    We have a recovery_run log file, with the detailed description of the recovery process running at standby.
    ----------The following is an extract from the alert log file.---------------
    Media Recovery Log /oracle/P71/saparch/P71arch1_334825.dbf
    Wed Dec 7 13:46:16 2005
    ALTER DATABASE RECOVER standby database
    Wed Dec 7 13:46:16 2005
    ORA-1153 signalled during: ALTER DATABASE RECOVER standby database ...
    Wed Dec 7 13:46:18 2005
    ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
    Wed Dec 7 13:46:18 2005
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Media Recovery Log /oracle/P71/saparch/P71arch1_334826.dbf
    Wed Dec 7 13:47:03 2005
    ALTER DATABASE RECOVER standby database
    Wed Dec 7 13:47:03 2005
    ORA-1153 signalled during: ALTER DATABASE RECOVER standby database ...
    Wed Dec 7 13:47:27 2005
    ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
    Wed Dec 7 13:47:27 2005
    --------The following is an extract from the Recovery_run log file.----------
    SQL*Plus: Release 9.2.0.5.0 - Production on Wed Dec 7 13:51:29 2005
    SQL> Connected.
    SQL> ORA-01153: an incompatible media recovery is active
    SQL> SP2-0042: unknown command "auto" - rest of line ignored.
    SQL> Disconnected from Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
    With the Partitioning option
    JServer Release 9.2.0.5.0 - Production
    Wed Dec 7 13:51:31 NFT 2005
    SQL*Plus: Release 9.2.0.5.0 - Production on Wed Dec 7 13:52:00 2005
    SQL> Connected.
    SQL> ORA-01153: an incompatible media recovery is active
    SQL> SP2-0042: unknown command "auto" - rest of line ignored.
    SQL> Disconnected from Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
    With the Partitioning option
    JServer Release 9.2.0.5.0 - Production
    Wed Dec 7 13:52:01 NFT 2005
    -------------The following is extract from the script that fires the recovery command-------------
    auto_recover()
    echo "connect / as sysdba" > /tmp/reco.sql
    echo "recover standby database " >> /tmp/reco.sql
    echo "auto" >> /tmp/reco.sql
    echo "exit" >> /tmp/reco.sql
    su - ${ORAUSER} -c sqlplus "/NOLOG" < /tmp/reco.sql | grep -v "Corpo" | grep -v "Manager"
    i checked the v$lock, and found that there is only one active session, which is holding the MR locks.
    It was working fine, and today we started getting this error
    Any idea about what is happening over here?
    Thanks in advance,
    Don

    At the standby, i also checked
    SQL> select max(sequence#) from v$log_history;
    And the max sequence number is getting incremented.
    That means, the archive logs are getting applied in the standby perfectly... right?
    But, how can that happen, since we are getting error while this command is run from the script?
    please help me out , to solve this issue.
    Thanks in advance,
    Don

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

  • 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

  • 11g standby database media recovery failed due to ora-600

    hi friends,
    DB: 11g 11.1.0.6
    OS: Windows server 2003 ent
    I've setup datagaurd using 11g. but for last 2 days, not able to start media recovey on standby database.
    here's my alertlog file
    alter database recover managed standby database using current logfile disconnect from session
    Sat Jan 03 11:23:04 2009
    MRP0 started with pid=18, OS id=648
    Fast Parallel Media Recovery enabled
    Managed Standby Recovery starting Real Time Apply
    Media Recovery apply datafile 5 offline range
    parallel recovery started with 2 processes
    Waiting for all non-current ORLs to be archived...
    Media Recovery Log C:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\GOLDSBY\ARCHIVELOG\2008_12_30\BACKUP\O1_MF_1_297_4ON23Q00_.ARC
    Completed: alter database recover managed standby database using current logfile disconnect from session
    Media Recovery Log C:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\GOLDSBY\ARCHIVELOG\2008_12_31\BACKUP\O1_MF_1_298_4OP3CLWS_.ARC
    Errors in file c:\app\administrator\diag\rdbms\goldsby\gold\trace\gold_mrp0_648.trc (incident=544158):
    ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
    Incident details in: c:\app\administrator\diag\rdbms\goldsby\gold\incident\incdir_544158\gold_mrp0_648_i544158.trc
    Errors with log C:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\GOLDSBY\ARCHIVELOG\2008_12_31\BACKUP\O1_MF_1_298_4OP3CLWS_.ARC
    MRP0: Background Media Recovery terminated with error 600
    Errors in file c:\app\administrator\diag\rdbms\goldsby\gold\trace\gold_mrp0_648.trc:
    ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
    Managed Standby Recovery not using Real Time Apply
    Shutting down recovery slaves due to error 600
    Recovery interrupted!
    Sat Jan 03 11:23:15 2009
    Trace dumping is performing id=[cdmp_20090103112315]
    Sat Jan 03 11:23:16 2009
    Recovered data files to a consistent state at change 92419435
    Errors in file c:\app\administrator\diag\rdbms\goldsby\gold\trace\gold_mrp0_648.trc:
    ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
    Errors in file c:\app\administrator\diag\rdbms\goldsby\gold\trace\gold_mrp0_648.trc:
    ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
    Sat Jan 03 11:23:17 2009
    Sweep Incident[544158]: completed
    MRP TRACE FILE
    ** 2009-01-03 11:05:36.140 1095 krsh.c
    MRP0: Background Managed Standby Recovery process started
    *** 2009-01-03 11:05:41.140
    *** 2009-01-03 11:05:41.140 1295 krsm.c
    Managed Recovery: Initialization posted.
    Started 11g Parallel Media Recovery
    Fast Parallel Media Recovery enabled
    *** 2009-01-03 11:05:41.156 1095 krsh.c
    Managed Standby Recovery starting Real Time Apply
    *** 2009-01-03 11:05:41.671
    Recovery target incarnation = 5, activation ID = 0
    Influx buffer limit = 31623 (50% x 63246)
    Successfully allocated 2 recovery slaves
    Start recovery at thread 1 ckpt scn 92413878 logseq 297 block 2
    *** 2009-01-03 11:05:43.281
    Media Recovery add redo thread 1
    *** 2009-01-03 11:05:43.296 1295 krsm.c
    Managed Recovery: Active posted.
    *** 2009-01-03 11:05:43.500
    Media Recovery Log C:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\GOLDSBY\ARCHIVELOG\2008_12_30\O1_MF_1_297_4ON1Y6NZ_.ARC
    *** 2009-01-03 11:05:44.093
    Media Recovery Log C:\APP\ADMINISTRATOR\FLASH_RECOVERY_AREA\GOLDSBY\ARCHIVELOG\2008_12_31\O1_MF_1_298_4ON74ROZ_.ARC
    *** 2009-01-03 11:05:44.906
    Incident 520220 created, dump file: c:\app\administrator\diag\rdbms\goldsby\gold\incident\incdir_520220\gold_mrp0_4044_i520220.trc
    ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
    *** 2009-01-03 11:05:45.687 1095 krsh.c
    MRP0: Background Media Recovery terminated with error 600
    ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
    *** 2009-01-03 11:05:45.687 1095 krsh.c
    Managed Standby Recovery not using Real Time Apply
    kcrrgaptime: no snapshot information available
    ----- Redo read statistics for thread 1 -----
    Read rate (ASYNC): 21376Kb in 2.55s => 8.19 Mb/sec
    Total redo bytes: 23424Kb Longest record: 14Kb, moves: 17/62299 moved: 0Mb (0%)
    Longest LWN: 804Kb, reads: 2357
    Last redo scn: 0x0000.05823f03 (92421891)
    Change vector header moves = 8621/118937 (7%)
    *** 2009-01-03 11:05:45.828
    Media Recovery drop redo thread 1
    Completed 11g Parallel Media Recovery
    Starting in-flux buffer recovery from SCN 0.92413878 to SCN (non-inclusive) 0.92419435
    *** 2009-01-03 11:05:46.265
    Influx Media Recovery add redo thread 1
    *** 2009-01-03 11:05:47.531
    *** 2009-01-03 11:05:47.531 1295 krsm.c
    Managed Recovery: Not Active posted.
    ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
    ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
    error 473 detected in background process
    OPIRIP: Uncaught error 447. Error stack:
    ORA-00447: fatal error in background process
    ORA-00600: internal error code, arguments: [3012], [5], [131], [0], [92421891], [0], [92413878], []
    could you help on this...?
    waiting for your favorable reply,
    thanks in advance..
    Regards

    Hi;
    This error occurs when you have run a switchover/ failover, you may have two parallel standby's but when you pass the command for switchover the one standby is not aware of what you have done.
    The point is that all standby should know who is your primary & standby's should also be aware of each other in their "pfiles" now, you should either recreate the standby or open with reset logs.
    ora-600 occurs due to different incarnation.
    Hope this will help you
    if you switch multiple logfiles in primary, & run >>
    alter database recover managed standby database disconnect;
    your standby will start syncing.
    Hope this will help you

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

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

  • ORA-01113: file5 needs media recovery

    Dear All
    When I connected to my database, I got message the database is shutdown.
    When I shutdown my database and try to restart my database again, I got the following errors:
    ORA-01113: file 5 needs media recovery
    ORA-01110: data file 5: C:\DB11\ORADATA\DB11\Example01.dbf
    Many thanks, Helen

    Dear Helen,
    Data from Example users like HR and any other example schemas if created in installation.
    If you create any user and assgn other tablespace (like users) you will not lose that data's.
    For more safely, shudown database and copy all you datafiles, controll file and redo log files other places (Cold Backup)
    Regards,
    Reza

  • Ora-01113: USERS01.dbf need's media recovery when starting database

    Bear with me if this seems a stupid question. (I'm a developer and just starting to catch up the DBA job).
    Our database server is down and when we tried to bring it back using DBA studio (logon as SYS), we got the following error: ora-01113: USERS01.dbf need's media recovery.
    From the documentation I know I can do a media recovery on the datafile. But with the database not being open, how am I getting access to SQL plus and perform this task? I tried to log on using the SYS credential and I could not log on. Please help. Thanks very much. Changsong

    Get connection from SQL*Plus at the command line to carry out that so:
    export ORACLE_SID<database_sid>
    sqlplus /nolog
    conn / as sysdba
    recover ....
    Joel Pèrez
    http://otn.oracle.com/experts

  • ORA-01123: cannot start online backup; media recovery not enabled

    the Oracle doc says:
    Action: Enable media recovery and retry this operation.
    how helpful it is!
    Could someone advise me on what is exactly the command
    for "enable media recovery"?
    Thanks.
    - Zack Hu

    but when I modified the init.ora file and re-start the
    db, I still have "NO archive mode", when I tried to
    set it to archive mode I got an error:
    SQL> startup pfile='D:\oracle\admin\WinMWDCS\pfile\initWinMWDCS.ora';
    ORACLE instance started.
    Total System Global Area 135863156 bytes
    Fixed Size 453492 bytes
    Variable Size 109051904 bytes
    Database Buffers 25165824 bytes
    Redo Buffers 1191936 bytes
    Database mounted.
    Database opened.
    SQL> archive log list;
    Database log mode No Archive Mode
    Automatic archival Enabled
    Archive destination d:\oracle\oradata\WinMWDCS\archive
    Oldest online log sequence 73
    Current log sequence 75
    SQL> alter database archivelog;
    alter database archivelog
    ERROR at line 1:
    ORA-01126: database must be mounted EXCLUSIVE and not open for this operation

  • ORA-279 signalled during recovery of standby database

    Hi All,
    I am preparing standby database after taking hot backup and copying those datafiles to standby,
    taken controlfile standby controlfile backup from primary
    mounted the standby database using standby controlfile using
    startup nomount pfile='/u01/stand.ora'
    alter database mount standby database;
    Now I have started applying archives on standby database after copying all archives from primary to standby box the archives generated during backup using..
    recover standby database;
    But I am getting the below warning on the recovery screen...
    ORA-00279: change 51667629050 generated at 07/02/2009 00:59:43 needed for
    thread 1
    ORA-00289: suggestion : /nodal-archive/archive/1_55118_652209172.arc
    ORA-00280: change 51667629050 for thread 1 is in sequence #55118
    ORA-00278: log file '/nodal-archive/archive/1_55117_652209172.arc' no longer
    needed for this recovery
    ORA-00279: change 51667703096 generated at 07/02/2009 01:06:04 needed for
    thread 1
    ORA-00289: suggestion : /nodal-archive/archive/1_55119_652209172.arc
    ORA-00280: change 51667703096 for thread 1 is in sequence #55119
    ORA-00278: log file '/nodal-archive/archive/1_55118_652209172.arc' no longer
    needed for this recovery
    ORA-00279: change 51667767649 generated at 07/02/2009 01:12:28 needed for
    thread 1
    ORA-00289: suggestion : /nodal-archive/archive/1_55120_652209172.arc
    ORA-00280: change 51667767649 for thread 1 is in sequence #55120
    ORA-00278: log file '/nodal-archive/archive/1_55119_652209172.arc' no longer
    needed for this recovery
    ORA-00279: change 51667831821 generated at 07/02/2009 01:19:40 needed for
    thread 1
    ORA-00289: suggestion : /nodal-archive/archive/1_55121_652209172.arc
    ORA-00280: change 51667831821 for thread 1 is in sequence #55121
    ORA-00278: log file '/nodal-archive/archive/1_55120_652209172.arc' no longer
    needed for this recovery
    and I am getting the below warning on the alert log..........
    Sun Jul 5 18:37:36 2009
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Sun Jul 5 18:37:36 2009
    Media Recovery Log /nodal-archive/archive/1_55256_652209172.arc
    Sun Jul 5 18:40:31 2009
    ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
    Sun Jul 5 18:40:31 2009
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Sun Jul 5 18:40:31 2009
    Media Recovery Log /nodal-archive/archive/1_55257_652209172.arc
    Please suggest what to do now.............
    Thanks in Advance,
    Sukanta Paul.

    Hi Sukanta,
    I didn't really understand what the problem is...
    Let me explain, hope it will be clear.
    You created a standby control file, and backed up the database (it doesn't matter in which order). Now, you have a standby database that is ready to apply logs. It will be able to apply log forever, until we will stop it.
    The messages you see say the following:
    ORA-00279: change 51667831821 generated at 07/02/2009 01:19:40 needed for thread 1 {color:blue} - this says that the recovery process is now at scn 51667831821 {color}
    ORA-00289: suggestion : /nodal-archive/archive/1_55121_652209172.arc {color:blue} - the information needed for the recover is in this file (this is only the default name, you can choose other name if the file is called differently) {color}
    ORA-00280: change 51667831821 for thread 1 is in sequence #55121 {color:blue} - same here, the needed archive is sequence 55121 {color}
    ORA-00278: log file '/nodal-archive/archive/1_55120_652209172.arc' no longer needed for this recovery {color:blue} - this message is after Oracle has applied the log, and it means that this log is no longer needed {color}
    Now it will wait for the next log. Again, this process is endless, this is how it is made to allow the standby database to be always synched with the primary.
    Liron Amitzi
    Senior DBA consultant
    [www.dbsnaps.com]
    [www.orbiumsoftware.com]

  • ORA-1093 during Database Recovery in 11g R2

    1. PSEUDO Process present in the standby db preventing the switch to recovery mode (initiated by the application)
    Excerpt from the alert log
    Active process 0 user '' program 'PSEUDO'
    Active process 0 user '' program 'PSEUDO'
    Active process 0 user '' program 'PSEUDO'
    Active process 0 user '' program 'PSEUDO'
    Active process 0 user '' program 'PSEUDO'
    CLOSE: Active sessions prevent database close operation
    CLOSE: Error 1093 during database close
    ORA-1093 signalled during: ALTER DATABASE RECOVER standby database ...
    2. Active process in the standby db preventing the switch to recovery mode (initiated by the application)
    Excerpt from the alert log
    CLOSE: Active sessions prevent database close operation
    CLOSE: Error 1093 during database close
    ORA-1093 signalled during: ALTER DATABASE RECOVER standby database ...
    Fri Nov 05 17:25:27 2010
    ALTER DATABASE RECOVER standby database
    Active process 9467 user 'oracle' program 'oracle@xldn0917dor'
    3.Media Recovery halts abruptly on standby (while running in recovery mode) / Media Recovery switches from parallel recovery to single threaded
    The Work around for all the 3 Scenarios is to bounce the standby database, and its back to normal functioning.
    I have already sent the DB/Server Details for LH Global env's, Pl. review them and let me know if there are any gaps in info.
    Pls advice.

    I made changes as per your suggestion, i am still getting same error.
    here is my tns entires
    [orawiz@wizapp admin]$ cat tnsnames.ora
    # tnsnames.ora Network Configuration File: /wiz_app/wiz/oracle/product/11.2.0/db_1/network/admin/tnsnames.ora
    # Generated by Oracle configuration tools.
    LISTENER =
    (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.172.20.236)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = wiz)
    WIZ =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 10.172.20.236)(PORT = 1521))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = wizapp.com)
    [orawiz@wizapp admin]$
    [orawiz@wizapp admin]$ tnsping wiz
    TNS Ping Utility for Linux: Version 11.2.0.1.0 - Production on 20-FEB-2012 17:23:18
    Copyright (c) 1997, 2009, Oracle. All rights reserved.
    Used parameter files:
    /wiz_app/wiz/oracle/product/11.2.0/db_1/network/admin/sqlnet.ora
    TNS-03505: Failed to resolve name
    [orawiz@wizapp admin]$ lsnrctl status
    LSNRCTL for Linux: Version 11.2.0.1.0 - Production on 20-FEB-2012 17:23:44
    Copyright (c) 1991, 2009, Oracle. All rights reserved.
    Connecting to (ADDRESS=(PROTOCOL=tcp)(HOST=)(PORT=1521))
    STATUS of the LISTENER
    Alias LISTENER
    Version TNSLSNR for Linux: Version 11.2.0.1.0 - Production
    Start Date 20-FEB-2012 17:12:30
    Uptime 0 days 0 hr. 11 min. 14 sec
    Trace Level off
    Security ON: Local OS Authentication
    SNMP OFF
    Listener Parameter File /wiz_app/wiz/oracle/product/11.2.0/db_1/network/admin/listener.ora
    Listener Log File /wiz_app/wiz/oracle/diag/tnslsnr/wizapp/listener/alert/log.xml
    Listening Endpoints Summary...
    (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=wizapp.com)(PORT=1521)))
    Services Summary...
    Service "wiz" has 2 instance(s).
    Instance "wiz", status UNKNOWN, has 1 handler(s) for this service...
    Instance "wiz", status READY, has 1 handler(s) for this service...
    Service "wizXDB" has 1 instance(s).
    Instance "wiz", status READY, has 1 handler(s) for this service...
    The command completed successfully
    [orawiz@wizapp admin]$ cat

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

  • ORA-27023: skgfqsbi: media manager protocol error

    can some one please tell me what to do regarding this error, and how can i solve it. the result log is stated below...
    Recovery Manager: Release 10.2.0.1.0 - Production on Tue Oct 16 15:26:49 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    RMAN>
    connected to target database: MOT (DBID=2759813257)
    using target database control file instead of recovery catalog
    RMAN>
    echo set on
    RMAN> run {
    2> allocate channel oem_sbt_backup type 'sbt_tape' format '%U';
    3> backup as BACKUPSET current controlfile tag '10162007032648';
    4> restore controlfile validate from tag '10162007032648';
    5> release channel oem_sbt_backup;
    6> }
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of allocate command on oem_sbt_backup channel at 10/16/2007 15:26:50
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27023: skgfqsbi: media manager protocol error
    ORA-19511: Error received from media manager layer, error text:
    sbt__rpc_connect: Internal error - could not connect to obproxyd (Oracle Secure Backup error: 'bad port name specified (OB SBT proxy manager)').
    RMAN> allocate channel for maintenance type 'sbt_tape' ;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of allocate command on ORA_MAINT_SBT_TAPE_1 channel at 10/16/2007 15:26:51
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27023: skgfqsbi: media manager protocol error
    ORA-19511: Error received from media manager layer, error text:
    sbt__rpc_connect: Internal error - could not connect to obproxyd (Oracle Secure Backup error: 'bad port name specified (OB SBT proxy manager)').
    RMAN> delete noprompt backuppiece tag '10162007032648';
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=125 devtype=DISK
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of delete command at 10/16/2007 15:26:51
    RMAN-06168: no backup pieces with this tag found: 10162007032648
    RMAN> exit;
    Recovery Manager complete.

    can some one please tell me what to do regarding this error, and how can i solve it. the result log is stated below...
    Recovery Manager: Release 10.2.0.1.0 - Production on Tue Oct 16 15:26:49 2007
    Copyright (c) 1982, 2005, Oracle. All rights reserved.
    RMAN>
    connected to target database: MOT (DBID=2759813257)
    using target database control file instead of recovery catalog
    RMAN>
    echo set on
    RMAN> run {
    2> allocate channel oem_sbt_backup type 'sbt_tape' format '%U';
    3> backup as BACKUPSET current controlfile tag '10162007032648';
    4> restore controlfile validate from tag '10162007032648';
    5> release channel oem_sbt_backup;
    6> }
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of allocate command on oem_sbt_backup channel at 10/16/2007 15:26:50
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27023: skgfqsbi: media manager protocol error
    ORA-19511: Error received from media manager layer, error text:
    sbt__rpc_connect: Internal error - could not connect to obproxyd (Oracle Secure Backup error: 'bad port name specified (OB SBT proxy manager)').
    RMAN> allocate channel for maintenance type 'sbt_tape' ;
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03009: failure of allocate command on ORA_MAINT_SBT_TAPE_1 channel at 10/16/2007 15:26:51
    ORA-19554: error allocating device, device type: SBT_TAPE, device name:
    ORA-27023: skgfqsbi: media manager protocol error
    ORA-19511: Error received from media manager layer, error text:
    sbt__rpc_connect: Internal error - could not connect to obproxyd (Oracle Secure Backup error: 'bad port name specified (OB SBT proxy manager)').
    RMAN> delete noprompt backuppiece tag '10162007032648';
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=125 devtype=DISK
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of delete command at 10/16/2007 15:26:51
    RMAN-06168: no backup pieces with this tag found: 10162007032648
    RMAN> exit;
    Recovery Manager complete.

  • 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

Maybe you are looking for

  • Error while posting .ZIP file

    Hi All, I am working on file to file scenario.. I want to post .zip file from source to target. I am not using any mapping for this... I m using the Integrated configuration for theis scenario.. We are using sFTP advantco adapter for both sender and

  • .CR2 files won't open in Photoshop CS4

    I recently got CS4 Extended version of Photoshop and need to work on my RAW files, but they won't open. I can see the thumbnails in Bridge and when I try to open them Photoshop says they're "not the right type of document"...so...not sure what to do.

  • Overwriting AQ Queue name dynamically in OSB

    Hi, Can any one please help me on this. Is there any way we can overwrite the AQ Queue name dynamically at runtime in OSB . I copuld see that its a property within the .jca file. Is there any way we can overwrite it at run time. Thanks, Naveen

  • My Macbook Pro gets slow the longer I use it?!

    Hi everyone, recently my MacBook Pro 2011 has been very slow. It started acting up about a week ago after I left my laptop on stand by mode for a while and when I returned to using it, the laptop was really slow, significantly slower compared to befo

  • Service Book Entry

    Dear, i have a BB 8520 and i accidentely deleted almost everyting from the SERVICE BOOK enrty. now if i want to open Twitter it says - "could not find a service book entry for IPPP". if i try to open BB app world it says - "please contact your servic