免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
› 论坛 › IT运维 › 存储备份 › Veritas技术交流区 › NBU异机恢复Oracle出错
12
最近访问板块 发新帖
楼主: 放羊的骆驼
打印 上一主题 下一主题

[Veritas NBU] NBU异机恢复Oracle出错 [复制链接]

花和尚

论坛徽章:
0
11楼 [报告]
发表于 2009-08-12 11:41 |只看该作者
原帖由 无牙 于 2009-8-10 23:40 发表


Oralce允许将控制文件建在裸设备上牙？



呵呵，不好意思，没说清楚。

控制文件先恢复到/test/这个目录中，然后复制到/dev/下面的，而这个'/dev/rlvloginkctrl03'是AIX下面创建的一个裸设备文件。把控制文件这样复制过来会有问题的。
实战分享：从技术角度谈机器学习入门| 【大话IT】RadonDB低门槛向MySQL集群下战书 | ChinaUnix打赏功能已上线！ | 新一代分布式关系型数据库RadonDB知多少？
无牙

论坛徽章:
1
CU十二周年纪念徽章 日期:2013-10-24 15:41:34
12楼 [报告]
发表于 2009-08-12 16:31 |只看该作者

回复 #11 花和尚 的帖子

肯定不能复制牙，用dd.
实战分享：从技术角度谈机器学习入门| 【大话IT】RadonDB低门槛向MySQL集群下战书 | ChinaUnix打赏功能已上线！ | 新一代分布式关系型数据库RadonDB知多少？
花和尚

论坛徽章:
0
13楼 [报告]
发表于 2009-08-14 14:15 |只看该作者

回复 #12 无牙 的帖子

是的，我刚调整了下，把控制文件存放在文件系统中，修改init.ora参数后可以开始恢复了。但还是报错。我把结果贴出来。总共做了两次恢复，第一次直接恢复的。第二次做了下验证。
$ rman target / nocatalog

Recovery Manager: Release 10.2.0.4.0 - Production on Fri Aug 14 11:31:45 2009

Copyright (c) 1982, 2007, Oracle.  All rights reserved.

connected to target database: logink (not mounted)
using target database control file instead of recovery catalog

RMAN> shutdown immediate

Oracle instance shut down

RMAN> startup mount pfile='/usr/ygora/admin/logink/pfile/init.ora';

connected to target database (not started)
Oracle instance started
database mounted

Total System Global Area    4932501504 bytes

Fixed Size                     2090760 bytes
Variable Size                889194744 bytes
Database Buffers            4026531840 bytes
Redo Buffers                  14684160 bytes

RMAN> run {
2> allocate channel c1 type sbt;
3> allocate channel c2 type sbt;
4> send 'NB_ORA_SERV=back_svr,NB_ORA_CLIENT=logink_back';
5> set until time "to_date('2009-08-12 02:00:00','YYYY-MM-DD HH24:MI:SS')";
6> restore database;
7> recover database;
8> release channel c1;
9> release channel c2;
10> }

allocated channel: c1
channel c1: sid=542 devtype=SBT_TAPE
channel c1: Veritas NetBackup for Oracle - Release 6.5 (2007072323)

allocated channel: c2
channel c2: sid=540 devtype=SBT_TAPE
channel c2: Veritas NetBackup for Oracle - Release 6.5 (2007072323)

sent command to channel: c1
sent command to channel: c2

executing command: SET until clause

Starting restore at 14-AUG-09

