We help IT Professionals succeed at work.

MSSQLServer 2005 msdd

vera2006
vera2006 asked
on
My msdblog.ldf is over 16 GB. I tryed to do a dbcc checkdb and a dbcc checkalloc on the msdb database but I received a latch 3 timeout error,I tryed to do a backup and I received the same latch 3 timeout error. I moved the msdb.mdf and the msdlog.ldf to another disk and tryed to do the same things again but I received the same latch 3 time-out error. I checked my query exection in the Microsoft SQL Server management Studio and the exection time-out is set to 0. I upgrade my service pack 2 to service pack 3 and tryed to do all the above but I still got latch 3 time-out error. I am wondering if someone can please help me solve this problem.
Many thanks in advance. Error code:A database snapshot cannot be created because it failed to start.
Msg 7928, Level 16, State 1, Line 1
The database snapshot for online checks could not be created. Either the reason is given in a previous error or one of the underlying volumes does not support sparse files or alternate streams. Attempting to get exclusive access to run checks offline.
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.
Msg 845, Level 17, State 1, Line 1
Time-out occurred while waiting for buffer latch type 3 for page (1:708), database ID 4.
Comment
Watch Question

Engineering Manager
Commented:
The service is not yet started, you need to start the service first going to this path

Replication Monitor > Agents > Snapshot Agents > Start Agent

then run your steps
Commented:
Please try running the below query:

dbcc checkdb with tablock

(Tablock is used to skip the database snapshot creation while doing checkdb)

If you are still facing any error, please post the same.

Author

Commented:
When I do a dbcc checkdb with tablock on my msdb I received the following error:
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.
Scott PletcherSenior DBA
Most Valuable Expert 2018
Distinguished Expert 2019
Commented:
I'm not sure why do you need to check msdb db, but you should be able to:

Backup msdb;

Restore it to a different name, i.e.:
RESTORE DATABASE mddb_work FROM DISK = '...\msdb.bak'

Then run the CHECKDB on *that* db.

Naturally the table names, object names, object ids, etc., should still be the same.