Professional Web Applications Themes

lock escalation - IBM DB2

Removed by Administrator...

  1. Moderated Post

    Default lock escalation

    Removed by Administrator
    xixi Guest
    Moderated Post

  2. Moderated Post

    Default Re: lock escalation

    Removed by Administrator
    Sean Guest
    Moderated Post

  3. Moderated Post

    Default Re: lock escalation

    Removed by Administrator
    Mark Guest
    Moderated Post

  4. #4

    Default Re: lock escalation

    hello,

    our application use auto commit, so i will assume after every update,
    the commit will execute immediately. our concurrencey type is cursor
    stability. so why the lock still escalate? Since the application will
    have update file process, i am afraid this will cause the problem.

    thanks
    xixi Guest

  5. #5

    Default Re: lock escalation

    The commit will be driven _after_ the update completes. During the
    update, more and more locks are taken, until they are escalated to a
    table level lock. Mark explained how to possibly avoid this in his
    previous posting.

    xixi wrote: 

    Sean Guest

  6. #6

    Default Re: lock escalation

    hello,

    sorry i still confuse.

    you said the commit will be driven _after_ the update completes. so
    what does complete means ? our application will do read one row, lock
    the row, then update this rows data, should it be auto commit
    immediately and release the lock? in order to lock the row, the
    concurrency type changes to read stability when read the row. (
    because i need to have row lock when cursor stays on the row, so i set
    the concurrency to read stability, open the sensitive updatable
    resultset with query have where clause where id = xx, there is index
    created on id), but right after update, i set the concurrency type
    back to cursor stability. thanks
    xixi Guest

  7. #7

    Default Re: lock escalation

    this time i have

    ADM5503E The escalation of "875" locks on table "x" to lock
    intent "S" has failed. The SQLCODE is "-911".

    what does it means? i don't see why we have 875 number of locks. when
    i tried o insert a row on this table i get the sql error 911.
    xixi Guest

  8. #8

    Default Re: lock escalation

    It means you couldn't escalate to a table level lock because of a deadlock.

    xixi wrote: 

    Sean Guest

  9. #9

    Default Re: lock escalation

    Until you commit or roll back, your update will hold 1 row lock per row
    updated...transactions can't be finished, and locks can't be released in
    the middle of a statement.

    xixi wrote:
     

    Sean Guest

Similar Threads

  1. How to lock pdf's??
    By Specialty_Pub@adobeforums.com in forum Adobe Acrobat Macintosh
    Replies: 1
    Last Post: November 10th, 08:52 PM
  2. binding v8 client to v7 f10 server escalation questions
    By Alexandre H. Guerra in forum IBM DB2
    Replies: 0
    Last Post: August 26th, 09:32 PM
  3. NUM LOCK
    By Larry in forum Windows XP/2000/ME
    Replies: 3
    Last Post: July 25th, 01:55 PM
  4. Lock out
    By luds in forum Windows Setup, Administration & Security
    Replies: 0
    Last Post: July 24th, 11:42 PM
  5. NO Lock
    By Ray Hinton in forum Windows Setup, Administration & Security
    Replies: 0
    Last Post: July 17th, 01:10 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139