Database Crash - Media Recovery Required - [SOLVED]

I am trying to understand why media recovery was required when our database had crashed ( this was 2 months ago ). This is just for my understanding and I would appreciate if you could explain it to me.
We have a 10g database on Solaris 10 and EMC SAN for storage. One of the technicians came in look at some electrical issue. And accidentally turned off the power supply to the SAN.
This caused the database instance to crash.
When the DBA tried to startup the database, he said that he was getting errors that some datafiles were corrupted and ruled that media recovery was required.
He took the backups taken 12 hours ago and applied the archived redo logs. Everything was fine except for the downtime ( it took 6 hours for this whole process).
I have several questions:
1. why would the datafiles get corrupted? was the disk in the process of writing and could not complete the task?
2. why did the database not do crash recovery i.e use redo logs? why did we have to use backup?
Thanks.
Message was edited by:
sayeed

1. why would the datafiles get corrupted? was the
disk in the process of writing and could not complete
the task?This could happen if a datafile being accessed during the power failure resulting in corrupting the file which can happen to any file during power failure..In this case it was datafile resulting in dataabse crash...
2. why did the database not do crash recovery i.e
use redo logs? why did we have to use backup?Since the file is corrupted you need to replace it with a last backup and apply logs to bring it consistent state....
Again ..This is what i have understood so far
correct me if i am wrong

