Post reply

key blocking and resource id is ffffffffffff

  • March 11, 2004 at 6:27 pm

    #101912

    Hi, All

    I run a load testing with 80 user. The system hung. So, I run enterprise manager and using management/Current activity/locks to find the reason why system hung. I found that spid52, spid53, spid54, spid55, spid56,spid57 and spid 58 all wait spid51.

    While spid51 is blocking on key named for eample foo or table bar. the mode is RangeS-S. CAn anyone tell me what that mean and how to solve the problem?

    Also, does anyone know any package of JDBC support timeout on statement level?

     

    Thanks

     

     

  • March 12, 2004 at 4:17 am

    #498465

    BOL and msdn site will explain locks and such like. use dbcc inputbuffer(spid) to see what was run to cause the lock in the first place. If you sort that the other waits should be released.

    [font="Comic Sans MS"]The GrumpyOldDBA[/font]
    www.grumpyolddba.co.uk
    http://sqlblogcasts.com/blogs/grumpyolddba/

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

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