Quantcast
Channel: SQL Server High Availability and Disaster Recovery forum
Viewing all articles
Browse latest Browse all 4689

DBCC CHECDB REPAIR does not fix errors ?

$
0
0

Hi There

This is on Sql Server 2000, SP3.

When i run DBCC CHECKDB i get the following errors:

============================================================================================

Server: Msg 8928, Level 16, State 1, Line 1
Object ID 2, index ID 255: Page (1:76914) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 2, index ID 255, page (1:76914). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
CHECKDB found 0 allocation errors and 2 consistency errors in table 'sysindexes' (object ID 2).
CHECKDB found 0 allocation errors and 2 consistency errors in database 'OLTP3PRO'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (OLTP3PRO ).

============================================================================================

The database is not suspect and everything seems to be working fine, so after hours i run the follwing:

DBCC CHECKDB('OLTP3PRO', REPAIR_ALLOW_DATA_LOSS)

But i get the same errors?

Server: Msg 8928, Level 16, State 1, Line 1
Object ID 2, index ID 255: Page (1:76914) could not be processed. See other errors for details.
Server: Msg 8939, Level 16, State 1, Line 1
Table error: Object ID 2, index ID 255, page (1:76914). Test (IS_ON (BUF_IOERR, bp->bstat) && bp->berrcode) failed. Values are 2057 and -1.
Table error, The text, ntext or image node at page (1:76914), slot 0, text ID 2129023023802 is referenced by page (1:3859) but was not seen in the scan.

The repair level on the DBCC statement caused this repair to be bypassed.

CHECKDB found 4  found 4 consistancy errors.

So it seems CHECKDB with repair does not help ? How do i fix this ?

Thanx


Viewing all articles
Browse latest Browse all 4689

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>