Database integrity check

  • I have a question about the IntegrityCheck job that I used OLA Hallengren's maintainance solution.

    I see the job failed with error in log:

    Message

    Cannot create file 'E:\MSSQL\DATA\mydb.mdf_MSSQL_DBCC13' because it already exists. Change the file path or the file name, and retry the operation.

    Error: 5170, Severity: 16, State: 1.

    I did some search, it seems when doing DBCC it creates a snapshot of database. Our db is 300 GB.

    And the mydb.mdf_MSSQL_DBCC13 created on the drive is 150 GB.

    I wonder if it failed because the space issue or some other reason?

    Does the snapshot need the same space of the original db, if so that will be a lot.

    How can I fix this error

  • With the error being that the snapshot already exists, it seems like it may be trying the integrity check twice and they overlap.

    Possibly you are specifying the database database more than once either in the script itself or maybe you have more than one integrity check process, job and the database is specified in both. Something along those lines.

    Sue

  • Thanks, I found the reason is because during a week ago job run, there is a windows update reboot server that interupts the DBCC.

    Got fixed

    Thanks,

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply