CHECKDB found 0 allocation errors and 2 consistency errors in table in

[Former Member]

Dear all,

Part for VMware hardware migration ->

We have installed new SAP BW server 3.1C. then attached the prodcution server database as source database

OS: Windows 2003, DB:SQL 2000 Server & SP4.

After DB attach We ran the DBCC CHECKDB in DB13. After one and half hours we received the below error message on the

log files. CCMS_CHECK_DB_HIST_2010.txt

Microsoft SQL Server  2000 - 8.00.2039 (Intel X86)  	May  3 2005 23:18:38  	Copyright (c) 1988-2003 Microsoft 
Corporation	Enterprise Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
Msg 8928, Sev 16: Object ID 968088793, index ID 0: Page (4:10220119) could not be processed. See other errors for details. 
[SQLSTATE 42000] Msg 8939, Sev 16: Table error: Object ID 968088793, index ID 0, page (4:10220119). Test (IS_ON (BUF_IOERR, bp->bstat) &&bp->berrcode) failed. Values are 2057 and -1. [SQLSTATE 42000]
Msg 8990, Sev 16: CHECKDB found 0 allocation errors and 2 consistency errors in table '<sid>./BXX/AXXXXX300' (object ID 
968088793). [SQLSTATE 01000]
Msg 8989, Sev 16: CHECKDB found 0 allocation errors and 2 consistency errors in database '<SID>'. [SQLSTATE 01000]
Msg 8958, Sev 16: repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (XXX ). [SQLSTATE 
01000]

Please let me know how to correct the 2 consistency errors in my Table '<sid>./BXX/AXXXXX300'

Thanks

Malai

[markus_doehr2]

> Part for VMware hardware migration ->

> We have installed new SAP BW server 3.1C. then attached the prodcution server database as source database

> OS: Windows 2003, DB:SQL 2000 Server & SP4.

You're aware that

- 32bit operating systems are not supported under VMWare?

- SQL Server 2000 is not supported under VMWare?

> Msg 8989, Sev 16: CHECKDB found 0 allocation errors and 2 consistency errors in database '<SID>'. [SQLSTATE 01000]

> Msg 8958, Sev 16: repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (XXX ). [SQLSTATE

> 01000]

>

> Please let me know how to correct the 2 consistency errors in my Table '<sid>./BXX/AXXXXX300'

Your have corruptions on your database. You can use (as suggested) DBCC CHECKDB ('tablename', repair_allow_data_loss) but you may really loose data and make the system inconsistent.

I'd execute that check on the source database first and see if you have the same error there.

Anyway, you may be lost since your configuration is unsupported.

Markus

[Former Member]

Marcus,

Thank you..

Malai