设为首页 加入收藏

TOP

恢复丢失的控制文件(三)
2014-11-24 00:56:43 来源: 作者: 【 】 浏览:69
Tags:恢复 丢失 控制 文件
' no longer needed
  • for this recovery
  • Specify log: {=suggested | filename | AUTO | CANCEL}
  • ORA-00308: cannot open archived log '/zxm/
    cindytest/arch/1_24_747160176.dbf'
  • ORA-27037: unable to obtain file status
  • Linux-x86_64 Error: 2: No such file or directory
  • Additional information: 3
  • rman会自己猜测归档日志文件,我们只需要按下回车键就可以了,不过最后一个需要注意,第24号日志文件实际是联机日志,并不是控制文件,所以需要我们明确告诉rman这个日志文件的位置。

    如果不记得到底哪一个是当前日志了,那就从第一个开始吧,再次输入这个命令,在遇到提示时输入联机日志的位置;

    1. SQL> recover database using backup controlfile;
    2. ORA-00279: change 76850708336 generated at
      04/13/2011 11:36:21 needed for
    3. thread 1
    4. ORA-00289: suggestion : /zxm/cindytest/arch/1_24_747160176.dbf
    5. ORA-00280: change 76850708336 for thread 1 is in sequence #24
    6. Specify log: {=suggested | filename | AUTO | CANCEL}

    输入文件位置:

    1. /zxm/cindytest/redo01.log

    恢复成功:

    1. Log applied.
    2. Media recovery complete.
    David备注:我实验时,如果使用SQL与上面完全相同,但是如果使用rman可以直接recover database,加using backup controlfile会报语法错:
    SQL> startup
    ORA-32004: obsolete or deprecated parameter(s) specified for RDBMS instance
    ORACLE instance started.

    Total System Global Area 572043264 bytes
    Fixed Size 2230432 bytes
    Variable Size 520095584 bytes
    Database Buffers 46137344 bytes
    Redo Buffers 3579904 bytes
    ORA-00205: error in identifying control file, check alert log for more info

    restore控制文件后: alter database mount;
    Database altered.

    SQL> select sequence# from v$log;

    SEQUENCE#
    ----------
    16
    15
    17
    RMAN> recover database;


    Starting recover at 12-JAN-14
    released channel: ORA_DISK_1
    Starting implicit crosscheck backup at 12-JAN-14
    allocated channel: ORA_DISK_1
    channel ORA_DISK_1: SID=26 device type=DISK
    Crosschecked 4 objects
    Finished implicit crosscheck backup at 12-JAN-14

    Starting implicit crosscheck copy at 12-JAN-14
    using channel ORA_DISK_1
    Finished implicit crosscheck copy at 12-JAN-14

    searching for all files in the recovery area
    cataloging files...
    cataloging done


    List of Cataloged Files
    =======================
    File Name: /opt/app/oracle/fast_recovery_area/IPCDB/archivelog/2014_01_12/o1_mf_1_19_9f4vkr74_.arc
    File Name: /opt/app/oracle/fast_recovery_area/IPCDB/archivelog/2014_01_12/o1_mf_1_17_9f4vjvms_.arc
    File Name: /opt/app/oracle/fast_recovery_area/IPCDB/archivelog/2014_01_12/o1_mf_1_18_9f4vkbbg_.arc
    File Name: /opt/app/oracle/fast_recovery_area/IPCDB/backupset/2014_01_12/o1_mf_ncsnf_TAG20140112T181519_9f4tvm53_.bkp

    using channel ORA_DISK_1
    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
    ORACLE error from target database:
    ORA-19922: there is no parent row with id 0 and level 1

    starting media recovery

    archived log for thread 1 with sequence 17 is already on disk as file /opt/app/oracle/fast_recovery_area/IPCDB/archivelog/2014_01_12/o1_mf_1_17_9f4vjvms_.arc
    archived log for thread 1 with sequence 18 is already on disk as file /opt/app/oracle/fast_recovery_area/IPCDB/archivelog/2014_01_12/o1_mf_1_18_9f4vkbbg_.arc
    archived log for thread 1 with sequence 19 is already on disk as file /opt/app/oracle/fast_recovery_area/IPCDB/archivelog/2014_01_12/o1_mf_1_19_9f4vkr74_.arc
    archived log for thread 1 with sequence 20 is already on disk as file +DATA/ipcdb/onlinelog/group_2.268.835737765
    archived log file name=/opt/app/oracle/fast_recover
    首页 上一页 1 2 3 4 5 6 下一页 尾页 3/6/6
    】【打印繁体】【投稿】【收藏】 【推荐】【举报】【评论】 【关闭】 【返回顶部
    分享到: 
    上一篇Oracle/JSP技术涉及日期和时间问.. 下一篇Oracle数据库中日期时间的操作比..

    评论

    帐  号: 密码: (新用户注册)
    验 证 码:
    表  情:
    内  容: