數(shù)據(jù)庫日志文件丟失，怎么能讀取數(shù)據(jù)

sl0325

請問版主，為什么不讓我發(fā)這個(gè)主題的帖子�。�
好不容易解決了一些問題，還有問題想請問大家啊！

sl0325

請問大家，如下報(bào)錯(cuò)應(yīng)該如何處理啊
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

回復(fù) 28# andkylee

已經(jīng)BCP出來重要表的數(shù)據(jù)，謝謝大家這些天來給我的幫助，也謝謝網(wǎng)站給大家了一個(gè)技術(shù)交流的環(huán)境。


   

andkylee

回復(fù) 33# sl0325


    恭喜啊。
只要數(shù)據(jù)設(shè)備沒有丟，且數(shù)據(jù)設(shè)備是完好的，數(shù)據(jù)肯定是可以導(dǎo)出來的。

andkylee

回復(fù) 31# sl0325


    這是一個(gè)技術(shù)交流的論壇， 怎么可能有這樣的斑竹呢？

andkylee

回復(fù) 31# sl0325


    這是一個(gè)技術(shù)交流的論壇， 怎么可能有這樣的版主呢？

wfcjz

能在-32768下啟動(dòng)起來，BCP OUT出去數(shù)據(jù)，再建庫，然后BCP IN進(jìn)來，很快的，其實(shí)處理問題先確定思路是很重要的！

sychangchun

數(shù)據(jù)庫丟失文件日志是比較難搞的啊。