Maintenance plan for database integrity check is not working for all the databases

  • Hello,

    I have created a maintenance plan task database Intigrity for all databases in sql server 2005 EE and scheduled to run at 9:00pm weekly

    But in the error log I can see DBCC CHECKDB for only system databases master and mssqlsystemresource many times but not the other databases.

    from the error log:

    DBCC CHECKDB (master) WITH no_infomsgs executed by abc\sqlservice found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 34 seconds.

    2008-12-28 21:00:53.21 spid79 DBCC CHECKDB (mssqlsystemresource) WITH no_infomsgs executed by abc\sqlservice found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.

    2008-12-28 21:00:53.79 spid58 DBCC CHECKDB (master) WITH no_infomsgs executed by abc\sqlservice found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.

    2008-12-28 21:00:54.49 spid58 DBCC CHECKDB (mssqlsystemresource) WITH no_infomsgs executed by abc\sqlservice found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.

    2008-12-28 21:00:54.99 spid58 DBCC CHECKDB (master) WITH no_infomsgs executed by abc\sqlservice found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.

    2008-12-28 21:00:55.60 spid58 DBCC CHECKDB (mssqlsystemresource) WITH no_infomsgs executed by CIGINSURANCE\sqlservice found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.

    2008-12-28 21:00:56.08 spid58 DBCC CHECKDB (master) WITH no_infomsgs executed by abc\sqlservice found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.

    2008-12-28 21:00:56.66 spid58 DBCC CHECKDB (mssqlsystemresource) WITH no_infomsgs executed by abc\sqlservice found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.

    2008-12-28 21:00:57.13 spid58 DBCC CHECKDB (master) WITH no_infomsgs executed by abc\sqlservice found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.

    DBCC CHECKDB (mssqlsystemresource) WITH no_infomsgs executed by ABC\sqlservice found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 0 seconds.

    So Iam confused where Iam going wrong? please advice me

  • What version are you running? There was a version released that had this bug - and you are going to need to upgrade to solve the problem.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • Just an add on, build 3152 has got the problem described here. You would need to upgrade to at least 3159.

  • Thank you..

    We have SQL Server 2005 EE x64 with SP2 installed....So this configuration still We have any concern with maintenance plan as I explained in my case...

    Thanks for your help

  • Can you run SELECT @@VERSION and find out what version you have?

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • thanks,

    Select @@version

    Microsoft SQL Server 2005 - 9.00.3042.00 (X64)

    Feb 10 2007 00:59:02

    Copyright (c) 1988-2005 Microsoft Corporation

    Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)

  • This looks like the original SP2 release - which had several problems. I would recommend upgrading to at least 9.0.3054 (at a minimum). Ideally, if you can apply the latest cumulative update that would be best.

    Jeffrey Williams
    “We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

    ― Charles R. Swindoll

    How to post questions to get better answers faster
    Managing Transaction Logs

  • Me too help Please.

    All of a sudden the check database integrit task in maintenance plan started failing on one of our Sql servers:

    Microsoft SQL Sql Server 2005- 9.00.4053.00

    Some of my reseach shows that others have had the same issue.

    CheckDBCC works fine when run as a query.

    Others have noted that this might be because the allow updates was reset to off (1)

    I checked and mine is set to on (default = 0)

    Others also have said that this might be because affinity I/O mask, affinity mask were turned off (1)

    Both of these values are on (0).

    Another box with the same build works fine. The only server configuration that differ between the boxes is that the working boxes is that the clr enabled property is off (default) I have a hard time believing this should have anything to do with it.

    The job and history logs are of no help.

    Please help

Viewing 8 posts - 1 through 7 (of 7 total)

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