数据库日志文件丢失，怎么能读取数据

sl0325

请问版主，为什么不让我发这个主题的帖子啊？
好不容易解决了一些问题，还有问题想请问大家啊！

sl0325

请问大家，如下报错应该如何处理啊
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).

sl0325

回复 28# andkylee

已经BCP出来重要表的数据，谢谢大家这些天来给我的帮助，也谢谢网站给大家了一个技术交流的环境。


   

andkylee

回复 33# sl0325


    恭喜啊。
只要数据设备没有丢，且数据设备是完好的，数据肯定是可以导出来的。

andkylee

回复 31# sl0325


    这是一个技术交流的论坛， 怎么可能有这样的斑竹呢？

andkylee

回复 31# sl0325


    这是一个技术交流的论坛， 怎么可能有这样的版主呢？

wfcjz

能在-32768下启动起来，BCP OUT出去数据，再建库，然后BCP IN进来，很快的，其实处理问题先确定思路是很重要的！

sychangchun

数据库丢失文件日志是比较难搞的啊。