DBCC CHECKDB HELP

Question

Post reply

DBCC CHECKDB HELP

mgarier

SSC Journeyman

Points: 82
More actions
April 27, 2005 at 9:25 am

#85966

HI DBAs,
i just want to get your view with DBCC CHECKDB...
I am running DBCC CHECKDB WITH FIX OPTION on our DEV Server since monday...and its now about 52 hours and still going. the size of the database is 168gb...based on your experience, does it really takes this long to process this? Can it be measured in terms of hours against 168gb of Database? Is there any other way to fix the integrity error / corruption error in the DB?

Help Please,

mgarier

mgarier

Viewing 8 posts - 1 through 7 (of 7 total)

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

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 1

Your dbcc sounds like to be blocked. Run sp_who2 active to confirm it.

mgarier SSC Journeyman Points: 82 More actions · Answer 2

no one is using the server and the database is on single user mode

mgarier

Allen Cui-55137 SSC Guru Points: 51650 More actions · Answer 3

In this case, you have to wait until it completes, Cancelling the process colud trigger the rollback which may take even longer time.

I wouldn't run dbcc check with repair option, instead, Run dbcc checkdb to find out whether database has integrity issues, If it does, the dbcc checkdb will tell you which objects are in trouble and you can fix them by running dbcc checktable with repair.

mgarier SSC Journeyman Points: 82 More actions · Answer 4

Hi Allen,

Thanks for the tip...I will definitely learn from this experience...

mgarier

Cesar-134342 Ten Centuries Points: 1319 More actions · Answer 5

I had the same problem before, but fortunately, the DB was separated in several filegroups. So we ran the DBCC CHECKFILEGROUP on each of them separately, and time them to have an idea for how long it will run for the biggest ones.

If you fear corruption, you can run individual CHECKTABLE statements; painful and time-consuming, but can work to streamline your process.

Also check the size and growth size of TempDB. You will need a lot of space on it for this function, specially for big DB.

mgarier SSC Journeyman Points: 82 More actions · Answer 6

Yeah...Its really time consuming and very painfull...I have 2 servers that have the same error...I will really really be carefull with this on now...

Thanks for the shout.

Cheers

mgarier

mgarier SSC Journeyman Points: 82 More actions · Answer 7

Hi DBAs,

My DBCC CHECKDB finished for about 93 hours...(ouchhhhh...)

and it gave me this kind of report...any idea how to fix this

DBCC results for 'tblCameoUKGroupDescriptions'.

Server: Msg 8928, Level 16, State 1, Line 1

Object ID 394484484, index ID 5: Page (1:881467) could not be processed. See other errors for details.

Server: Msg 8976, Level 16, State 1, Line 1

Table error: Object ID 394484484, index ID 5. Page (1:881467) was not seen in the scan although its parent (1:881369) and previous (1:881466) refer to it. Check any previous errors.

Server: Msg 8978, Level 16, State 1, Line 1

Table error: Object ID 394484484, index ID 5. Page (1:881468) is missing a reference from previous page (1:881467). Possible chain linkage problem.

Server: Msg 8928, Level 16, State 1, Line 1

Object ID 394484484, index ID 6: Page (1:547756) could not be processed. See other errors for details.

Server: Msg 8976, Level 16, State 1, Line 1

Table error: Object ID 394484484, index ID 6. Page (1:547756) was not seen in the scan although its parent (1:545059) and previous (1:547755) refer to it. Check any previous errors.

There are 10 rows in 1 pages for object 'tblCameoUKGroupDescriptions'.

DBCC results for 'tblPRFSRByDistrictAndCameoFinancialONLY'.

There are 24 rows in 1 pages for object 'tblPRFSRByDistrictAndCameoFinancialONLY'.

DBCC results for 'tblPRFSRByDistrictAndBandONLY'.

There are 23 rows in 1 pages for object 'tblPRFSRByDistrictAndBandONLY'.

DBCC results for 'tblCameoFinancialGroupDescriptions'.

There are 7 rows in 1 pages for object 'tblCameoFinancialGroupDescriptions'.

DBCC results for 'tblEditStatus'.

There are 7 rows in 1 pages for object 'tblEditStatus'.

DBCC results for 'tblEurodirect'.

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

mgarier