none
DBCC CHECKDB Internal database snapshot has split point LSN

    Question


  • The integrity check of my databases is showing failure.  Each and every database has this message foungd in the sql log.
    >>
    DBCC CHECKDB <database> WITH no_infomsgs executed by <user> found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.  Internal database snapshot has split point LSN = 000000de:000001d5:0001 and first LSN = 000000de:000001d4:0001.  This is an informational message only. No user action is required.
    >>

    The message is saying no errors and no action required, but the step fails in my maintenance plan.

    I ran 'dbcc checkdb' on each database and all show:
    >>
    CHECKDB found 0 allocation errors and 0 consistency errors in database <database name>.
    <<

    I have restarted the sql server instance and the server, but it made no difference.  I ran chkdsk afianst drives - ok.

    SQL server is Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)   Apr  2 2010 15:48:46   Copyright (c) Microsoft Corporation  Standard Edition (64-bit) on Windows NT 6.0 <X64> (Build 6002: Service Pack 2) (Hypervisor) .

    Server is a Virtual Machine.

    No updates to server recently.  Only thing different yesterday was ... that I was working with Reporting Services on the server yesterday.

    So, why does Integrity check fail if no errors indicated.  Is this in fact something to worry about?

    Any assistance woulb be appreciated.

    Tuesday, July 12, 2011 7:19 PM

Answers

  • Hi,

    Can you find an OS 665 error - The requested operation could bit be completed due to a file system limitation? If so, it is probably due to that there is not enough free space on the disk drive where data file resides. When executing a DBCC command, a read-only snapshot will be created in the same disk drive where corresponding database files are located. If you have current data changes in the database, that snapshot will grow which may experience disk space issue in return. 

    The following KB article states the same error message, http://support.microsoft.com/kb/926070.


    Best Regards
    Alex Feng | Forum Support

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Wednesday, July 13, 2011 6:53 AM

All replies

  • Hi,

    Can you find an OS 665 error - The requested operation could bit be completed due to a file system limitation? If so, it is probably due to that there is not enough free space on the disk drive where data file resides. When executing a DBCC command, a read-only snapshot will be created in the same disk drive where corresponding database files are located. If you have current data changes in the database, that snapshot will grow which may experience disk space issue in return. 

    The following KB article states the same error message, http://support.microsoft.com/kb/926070.


    Best Regards
    Alex Feng | Forum Support

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
    Wednesday, July 13, 2011 6:53 AM
  • It is normal behavior. I can not see anything unusual.
    SQL Server every time generates a snapshot to perform DBCC CHECKDB and the second portion of data from this message relates to snapshot split point because SQL Sever should recover the snapshot at an exact LSN.

    Wednesday, July 11, 2012 3:14 AM