DBCC CheckDB

Question

DBCC CheckDB

suchita0805

SSC Veteran

Points: 271
More actions
October 15, 2016 at 7:24 am

#331037

CHECKDB found 0 allocation errors and 14 consistency errors in database 'Test'.
repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (Test).
This is the suggestion what i received.
Having no backup of the database ..
Please advise
October 19, 2016 at 12:42 am

This was removed by the editor as SPAM

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 1

Can you post the full output of CheckDB?

All I can tell you from what you posted is that you're going to lose data fixing this (and without a backup, checkdb with the repair_allow_data_loss option is about your only remaining choice. and yes, it will lose data)

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 2

suchita0805 (10/15/2016)
Having no backup of the database ..

JasonClark (10/19/2016)
So before going to restore your database you must verify the back health using restore verifyonly.

Um.... Can't exactly verify something that doesn't exist (not that restore verifyonly does any useful validation anyway)

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

suchita0805 SSC Veteran Points: 271 More actions · Answer 3

Please find the whole error below

Failed:(-1073548784) Executing the query "DBCC CHECKDB(N'test') WITH NO_INFOMSGS

" failed with the following error: "Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 14431804106256 (type Unknown), page (1:73944). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -1.

Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 28829995946667264 (type Unknown), page ID (1:74012) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 28832159061256128 (type Unknown), page ID (1:74011) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 28833677411961856 (type Unknown), page ID (1:73943) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 28834977398347264 (type Unknown), page ID (1:74013) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 28842413864100352 (type Unknown), page ID (1:73945) contains an incorrect page ID in its page header. The PageId in the page header = (0:0).

Table error: Object ID 0, index ID -1, partition ID 0, alloc unit ID 33146494601506880 (type Unknown), page (1:728). Test (IS_OFF (BUF_IOERR, pBUF->bstat)) failed. Values are 12716041 and -10.

Object ID 62537280, index ID 0, partition ID 3948788318208, alloc unit ID 3948788318208 (type In-row data): Page (1:73943) could not be processed. See other errors for details.

Object ID 62537280, index ID 0, partition ID 3948788318208, alloc unit ID 3948788318208 (type In-row data): Page (1:73944) could not be processed. See other errors for details.

Object ID 62537280, index ID 0, partition ID 3948788318208, alloc unit ID 3948788318208 (type In-row data): Page (1:73945) could not be processed. See other errors for details.

Object ID 62537280, index ID 0, partition ID 3948788318208, alloc unit ID 3948788318208 (type In-row data): Page (1:73946) could not be processed. See other errors for details.

Object ID 62537280, index ID 0, partition ID 3948788318208, alloc unit ID 3948788318208 (type In-row data): Page (1:74011) could not be processed. See other errors for details.

Object ID 62537280, index ID 0, partition ID 3948788318208, alloc unit ID 3948788318208 (type In-row data): Page (1:74012) could not be processed. See other errors for details.

Object ID 62537280, index ID 0, partition ID 3948788318208, alloc unit ID 3948788318208 (type In-row data): Page (1:74013) could not be processed. See other errors for details.

CHECKDB found 0 allocation errors and 7 consistency errors not associated with any single object.

CHECKDB found 0 allocation errors and 7 consistency errors in table 'test_200' (object ID 62537280).

CHECKDB found 0 allocation errors and 14 consistency errors in database 'test'.

repair_allow_data_loss is the minimum repair level for the errors found by DBCC CHECKDB (test).". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.