update statistics error -1073548784

  • Team,

    My MaintenancePlan has failed today with stating the error as

    Executing the query "UPDATE STATISTICS [dbo].[ItemLogitech]

    WITH FULLSCAN" failed with the following error: "A severe error occurred on the current command.

    The results, if any, should be discarded.

    A severe error occurred on the current command. The results, if any, should be discarded.".

    Possible failure reasons: Problems with the query, "ResultSet" property not set correctly,

    parameters not set correctly, or connection not established correctly.

    There are no error msgs in DBCC Checkdb

  • Even I faced similar issue/error

    Check Database integrity on Local server connection

    Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.

    Databases: All databases

    Include indexes

    Task start: 2010-06-27T00:00:15.

    Task end: 2010-06-27T06:39:44.

    Failed:(-1073548784) Executing the query "DBCC CHECKDB WITH NO_INFOMSGS

    " failed with the following error: "A severe error occurred on the current command. The results, if any, should be discarded.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

    We had noticed following timeout errors first time, not sure if it's related to this failure.

    Message

    A time-out occurred while waiting for buffer latch -- type 2, bp 000000041EFF0400, page 1:3264049, stat 0xbc2040d, database id: 10, allocation unit Id: 72057594061324288, task 0x000000000903BC18 : 13, waittime 300, flags 0x100000001a, owning task 0x000000000903BC18. Not continuing to wait.

    In addtion to this we always see below I/O realated messages whenever Optimization/Integrity check job runs

    Message

    SQL Server has encountered 1 occurrence(s) of I/O requests taking longer than 15 seconds to complete on file [H:\ECMDatabase\ManageSoft.mdf:MSSQL_DBCC10] in database [ManageSoft] (10). The OS file handle is 0x000000000000396C. The offset of the latest long I/O is: 0x000000be160000

    Any suggestions?

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

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