ORA-00313: open failed for members during restore from COLD backup

Hi all,
I took a cold backup of an 11.1 database using RMAN (database in mount state).
I used the following command to restore it:
restored the controlfile and then
RESTORE DATABASE FROM TAG 'TAGxxxxxxxxxx';
Now I'm restoring it and it's taking too much time. When checking alert log it says:
ORA-51106: check failed to complete due to an error. See error below
ORA-48318: ADR Relation [HM_FINDING] of version=3 cannot be supported
ORA-00313: open failed for members of log group 1 of thread 1
ORA-00312: online log 1 thread 1: '/oracle1/oradata/******/redo1_02.log'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
Additional information: 3
RMAN is still in progress, why does it complain about redo?
I'm not doing recovery since it was a cold backup.
Thanks in advance.

Hi Michael,
Yes, it's the correct one because it says "full restore complete":
ORA-00312: online log 1 thread 1: '/oracle1/oradata/******/redo1_01.log'
ORA-27037: unable to obtain file status
HPUX-ia64 Error: 2: No such file or directory
Additional information: 3
Tue Apr 30 14:38:14 2013
Full restore complete of datafile 32 /oracle1/oradata/******/apr_sesm_index_01.dbf. Elapsed time: 1:25:42
checkpoint is 12652187135448
last deallocation scn is 12651877642745
Tue Apr 30 15:38:04 2013
Full restore complete of datafile 34 /oracle1/oradata/******/apr_stage_data_01.dbf. Elapsed time: 6:42:52
checkpoint is 12652187135448
last deallocation scn is 12651877637877
thanks,

Similar Messages

  • ORA-00313: open failed for members of log group 1 of thread 1

    Hi
    I'm restoring a database on a different host. I have the backups, from which I want to restore the database. I made the corresponding changes in the initSID.ora file and started the script to do the restore.These are the steps I followed:
    connect target=/
    run{
    startup nomount;
    allocate channel c1 type disk;
    allocate channel c2 type disk;
    allocate channel c3 type disk;
    allocate channel c4 type disk;
    restore controlfile from '/tmp_backups/rman/lev0_open_cf_SID_2826_1';
    alter database mount;
    set newname for all datafiles
    restore database;
    set until logseq = 29317 thread = 1;
    switch datafile all;
    recover database;
    alter database open resetlogs;
    One mistake I made here is that logseq should have been last seq+1, which I did not do. I have it as last seq.
    Restore of datafiles and switching of datafiles was fine. But I get error for redo log files.
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u13/oradata/SID/redo02a.log'
    ORA-27037: unable to obtain file status
    SVR4 Error: 2: No such file or directory
    Additional information: 3
    Why is it looking for at the old path yet?
    I'm not sure what I missed and how to proceed. Please help.
    Thanks,
    Mamata

    I do believe that set newname for all datafiles only means actual datafiles and no redo logs. So with open resetlogs, Oracle tries to create new redo logfiles where the backup controlfiles says they are.
    As with creating a auxilliary database in another filesystem, we use DB_NAME_FILE_CONVERT and LOG_FILE_NAME_CONVERT.
    I am not sure if it is possible to type "set newname for all datafiles" and expect also the redo logfiles to change location.
    You might try to set these two parameters and see if it works.
    good luck.
    rgds
    Kjell Ove

  • ORA-00313: open failed for members of log group 3 of thread 1

    Whenever I try to login as a user I get the following:
    sqlplus user/user
    SQL*Plus: Release 10.2.0.2.0 - Production on Fri Nov 9 10:43:39 2007
    Copyright (c) 1982, 2005, Oracle. All Rights Reserved.
    ERROR:
    ORA-01033: ORACLE initialization or shutdown in progress
    So It occurs to me to login as sysdba and restart the DB …
    SQL> connect sys/manager as sysdba
    Connected.
    SQL> shutdown immediate;
    ORA-01109: database not open
    Database dismounted.
    ORACLE instance shut down.
    SQL> startup
    ORACLE instance started.
    Total System Global Area 536870912 bytes
    Fixed Size 1281264 bytes
    Variable Size 150995728 bytes
    Database Buffers 377487360 bytes
    Redo Buffers 7106560 bytes
    Database mounted.
    ORA-00313: open failed for members of log group 3 of thread 1
    ORA-00312: online log 3 thread 1: '/u06/oradata/RKDB/redo03.log'
    ORA-27037: unable to obtain file status
    Intel SVR4 UNIX Error: 2: No such file or directory
    Additional information: 3
    SQL> quit
    I now realized what happened and how this happened. During a clean-up effort this file was accidentally deleted and unfortunately we don’t have any backups.
    I am willing to lose the data. Is there something I can do so that the startup does not try to open this file ?
    All I am able to do now is to mount the database but not open it.
    Thanks in advance,
    Daniel

    this is what I get now ...
    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: '/u02/oradata/RKDB/system01.dbf'
    SQL> Recover database until cancel;
    ORA-00279: change 608619 generated at 11/09/2007 10:00:41 needed for thread 1
    ORA-00289: suggestion : /u05/oradata/RKDB/arch/log1_33_633207859.arc
    ORA-00280: change 608619 for thread 1 is in sequence #33
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    ORA-00308: cannot open archived log
    '/u05/oradata/RKDB/arch/log1_33_633207859.arc'
    ORA-27037: unable to obtain file status
    Intel SVR4 UNIX Error: 2: No such file or directory
    Additional information: 3
    ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
    ORA-01194: file 1 needs more recovery to be consistent
    ORA-01110: data file 1: '/u02/oradata/RKDB/system01.dbf'
    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: '/u02/oradata/RKDB/system01.dbf'
    SQL>

  • ORA-00313: open failed for members of log group 2 of thread 1

    We have a 4 node 32bit linux RAC (Dell/EMC) system running 9.2.0.4. It is very stable but over the past couple of months we've encountered a few ORA-00313 errors, while the system is running.
    No patterns. Different loads, times of day, nodes.
    The redo can't be opened, the node crashes, we look for errors, can't find any and then restart. The file is there and the permissions are fine. No other processes are accessing the files. No other Db errors. No O/S, SAN, Fiber, errors.
    All the research I've done shows that this is an error you'd only get on startup.
    We're going to log a TAR, but I can't believe we're the only ones to ever see this occur.
    [directory and server names have been modified to protect the system. Don't get hung up on typos or possible file system config problems too much - this system has been and is running now]
    ======================================================
    Log entries:
    Mon Oct 24 22:51:58 2005
    Errors in file /u01/app/oracle/admin/sampdb/bdump/sampdb1_lgwr_2237.trc:
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/sampledb/redo0/oradata/sampdb/redo/redo102.log'
    ORA-27041: unable to open file
    Linux Error: 13: Permission denied
    Additional information: 2
    Mon Oct 24 22:51:58 2005
    Errors in file /u01/app/oracle/admin/sampdb/bdump/sampdb1_lgwr_2237.trc:
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/sampledb/redo0/oradata/sampdb/redo/redo102.log'
    ORA-27041: unable to open file
    Linux Error: 13: Permission denied
    Additional information: 2
    Mon Oct 24 22:51:58 2005
    LGWR: terminating instance due to error 313
    Below are the contents of the trace file mentioned in the above log:
    trace file /u01/app/oracle/admin/sampdb/bdump/sampdb1_lgwr_2237.trc:
    [oracle@db1 bdump]$ more /u01/app/oracle/admin/sampdb/bdump/sampdb1_lgwr_2237.trc
    /u01/app/oracle/admin/sampdb/bdump/sampdb1_lgwr_2237.trc
    Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
    With the Partitioning, Real Application Clusters, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.4.0 - Production
    ORACLE_HOME = /u01/app/oracle/product/920
    System name: Linux
    Node name: db1.sample.com
    Release: 2.4.9-e.59enterprise
    Version: #1 SMP Mon Jan 17 07:02:16 EST 2005
    Machine: i686
    Instance name: sampdb1
    Redo thread mounted by this instance: 0 <none>
    Oracle process number: 24
    Unix process pid: 2237, image: [email protected] (LGWR)
    *** SESSION ID:(25.1) 2005-10-11 22:31:02.315
    CMCLI WARNING: CMInitContext: init ctx(0xad96e80)
    *** 2005-10-24 22:51:58.192
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/sampledb/redo0/oradata/sampdb/redo/redo102.log'
    ORA-27041: unable to open file
    Linux Error: 13: Permission denied
    Additional information: 2
    error 313 detected in background process
    ORA-00313: open failed for members of log group 2 of thread 1
    ORA-00312: online log 2 thread 1: '/sampledb/redo0/oradata/sampdb/redo/redo102.log'
    ORA-27041: unable to open file
    Linux Error: 13: Permission denied
    Additional information: 2
    ksuitm: waiting for [5] seconds before killing DIAG

    The only thing I can still think of is file permissions.
    If the system has recently been restored or Redo Log recreated, check the file permissions and ensure that Oracle has Read and Write Access to the Directory and Files.
    At least the file permissions on the directory and files should look something like this example
    $ls -l /sampledb/redo0/oradata/sampdb/
    drwxr-xr-x oracle oinstall 4096 19 May 17:46 redo
    $ls -l /sampledb/redo0/oradata/sampdb/redo/
    -rw-r----- oracle oinstall 524288512 27 Oct 15:07 redo101.log
    $ls -l /sampledb2/redo0/oradata/sampdb/redo2/
    -rw-r----- oracle oinstall 524288512 27 Oct 15:21 redo102.log
    $ls -l /sampledb3/redo0/oradata/sampdb/redo3/
    -rw-r----- oracle oinstall 524288512 27 Oct 15:33 redo103.log

  • ORA-00313: open failed for members of log group 4 of thread 2

    Hi.
    i have found the below error in one of RAC instance.Could you please advise on this since i am new to RAC env
    ORA-00313: open failed for members of log group 4 of thread 2
    ORA-00312: online log 4 thread 2: '+NEWDISK_GROUP/DEMO/onlinelog/group_4.1453.1029312423'
    ORA-17503: ksfdopn:2 Failed to open file +NEWDISK_GROUP/DEMO/onlinelog/group_4.1453.1029312423
    ORA-15032: not all alterations performed
    ORA-29702: error occurred in Cluster Group Service operation
    ORA-29702: error occurred in Cluster Group Service operation
    Thanks
    Sai

    any update on this?

  • ORA-00313: open failed for members of log group

    Hi,
    on 11g R2, on standby I have this in alertlog :
    ORA-00313: open failed for members of log group 21 of thread 1
    Deleted Oracle managed file +DGRECO_FSCM/xxx/onlinelog/group_21.1721.791875667
    Tue Aug 21 14:37:34 2012
    Clearing online redo logfile 21 complete
    Errors in file /data01/oracle/diag/rdbms/xxx_mrp0_22843.trcAnd this in trace file
    *** 2012-08-21 14:35:57.192 4265 krsh.c
    *** 2012-08-21 14:37:26.406 4265 krsh.c
    Clearing online redo logfile 21 +DGRECO_FSCM/xxxx/onlinelog/group_21.1721.791875667
    DDE: Problem Key 'ORA 313' was flood controlled (0x5) (no incident)
    ORA-00313: open failed for members of log group 21 of thread 1Any explanation please ?
    Thank you.

    Refer to the below note:
         ORA-19527 reported in Standby Database when starting Managed Recovery [ID 352879.1]

  • Open failed for members of log group

    HI,
    OS : LINUX 5.1
    DB : 10.2.0.3
    i have configured physical standby and its working fine. but in alert log i m getting below error.
    i have checked the physical location of member. it is very much available.
    Mon May 24 23:54:19 2010
    Errors in file /u001/app/oracle/admin/YAHOO/bdump/yahoo_mrp0_3526.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u001/app/oracle/oradata/YAHOO/redo01.log'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Mon May 24 23:54:19 2010
    Errors in file /u001/app/oracle/admin/YAHOO/bdump/yahoo_mrp0_3526.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u001/app/oracle/oradata/YAHOO/redo01.log'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Clearing online redo logfile 1 /u001/app/oracle/oradata/YAHOO/redo01.log
    Clearing online log 1 of thread 1 sequence number 31
    Mon May 24 23:54:19 2010
    Errors in file /u001/app/oracle/admin/YAHOO/bdump/yahoo_mrp0_3526.trc:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u001/app/oracle/oradata/YAHOO/redo01.log'
    ORA-27037: unable to obtain file status
    Linux Error: 2: No such file or directory
    Additional information: 3
    Mon May 24 23:54:19 2010
    Errors in file /u001/app/oracle/admin/YAHOO/bdump/yahoo_mrp0_3526.trc:
    ORA-19527: physical standby redo log must be renamed
    ORA-00312: online log 1 thread 1: '/u001/app/oracle/oradata/YAHOO/redo01.log'
    can any one suggest?
    Regards,
    BK

    Hi,
    Below note was taken from metalink;
    Symptoms
    Following errors in alert.log of standby database during startup of the standby database:
    ORA-00313: open failed for members of log group 1 of thread 1
    ORA-00312: online log 1 thread 1: '/u03/oradata/prod/redo01b.log'
    ORA-27037: unable to obtain file status
    Cause
    Online Redo logs missing on standby database.
    Solution
    You can safely ignore these messages. Online redo logs will be created automatically when you activate the standby after switchover or failover.
    If you want to fix these messages then please use following steps:
    1. Check and set "log_file_name_convert" parameter if the location of log files are different on primary and standby.
    SQL> alter system set log_file_name_convert = "'<location on primary>','<location on standby>'" scope=spfile;
    If you are using pfile then set the parameter in init file after shutting down the database:
    *.log_file_name_convert = '<location on primary>','<location on standby>'
    For 10gR2 only : Set this parameter even if the location of the redo logs are same on both primary and standby otherwise you may get ORA-19527 and ORA-312 while or after implementing the below steps.
    This is due to internal bug in 10.2.
    2. Cancel Managed Recovery process on the standby:
    SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
    3. Execute the command to clear all log groups on standby for each log group (for each log group):
    SQL>alter database clear logfile group 1;
    4. Check the v$log view to confirm the size and status.
    5. Recreate standby redo logs on standby (only if standby Redo logs are also missing) using:
    (a) Drop the standby redo logfile group(s) (check v$standby_log)
    SQL> alter database drop standby logfile group 4;
    (b) Recreate the standby logfile group(s)
    SQL> alter database add standby logfile group 4 ('/u03/redo/stby01.log') size 50m;
    Hope it helps you.

  • Restore from cold backup (rac server)

    Hi All,
    Oracle version : 10g
    OS : SunOS dixie1 5.10 Generic_118855-36 i86pc i386 i86pc
    I am having cold backup of RAC server (2 nodes), I want to restore from cold backup.
    The problem is that : when i performed the cold backup using rman at that time Oracle was having 3 ASM diskgroups.But unforunately that disk is no more in use due to some fault.
    Now my question is how can i restore from the cold backup as when i'll restore from the cold backup this will ask for the same ASM diskgroups.Even more if i creates the same diskgroup with the same name and same configuration then my doubt is that rman will allow me to restore the same from the cold backup as ASM disk header changed now ?
    Thanks,
    Vipin

    VipinK wrote:
    Hi All,
    Oracle version : 10g
    OS : SunOS dixie1 5.10 Generic_118855-36 i86pc i386 i86pc
    I am having cold backup of RAC server (2 nodes), I want to restore from cold backup.
    The problem is that : when i performed the cold backup using rman at that time Oracle was having 3 ASM diskgroups.But unforunately that disk is no more in use due to some fault.
    Now my question is how can i restore from the cold backup as when i'll restore from the cold backup this will ask for the same ASM diskgroups.Even more if i creates the same diskgroup with the same name and same configuration then my doubt is that rman will allow me to restore the same from the cold backup as ASM disk header changed now ?
    Yes.You can do these and restore/recover your database.First you need startup your ASM instance then create your ASM disk groups and do following:
    1.Edit pfile and change controlfile location to diskgroup(Consder that +dgr1)
    2.Restore controlfile to this disk group using backup of controlfiles(you say that is cold backup)
    rman target /
    /*Instance  need starting up from pfile*/
    startup nomount ;
    /*then restore controlfile,give full path of controlfile from coldbackup*/
    restore controlfile from 'coldbackup_location\coltrolfile';
    alter database mount;
    catalog start with 'coldbackup_location';
    backup as copy database format  '+dgr1';
    switch database to copy;
    alter database open;

  • A question about restoring from cold backup(control file backup not clear)

    Hi,
    I had another question about restoring the cold backup. My database is in noarchivelog mode and after taking a consistent cold backup, all I need to do is to restore the backup right? -Why I got this question is because: when I backup my control file to trace, I see statements like this:-----
    -- Commands to re-create incarnation table
    -- Below log names MUST be changed to existing filenames on
    -- disk. Any one log file from each branch can be used to
    -- re-create incarnation records.
    -- ALTER DATABASE REGISTER LOGFILE '/uo1/app1/arch1_1_647102958.dbf';
    -- Recovery is required if any of the datafiles are restored backups,
    -- or if the last shutdown was not normal or immediate.
    RECOVER DATABASE
    -- Database can now be opened normally.
    ALTER DATABASE OPEN;
    My database is in noarchivelog mode now so don't know why these statements (of register the logfile) is there in the backup of control file? so when I restore the cold backup of this database, it will still work correct? (there is no logfile I have only CRD files in cold backup -no archive log files.)
    thanks
    Nirav

    Thanks for your inputs! It is most useful to me.
    Regards
    Nirav

  • ORA-00314 -  Restoring from Cold Backup.  ( Redologs on Raw Disk startup)

    Greetings,
    We're running Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit Production ( Solaris Sparc )
    we've recently switched to redologs on raw disks to improve DB write performance. Have taken a cold backup of db , But db denies to open normally after restoration.
    Any ideas what could be wrong? and how to fix this?
    TIA,
    SQL> startup;
    ORACLE instance started.
    Total System Global Area 1.0737E+10 bytes
    Fixed Size 1996520 bytes
    Variable Size 3640658200 bytes
    Database Buffers 7063207936 bytes
    Redo Buffers 31555584 bytes
    Database mounted.
    ORA-00314: log 1 of thread 1, expected sequence# doesn't match
    ORA-00312: online log 1 thread 1: '/dev/rdsk/c1t4d0s3'
    ORA-00312: online log 1 thread 1: '/dev/rdsk/c1t5d0s3'

    Try this ..
    First i create a backup of control file:
    SQL> alter database backup controlfile to trace;
    Database altered.
    Then i check udump directory. There are some trace files To find out which one contains control file, i simply make a text search :
    testdb oracle@aurora:/data06/app/oracle/admin/testdb/udump> grep 'CREATE CONTROLFILE REUSE DATABASE' *.*
    testdb_ora_181267.trc:CREATE CONTROLFILE REUSE DATABASE "testdb" NORESETLOGS NOARCHIVELOG
    testdb_ora_181267.trc:CREATE CONTROLFILE REUSE DATABASE "testdb" RESETLOGS NOARCHIVELOG
    I execute the commands which is included with CREATE CONTROLFILE REUSE DATABASE
    SQL> startup nomount
    ORACLE instance started.
    Total System Global Area 314572800 bytes
    Fixed Size 1302944 bytes
    Variable Size 106700384 bytes
    Database Buffers 205520896 bytes
    Redo Buffers 1048576 bytes
    SQL> CREATE CONTROLFILE REUSE DATABASE "testdb" RESETLOGS NOARCHIVELOG
    2 MAXLOGFILES 4
    3 MAXLOGMEMBERS 4
    4 MAXDATAFILES 1000
    5 MAXINSTANCES 1
    6 MAXLOGHISTORY 4544
    7 LOGFILE
    8 GROUP 1 '/data07/oradata/testdb/redo01.log' SIZE 50M,
    9 GROUP 2 '/data07/oradata/testdb/redo02.log' SIZE 50M,
    10 GROUP 3 '/data07/oradata/testdb/redo03.log' SIZE 50M
    11 DATAFILE
    12 '/data07/oradata/testdb/system01.dbf',
    13 '/data07/oradata/testdb/undo01.dbf',
    14 '/data07/oradata/testdb/sysaux01.dbf',
    15 '/data07/oradata/testdb/users01.dbf',
    16 '/data07/oradata/testdb/data01.dbf',
    17 '/data07/oradata/testdb/work01.dbf',
    18 '/data07/oradata/testdb/ascs01.dbf',
    19 '/data07/oradata/testdb/uccs_data01.dbf',
    20 '/data07/oradata/testdb/uccs_index01.dbf'
    21 CHARACTER SET WE8ISO8859P9
    22 ;
    Control file created.
    Then recover db.
    SQL> RECOVER DATABASE USING BACKUP CONTROLFILE

  • I was just wondering if there was a way for me to restore from iCloud backup without restoring the device itself again.

    I had restored my iPod touch 4th generation this morning and accidently hit set up as new device. Is there a way where I can take everything from iCloud and put it back on my device without restoring again? Thanks.

    Welcome to the Apple community.
    Back ups can only be used to restore the phone as a whole, you cannot selectively restore from a back up.

  • Database Restore from COLD Backup

    Dear all,
    I .m trying to restore a production database from a COLD backup. Before the COLD BAckup, we have take a HOT backup as usual and then shutdown the database to perform the Cold Backup.
    After restirong all the oracle files and arch redo log, i have tried to restart the datbase but it failed with the followgin error message:
    SVRMGR> connect internal
    Connected.
    SVRMGR> startup
    ORACLE instance started.
    Total System Global Area 625729520 bytes
    Fixed Size 69616 bytes
    Variable Size 133795840 bytes
    Database Buffers 491520000 bytes
    Redo Buffers 344064 bytes
    Database mounted.
    ORA-01113: file 1 needs media recovery
    ORA-01110: data file 1: '/usr/oracle/8.1.6/disk1/IF1/system01.dbf'
    SVRMGR> exit
    Server Manager complete.
    root@dbserver#su - oracle
    Sun Microsystems Inc. SunOS 5.8 Generic Patch October 2001
    Then i have recovered but it seems that the Oracle process do not started and here is what i have found in alert log file:
    Errors in file /usr/oracle/8.1.6/admin/IF1/bdump/if1_smon_609.trc:
    ORA-00600: internal error code, arguments: [4194], [52], [52], [], [], [], [], []
    Mon Mar 8 11:42:46 2004
    Recovery of Online Redo Log: Thread 1 Group 1 Seq 29954 Reading mem 0
    Mem# 0 errs 0: /usr/oracle/8.1.6/disk2/IF1/redo1a.rdo
    SMON: terminating instance due to error 600
    Instance terminated by SMON, pid = 609
    WARNING! Recovering data file 1 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    WARNING! Recovering data file 2 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    WARNING! Recovering data file 3 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    WARNING! Recovering data file 4 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    WARNING! Recovering data file 5 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    WARNING! Recovering data file 7 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    WARNING! Recovering data file 8 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    WARNING! Recovering data file 9 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    WARNING! Recovering data file 26 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    WARNING! Recovering data file 27 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    WARNING! Recovering data file 29 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    WARNING! Recovering data file 31 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    WARNING! Recovering data file 34 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    WARNING! Recovering data file 36 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    WARNING! Recovering data file 40 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    WARNING! Recovering data file 43 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    WARNING! Recovering data file 49 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    WARNING! Recovering data file 53 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    WARNING! Recovering data file 54 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    WARNING! Recovering data file 55 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    WARNING! Recovering data file 58 from a fuzzy backup. It might be an online
    backup taken without entering the begin backup command.
    Media Recovery Log
    Could someone explain to me what i did wrong?
    Thank you
    ORA-01113
    ORA-01110
    ORA-00600: internal error code, arguments: [4194], [52], [52], [], [], [], [], []

    Please do not confuse between the backup copies you have. Ensure that you have the latest copy whether cold or hot. If you have COLD copy then simply replace all the data files, redo log files, and the control files and start the database it should start. I do not understand your back up strategy because if you have a Hot backup then why do you need a cold backup. Please let me know in what mode your database is running?
    Regards,
    DJ

  • Recovery of Database -- Restore from Cold Backup

    Hi All
    I was trying to understand the possible failures so as to enhance my recovery capabilities of Oracle database 10.2.0.4.
    We take weekly hot back up of the database on every sunday including archive logs. Archive logs are also backed up when the log_archive_dest_1 disk space utilization grows beyond 80%. All the backup goes into an alterate disk made available on the host. The archive back up is triggered mostly twice a week, on one of the thursday/friday/Saturday depending on the redo generation in that week.
    Imagine we have a failure on thursday leading me to restore the complete database from backup taken on the earlier sunday. I also realise there is 1 archive log from tuesday missing and its not backed up for sure. I restore from backup and try to recover. As all the archive logs are available since Sunday till the point of failure except for that one missing file from Tuesday, I want to recover the database until the point of failure although there is one log sequence missing in archive destination. how can I do that? Is it possible? Please advice.
    I remember reading on net that recover database command can be hinted by an init parameter so as it does not check for sequece numbers and continue to apply archives (does not check sequence numbers) as they are available. But I am not able to recollect it exactly. while I was searching on net, I came to this forum hoping if some one knew it.
    Let me know if you know how to go about this. Thanks in advance.
    Sarat.

    You cannot skip an archivelog (there is no init parameter to do so).
    Think about this :
    Imagine that there is one very long transaction. A transaction that deletes or updates 1 million records. With the redo logs being, say, 100MB each, the transaction spans multiple redo logs.
    These redo logs are archived as, say, sequence #121 to 128.
    Supposing that sequnece #123 is deleted by mistake.
    Can you recover the database with sequence# 121, 122, 124-128 ? Can that transaction be consistent ?
    OR think about this :
    A redo log file is 99% full. A transaction for 1000 rows begins. All the redo entries for that transaction do not fit into that last 1%. The transaction spans into the next redo log file.
    Can recovery be done with either of these missing ?
    If you think through these scenarios, you will see that there will almost always be transactions spanning redo logs. That means, that you cannot skip redo logs during recovery.
    Hemant K Chitale
    http://hemantoracledba.blogspot.com

  • Partial restore from Cold backup

    Hi,
    I want to create a copy of our dev database to another server.
    We have Oracle 10.2.0.4 server running on Solaris 10 OS.
    This database is @ 120GB in size and has got lots of application data.
    Now I want to create a copy of this DB without having the application data.
    Can I do the following?
    1. Take cold backup of this database.
    2. copy the oracle binaries, controlfile, logfile to target server.
    3. copy the datafiles only for SYSTEM, UNDO, TEMP and SYSAUX tablespace to target.
    4. restore / create the new database? - will you pls provide me the steps for this?
    Thanks,
    DR

    Hi,
    In order to create a clone of your dev database trough the copy procedure you have to follow these steps:
    1. Take a cold backup of your database files (and i mean ALL the files: controlfile, data files, etc)
    2. Take a "cold" backup of oracle binaries (with your instance down, copy $ORACLE_HOME dir)
    3 You have to ensure you have the directory structure in the new server.
    4. The new server must accomplish with all the libraries requiered for clean installation (that's because you have to relink oracle binaries)
    5. Once the oracle binaries are in $ORACLE_HOME, run "relink all". If everything is fine, you don't have to see any errors; if not, check the log.
    6. After a succesful relink, you have to copy the database files on their corresponding directories.
    7. Start the instance.
    I know, it's not a friendly process, but it works.
    I offer you another way.
    1. Install another engine (same as your dev server).
    2. Clone your dev database with one of the following procedures:
    2.a. RMAN Clone
    2.b. Directly import with oracle data pump.
    regards

  • RMAN Restore from cold backup ?

    Hi ,
    I am trying to restore the database from production db using the RMAN cold Backup. Both the prod and test(Restore database) are on the same machine. And also I wanted to have the restore db name should be different.
    And the restore db name should be different. What are the options I have ?

    refer the thread:-
    RMAN Restore using RMAN COLD Backup!!
    RMAN Restore using RMAN COLD Backup!!

Maybe you are looking for