Endpoint Protection

 View Only

  • 1.  Log reports "Transaction deadlocked" in SEPM

    Posted Sep 16, 2013 07:34 AM
    In scm-server-0.log I see a lot of logs like these:
     
    THREAD 73 GRAVE: 
    java.sql.SQLException: Transaction (Process ID 96) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
     
    2013-09-16 13:25:21.336 THREAD 40 GRAVE: Datastore error in: com.sygate.scm.server.task.AgentAVLogCollector
    java.sql.SQLException: Transaction (Process ID 99) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

    What could it be?



  • 2.  RE: Log reports "Transaction deadlocked" in SEPM

    Posted Sep 16, 2013 07:50 AM

    What kind of DB are you running?

    That's essentially saying that the SEPM tried to write something to the DB, but something else was accessing it at the same time, so the SEPM was blocked access.

    Have you got the proper maintenance plans in place?



  • 3.  RE: Log reports "Transaction deadlocked" in SEPM

    Posted Sep 16, 2013 07:57 AM

    SQL Server 2005
    The normal maintenance operations are in place from SEPM (truncate and rebuild) and not from SQL.

    Are there any other logs I can check in order to understand what is happening?



  • 4.  RE: Log reports "Transaction deadlocked" in SEPM

    Posted Sep 16, 2013 07:59 AM

    It;s far easier to troubleshoot deadlocks from the SQL side of things.  The below should get you on your way:

    http://technet.microsoft.com/en-us/library/ms178104(v=sql.105).aspx



  • 5.  RE: Log reports "Transaction deadlocked" in SEPM

    Broadcom Employee
    Posted Sep 16, 2013 12:14 PM

    Hi,

    Thank you for posting in Symantec community.

    Couldy you please cross verify there is no default maintenance scheduled by SQL database.

    Because it's strongly recommended to uncheck database maintenace options if SQL database backup is in place.