skipping datafile 2; already restored to file /dev/rlvloginkundo01
channel c1: starting datafile backupset restore
channel c1: specifying datafile(s) to restore from backup set
restoring datafile 00009 to /dev/rlvloginkdata04
restoring datafile 00013 to /dev/rlvloginkindx04
channel c1: reading from backup piece bk_351_1_694634266
channel c2: starting datafile backupset restore
channel c2: specifying datafile(s) to restore from backup set
restoring datafile 00008 to /dev/rlvloginkdata03
restoring datafile 00012 to /dev/rlvloginkindx03
channel c2: reading from backup piece bk_350_1_694634266
channel c2: restored backup piece 1
piece handle=bk_350_1_694634266 tag=HOT_DB_BK_LEVEL0
restore not complete
Restore did not complete for file 12 from backup piece bk_350_1_694634266 (devtype=NULL, piecenum=1, pieces_done=1, done=FALSE, failover=FALSE)
channel c2: starting datafile backupset restore
channel c2: specifying datafile(s) to restore from backup set
restoring datafile 00010 to /dev/rlvloginkdata05
channel c2: reading from backup piece bk_352_1_694640032
channel c1: restored backup piece 1
piece handle=bk_351_1_694634266 tag=HOT_DB_BK_LEVEL0
restore not complete
Restore did not complete for file 13 from backup piece bk_351_1_694634266 (devtype=NULL, piecenum=1, pieces_done=1, done=FALSE, failover=FALSE)
channel c1: starting datafile backupset restore
channel c1: specifying datafile(s) to restore from backup set
restoring datafile 00001 to /dev/rlvloginksys01
restoring datafile 00005 to /dev/rlvloginkdata01
channel c1: reading from backup piece bk_353_1_694640727
released channel: c1
released channel: c2
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of restore command at 08/14/2009 11:59:56
ORA-19870: error reading backup piece bk_352_1_694640032
ORA-00227: corrupt block detected in control file: (block 336, # blocks 1)
ORA-00202: control file: '/test/control03.ctl'


验证恢复

RMAN> run {
2> allocate channel c1 type sbt;
3> allocate channel c2 type sbt;send 'NB_ORA_SERV=back_svr,NB_ORA_CLIENT=logink_back';
4> set until time "to_date('2009-08-12 02:00:00','YYYY-MM-DD HH24:MI:SS')";
5> restore database validate check logical;
6> release channel c1;
7> release channel c2;
8> }

allocated channel: c1
channel c1: sid=542 devtype=SBT_TAPE
channel c1: Veritas NetBackup for Oracle - Release 6.5 (2007072323)

allocated channel: c2
channel c2: sid=540 devtype=SBT_TAPE
channel c2: Veritas NetBackup for Oracle - Release 6.5 (2007072323)

sent command to channel: c1
sent command to channel: c2

executing command: SET until clause

Starting restore at 14-AUG-09

channel c1: starting validation of datafile backupset
channel c2: starting validation of datafile backupset
channel c1: reading from backup piece bk_351_1_694634266
channel c2: reading from backup piece bk_350_1_694634266
channel c2: restored backup piece 1
piece handle=bk_350_1_694634266 tag=HOT_DB_BK_LEVEL0
restore not complete
Restore did not complete for archived log thread sequence  from backup piece bk_350_1_694634266 (devtype=NULL, piecenum=1, pieces_done=1, done=FALSE, failover=FALSE)
channel c2: starting validation of datafile backupset
channel c2: reading from backup piece bk_352_1_694640032
channel c1: restored backup piece 1
piece handle=bk_351_1_694634266 tag=HOT_DB_BK_LEVEL0
restore not complete
Restore did not complete for archived log thread sequence  from backup piece bk_351_1_694634266 (devtype=NULL, piecenum=1, pieces_done=1, done=FALSE, failover=FALSE)
channel c1: starting validation of datafile backupset
channel c1: reading from backup piece bk_353_1_694640727
channel c2: restored backup piece 1
piece handle=bk_352_1_694640032 tag=HOT_DB_BK_LEVEL0
channel c2: validation complete, elapsed time: 00:11:01
channel c2: starting validation of datafile backupset
channel c2: reading from backup piece bk_354_1_694641232
channel c1: restored backup piece 1
piece handle=bk_353_1_694640727 tag=HOT_DB_BK_LEVEL0
restore not complete
Restore did not complete for archived log thread sequence  from backup piece bk_353_1_694640727 (devtype=NULL, piecenum=1, pieces_done=1, done=FALSE, failover=FALSE)
channel c1: starting validation of datafile backupset
channel c1: reading from backup piece bk_355_1_694641668
channel c2: restored backup piece 1
piece handle=bk_354_1_694641232 tag=HOT_DB_BK_LEVEL0
restore not complete
Restore did not complete for archived log thread sequence  from backup piece bk_354_1_694641232 (devtype=NULL, piecenum=1, pieces_done=1, done=FALSE, failover=FALSE)
channel c2: starting validation of datafile backupset
channel c2: reading from backup piece bk_356_1_694642083
channel c1: restored backup piece 1
piece handle=bk_355_1_694641668 tag=HOT_DB_BK_LEVEL0
channel c1: validation complete, elapsed time: 00:08:20
channel c2: restored backup piece 1
piece handle=bk_356_1_694642083 tag=HOT_DB_BK_LEVEL0
channel c2: validation complete, elapsed time: 00:02:30
failover to previous backup

channel c1: starting validation of datafile backupset
channel c2: starting validation of datafile backupset
channel c1: reading from backup piece bk_338_1_694547868
channel c2: reading from backup piece bk_339_1_694547868
channel c1: restored backup piece 1
piece handle=bk_338_1_694547868 tag=HOT_DB_BK_LEVEL0
restore not complete
Restore did not complete for archived log thread sequence  from backup piece bk_338_1_694547868 (devtype=NULL, piecenum=1, pieces_done=1, done=FALSE, failover=FALSE)
channel c2: restored backup piece 1
piece handle=bk_339_1_694547868 tag=HOT_DB_BK_LEVEL0
restore not complete
Restore did not complete for archived log thread sequence  from backup piece bk_339_1_694547868 (devtype=NULL, piecenum=1, pieces_done=1, done=FALSE, failover=FALSE)
channel c1: starting validation of datafile backupset
channel c2: starting validation of datafile backupset
channel c1: reading from backup piece bk_341_1_694552119
channel c2: reading from backup piece bk_342_1_694552194
channel c1: restored backup piece 1
piece handle=bk_341_1_694552119 tag=HOT_DB_BK_LEVEL0
restore not complete
Restore did not complete for archived log thread sequence  from backup piece bk_341_1_694552119 (devtype=NULL, piecenum=1, pieces_done=1, done=FALSE, failover=FALSE)
channel c2: restored backup piece 1
piece handle=bk_342_1_694552194 tag=HOT_DB_BK_LEVEL0
channel c2: validation complete, elapsed time: 00:10:05
failover to previous backup

channel c1: starting validation of datafile backupset
channel c2: starting validation of datafile backupset
channel c1: reading from backup piece bk_329_1_694461468
channel c2: reading from backup piece bk_328_1_694461468
channel c2: restored backup piece 1
piece handle=bk_328_1_694461468 tag=HOT_DB_BK_LEVEL0
channel c2: validation complete, elapsed time: 00:11:15
channel c2: starting validation of datafile backupset
channel c2: reading from backup piece bk_331_1_694465549
channel c1: restored backup piece 1
piece handle=bk_329_1_694461468 tag=HOT_DB_BK_LEVEL0
restore not complete
Restore did not complete for archived log thread sequence  from backup piece bk_329_1_694461468 (devtype=NULL, piecenum=1, pieces_done=1, done=FALSE, failover=FALSE)
channel c2: restored backup piece 1
piece handle=bk_331_1_694465549 tag=HOT_DB_BK_LEVEL0
channel c2: validation complete, elapsed time: 00:07:50
failover to previous backup

channel c1: starting validation of datafile backupset
channel c1: reading from backup piece bk_319_1_694375069
channel c1: restored backup piece 1
piece handle=bk_319_1_694375069 tag=HOT_DB_BK_LEVEL0
channel c1: validation complete, elapsed time: 00:09:16
Finished restore at 14-AUG-09

released channel: c1

released channel: c2



我看不出问题出在哪里，请指教。

[ 本帖最后由 花和尚 于 2009-8-14 14:23 编辑 ]
实战分享：从技术角度谈机器学习入门| 【大话IT】RadonDB低门槛向MySQL集群下战书 | ChinaUnix打赏功能已上线！ | 新一代分布式关系型数据库RadonDB知多少？
花和尚

论坛徽章:
0
14楼 [报告]
发表于 2009-08-14 14:18 |只看该作者
我怀疑是出在备份集完整性出错，因为是备份到VTL的，该VTL有重复数据删除技术，我怀疑是重复数据删除导致的备份片出错。不知道有没有道理。请拍砖。
实战分享：从技术角度谈机器学习入门| 【大话IT】RadonDB低门槛向MySQL集群下战书 | ChinaUnix打赏功能已上线！ | 新一代分布式关系型数据库RadonDB知多少？
无牙

论坛徽章:
1
CU十二周年纪念徽章 日期:2013-10-24 15:41:34
15楼 [报告]
发表于 2009-08-14 18:36 |只看该作者
日志难道被VTL给和谐了？

我再仔细看看日志。
实战分享：从技术角度谈机器学习入门| 【大话IT】RadonDB低门槛向MySQL集群下战书 | ChinaUnix打赏功能已上线！ | 新一代分布式关系型数据库RadonDB知多少？
南希

论坛徽章:
0
16楼 [报告]
发表于 2009-08-14 20:53 |只看该作者
restore  database 阶段, 应该还没有开始介质恢复啦,  应该还只是在把 backup piece 包含的数据文件恢复到磁盘上,  还没有开始做recovery.

能不能讲讲的环境, 以及 备份是怎么做的?
实战分享：从技术角度谈机器学习入门| 【大话IT】RadonDB低门槛向MySQL集群下战书 | ChinaUnix打赏功能已上线！ | 新一代分布式关系型数据库RadonDB知多少？
南希

论坛徽章:
0
17楼 [报告]
发表于 2009-08-14 21:38 |只看该作者
是不是可以试着把控制文件恢复到裸设备上, 然后再做恢复.  但是觉得这个应该没什么区别.  可以试试看.
实战分享：从技术角度谈机器学习入门| 【大话IT】RadonDB低门槛向MySQL集群下战书 | ChinaUnix打赏功能已上线！ | 新一代分布式关系型数据库RadonDB知多少？
mike79

论坛徽章:
12
CU大牛徽章 日期:2013-09-18 15:20:4815-16赛季CBA联赛之同曦 日期:2016-02-01 20:28:25IT运维版块每日发帖之星 日期:2015-11-10 06:20:00操作系统版块每日发帖之星 日期:2015-10-28 06:20:002015亚冠之塔什干棉农 日期:2015-06-04 11:41:56丑牛 日期:2014-05-10 16:11:33技术图书徽章 日期:2013-09-23 13:25:58CU大牛徽章 日期:2013-09-18 15:21:17CU大牛徽章 日期:2013-09-18 15:21:12CU大牛徽章 日期:2013-09-18 15:21:06CU大牛徽章 日期:2013-09-18 15:20:58数据库技术版块每日发帖之星 日期:2016-02-08 06:20:00
18楼 [报告]
发表于 2009-08-15 23:29 |只看该作者
出错的都是归档日志？是否归档日志文件系统有问题？
实战分享：从技术角度谈机器学习入门| 【大话IT】RadonDB低门槛向MySQL集群下战书 | ChinaUnix打赏功能已上线！ | 新一代分布式关系型数据库RadonDB知多少？
12
返回列表 发新帖
高级模式
B Color Image Link Quote Code Smilies
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

北京盛拓优讯信息技术有限公司. 版权所有 京ICP备16024965号-6 北京市公安局海淀分局网监中心备案编号：11010802020122 niuxiaotong@pcpop.com 17352615567
未成年举报专区
中国互联网协会会员  联系我们：huangweiwei@itpub.net
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP