Post reply

History cleanup job in Maintainance plan fails persistently

  • May 27, 2009 at 4:24 am

    #131537

    Hi Guys,

    I facing an frequent error in SQL server 2005 Maintainance Plan where history cleanup job fails with below mentioned error :

    Executing the query "EXECUTE msdb..sp_maintplan_delete_log null,null,'2009-05-13T00:00:11'

    " failed with the following error: "Transaction (Process ID 63) was deadlocked on lock resources

    with another process and has been chosen as the deadlock victim.

    Rerun the transaction.". Possible failure reasons: Problems with the query,

    "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.

    I have searched a lot on this but didnt got any specific solution.

    Any idea how to resolve this issue...?

    Thanks in Advance

    Regards,

    Vishal.....:-)

  • June 1, 2009 at 7:13 am

    #1002734

    This message is telling you that two process were trying to access the same data at the same time: look up "deadlock". The job cannot complete while other people or processes are accessing the data at the same time.

  • June 1, 2009 at 7:46 am

    #1002762

    Hello,

    Here is a decent article on tracking down the causes of Deadlocks:-

    http://www.simple-talk.com/sql/learn-sql-server/how-to-track-down-deadlocks-using-sql-server-2005-profiler/

    The good news for you is you know when the Deadlocks usually happen and therefore when to profile.

    Regards,

    John Marsh

    www.sql.lu
    SQL Server Luxembourg User Group

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

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