SQLTeam.com | Weblogs | Forums

Master.mdf_mssql_dbcc9 file?


#1

Hi,

Is it okey just to remove the master.mdf_mssql_dbcc9 file? It's stopping dbcc to be run on the master database.

A database snapshot cannot be created because it failed to start. Msg 1823, Level 16, State 8, Server STADSNATSRV003, Line 1 A database snapshot cannot be created because it failed to start. Msg 5170, Level 16, State 1, Server STADSNATSRV003, Line 1 Cannot create file 'D:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf_MSSQL_DBCC9' because it already exists.


#2

Refer the link This may be help you https://support.microsoft.com/en-us/kb/926070

Better to post the error log details. That will help to identify the actual issue


#3

A database snapshot cannot be created because it failed to start. Msg 1823, Level 16, State 8, Server STADSNATSRV003, Line 1 A database snapshot cannot be created because it failed to start. Msg 5170, Level 16, State 1, Server STADSNATSRV003, Line 1 Cannot create file 'D:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\DATA\master.mdf_MSSQL_DBCC9' because it already exists. Change the file path or the file name, and retry the operation. Msg 7928, Level 16, State 1, Server STADSNATSRV003, 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, Server STADSNATSRV003, Line 1 The database could not be exclusively locked to perform the operation. Msg 7926, Level 16, State 1, Server STADSNATSRV003, 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. Outcome: Failed Duration: 00:00:00 Date and time: 2016-03-24 04:00:00 Date and time: 2016-03-24 04:00:00 Database: [model] Status: ONLINE Standby: No Updateability: READ_WRITE User access: MULTI_USER Is accessible: Yes Recovery model: FULL Date and time: 2016-03-24 04:00:00 Command: DBCC CHECKDB ([model]) WITH NO_INFOMSGS, ALL_ERRORMSGS, DATA_PURITY Outcome: Succeeded Duration: 00:00:00 Date and time: 2016-03-24 04:00:00 Date and time: 2016-03-24 04:00:00 Database: [msdb] Status: ONLINE Standby: No Updateability: READ_WRITE User access: MULTI_USER Is accessible: Yes Recovery model: SIMPLE Date and time: 2016-03-24 04:00:00 Command: DBCC CHECKDB ([msdb]) WITH NO_INFOMSGS, ALL_ERRORMSGS, DATA_PURITY Outcome: Succeeded Duration: 00:00:01 Date and time: 2016-03-24 04:00:01 Date and time: 2016-03-24 04:00:01. Process Exit Code 1. The step failed.


#4

DBCC CHECKDB uses hidden snapshot which is taken using NTFS alternate streams.
If that's the case only server restart will help. That's because if you have already existing broken alternate streams the only way to remove it is to restart server. But please check your event log first.
Please go this one to know more why the error occurs in database: http://www.sqlskills.com/blogs/paul/database-snapshots-when-things-go-wrong/