Cold backup Restoration

Hi,
OS: IBM AIX
Oracle 10g.
My database is running in Archivelog mode.
I have to take coldbakup and restore in the new location.
I will use the following steps.
1. Shutdown immediate
2. tar (.dbf, ctr, redolog and archivelog)
Here I have doubt while restoring the database.
Is that necessary to apply archivelog while restoring the backup ( I hope it is not required)
Please suggest me.
Please provide me steps for backup and restore and recovery using coldbackup.
Thanks in advance
KSG

Hi, it is not necessary to restore archived redo logs if you only want to restore to the point of backup, otherwise it is necessary. Why are you using this method anyway and not using RMAN which would be far simpler ?
regards,
graham

Similar Messages

  • Cold backup restore to a different bit level

    Hi all. I am planning for a coldback restore between two databases. The source db is 10.2.0.3 on 32-bit server Windows 2003 and the destination db is 10.2.0.4 on windows 64-bit. Is it possible to perform this restore? Also is RMAN restore possible? Thanks for any responses.

    Hi, I performed a restore of cold backup from 10.2.0.3 database to 10.2.0.4 database on another server. I am receiving this error:
    ORA-01503: CREATE CONTROLFILE failed
    ORA-01159: file is not from same database as previous files - wrong database id
    I am restoring only the schema specific datafiles from the old database and not system, sysaux files .. I understand that there is a mismatch here because the source datafiles are not compatible with the new system files. Any idea what can be done here to get around this error? I am trying to perform a clone of the database into another server. The database name is same.

  • Cold backup restore on fail safe environment.

    Hi,
    The setup:
    Windows 2008 with 2 node MSCS cluster in active/passive configuration.
    Oracle Database 11.1.0.6 .
    Oracle Failsafe 3.4.2
    Database :test database; 2 in no. ,both Single instance. Both database are created with cold backup from production.
    The Requirement:
    To refresh both the test database with cold backup from the same production database as before. And then with the same cold backup create a physical standby database of the newly recreated testing database.
    The Plan:
    1.take all dbfile,controlfile,redologfiles,standbyredologfiles,tempfiles backup from production.
    2.after taking the testing database offline from failsafe and normaly starting on node1; restore dbfile,controlfiles,redologs,srl,tempfiles to testing server. spfile should be properly pointing the new controlfile.
    3.startup mount.
    4.directory structure for control,redo,srl,dbfiles,tempfiles are diffrent.so,rename file for all dbfiles,redologs,srl,tempfiles.
    5.creating a standby controlfile for creating physical standby db of this testing database.
    6.open the database.
    7.shutdown immediate.
    8.start with failsafe.
    The doubt:
    1. is this plan ok for refresh of the test databases?
    2. with the backup taken at step1 and standby ctl file created at step 5 can i create a physical standby database of the testing db?
    Please note, the production database is only in picture while taking backup.
    Please guys help me for clearing the said doubts.
    regards.
    g

    The doubt:
    1. is this plan ok for refresh of the test databases?
    2. with the backup taken at step1 and standby ctl file created at step 5 can i create a physical standby database of the testing db?
    Please note, the production database is only in picture while taking backup. You are taking cold backup, So the mentioned procedure you can follow. But ensure all the services/background processes related to database are not running.
    Once you prepare Primary database, even from that database you can create standby control file, so that it will be used for standby database.
    But i'm not aware of how fail safe it works, As per the core database part whatever the steps you mentioned, it looks fine.
    Thank You.

  • Cold backup restore error

    Hi,
    i tried to restore coldbackup on solaris.while starting instance i got this error.
    LRM-00109: could not open parameter file '/oracle/app/oracle/product/9.2.0.8/dbs/initcdmsd1.ora'
    ORA-01078: failure in processing system parameters
    now in this path init file is there.
    $ cd /oracle/app/oracle/product/9.2.0.8/dbs
    $ ls
    c-2448946487-20090420-00 init.ora initcdmsv1.ora lkCDMSP1 snapcf_cdmsp1.f spfilecdmsv1.ora
    c-2448946487-20090421-00 initcdmsp1.ora initcdmsv1_bkup.ora lkCDMSV1 snapcf_cdmsv1.f
    c-2448946487-20090422-00 initcdmsp1_bkup.ora initdw.ora orapwcdmsv1 spfilecdmsp1.ora
    $
    even tried with giving init path
    SQL> startup pfile='/oracle/app/oracle/product/9.2.0.8/dbs/initcdmsd1.ora';
    LRM-00109: could not open parameter file '/oracle/app/oracle/product/9.2.0.8/dbs/initcdmsd1.ora'
    ORA-01078: failure in processing system parameters
    SQL> exit
    but error is still there.on this server one db is there.for which it giving same error.
    pls help me early as possible
    Nareshs

    s they are there
    root@CDM-PRDR-OCLD-1 # cd cdmsp1
    root@CDM-PRDR-OCLD-1 # ls
    arch dcm.dbf ocl_dcmq.dbf ocl_li.dbf portal.dbf tms_clob1.dbf
    attrs1_oid.dbf discopltc1.dbf ocl_dcmq_idx.dbf ocl_li_idx.dbf ptldoc.dbf tms_data1.dbf
    b2b_dt.dbf discopltm1.dbf ocl_def.dbf ocl_lr.dbf ptlidx.dbf tms_idx1.dbf
    b2b_idx.dbf drsys01.dbf ocl_def_idx.dbf ocl_lr_idx.dbf ptllog.dbf tools01.dbf
    b2b_lob.dbf gcats1_oid.dbf ocl_des.dbf ocl_resp.dbf redo01_a.log uddisys01.dbf
    b2b_rt.dbf gdefault1_oid.dbf ocl_des_idx.dbf ocl_resp_idx.dbf redo01_b.log undotbs01.dbf
    bam.dbf ias_meta01.dbf ocl_disc.dbf ocl_temp1.dbf redo02_a.log users01.dbf
    battrs1_oid.dbf indx01.dbf ocl_disc_idx.dbf ocl_test_data.dbf redo02_b.log wcrsys01.dbf
    bc4j_internal_data.dbf oca.dbf ocl_disc_rep_data.dbf ocl_test_index.dbf redo03_a.log xdb01.dbf
    control01.ctl ocl_app.dbf ocl_dx_index_data.dbf ocl_vrv.dbf redo03_b.log xdb02.dbf
    control02.ctl ocl_app_idx.dbf ocl_dx_table_data.dbf ocl_vrv_idx.dbf svrmg1_oid.dbf
    control03.ctl ocl_dcd.dbf ocl_glib.dbf orabpel.dbf system01.dbf
    cwmlite01.dbf ocl_dcd_idx.dbf ocl_glib_idx.dbf oss_sys01.dbf temp01.dbf

  • COLD BACKUP을 받은 후 ARCHIVE LOG로 변환하여 사용한 경우 INCOMPLETE RECOVERY.

    제품 : ORACLE SERVER
    작성날짜 : 2002-04-09
    COLD BACKUP을 받은 후 ARCHIVE LOG로 변환하여 사용한 경우 INCOMPLETE RECOVERY.
    ======================================================================
    PURPOSE
    COLD BACKUP을 받은 후 ARCHIVE LOG MODE로 변환하여 사용한 경우의 RECOVERY
    과정을 TEST로 확인하여 본다.
    Examples
    No Archive log mode.
    SQL> select * from tab ;
    TNAME TABTYPE CLUSTERID
    EMP TABLE
    EMP1 TABLE
    EMP2 TABLE
    EMP3 TABLE
    EMP4 TABLE
    10 rows selected.
    SQL> select count(*) from emp3 ;
    COUNT(*)
    0
    SQL> select count(*) from emp4 ;
    COUNT(*)
    0
    Cold backup을 받은후 Archive log mode 변경한 경우
    SVRMGR> startup mount
    SVRMGR> archive log list
    Database log mode No Archive Mode
    Automatic archival Enabled
    Archive destination D:\Oracle\oradata\SNAP\archive
    Oldest online log sequence 26
    Current log sequence 28
    SVRMGR> alter database archivelog ;
    SVRMGR> alter database open ; => archive log mode 변경.
    SQL> select * from tab ;
    TNAME TABTYPE CLUSTERID
    EMP TABLE
    EMP1 TABLE
    EMP2 TABLE
    EMP3 TABLE
    EMP4 TABLE
    10 rows selected.
    SQL> insert into emp3 select * from emp ;
    14 rows created.
    SQL> commit ;
    Commit complete.
    SQL> insert into emp4 select * from emp1 ;
    71680 rows created.
    SQL> commit ;
    Commit complete.
    SQL> select count(*) from emp3 ;
    COUNT(*)
    14
    SQL> select count(*) from emp4 ;
    COUNT(*)
    71680
    ## log switch 발생.
    SVRMGR> alter system switch logfile ;
    SQL> insert into emp3 select * from emp ; -- current log에 반영.
    14 rows created.
    SQL> commit ;
    SQL> select count(*) from emp3 ;
    COUNT(*)
    28
    SQL> select count(*) from emp4 ;
    COUNT(*)
    71680
    # ALL DATABASE CRASH #
    # recover 과정... #
    1. Restore Cold-backup
    2. modify initSID.ora
    log_archive_start = true
    log_archive_dest_1 = "location=D:\Oracle\oradata\SNAP\archive"
    log_archive_format = %%ORACLE_SID%%T%TS%S.ARC
    3. svrmgrl
    Statement processed.
    SVRMGR> startup mount
    ORACLE instance started.
    Total System Global Area 40703244 bytes
    Fixed Size 70924 bytes
    Variable Size 23777280 bytes
    Database Buffers 16777216 bytes
    Redo Buffers 77824 bytes
    Database mounted.
    SVRMGR> archive log list
    Database log mode No Archive Mode
    Automatic archival Enabled
    Archive destination D:\Oracle\oradata\SNAP\archive
    Oldest online log sequence 26
    Current log sequence 28
    SVRMGR> alter database archivelog ;
    Statement processed.
    SVRMGR> recover database using backup controlfile until cancel ;
    ORA-00279: change 340421 generated at 04/29/2001 23:42:20 needed for thread 1
    ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00028.ARC
    ORA-00280: change 340421 for thread 1 is in sequence #28
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    Log applied.
    ORA-00279: change 340561 generated at 04/29/2001 23:47:29 needed for thread 1
    ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00029.ARC
    ORA-00280: change 340561 for thread 1 is in sequence #29
    ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00028.ARC' no longe
    r needed for this recovery
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    Log applied.
    ORA-00279: change 340642 generated at 04/29/2001 23:47:35 needed for thread 1
    ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00030.ARC
    ORA-00280: change 340642 for thread 1 is in sequence #30
    ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00029.ARC' no longe
    r needed for this recovery
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    Log applied.
    ORA-00279: change 340723 generated at 04/29/2001 23:47:40 needed for thread 1
    ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00031.ARC
    ORA-00280: change 340723 for thread 1 is in sequence #31
    ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00030.ARC' no longe
    r needed for this recovery
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    Log applied.
    ORA-00279: change 340797 generated at 04/29/2001 23:48:01 needed for thread 1
    ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00032.ARC
    ORA-00280: change 340797 for thread 1 is in sequence #32
    ORA-00278: log file 'D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00031.ARC' no longe
    r needed for this recovery
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    cancel
    Media recovery cancelled.
    SVRMGR> alter database open resetlogs ;
    Statement processed.
    SVRMGR>
    SQL> connect scott/tiger
    SQL> select count(*) from emp3 ;
    COUNT(*)
    14
    SQL> select count(*) from emp4 ;
    COUNT(*)
    71680
    # 결론...... #
    따라서 current log file에 기록된 14 row에 대한 부분은 recover가 될수
    없지만 archive log file에 적용된 log에 대한 data는 정상적으로 복구가
    가능하다.
    # 주의 사항 #
    cold backup을 restore한 후 database open후 shutdown 한 다음 archive
    log mode로 변경하여 recover를 진행하는 경우 SCN number가 변경되기
    때문에 ora-600 error가 발생하며 media recovery를 필요로 하기 때문에
    주의하여야 한다.
    SVRMGR> startup
    ORACLE instance started.
    Total System Global Area 40703244 bytes
    Fixed Size 70924 bytes
    Variable Size 23777280 bytes
    Database Buffers 16777216 bytes
    Redo Buffers 77824 bytes
    Database mounted.
    Database opened.
    SVRMGR> shutdown
    Database closed.
    Database dismounted.
    ORACLE instance shut down.
    SVRMGR> startup mount
    ORACLE instance started.
    Total System Global Area 40703244 bytes
    Fixed Size 70924 bytes
    Variable Size 23777280 bytes
    Database Buffers 16777216 bytes
    Redo Buffers 77824 bytes
    Database mounted.
    SVRMGR> alter database archivelog ;
    Statement processed.
    SVRMGR> recover database using backup controlfile until cancel ;
    ORA-00279: change 339542 generated at 04/29/2001 23:30:57 needed for thread 1
    ORA-00289: suggestion : D:\ORACLE\ORADATA\SNAP\ARCHIVE\SNAPT001S00003.ARC
    ORA-00280: change 339542 for thread 1 is in sequence #3
    Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
    ORA-00283: recovery session canceled due to errors
    ORA-00600: internal error code, arguments: [3020], [8390146], [1], [3], [143], [
    240], [], []
    SVRMGR> exit
    Server Manager complete.
    Rederence Documents
    ---------------------

  • How to restore cold backup + archived log files

    Hi,
    Suppose I take a cold backup on 18th. After that I have four days of archived log files. if the database crashes on 5th day, I have to restore the 18th cold back + 4 days of archived log files. How do I restore since it is a cold backup and I cant do incomplete recovery.
    can I use
    Recover database ( with 18th cold backup) in mount state and apply archived logs.
    Prabhath

    The details of how you perform forward recovery using a cold backup depends on
    1- rman or manual backup
    2- using current or backup control file
    3- if rman, recovery catalog or no recovery catalog
    4- if full database recovered or only a few files
    Each of these conditions will affect what is known to Oracle and what needs to be done. For example if you restored the entire cold backup including the control file then Oracle would see a consistent database and not need to perform recovery so you would need to startup mount and tell the database to perform recovery using a backup control file. If using rman and no recovery catalog you might need to catalog some of the archived redo logs, etc....
    It is advisable to consult the Backup and Recovery manuals before attempting recovery for any new scenario.
    HTH -- Mark D Powell --

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

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

  • Problem with restoring a database from cold backup

    All,
    I've got a 10.2.0.4 database that we perform a cold backup on every night with RMAN. On Sunday 2/21, we have level 0 backup. On Monday-Wednesday nights, we take a cold level 1. We also perform a controlfile auto backup each night.
    On a second server where I want to restore the database (same version of Oracle 10.2.0.4), I've copied the control file auto backups, the level 0 and the most recent level 1. I now want to restore. I use an RMAN script similar to the following to restore the control files:
    connect target /;
    set dbid 1973354860;
    # Restore the controlfile from the tag that auto backed up the controlfile at the end of the level 0
    run
    startup nomount;
    allocate channel c1 type disk;
    restore controlfile to '/u01/app/oracle/oradata/ORADB1/control01.ctl' from AUTOBACKUP;
    restore controlfile to '/u02/app/oracle/oradata/ORADB1/control02.ctl' from AUTOBACKUP;
    restore controlfile to '/u03/app/oracle/oradata/ORADB1/control03.ctl' from AUTOBACKUP;
    release channel c1;
    shutdown immediate;
    After the control files restore successfully, I perform some RMAN checks to ensure that all of the files I need for a recovery are there. The RMAN> list backup of database; command shows all of my backup savesets as AVAILABLE for the level0 and level1 backups.
    I then try a restore database command; and get the following errors:
    RMAN> run
    2> {
    3> allocate channel c1 type disk;
    4> allocate channel c2 type disk;
    5> allocate channel c3 type disk;
    6> allocate channel c4 type disk;
    7> restore database from tag='TAG20100221T200045';
    8> }
    using target database control file instead of recovery catalog
    allocated channel: c1
    channel c1: sid=74 devtype=DISK
    allocated channel: c2
    channel c2: sid=70 devtype=DISK
    allocated channel: c3
    channel c3: sid=166 devtype=DISK
    allocated channel: c4
    channel c4: sid=168 devtype=DISK
    Starting restore at 25-FEB-10
    released channel: c1
    released channel: c2
    released channel: c3
    released channel: c4
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 02/25/2010 13:33:19
    RMAN-06026: some targets not found - aborting restore
    RMAN-06023: no backup or copy of datafile 44 found to restore
    RMAN-06023: no backup or copy of datafile 43 found to restore
    RMAN-06023: no backup or copy of datafile 42 found to restore
    RMAN-06023: no backup or copy of datafile 40 found to restore
    RMAN-06023: no backup or copy of datafile 39 found to restore
    RMAN-06023: no backup or copy of datafile 38 found to restore
    RMAN-06023: no backup or copy of datafile 37 found to restore
    RMAN-06023: no backup or copy of datafile 36 found to restore
    RMAN-06023: no backup or copy of datafile 35 found to restore
    RMAN-06023: no backup or copy of datafile 34 found to restore
    RMAN-06023: no backup or copy of datafile 33 found to restore
    RMAN-06023: no backup or copy of datafile 32 found to restore
    RMAN-06023: no backup or copy of datafile 31 found to restore
    RMAN-06023: no backup or copy of datafile 30 found to restore
    RMAN-06023: no backup or copy of datafile 29 found to restore
    RMAN-06023: no backup or copy of datafile 28 found to restore
    RMAN-06023: no backup or copy of datafile 27 found to restore
    RMAN-06023: no backup or copy of datafile 26 found to restore
    RMAN-06023: no backup or copy of datafile 25 found to restore
    RMAN-06023: no backup or copy of datafile 24 found to restore
    RMAN-06023: no backup or copy of datafile 23 found to restore
    RMAN-06023: no backup or copy of datafile 22 found to restore
    RMAN-06023: no backup or copy of datafile 21 found to restore
    RMAN-06023: no backup or copy of datafile 20 found to restore
    RMAN-06023: no backup or copy of datafile 19 found to restore
    RMAN-06023: no backup or copy of datafile 18 found to restore
    RMAN-06023: no backup or copy of datafile 17 found to restore
    RMAN-06023: no backup or copy of datafile 16 found to restore
    RMAN-06023: no backup or copy of datafile 15 found to restore
    RMAN-06023: no backup or copy of datafile 14 found to restore
    RMAN-06023: no backup or copy of datafile 13 found to restore
    RMAN-06023: no backup or copy of datafile 12 found to restore
    RMAN-06023: no backup or copy of datafile 11 found to restore
    RMAN-06023: no backup or copy of datafile 10 found to restore
    RMAN-06023: no backup or copy of datafile 9 found to restore
    RMAN-06023: no backup or copy of datafile 8 found to restore
    RMAN-06023: no backup or copy of datafile 7 found to restore
    RMAN-06023: no backup or copy of datafile 6 found to restore
    RMAN-06023: no backup or copy of datafile 5 found to restore
    RMAN-06023: no backup or copy of datafile 4 found to restore
    RMAN-06023: no backup or copy of datafile 3 found to restore
    RMAN-06023: no backup or copy of datafile 2 found to restore
    RMAN-06023: no backup or copy of datafile 1 found to restore
    RMAN>
    But I know from the RMAN crosscheck and list backup commands that the savesets are available on disk. For example:
    RMAN> list backup of datafile 1;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    4875 Incr 0 4.37G DISK 00:22:53 21-FEB-10
    BP Key: 4875 Status: AVAILABLE Compressed: YES Tag: TAG20100221T200045
    Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4929_piece_1_date_20100221_711578185
    List of Datafiles in backup set 4875
    File LV Type Ckp SCN Ckp Time Name
    1 0 Incr 5086110241948 21-FEB-10 /u01/app/oracle/oradata/ORADB1/system01.dbf
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    4894 Incr 1 1.92G DISK 00:13:46 24-FEB-10
    BP Key: 4894 Status: AVAILABLE Compressed: YES Tag: TAG20100224T200037
    Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4949_piece_1_date_20100224_711836434
    List of Datafiles in backup set 4894
    File LV Type Ckp SCN Ckp Time Name
    1 1 Incr 5086113791743 24-FEB-10 /u01/app/oracle/oradata/ORADB1/system01.dbf
    RMAN> list backup of datafile 44; (the first one in the list above)
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    4872 Incr 0 7.15G DISK 00:35:17 21-FEB-10
    BP Key: 4872 Status: AVAILABLE Compressed: YES Tag: TAG20100221T200045
    Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4927_piece_1_date_20100221_711576046
    List of Datafiles in backup set 4872
    File LV Type Ckp SCN Ckp Time Name
    44 0 Incr 5086110241948 21-FEB-10 /u04/app/oracle/oradata/ORADB1/NETINSIGHT_INDEXES_03.dbf
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    4893 Incr 1 4.06G DISK 00:26:52 24-FEB-10
    BP Key: 4893 Status: AVAILABLE Compressed: YES Tag: TAG20100224T200037
    Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4947_piece_1_date_20100224_711835238
    List of Datafiles in backup set 4893
    File LV Type Ckp SCN Ckp Time Name
    44 1 Incr 5086113791743 24-FEB-10 /u04/app/oracle/oradata/ORADB1/NETINSIGHT_INDEXES_03.dbf
    As you can see, the level 0 and level 1 backups are showing as available. To double check, I perform a crosscheck backup of database;
    RMAN> crosscheck backup of database;
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: sid=74 devtype=DISK
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4927_piece_1_date_20100221_711576046 recid=4872 stamp=711576046
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4928_piece_1_date_20100221_711576046 recid=4873 stamp=711576046
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4930_piece_1_date_20100221_711578189 recid=4874 stamp=711578189
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4929_piece_1_date_20100221_711578185 recid=4875 stamp=711578186
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4932_piece_1_date_20100221_711579570 recid=4876 stamp=711579570
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4931_piece_1_date_20100221_711579392 recid=4877 stamp=711579393
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4934_piece_1_date_20100221_711580369 recid=4878 stamp=711580370
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4935_piece_1_date_20100221_711580535 recid=4879 stamp=711580535
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4933_piece_1_date_20100221_711580122 recid=4880 stamp=711580123
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4948_piece_1_date_20100224_711835237 recid=4892 stamp=711835238
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4947_piece_1_date_20100224_711835238 recid=4893 stamp=711835238
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4949_piece_1_date_20100224_711836434 recid=4894 stamp=711836436
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4950_piece_1_date_20100224_711836866 recid=4895 stamp=711836866
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4951_piece_1_date_20100224_711837267 recid=4896 stamp=711837268
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4952_piece_1_date_20100224_711837971 recid=4897 stamp=711837972
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4953_piece_1_date_20100224_711837989 recid=4898 stamp=711837989
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4955_piece_1_date_20100224_711838522 recid=4899 stamp=711838522
    crosschecked backup piece: found to be 'AVAILABLE'
    backup piece handle=/u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4954_piece_1_date_20100224_711838520 recid=4900 stamp=711838521
    Crosschecked 18 objects
    RMAN>
    So I'm unclear as to why RMAN believes the backups of these files don't exist when I attempt to restore the database. Anyone have a clue?
    NOTE: I've also tried to restore spcifically with the tag= clause but I get the same results:
    RMAN> restore database from tag='TAG20100221T200045';
    Starting restore at 25-FEB-10
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 02/25/2010 13:41:04
    RMAN-06026: some targets not found - aborting restore
    RMAN-06023: no backup or copy of datafile 44 found to restore
    RMAN-06023: no backup or copy of datafile 43 found to restore
    RMAN-06023: no backup or copy of datafile 42 found to restore
    RMAN-06023: no backup or copy of datafile 40 found to restore
    RMAN-06023: no backup or copy of datafile 39 found to restore
    RMAN-06023: no backup or copy of datafile 38 found to restore
    RMAN-06023: no backup or copy of datafile 37 found to restore
    RMAN-06023: no backup or copy of datafile 36 found to restore
    RMAN-06023: no backup or copy of datafile 35 found to restore
    RMAN-06023: no backup or copy of datafile 34 found to restore
    RMAN-06023: no backup or copy of datafile 33 found to restore
    RMAN-06023: no backup or copy of datafile 32 found to restore
    RMAN-06023: no backup or copy of datafile 31 found to restore
    RMAN-06023: no backup or copy of datafile 30 found to restore
    RMAN-06023: no backup or copy of datafile 29 found to restore
    RMAN-06023: no backup or copy of datafile 28 found to restore
    RMAN-06023: no backup or copy of datafile 27 found to restore
    RMAN-06023: no backup or copy of datafile 26 found to restore
    RMAN-06023: no backup or copy of datafile 25 found to restore
    RMAN-06023: no backup or copy of datafile 24 found to restore
    RMAN-06023: no backup or copy of datafile 23 found to restore
    RMAN-06023: no backup or copy of datafile 22 found to restore
    RMAN-06023: no backup or copy of datafile 21 found to restore
    RMAN-06023: no backup or copy of datafile 20 found to restore
    RMAN-06023: no backup or copy of datafile 19 found to restore
    RMAN-06023: no backup or copy of datafile 18 found to restore
    RMAN-06023: no backup or copy of datafile 17 found to restore
    RMAN-06023: no backup or copy of datafile 16 found to restore
    RMAN-06023: no backup or copy of datafile 15 found to restore
    RMAN-06023: no backup or copy of datafile 14 found to restore
    RMAN-06023: no backup or copy of datafile 13 found to restore
    RMAN-06023: no backup or copy of datafile 12 found to restore
    RMAN-06023: no backup or copy of datafile 11 found to restore
    RMAN-06023: no backup or copy of datafile 10 found to restore
    RMAN-06023: no backup or copy of datafile 9 found to restore
    RMAN-06023: no backup or copy of datafile 8 found to restore
    RMAN-06023: no backup or copy of datafile 7 found to restore
    RMAN-06023: no backup or copy of datafile 6 found to restore
    RMAN-06023: no backup or copy of datafile 5 found to restore
    RMAN-06023: no backup or copy of datafile 4 found to restore
    RMAN-06023: no backup or copy of datafile 3 found to restore
    RMAN-06023: no backup or copy of datafile 2 found to restore
    RMAN-06023: no backup or copy of datafile 1 found to restore

    Just as a follow on to my last post, after the RMAN-06023 messages, I list backups of the three datafiles and as you can see RMAN thinks that they are available. If I exit RMAN and list them at the OS level, they are where RMAN things they should be:
    RMAN> restore database;
    Starting restore at 25-FEB-10
    using channel ORA_DISK_1
    RMAN-00571: ===========================================================
    RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
    RMAN-00571: ===========================================================
    RMAN-03002: failure of restore command at 02/25/2010 16:17:39
    RMAN-06026: some targets not found - aborting restore
    RMAN-06023: no backup or copy of datafile 4 found to restore
    RMAN-06023: no backup or copy of datafile 3 found to restore
    RMAN-06023: no backup or copy of datafile 1 found to restore
    RMAN> list backup of datafile 4;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    4880 Incr 0 1.36G DISK 00:08:57 21-FEB-10
    BP Key: 4880 Status: AVAILABLE Compressed: YES Tag: TAG20100221T200045
    Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4933_piece_1_date_20100221_711580122
    List of Datafiles in backup set 4880
    File LV Type Ckp SCN Ckp Time Name
    4 0 Incr 5086110241948 21-FEB-10 /u02/app/oracle/oradata/ORADB1/users01.dbf
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    4890 Incr 1 934.82M DISK 00:09:42 22-FEB-10
    BP Key: 4890 Status: AVAILABLE Compressed: YES Tag: TAG20100222T200047
    Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4943_piece_1_date_20100222_711664989
    List of Datafiles in backup set 4890
    File LV Type Ckp SCN Ckp Time Name
    4 1 Incr 5086111401249 22-FEB-10 /u02/app/oracle/oradata/ORADB1/users01.dbf
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    4898 Incr 1 947.57M DISK 00:08:49 24-FEB-10
    BP Key: 4898 Status: AVAILABLE Compressed: YES Tag: TAG20100224T200037
    Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4953_piece_1_date_20100224_711837989
    List of Datafiles in backup set 4898
    File LV Type Ckp SCN Ckp Time Name
    4 1 Incr 5086113791743 24-FEB-10 /u02/app/oracle/oradata/ORADB1/users01.dbf
    RMAN>
    RMAN> list backup of datafile 3;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    4874 Incr 0 2.65G DISK 00:19:50 21-FEB-10
    BP Key: 4874 Status: AVAILABLE Compressed: YES Tag: TAG20100221T200045
    Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4930_piece_1_date_20100221_711578189
    List of Datafiles in backup set 4874
    File LV Type Ckp SCN Ckp Time Name
    3 0 Incr 5086110241948 21-FEB-10 /u02/app/oracle/oradata/ORADB1/sysaux01.dbf
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    4885 Incr 1 1.95G DISK 00:15:54 22-FEB-10
    BP Key: 4885 Status: AVAILABLE Compressed: YES Tag: TAG20100222T200047
    Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4940_piece_1_date_20100222_711663910
    List of Datafiles in backup set 4885
    File LV Type Ckp SCN Ckp Time Name
    3 1 Incr 5086111401249 22-FEB-10 /u02/app/oracle/oradata/ORADB1/sysaux01.dbf
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    4895 Incr 1 1.97G DISK 00:18:13 24-FEB-10
    BP Key: 4895 Status: AVAILABLE Compressed: YES Tag: TAG20100224T200037
    Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4950_piece_1_date_20100224_711836866
    List of Datafiles in backup set 4895
    File LV Type Ckp SCN Ckp Time Name
    3 1 Incr 5086113791743 24-FEB-10 /u02/app/oracle/oradata/ORADB1/sysaux01.dbf
    RMAN>
    RMAN>
    RMAN> list backup of datafile 1;
    List of Backup Sets
    ===================
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    4875 Incr 0 4.37G DISK 00:22:53 21-FEB-10
    BP Key: 4875 Status: AVAILABLE Compressed: YES Tag: TAG20100221T200045
    Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level0_set_4929_piece_1_date_20100221_711578185
    List of Datafiles in backup set 4875
    File LV Type Ckp SCN Ckp Time Name
    1 0 Incr 5086110241948 21-FEB-10 /u01/app/oracle/oradata/ORADB1/system01.dbf
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    4884 Incr 1 1.93G DISK 00:12:34 22-FEB-10
    BP Key: 4884 Status: AVAILABLE Compressed: YES Tag: TAG20100222T200047
    Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4939_piece_1_date_20100222_711663601
    List of Datafiles in backup set 4884
    File LV Type Ckp SCN Ckp Time Name
    1 1 Incr 5086111401249 22-FEB-10 /u01/app/oracle/oradata/ORADB1/system01.dbf
    BS Key Type LV Size Device Type Elapsed Time Completion Time
    4894 Incr 1 1.92G DISK 00:13:46 24-FEB-10
    BP Key: 4894 Status: AVAILABLE Compressed: YES Tag: TAG20100224T200037
    Piece Name: /u03/oracle_backups/ORADB1/offline/ORADB1_level1_set_4949_piece_1_date_20100224_711836434
    List of Datafiles in backup set 4894
    File LV Type Ckp SCN Ckp Time Name
    1 1 Incr 5086113791743 24-FEB-10 /u01/app/oracle/oradata/ORADB1/system01.dbf
    RMAN> exit
    $ ls -ltr /u03/oracle_backups/ORADB1/offline
    total 59743688
    -rwx------ 1 oracle oinstall 7677960192 2010-02-25 11:13 ORADB1_level0_set_4927_piece_1_date_20100221_711576046
    -rwx------ 1 oracle oinstall 7980834816 2010-02-25 11:24 ORADB1_level0_set_4928_piece_1_date_20100221_711576046
    -rwx------ 1 oracle oinstall 4691853312 2010-02-25 11:29 ORADB1_level0_set_4929_piece_1_date_20100221_711578185
    -rwx------ 1 oracle oinstall 2847391744 2010-02-25 11:34 ORADB1_level0_set_4930_piece_1_date_20100221_711578189
    -rwx------ 1 oracle oinstall 3530924032 2010-02-25 11:39 ORADB1_level0_set_4931_piece_1_date_20100221_711579392
    -rwx------ 1 oracle oinstall 1566449664 2010-02-25 11:41 ORADB1_level0_set_4932_piece_1_date_20100221_711579570
    -rwx------ 1 oracle oinstall 1459781632 2010-02-25 11:43 ORADB1_level0_set_4933_piece_1_date_20100221_711580122
    -rwx------ 1 oracle oinstall 561774592 2010-02-25 11:44 ORADB1_level0_set_4934_piece_1_date_20100221_711580369
    -rwx------ 1 oracle oinstall 58753024 2010-02-25 11:44 ORADB1_level0_set_4935_piece_1_date_20100221_711580535
    -rwx------ 1 oracle oinstall 4364124160 2010-02-25 11:56 ORADB1_level1_set_4947_piece_1_date_20100224_711835238
    -rwx------ 1 oracle oinstall 2971877376 2010-02-25 12:01 ORADB1_level1_set_4948_piece_1_date_20100224_711835237
    -rwx------ 1 oracle oinstall 2066546688 2010-02-25 12:03 ORADB1_level1_set_4949_piece_1_date_20100224_711836434
    -rwx------ 1 oracle oinstall 2119360512 2010-02-25 12:06 ORADB1_level1_set_4950_piece_1_date_20100224_711836866
    -rwx------ 1 oracle oinstall 1003356160 2010-02-25 12:06 ORADB1_level1_set_4951_piece_1_date_20100224_711837267
    -rwx------ 1 oracle oinstall 1637105664 2010-02-25 12:08 ORADB1_level1_set_4952_piece_1_date_20100224_711837971
    -rwx------ 1 oracle oinstall 993607680 2010-02-25 12:08 ORADB1_level1_set_4953_piece_1_date_20100224_711837989
    -rwx------ 1 oracle oinstall 1130496 2010-02-25 12:09 ORADB1_level1_set_4955_piece_1_date_20100224_711838522
    -rwx------ 1 oracle oinstall 283344896 2010-02-25 12:09 ORADB1_level1_set_4954_piece_1_date_20100224_711838520
    -rwx------ 1 oracle oinstall 4344365056 2010-02-25 16:01 ORADB1_level1_set_4937_piece_1_date_20100222_711662448
    -rwx------ 1 oracle oinstall 2959015936 2010-02-25 16:05 ORADB1_level1_set_4938_piece_1_date_20100222_711662448
    -rwx------ 1 oracle oinstall 2067202048 2010-02-25 16:07 ORADB1_level1_set_4939_piece_1_date_20100222_711663601
    -rwx------ 1 oracle oinstall 2089304064 2010-02-25 16:08 ORADB1_level1_set_4940_piece_1_date_20100222_711663910
    -rwx------ 1 oracle oinstall 955711488 2010-02-25 16:09 ORADB1_level1_set_4941_piece_1_date_20100222_711664370
    -rwx------ 1 oracle oinstall 1623564288 2010-02-25 16:11 ORADB1_level1_set_4942_piece_1_date_20100222_711664872
    -rwx------ 1 oracle oinstall 980238336 2010-02-25 16:12 ORADB1_level1_set_4943_piece_1_date_20100222_711664989
    -rwx------ 1 oracle oinstall 280952832 2010-02-25 16:12 ORADB1_level1_set_4944_piece_1_date_20100222_711665385
    -rwx------ 1 oracle oinstall 1130496 2010-02-25 16:12 ORADB1_level1_set_4945_piece_1_date_20100222_711665521

  • 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

  • ORA-12560 in database restore cold backup

    Hi guys,
    I'm trying to restore a cold backup (WINDOWS NT) and I did the following:
    1. Restore the datafiles in a specific location, according to the directory that the files were before.
    2. Create the service:
    C:\>oradim -new -sid ORCL -startmode auto -pfile C:\oracle\admin\ORCL\pfile\initORCL.ora
    3. startup the listener with the instance.
    4. When I try to connect as follows, I receive the following error:
    C:\>connect "/as sysdba"
    'connect' is not recognized as an internal or external command,
    operable program or batch file.
    C:\>sqlplus "/as sysdba"
    SQL*Plus: Release 9.2.0.3.0 - Production on MiΘ Ago 13 17:20:32 2003
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    ERROR:
    ORA-12560: TNS:protocol adapter error
    Enter user-name:
    C:\>
    What am I missing???
    TIA.

    You may be hitting bug 4598734. See Metalink Note:359428.1 - Windows: Starting the instance service fails to start the database in Server rel. 10g

  • 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

  • Restoring archive log after cold backup

    Hello forums users,
    I read many thing on this topic but I didn't find the good answer.
    I performed a cold backup each sunday.
    My database is in ARCHIVE LOG mode.
    Is it possible to restore ARCHIVE LOG files after restoring COLD backup?
    Sunday : cold backup
    Monday : new archive log have been created since cold backup
    Tuesday : same as Monday
    Wednesday : I would like to restore to Monday 22:00 for example
    Can I restore cold backup + apply archive log until Monday 22:00 ?
    Regards,
    Guillaume

    recover database using backup controlfile until cancel|time|logseq|scn
    will do this and prompt you for the archivelogs.
    Known as 'incomplete recovery'
    Hth
    Sybrand Bakker
    Senior Oracle DBA

  • Restoring tigger from cold backup.

    Hi
    I have one problem..... recently i have drooped 1 trigger by mistake of one of my user in database. Now the problem is... we never take the logical backup of that DB.
    Backup mechanism of the database is Cold Backup and size is *2TB*.
    Now i have to restore that trigger from the cold backup with minimum effort , do i have to create the Clone database with the Cold backup using all the datafiles ...? or System tablespace ( or datafile) and default Schema tablespace(Schema which holds the trigger and its tables) in enough for restoring the trigger ?
    I hope i am clear with my question. please let me know if you need more details.
    Please suggest some best and fast way to solve this problem.
    Thanks,

    You need to restore enough to OPEN the DB can you please elaborate this clearly....
    The version is :
    Oracle Database 11g Release 11.1.0.7.0 - 64bit Production
    PL/SQL Release 11.1.0.7.0 - Production
    CORE    11.1.0.7.0 ;     Production
    TNS for Linux: Version 11.1.0.7.0 - Production
    NLSRTL Version 11.1.0.7.0 - Production I have dropped in this Monday. Flashback is not implemented.
    Edited by: user10915512 on May 10, 2011 7:15 AM

  • Test Restore Database Instance from Cold backup

    Hi - I have a customer who is using an Oracle database instance not in archivelog mode
    currently, I have managed to persuade them to backup at least weekly using an RMAN cold backup.
    Prior to my being allowed to do anything else they want to perform a test restore from the cold backup
    I want to find a simple procedure to do this which will enable me to tick the box then hopefully I may be able to persuade them that Hot Backups are the way to go.
    Has anyone got any good suggestions for this please?

    Ah if only things were quite so simple - my hands are tied somewhat there isn't a second machine available at the moment so I was hoping to be able to run a test restore to the same machine !
    No they do not worry about data in this situation - Oracle is used almost as a query engine maybe a very odd solution as the actual data is not really held within this oracle database but the resultant queries are!
    Anyway I think I will just do a virtual restore using the restore database validate command then armtwist a couple of managers!
    One of the areas they had difficulty with is that apparently they had archivelogging on but the rate of writing archivelogs was huge and it was affecting performance. I am not knowledgeable enough to know how to tune that problem!!

Maybe you are looking for