Database Maintenance Plan fails at SSB Check

  • I have a maintenance plan created with the wizard that includes Check Database Integrity as one of the tasks. When this plan executes, the activity monitor indicates that the command DBCC SSB CHECK is in a suspended status with a Wait Type of PAGEIOLATCH_EX. I have let this run for as long a 36 hours, but it will never advance. When I kill that process, the rest of the task seems to run. The log however, indicates that the Task Check Database Integrity failed with the following error."A severe error occured on the current command......Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

    Any ideas on what is causing this and how to cure it?

  • Can you run CheckDB manually on that database?

    DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

    The 'severe error on the current command' is likely because you killed the connection.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • I am able to do a DBCC CheckDB with Physical_Only.

    I did not intentionally cross post. After I had posted in the Admin forum, I thought I should have posted in the Backup forum. My Bad

  • psturn 72558 (3/19/2010)


    I am able to do a DBCC CheckDB with Physical_Only.

    Do you get an error message when trying to perform the

    DBCC Checkdb WITH NO_INFOMSGS

    command that Gail requested?

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • I am trying that now.

  • I'm having this problem too. Was there a solution to this post?

    I issued the Command, DBCC CHECKDB MYDB WITH NO_INFOMSGS.

    It shows up as SUSPENDED and PAGEIOLATCH_EX. It has been in this state for over 16 hours with no end in sight.

    I want to kill it but am concerned about the fallout from doing so.

    Please Help.

Viewing 6 posts - 1 through 6 (of 6 total)

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