Similar Messages

  • SYSAUX DATAFILE CONSTANTLY REQUIRES MEDIA RECOVERY

    Hello,
    Can anyone help me with this reoccurring problem in my Oracle 10g EE R2 database? My sysaux datafile is always going offline and requires media recovery before it can be brought back online. I have created additional datafiles but that didn't resolve the issue.
    Thank you.

    As for your "Failed to find ARCH for message..."
    Check this out:
    Cause
    Bug 4704334 - ''TKCRRSARC: (WARN) FAILED TO FIND ARCH FOR MESSAGE (MESSAGE:0X1)''
    These messages are warning messages and are a consequence of the internal archive process spawning and releasing.
    There can be different reasons for this message to appear, but it is in fact related to internal work.
    Solution
    These are only diagnostic messages and can be safely ignored.
    However, there are two options:
    Option 1
    Ignore the messages.
    Option 2
    Increase the log_archive_max_processes equal to/or greater than 10
    *Testing information about Option 2
    log_archive_max_processes=2 may still cause messages, and 4 may cause less.
    Recommended setting is 10 or higher as testing has verified that messages disappeared completely at this setting.
    References
    Bug 4704334 - ''TKCRRSARC: (WARN) FAILED TO FIND ARCH FOR MESSAGE (MESSAGE:0X1)''

  • 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

  • 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

  • Need a Query to find whether the database needs any media recovery...

    Hi,
    I am at the mount stage of a database and yet be opened.at this stage any Query is available or any other way is there to find whether the database needs any media recovery or Instance recovery..?
    my objective is before opening the database i need to make sure it is consistent or inconsistent and any form of recovery is needed..
    thanks &regards,
    Ragunath
    Edited by: ragu.dba.in on Mar 6, 2013 12:57 AM

    Hi Ragunath,
    Use these queries , SCN should be consistent .. no fuzzy files, check for recovery of files in v$recover_file .. pass sufficient archives & fulfill the checks before open reset-logs
    set line 900
    set pages 900
    set echo on
    alter session set nls_date_format='dd-mon-yyyy hh24:mi:ss';
    set numwidth 13
    col CHECKPOINT_CHANGE# for 9999999999999999
    col CHANGE# for 9999999999999999
    column error format a10
    column member format a60
    show parameter db_recover
    select * from v$recover_file;
    select file#, status from v$datafile;
    select file#, checkpoint_change#, checkpoint_time, error from v$datafile_header;
    select distinct status from v$backup;
    select distinct  checkpoint_change#  from v$datafile_header;
    select hxfil file_id, fhscn scn, fhthr thread, fhrba_seq sequence, fhsta status from x$kcvfh;
    select distinct fhscn from x$kcvfh;
    select hxfil file_id, fhtnm tablespace_name from x$kcvfh;
    ##### Fuzzy Check ####
    alter session set nls_date_format = 'DD-MON-YYYY HH24:MI:SS';
    set feedback on
    set heading on
    set pagesize 1000
    set linesize 175
    column checkpoint_change# format 999999999999999999999
    select status, checkpoint_change#, fuzzy,
    to_char(checkpoint_time, 'DD-MON-YYYY HH24:MI:SS') as checkpoint_time,
    count(*)
    from v$datafile_header
    group by status, checkpoint_change#, fuzzy, checkpoint_time
    order by status, checkpoint_change#, fuzzy, checkpoint_time;Thanks,
    Ajay More
    http://www.moreajays.com

  • 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

  • ORACLE 9I DATABASE - CRASH & RECOVER

    I AM USING ORACLE 9I FOR LINUX IN A DUAL XEON PROCESSOR SERVER. NOW DATABASE DOES NOT OPEN PROPERLY AND SHOW FOLLOWING MESSAGES:-
    1) for SYSDBA user message for startup database
    SQL*Plus: Release 9.2.0.1.0 - Production on Thu Aug 21 18:49:14 2003
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    Enter user-name: sys as sysdba
    Enter password:
    Connected to an idle instance.
    SQL> startup
    ORACLE instance started.
    Total System Global Area 621875780 bytes
    Fixed Size 451140 bytes
    Variable Size 335544320 bytes
    Database Buffers 285212672 bytes
    Redo Buffers 667648 bytes
    Database mounted.
    ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
    SQL>
    2) Then we reset the logs the message is:
    SQL> alter database open resetlogs;
    alter database open resetlogs
    ERROR at line 1:
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/C/app/oracle9ir2/oradata/tepiapp/system01.dbf'
    SQL>
    3) When connecting with different user the message is :
    Enter user-name: mis-dba
    Enter password:
    ERROR:
    ORA-01033: ORACLE initialization or shutdown in progress
    SP2-0157: unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus
    0;oracle@tepiapp:~[oracle@tepiapp oracle]$
    Please guide me for detail solutions for this problem
    Regards,
    FSL

    hmmm ok, so it seems that you dont use RMAN to backup your database...
    It seems there that your have a controlfile problem after a disk crash. I hope your database is on ARCHIVELOG mode.
    Does your database crashed during activity or was idle ?
    1. Mount the database
    2. set autorecovery on ;
    recover database using backup controlfile ;
    media recovery complete <= this means that all is ok now
    3. alter database open resetlogs ;
    if #2 doesnt work cause of redo log problem such as corrupted redo log, or some transactions "blocked" in theses redo log cause of a big crash during the database activity, Oracle will tell you that a redo log is corrupted and will give you the hour of the redo log log entry that Oracle need to recover.
    So you will have to make an incomplete recovery (that means you will lose some datas, no much but some) until time.
    For example, your redo entry has been corrupted at 12:00:50
    1. recover database until time '2003-08-25:12:00:00' ;
    2. alter database open resetlogs ;
    3. Make a full backup of your database !
    Fred

  • 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

  • About Media Recovery

    Hi,
    I'm confused what will cause the Media Recovery. I found some documents said when the Checkpoint SCN in datafile does not equal to the SCN in control file will lead to Media Recovery, but some documents said it's caused by the difference of the Checkpoint Count. All the refered document are come from Oracle.
    Besides, when the tablespace be online backup, the SCN in datafile and control file are frezed, but the Checkpoint Count in datafile is still changed. I'm not the checkpoint count in control file is also changed or not? But if shutdown database without ending the online backup, it will raise the ora-01113 error. Is it said the Checkpoint Count the judging condition?
    Regards,
    Edgar

    Hi
    . A recovery that SMON can perform entirely automatically is known as an instance recovery. One which requires manual intervention from the DBA is known as a media recovery.
    A reasonable question to ask is, 'On what basis does SMON assess a database as being healthy or in need of recovery?'. To which the answer is: checkpoint change numbers. Periodically, the database is "timestamped" with a new sequence number (the latest number from a pool of ever-increasing sequence numbers). So long as every file in the database has been stamped with the same number, we can say that the database is 'consistent to that point of time'. If all the checkpoint change numbers that SMON reads during the database opening procedure, and which are stored in the headers of every physical file constituting the database, are the same, the database is healthy. If they are not all the same, and if there are no good reasons for the difference, the database is presumed to have suffered some sort of failure and a recovery procedure is therefore invoked.
    CKPT (Checkpoint) is another reasonable question to then ask, 'What writes the checkpoint change number, which SMON reads, into the headers of each database file?'. To which the answer is, 'Another background process called Checkpoint, abbreviated as CKPT'. The occasions when CKPT writes its information into the headers of all database files are known as checkpoint events.
    Every transaction that takes place on an Oracle database (that is, every insert, update or delete of a record) causes a system-wide sequence number called the System Change Number or SCN to be incremented. At a checkpoint event, the latest SCN is deemed to be the latest Checkpoint change number, and it is this CCN which is written by CKPT into the headers of all database files.
    It is fair to say that, during prolonged database operation, CKPT will forever be writing new checkpoint change numbers into the headers of all the database files; it is SMON's job, at the opening of the database, to ensure that every constituent component of the database agrees on what the latest checkpoint change number should be. If they are all in agreement, the database opens. If there is disagreement, recovery is called for.
    To make things even simpler: SMON reads what CKPT writes, and both processes are intimately involved in identifying when databases need recovery, and how much recovery they need, if any.
    Govinda Krishna

  • Oracle Database Point intime recovery with File System backup.

    Hi.. Experts...
    We have shutdown the database and have take a file system backup on
    09.10.2010 @ 10 AM.
    We started the database and all the  archive logs generated after that are already
    available in archive directory till now.
    We discovered there were some  deletions took place. Yesterday evening at 4 PM.
    Requirement.
    We want to recover the database till  yesterday 3.30 PM.
    Can any one send steps to recover with above backup and available archive logs till 3.30 PM Yesterday.
    Regards

    Experts.....Nick Loy, Varadharajan M, Mark & Volker.............Thanks U Very Much.
    TAIL END MESSAGE OF RECOVERY COMMAND
    ORA-00279: change 11331655931 generated at 10/10/2010 11:30:56 needed for
    thread 1
    ORA-00289: suggestion : /oracle/D10/oraarch/D10arch1_123487_607825009.dbf
    ORA-00280: change 11331655931 for thread 1 is in sequence #123487
    ORA-00278: log file '/oracle/D10/oraarch/D10arch1_123486_607825009.dbf' no
    longer needed for this recovery
    Log applied.
    Media recovery complete.
    SQL>
    SQL>
    SQL> ALTER DATABASE OPEN RESETLOGS;
    Database altered.
    SQL>
    SYSTEM RECOVERED TO DEMAND & RELEASED
    T H A N K S    --   T O    --   E V E R Y O N E .
    RGDS

  • How do I enable media recovery?

    I’m a student, trying to execute the following command:
    ALTER TABLESPACE USERS01 BEGIN BACKUP;
    But I keep getting an error telling me that I need to enable media recovery. What does this mean and how can I do it?

    Hi..
    This kind of backup is called hot backup, which requires the database to be ARCHIVELOG MODE.If the database is not in archive log mode, you will get error.This is because when you restore the database from this kind of backups, archivelogs will be required to bring the database in consistent mode.
    [http://download.oracle.com/docs/cd/B10501_01/server.920/a96519/backup.htm#1004914]
    HTH
    Anand
    Edited by: Anand... on Dec 9, 2008 9:44 AM Added link

  • Rman with commvault mml: database crash while delete obsolete

    Hello!
    I have a problem concerning RMAN, delete obsolete and CommVault media management library: Every night at 23:00 we run a RMAN "Backup" to delete the obsolete backup files from tape. Since the update to CommVault agent 8 (from version 7) the database crashes while the delete obsolete command. The normal backup (incremental 0/1) works without problem.
    After restarting the database i tried the delete obsolete via shell -> same result: CRASH.
    The CommVault support says that there is an Oracle bug with different MML's, that causes this behaviour - but i can't find anything at Metalink.
    This is the output of RMAN (tell me which other logs can be helpful):
    RMAN-Sperr-Policy wird f³r den Befehl angewendet
    RMAN-Sperr-Policy ist auf ein Recovery-Fenster von 0 Tagen festgelegt
    Die folgenden veralteten Backups und Kopien werden gel÷scht:
    Typ Schl³ssel Abschlusszeit Dateiname/Handle
    Backup Set 7 01.09.10
    Backup Piece 12 01.09.10 c-190884945-20100901-01
    Backup Set 9 01.09.10
    Backup Piece 17 01.09.10 c-190884945-20100901-02
    M÷chten Sie die obigen Objekte wirklich l÷schen (geben Sie YES oder NO ein)? yes
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-00601: fatal error in recovery manager
    RMAN-03004: Abbruchfehler bei der Ausf³hrung des Befehls
    ORA-12514: TNS: Listener kann in Connect-Deskriptor angegebenen Service aktuell nicht aufl÷sen -> listener can not resolve service name
    RMAN-03009: Fehler bei delete Befehl in ORA_MAINT_SBT_TAPE_1 Kanal auf 09/02/2010 08:57:37 -> error at delete command
    ORA-03135: connection lost contact
    Recovery Manager nicht kompatibel mit TARGET Datenbank: RMAN 14155912.14155908.14312748.1 bis 1651797107.0.27143.0 erforderlich -> recovery not compatible with TARGET database
    Best regards,
    Christian

    Hi,
    show parameter plsq
    plsql_code_type           string     INTERPRETED
    plsql_compiler_flags          string     INTERPRETED, NON_DEBUG
    That database is in interpreted mode.
    Check also the pacakages:
    select OWNER, OBJECT_NAME , PARAM_NAME ||'='||PARAM_VALUE param from DBA_STORED_SETTINGS where OBJECT_NAME in ( 'DBMS_RCVCAT','DBMS_RCVMAN' )and param_name = 'plsql_code_type'
    OWNER               OBJECT_NAME
    PARAM
    SYS               DBMS_RCVMAN plsql_code_type=INTERPRETED
    SYS               DBMS_RCVMAN plsql_code_type=INTERPRETED
    If it is native you have an issue!
    François,

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

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

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

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

Maybe you are looking for

  • Stills Resolution - Photo Browser vs. Importing into Event

    All, I am preparing a slideshow with photos of varying size.  I manage my photos in Aperture and usually use the photo browser in Final Cut Pro X to access them. Some of the photos are low-res (0.1 MB 286 x 369 pixels, for example).  If I bring the e

  • Time Capsule-unable to set up

    Currently have iMac G5 (1.8GHz PowerPC G5 OS 10.5.8) with Airport Extreme Base Station Model A1143 and PowerBook Pro 15" (2.53 GHz Intel Core Duo OS 10.5.8) and PowerBook Pro 13" (2.66 GHz Intel Core Duo OS 10.6.3). Purchased Time Capsule 1TB 802.11n

  • Not all Prefixes in VRF Tables are Reachable?

    Hello, During my studies with an MPLS VPN [MP-BGP] lab I found something unexpected.  I wonder if I am mistaken in my comprehension or if this normal: Not all prefixes in a VRF Table are pingable/reachable ? Seems that in the standard routing tables,

  • Backup Suspended on Agent Unreachable - 11GR2 Windows

    Hi as the title suggests an RMAN backup has gone into a state of Suspended on Agent Unreachable. I have a 2 node RAC and have run emctl status dbconsole on each node. On node 1 I get a message: EM Daemon is running. On node 2 I get a message: Oracle

  • Downloading and Installing Element

    I am trying to download Elements 10...First it would give me an error after it took forever to download...I downloaded it again and now when I install Akamai NetSession Interface it says The installation failed.  The installer encountered an error th