sl0325 发表于 2011-12-28 15:49

数据库恢复后，启动报错

数据库通过覆盖数据设备恢复后，启动报如下错误：
10:00000:00001:2011/12/27 17:14:59.07 serverUnable 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 serverUnable 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 serverUnable 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 serverUnable 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 serverUnable 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 serverUnable 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 18).
10:00000:00001:2011/12/27 17:14:59.07 server*** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 serverUnable 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 serverUnable 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 serverUnable 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 serverUnable 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 serverUnable 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 serverUnable 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 serverUnable 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 serverUnable 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 18).
10:00000:00001:2011/12/27 17:14:59.07 server*** WARNING ******************
10:00000:00001:2011/12/27 17:14:59.07 serverUnable 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 serverUnable 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 serverUnable 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 serverUnable 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 serverUnable 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 serverUnable 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).
请高手们看看，有什么办法修复吗？dbcc checkdb做过了，但没有修复。

junmeiguo 发表于 2011-12-29 15:15

这个报错我也遇到过，服务器异常断电导致的某个库的空间计算有问题

记得会疯狂的写日志一会儿功夫就生成几个G

我当时是删除重建的库，然后用热备恢复的

Eisen 发表于 2011-12-29 17:38

作dbcc gam

wfcjz 发表于 2012-01-07 14:19

这个做DBCC可以解决，实在不行，重建库，然后BCP IN

sychangchun 发表于 2012-01-31 09:34

只检查了未做修复。
页: [1]
查看完整版本: 数据库恢复后，启动报错