设为首页 收藏本站
查看: 702|回复: 0

[经验分享] NBU异机恢复ORACLE成功版本

[复制链接]
发表于 2018-9-21 13:18:04 | 显示全部楼层 |阅读模式
RMAN> RUN {  2> ALLOCATE CHANNEL ch00 TYPE  'SBT_TAPE';
  3> SEND 'NB_ORA_SERV=nbuserver,NB_ORA_CLIENT=oracle10grac1';
  4> set newname for datafile 1 to'/opt/oracle/oradata/orcl/system.256.779374375';
  5> set newname for datafile 2 to'/opt/oracle/oradata/orcl/undotbs1.258.779374377';
  6> set newname for datafile 3 to'/opt/oracle/oradata/orcl/sysaux.257.779374377';
  7> set newname for datafile 4 to'/opt/oracle/oradata/orcl/users.259.779374377';
  8> set newname for datafile 5 to'/opt/oracle/oradata/orcl/undotbs2.264.779374547';
  9> set newname for datafile 6 to'/opt/oracle/oradata/orcl/test01.dbf';
  10> RESTORE    DATABASE;
  11> switch datafile all;
  12> RESTORE ARCHIVELOG ALL;

  13>>  14> }
  allocated channel: ch00
  channel ch00: sid=542 devtype=SBT_TAPE

  channel ch00: Veritas NetBackup for Oracle ->  sent command to channel: ch00
  executing command: SET NEWNAME
  executing command: SET NEWNAME
  executing command: SET NEWNAME
  executing command: SET NEWNAME
  executing command: SET NEWNAME
  executing command: SET NEWNAME
  Starting restore at 12-APR-12
  Starting implicit crosscheck backup at 12-APR-12
  Finished implicit crosscheck backup at 12-APR-12
  Starting implicit crosscheck copy at 12-APR-12
  Crosschecked 2 objects
  Finished implicit crosscheck copy at 12-APR-12
  searching for all files in the recovery area
  cataloging files...
  no files cataloged
  channel ch00: starting datafile backupset restore
  channel ch00: specifying datafile(s) to restore from backup set
  restoring datafile 00001 to /opt/oracle/oradata/orcl/system.256.779374375
  restoring datafile 00004 to /opt/oracle/oradata/orcl/users.259.779374377
  restoring datafile 00005 to /opt/oracle/oradata/orcl/undotbs2.264.779374547
  channel ch00: reading from backup piece bk_409_1_780401068
  channel ch00: restored backup piece 1
  piece handle=bk_409_1_780401068 tag=HOT_DB_BK_LEVEL0
  channel ch00: restore complete, elapsed time: 00:00:56
  channel ch00: starting datafile backupset restore
  channel ch00: specifying datafile(s) to restore from backup set
  restoring datafile 00002 to /opt/oracle/oradata/orcl/undotbs1.258.779374377
  restoring datafile 00003 to /opt/oracle/oradata/orcl/sysaux.257.779374377
  restoring datafile 00006 to /opt/oracle/oradata/orcl/test01.dbf
  channel ch00: reading from backup piece bk_410_1_780401068
  channel ch00: restored backup piece 1
  piece handle=bk_410_1_780401068 tag=HOT_DB_BK_LEVEL0
  channel ch00: restore complete, elapsed time: 00:00:35
  Finished restore at 12-APR-12
  datafile 1 switched to datafile copy
  input datafile copy recid=12 stamp=780370845 filename=/opt/oracle/oradata/orcl/system.256.779374375
  datafile 2 switched to datafile copy
  input datafile copy recid=13 stamp=780370845 filename=/opt/oracle/oradata/orcl/undotbs1.258.779374377
  datafile 3 switched to datafile copy
  input datafile copy recid=14 stamp=780370845 filename=/opt/oracle/oradata/orcl/sysaux.257.779374377
  datafile 4 switched to datafile copy
  input datafile copy recid=15 stamp=780370845 filename=/opt/oracle/oradata/orcl/users.259.779374377
  datafile 5 switched to datafile copy
  input datafile copy recid=16 stamp=780370845 filename=/opt/oracle/oradata/orcl/undotbs2.264.779374547
  datafile 6 switched to datafile copy
  input datafile copy recid=17 stamp=780370845 filename=/opt/oracle/oradata/orcl/test01.dbf
  Starting restore at 12-APR-12
  released channel: ch00
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03002: failure of restore command at 04/12/2012 01:40:46
  RMAN-06026: some targets not found - aborting restore
  RMAN-06025: no backup of log thread 2 seq 130 lowscn 929777 found to restore
  RMAN-06025: no backup of log thread 2 seq 129 lowscn 929724 found to restore
  RMAN-06025: no backup of log thread 2 seq 128 lowscn 928733 found to restore
  RMAN-06025: no backup of log thread 2 seq 127 lowscn 907963 found to restore
  RMAN-06025: no backup of log thread 2 seq 126 lowscn 907776 found to restore
  RMAN-06025: no backup of log thread 2 seq 125 lowscn 906250 found to restore
  RMAN-06025: no backup of log thread 2 seq 124 lowscn 885594 found to restore
  RMAN-06025: no backup of log thread 2 seq 123 lowscn 865475 found to restore
  RMAN-06025: no backup of log thread 2 seq 122 lowscn 864010 found to restore
  RMAN-06025: no backup of log thread 2 seq 121 lowscn 863247 found to restore
  RMAN-06025: no backup of log thread 2 seq 120 lowscn 863140 found to restore
  RMAN-06025: no backup of log thread 2 seq 119 lowscn 859445 found to restore
  RMAN-06025: no backup of log thread 2 seq 118 lowscn 854593 found to restore
  RMAN-06025: no backup of log thread 2 seq 117 lowscn 854454 found to restore
  RMAN-06025: no backup of log thread 2 seq 116 lowscn 854003 found to restore
  RMAN-06025: no backup of log thread 2 seq 115 lowscn 851640 found to restore
  RMAN-06025: no backup of log thread 2 seq 114 lowscn 808961 found to restore
  RMAN-06025: no backup of log thread 2 seq 113 lowscn 785764 found to restore
  RMAN-06025: no backup of log thread 2 seq 112 lowscn 765763 found to restore
  RMAN-06025: no backup of log thread 2 seq 111 lowscn 765689 found to restore
  RMAN-06025: no backup of log thread 2 seq 110 lowscn 745300 found to restore
  RMAN-06025: no backup of log thread 2 seq 109 lowscn 723232 found to restore
  RMAN-06025: no backup of log thread 2 seq 108 lowscn 685345 found to restore
  RMAN-06025: no backup of log thread 2 seq 107 lowscn 685303 found to restore
  RMAN-06025: no backup of log thread 2 seq 106 lowscn 685194 found to restore
  RMAN-06025: no backup of log thread 2 seq 105 lowscn 685167 found to restore
  RMAN-06025: no backup of log thread 2 seq 104 lowscn 685012 found to restore
  RMAN-06025: no backup of log thread 2 seq 103 lowscn 684991 found to restore
  RMAN-06025: no backup of log thread 2 seq 102 lowscn 658111 found to restore
  RMAN-06025: no backup of log thread 2 seq 101 lowscn 658045 found to restore
  RMAN-06025: no backup of log thread 2 seq 100 lowscn 658006 found to restore
  RMAN-06025: no backup of log thread 2 seq 99 lowscn 657949 found to restore
  RMAN-06025: no backup of log thread 2 seq 98 lowscn 656969 found to restore
  RMAN-06025: no backup of log thread 2 seq 97 lowscn 656944 found to restore
  RMAN-06025: no backup of log thread 2 seq 96 lowscn 624908 found to restore
  RMAN-06025: no backup of log thread 2 seq 95 lowscn 624869 found to restore
  RMAN-06025: no backup of log thread 2 seq 94 lowscn 624260 found to restore
  RMAN-06025: no backup of log thread 2 seq 93 lowscn 623703 found to restore
  RMAN-06025: no backup of log thread 2 seq 92 lowscn 622621 found to restore
  RMAN-06025: no backup of log thread 2 seq 91 lowscn 622596 found to restore
  RMAN-06025: no backup of log thread 2 seq 90 lowscn 621818 found to restore
  RMAN-06025: no backup of log thread 2 seq 89 lowscn 621791 found to restore
  RMAN-06025: no backup of log thread 2 seq 88 lowscn 613706 found to restore
  RMAN-06025: no backup of log thread 2 seq 87 lowscn 613316 found to restore
  RMAN-06025: no backup of log thread 2 seq 86 lowscn 612817 found to restore
  RMAN-06025: no backup of log thread 2 seq 85 lowscn 592253 found to restore
  RMAN-06025: no backup of log thread 2 seq 84 lowscn 592225 found to restore
  RMAN-06025: no backup of log thread 2 seq 83 lowscn 587065 found to restore
  RMAN-06025: no backup of log thread 2 seq 82 lowscn 546386 found to restore
  RMAN-06025: no backup of log thread 2 seq 81 lowscn 522027 found to restore
  RMAN-06025: no backup of log thread 2 seq 80 lowscn 490716 found to restore
  RMAN-06025: no backup of log thread 2 seq 79 lowscn 490683 found to restore
  RMAN-06025: no backup of log thread 2 seq 78 lowscn 483478 found to restore
  RMAN-06025: no backup of log thread 2 seq 77 lowscn 483457 found to restore
  RMAN-06025: no backup of log thread 2 seq 76 lowscn 483217 found to restore
  RMAN-06025: no backup of log thread 2 seq 75 lowscn 483183 found to restore
  RMAN-06025: no backup of log thread 2 seq 74 lowscn 483040 found to restore
  RMAN-06025: no backup of log thread 2 seq 73 lowscn 483020 found to restore
  RMAN-06025: no backup of log thread 2 seq 72 lowscn 482284 found to restore
  RMAN-06025: no backup of log thread 2 seq 71 lowscn 482258 found to restore
  RMAN-06025: no backup of log thread 2 seq 70 lowscn 479954 found to restore
  RMAN> recover database;
  Starting recover at 12-APR-12
  allocated channel: ORA_DISK_1
  channel ORA_DISK_1: sid=542 devtype=DISK
  starting media recovery
  RMAN-00571: ===========================================================
  RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
  RMAN-00571: ===========================================================
  RMAN-03002: failure of recover command at 04/12/2012 01:41:26
  RMAN-06053: unable to perform media recovery because of missing log
  RMAN-06102: no channel to restore a backup or copy of log thread 2 seq 146 lowscn 971389
  RMAN-06102: no channel to restore a backup or copy of log thread 1 seq 146 lowscn 971386
  RMAN-06102: no channel to restore a backup or copy of log thread 2 seq 145 lowscn 970959
  RMAN-06102: no channel to restore a backup or copy of log thread 1 seq 145 lowscn 970956

  RMAN>>  database opened
  RMAN>


运维网声明 1、欢迎大家加入本站运维交流群:群②:261659950 群⑤:202807635 群⑦870801961 群⑧679858003
2、本站所有主题由该帖子作者发表,该帖子作者与运维网享有帖子相关版权
3、所有作品的著作权均归原作者享有,请您和我们一样尊重他人的著作权等合法权益。如果您对作品感到满意,请购买正版
4、禁止制作、复制、发布和传播具有反动、淫秽、色情、暴力、凶杀等内容的信息,一经发现立即删除。若您因此触犯法律,一切后果自负,我们对此不承担任何责任
5、所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其内容的准确性、可靠性、正当性、安全性、合法性等负责,亦不承担任何法律责任
6、所有作品仅供您个人学习、研究或欣赏,不得用于商业或者其他用途,否则,一切后果均由您自己承担,我们对此不承担任何法律责任
7、如涉及侵犯版权等问题,请您及时通知我们,我们将立即采取措施予以解决
8、联系人Email:admin@iyunv.com 网址:www.yunweiku.com

所有资源均系网友上传或者通过网络收集,我们仅提供一个展示、介绍、观摩学习的平台,我们不对其承担任何法律责任,如涉及侵犯版权等问题,请您及时通知我们,我们将立即处理,联系人Email:kefu@iyunv.com,QQ:1061981298 本贴地址:https://www.iyunv.com/thread-599456-1-1.html 上篇帖子: 浅谈Oracle SQL trace-ylw6006 下篇帖子: 配置Oracle 11g Active Dataguard-ylw6006
您需要登录后才可以回帖 登录 | 立即注册

本版积分规则

扫码加入运维网微信交流群X

扫码加入运维网微信交流群

扫描二维码加入运维网微信交流群,最新一手资源尽在官方微信交流群!快快加入我们吧...

扫描微信二维码查看详情

客服E-mail:kefu@iyunv.com 客服QQ:1061981298


QQ群⑦:运维网交流群⑦ QQ群⑧:运维网交流群⑧ k8s群:运维网kubernetes交流群


提醒:禁止发布任何违反国家法律、法规的言论与图片等内容;本站内容均来自个人观点与网络等信息,非本站认同之观点.


本站大部分资源是网友从网上搜集分享而来,其版权均归原作者及其网站所有,我们尊重他人的合法权益,如有内容侵犯您的合法权益,请及时与我们联系进行核实删除!



合作伙伴: 青云cloud

快速回复 返回顶部 返回列表