免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 2556 | 回复: 4
打印 上一主题 下一主题

数据库日志丢失已经能-32768启动,还要问题请教 [复制链接]

论坛徽章:
0
跳转到指定楼层
1 [收藏(0)] [报告]
发表于 2011-12-28 10:14 |只看该作者 |倒序浏览
版主和高手们大家好,经过指导数据库已能bypass启动,但还要如下报错:
请大家帮忙看看,有办法恢复吗?
10:00000:00001:2011/12/27 17:14:59.07 server  Unable to find the sysusages row that controls the allocation page -1130363945 while doing the extents accounting for OAM page 6, object ID 5, index ID 0, database ID 4 (OAM entry 2).
10:00000:00001:2011/12/27 17:14:59.07 server  *** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 server  Unable to find the sysusages row that controls the allocation page 115343360 while doing the extents accounting for OAM page 6, object ID 5, index ID 0, database ID 4 (OAM entry 3).
10:00000:00001:2011/12/27 17:14:59.07 server  *** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 server  Unable to find the sysusages row that controls the allocation page 1268252672 while doing the extents accounting for OAM page 6, object ID 5, index ID 0, database ID 4 (OAM entry 5).
10:00000:00001:2011/12/27 17:14:59.07 server  *** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 server  Unable to find the sysusages row that controls the allocation page 983040000 while doing the extents accounting for OAM page 6, object ID 5, index ID 0, database ID 4 (OAM entry 9).
10:00000:00001:2011/12/27 17:14:59.07 server  *** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 server  Unable to find the sysusages row that controls the allocation page 819200000 while doing the extents accounting for OAM page 6, object ID 5, index ID 0, database ID 4 (OAM entry 17).
10:00000:00001:2011/12/27 17:14:59.07 server  *** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 server  Unable to find the sysusages row that controls the allocation page 343965293 while doing the extents accounting for OAM page 6, object ID 5, index ID 0, database ID 4 (OAM entry 1.
10:00000:00001:2011/12/27 17:14:59.07 server  *** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 server  Unable to find the sysusages row that controls the allocation page 1347747840 while doing the extents accounting for OAM page 4, object ID 5, index ID 0, database ID 4 (OAM entry 11).
10:00000:00001:2011/12/27 17:14:59.07 server  *** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 server  Unable to find the sysusages row that controls the allocation page 1162104653 while doing the extents accounting for OAM page 4, object ID 5, index ID 0, database ID 4 (OAM entry 12).
10:00000:00001:2011/12/27 17:14:59.07 server  *** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 server  Unable to find the sysusages row that controls the allocation page -1130363945 while doing the extents accounting for OAM page 6, object ID 5, index ID 0, database ID 4 (OAM entry 2).
10:00000:00001:2011/12/27 17:14:59.07 server  *** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 server  Unable to find the sysusages row that controls the allocation page 115343360 while doing the extents accounting for OAM page 6, object ID 5, index ID 0, database ID 4 (OAM entry 3).
10:00000:00001:2011/12/27 17:14:59.07 server  *** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 server  Unable to find the sysusages row that controls the allocation page 1268252672 while doing the extents accounting for OAM page 6, object ID 5, index ID 0, database ID 4 (OAM entry 5).
10:00000:00001:2011/12/27 17:14:59.07 server  *** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 server  Unable to find the sysusages row that controls the allocation page 983040000 while doing the extents accounting for OAM page 6, object ID 5, index ID 0, database ID 4 (OAM entry 9).
10:00000:00001:2011/12/27 17:14:59.07 server  *** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 server  Unable to find the sysusages row that controls the allocation page 819200000 while doing the extents accounting for OAM page 6, object ID 5, index ID 0, database ID 4 (OAM entry 17).
10:00000:00001:2011/12/27 17:14:59.07 server  *** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 server  Unable to find the sysusages row that controls the allocation page 343965293 while doing the extents accounting for OAM page 6, object ID 5, index ID 0, database ID 4 (OAM entry 1.
10:00000:00001:2011/12/27 17:14:59.07 server  *** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 server  Unable to find the sysusages row that controls the allocation page 1347747840 while doing the extents accounting for OAM page 4, object ID 5, index ID 0, database ID 4 (OAM entry 11).
10:00000:00001:2011/12/27 17:14:59.07 server  *** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 server  Unable to find the sysusages row that controls the allocation page 1162104653 while doing the extents accounting for OAM page 4, object ID 5, index ID 0, database ID 4 (OAM entry 12).
10:00000:00001:2011/12/27 17:14:59.07 server  *** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 server  Unable to find the sysusages row that controls the allocation page -1130363945 while doing the extents accounting for OAM page 6, object ID 5, index ID 0, database ID 4 (OAM entry 2).
10:00000:00001:2011/12/27 17:14:59.07 server  *** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 server  Unable to find the sysusages row that controls the allocation page 115343360 while doing the extents accounting for OAM page 6, object ID 5, index ID 0, database ID 4 (OAM entry 3).
10:00000:00001:2011/12/27 17:14:59.07 server  *** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 server  Unable to find the sysusages row that controls the allocation page 1268252672 while doing the extents accounting for OAM page 6, object ID 5, index ID 0, database ID 4 (OAM entry 5).
10:00000:00001:2011/12/27 17:14:59.07 server  *** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 server  Unable to find the sysusages row that controls the allocation page 983040000 while doing the extents accounting for OAM page 6, object ID 5, index ID 0, database ID 4 (OAM entry 9).

论坛徽章:
33
ChinaUnix元老
日期:2018-07-04 15:10:362015年亚洲杯之阿联酋
日期:2015-02-06 17:15:532015亚冠之武里南联
日期:2015-06-06 15:40:252015亚冠之北京国安
日期:2015-06-17 15:42:412022北京冬奥会纪念版徽章
日期:2015-08-10 16:30:322015亚冠之阿尔纳斯尔
日期:2015-09-20 09:42:1215-16赛季CBA联赛之北京
日期:2016-01-15 10:03:5915-16赛季CBA联赛之青岛
日期:2016-04-26 16:44:4915-16赛季CBA联赛之广夏
日期:2018-07-04 15:33:21C
日期:2016-10-25 16:12:142017金鸡报晓
日期:2017-01-10 15:19:5615-16赛季CBA联赛之同曦
日期:2017-02-22 22:41:10
2 [报告]
发表于 2012-01-10 08:52 |只看该作者
能启动先BCP出来,实在不行重新建库,再BCP IN进去,

BCP麻烦的是只备份数据,对于库中的过程、表结构等相关的可以利用工具先导出来,然后建库再重建,再BCP IN。应该会很快的!

论坛徽章:
7
数据库技术版块每日发帖之星
日期:2015-08-09 06:20:00数据库技术版块每日发帖之星
日期:2015-11-03 06:20:00数据库技术版块每日发帖之星
日期:2016-02-20 06:20:00数据库技术版块每日发帖之星
日期:2016-07-13 06:20:00数据库技术版块每日发帖之星
日期:2016-07-31 06:20:00数据库技术版块每日发帖之星
日期:2016-08-01 06:20:00数据库技术版块每日发帖之星
日期:2016-08-18 06:20:00
3 [报告]
发表于 2012-01-10 09:10 |只看该作者
object 5 -- sysprocedures,编译对象索引系统表。试试dbcc修复一下。

论坛徽章:
33
ChinaUnix元老
日期:2018-07-04 15:10:362015年亚洲杯之阿联酋
日期:2015-02-06 17:15:532015亚冠之武里南联
日期:2015-06-06 15:40:252015亚冠之北京国安
日期:2015-06-17 15:42:412022北京冬奥会纪念版徽章
日期:2015-08-10 16:30:322015亚冠之阿尔纳斯尔
日期:2015-09-20 09:42:1215-16赛季CBA联赛之北京
日期:2016-01-15 10:03:5915-16赛季CBA联赛之青岛
日期:2016-04-26 16:44:4915-16赛季CBA联赛之广夏
日期:2018-07-04 15:33:21C
日期:2016-10-25 16:12:142017金鸡报晓
日期:2017-01-10 15:19:5615-16赛季CBA联赛之同曦
日期:2017-02-22 22:41:10
4 [报告]
发表于 2012-01-10 11:21 |只看该作者
这个做DBCC修复估计很费神!

论坛徽章:
0
5 [报告]
发表于 2012-01-30 21:48 |只看该作者
各种数据库的日志文件丢失都比较难办。
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

  

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

清除 Cookies - ChinaUnix - Archiver - WAP - TOP