June 9, 2008 at 9:25 pm
Msg 8967, Level 16, State 216, Line 1
An internal error occurred in DBCC which prevented further processing. Please contact Product Support.
DBCC results for 'pm_cdata_new'.
Msg 8921, Level 16, State 1, Line 1
Check terminated. A failure was detected while collecting facts. Possibly tempdb out of space or a system table is inconsistent. Check previous errors.
CHECKDB found 0 allocation errors and 0 consistency errors in database 'pm_cdata_new'.
Msg 5030, Level 16, State 12, Line 1
The database could not be exclusively locked to perform the operation.
Msg 7926, Level 16, State 1, Line 1
Check statement aborted. The database could not be checked as a database snapshot could not be created and the database or table could not be locked. See Books Online for details of when this behavior is expected and what workarounds exist. Also see previous errors for more details.
June 10, 2008 at 8:06 am
ok - we're already going back/forth on this in email - you're not going to get a different answer here.
You need to use the WITH TABLOCK option. You've got a corruption in the database but you're hitting the bug I documented in my blog - see http://www.sqlskills.com/blogs/paul/2008/05/22/CHECKDBBugThatPeopleAreHittingMsg8967Level16State216.aspxhttp://www.sqlskills.com/blogs/paul/2008/05/22/CHECKDBBugThatPeopleAreHittingMsg8967Level16State216.aspx
If you're getting an error about not being able to lock the database, you'll need to drop all connections to allow CHECKDB to run - it needs an exclusive database lock. Given that you don't see these errors UNLESS you have corruption already, I advise you to do that.
Thanks
Paul Randal
CEO, SQLskills.com: Check out SQLskills online training!
Blog:www.SQLskills.com/blogs/paul Twitter: @PaulRandal
SQL MVP, Microsoft RD, Contributing Editor of TechNet Magazine
Author of DBCC CHECKDB/repair (and other Storage Engine) code of SQL Server 2005
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply