September 29, 2014 at 9:33 am
Hello All,
CheckDB failed with error about cannot create snapshot.
Looks like CheckDB completed without allocation and consistency errors but got error message about ‘A database snapshot cannot be created because it failed to start.’
Please could someone advise.
Thanks,
David.
----------------------------------------------------------
Msg 1823, Level 16, State 2, Line 1
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.
DBCC results for 'ORSOS_Final'.
DBCC CHECKDB will not check SQL Server catalog or Service Broker consistency because a database snapshot could not be created or because WITH TABLOCK was specified.
DBCC results for 'sys.sysrscols'.
There are 12237 rows in 108 pages for object "sys.sysrscols".
DBCC results for 'sys.sysrowsets'.
There are 1489 rows in 20 pages for object "sys.sysrowsets".
DBCC results for 'sys.sysallocunits'.
There are 1 rows in 1 pages for object "MUNROE.FACILITY".
……
……
……
……
DBCC results for ‘SUPPLIER_GROUP'.
There are 0 rows in 0 pages for object " SUPPLIER_GROUP".
DBCC results for 'FACILITY_PATIENT'.
There are 214099 rows in 1513 pages for object " FACILITY_PATIENT".
DBCC results for 'IFExport'.
There are 0 rows in 0 pages for object " IFExport".
DBCC results for 'SURGEON_DOCUMENTS'.
There are 1 rows in 1 pages for object " SURGEON_DOCUMENTS".
CHECKDB found 0 allocation errors and 0 consistency errors in database 'ORSOS_Final'.
Msg 9001, Level 21, State 1, Line 1
The log for database 'ORSOS_Final' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
Msg 9001, Level 21, State 1, Line 1
The log for database 'ORSOS_Final' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
October 16, 2014 at 5:44 pm
During DBCC CHECKDB, If the database being checked has a heavy update workload, more and more pages are pushed into the database snapshot, causing it to grow.In a situation where the volumes hosting the database don’t have much space, this can mean the hidden database snapshot runs out of space and DBCC CHECKDB stops with an error
Refer these:
http://sqlism.blogspot.com/2014/10/a-database-snapshot-cannot-be-created.html
May 12, 2015 at 7:08 am
In SQL Server, DBCC commands use internal read-only database snapshots. These database snapshots are created on the same drive where the corresponding database data files are located. Database snapshots grow in proportion to the amount of changed data in the database against which the DBCC commands run. If transactional activity continues on this database, the database snapshots that are created by DBCC commands may experience disk space issues. Because the database snapshot files and the actual data files reside on the same disk drive, both sets of files compete for disk space. In this case, application transactions or user transactions are given preference. The internal database snapshot used by DBCC is marked as suspect. Therefore, the DBCC commands experience errors and cannot finish.
Disk Space is one reason why writes to the internal database snapshot may fail. Other reasons such as OS error codes 1450 and 665 can also contribute to similar issues and render the internal database snapshot to a suspect state.
This behavior is by design.
Please refer : https://support.microsoft.com/en-us/kb/926070
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply