workaround deadlocks

  • Hi,

    in one of our environment , we are using a pre-built software and we have developed our own Apis to work with same database as that pre-built software is using.

    we had many locks and sometimes we need to restart software services. I had traced and optimized many of select statements around and other. those reduced a lot of load and we started seeing very minimal locks. mostly those are not noticeable and I consider them as legitimate locks as RDBMS do that.

    But I still seeing deadlocks randomly. we cannot change code of pre-built solution but our Api. and both update same table/row that is causing collide.

    I am thinking to edit my update proc and add some logic to check if that row is already lock or not. if locked, return code to Api for retry else update. is this do able and what you can suggest to consider as a work around ?

     

    Thanks

     

  • Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

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

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