hi, we are using db2 udb v8.1 on 64 bit windows, this message is in
the db2diag.log file
ADM5502W The escalation of "38200" locks on table "xxx.xxx" to lock
intent "X" was successful.
currently i have locklist = 1075, maxlock=60, so based on the formula
(((locks held * 36)/ (locklist *4096)) *100) , i have the answer is
31, compare with maxlock 60, i should still have space for locks to
grow, so why this point the escalation happened? 12 7271
"xixi" <da****@yahoo.com> wrote in message
news:c0**************************@posting.google.c om... hi, we are using db2 udb v8.1 on 64 bit windows, this message is in the db2diag.log file
ADM5502W The escalation of "38200" locks on table "xxx.xxx" to lock intent "X" was successful.
currently i have locklist = 1075, maxlock=60, so based on the formula
(((locks held * 36)/ (locklist *4096)) *100) , i have the answer is 31, compare with maxlock 60, i should still have space for locks to grow, so why this point the escalation happened?
Locks are 56 bytes on 64-bit DB2, not 36. This means that these 38200 locks
are consuming 48.5% of the lock list, not 31%.
(See http://publib.boulder.ibm.com/infoce...n/r0000268.htm)
Lock escalation occurs when the TOTAL number of locks held by ALL
applications exceeds MAXLOCKS percent of the lock list.
While it is true that the 38200 locks held on table xxx.xxx only consume
48.5% of the lock list, these locks combined with all the other locks held
in the system exceeded the 60% threshold (set by MAXLOCKS)
Thus, DB2 chooses the table with the largest number of row locks and
escalates the row locks to table locks, in order to free up lock list.
--
Matt Emmerton
"xixi" <da****@yahoo.com> wrote in message
news:c0**************************@posting.google.c om... hi, we are using db2 udb v8.1 on 64 bit windows, this message is in the db2diag.log file
ADM5502W The escalation of "38200" locks on table "xxx.xxx" to lock intent "X" was successful.
currently i have locklist = 1075, maxlock=60, so based on the formula
(((locks held * 36)/ (locklist *4096)) *100) , i have the answer is 31, compare with maxlock 60, i should still have space for locks to grow, so why this point the escalation happened?
Locks are 56 bytes on 64-bit DB2, not 36. This means that these 38200 locks
are consuming 48.5% of the lock list, not 31%.
(See http://publib.boulder.ibm.com/infoce...n/r0000268.htm)
Lock escalation occurs when the TOTAL number of locks held by ALL
applications exceeds MAXLOCKS percent of the lock list.
While it is true that the 38200 locks held on table xxx.xxx only consume
48.5% of the lock list, these locks combined with all the other locks held
in the system exceeded the 60% threshold (set by MAXLOCKS)
Thus, DB2 chooses the table with the largest number of row locks and
escalates the row locks to table locks, in order to free up lock list.
--
Matt Emmerton
> Lock escalation occurs when the TOTAL number of locks held by ALL applications exceeds MAXLOCKS percent of the lock list. <snip> -- Matt Emmerton
That differs from what the Administration Guide: Performance says:
"When the number of locks held by any one application reaches this
percentage [defined in maxlocks] of the total lock list size, lock
escalation will occur for the locks held by that application. Lock
escalation also occurs if the lock list runs out of space."
> Lock escalation occurs when the TOTAL number of locks held by ALL applications exceeds MAXLOCKS percent of the lock list. <snip> -- Matt Emmerton
That differs from what the Administration Guide: Performance says:
"When the number of locks held by any one application reaches this
percentage [defined in maxlocks] of the total lock list size, lock
escalation will occur for the locks held by that application. Lock
escalation also occurs if the lock list runs out of space."
"Mark A" <ma@switchboard.net> wrote in message
news:rh**************@news.uswest.net... Lock escalation occurs when the TOTAL number of locks held by ALL applications exceeds MAXLOCKS percent of the lock list. <snip> -- Matt Emmerton That differs from what the Administration Guide: Performance says:
"When the number of locks held by any one application reaches this percentage [defined in maxlocks] of the total lock list size, lock escalation will occur for the locks held by that application. Lock escalation also occurs if the lock list runs out of space."
Sorry, my mistake.
--
Matt Emmerton
"Mark A" <ma@switchboard.net> wrote in message
news:rh**************@news.uswest.net... Lock escalation occurs when the TOTAL number of locks held by ALL applications exceeds MAXLOCKS percent of the lock list. <snip> -- Matt Emmerton That differs from what the Administration Guide: Performance says:
"When the number of locks held by any one application reaches this percentage [defined in maxlocks] of the total lock list size, lock escalation will occur for the locks held by that application. Lock escalation also occurs if the lock list runs out of space."
Sorry, my mistake.
--
Matt Emmerton
i agree, and so why the lock escalated?
"Mark A" <ma@switchboard.net> wrote in message news:<rh**************@news.uswest.net>... Lock escalation occurs when the TOTAL number of locks held by ALL applications exceeds MAXLOCKS percent of the lock list. <snip> -- Matt Emmerton That differs from what the Administration Guide: Performance says:
"When the number of locks held by any one application reaches this percentage [defined in maxlocks] of the total lock list size, lock escalation will occur for the locks held by that application. Lock escalation also occurs if the lock list runs out of space."
i agree, and so why the lock escalated?
"Mark A" <ma@switchboard.net> wrote in message news:<rh**************@news.uswest.net>... Lock escalation occurs when the TOTAL number of locks held by ALL applications exceeds MAXLOCKS percent of the lock list. <snip> -- Matt Emmerton That differs from what the Administration Guide: Performance says:
"When the number of locks held by any one application reaches this percentage [defined in maxlocks] of the total lock list size, lock escalation will occur for the locks held by that application. Lock escalation also occurs if the lock list runs out of space."
"xixi" <da****@yahoo.com> wrote in message
news:c0*************************@posting.google.co m... i agree, and so why the lock escalated?
Your application is taking out more locks than you're allowing (per
application or per instance). This may well be related to your other problem
(log space full): both being caused by not committing. Otherwise, increase
the lock list size. In any case (regardless of the explanation), use the DB2
monitor to monitor the lock list usage to see what's happening.
"Mark A" <ma@switchboard.net> wrote in message
news:<rh**************@news.uswest.net>... Lock escalation occurs when the TOTAL number of locks held by ALL applications exceeds MAXLOCKS percent of the lock list. <snip> -- Matt Emmerton That differs from what the Administration Guide: Performance says:
"When the number of locks held by any one application reaches this percentage [defined in maxlocks] of the total lock list size, lock escalation will occur for the locks held by that application. Lock escalation also occurs if the lock list runs out of space."
"xixi" <da****@yahoo.com> wrote in message
news:c0*************************@posting.google.co m... i agree, and so why the lock escalated?
Your application is taking out more locks than you're allowing (per
application or per instance). This may well be related to your other problem
(log space full): both being caused by not committing. Otherwise, increase
the lock list size. In any case (regardless of the explanation), use the DB2
monitor to monitor the lock list usage to see what's happening.
"Mark A" <ma@switchboard.net> wrote in message
news:<rh**************@news.uswest.net>... Lock escalation occurs when the TOTAL number of locks held by ALL applications exceeds MAXLOCKS percent of the lock list. <snip> -- Matt Emmerton That differs from what the Administration Guide: Performance says:
"When the number of locks held by any one application reaches this percentage [defined in maxlocks] of the total lock list size, lock escalation will occur for the locks held by that application. Lock escalation also occurs if the lock list runs out of space."
"Mark A" <ma@switchboard.net> wrote in message
news:<rh**************@news.uswest.net>... Lock escalation occurs when the TOTAL number of locks held by ALL applications exceeds MAXLOCKS percent of the lock list. <snip> -- Matt Emmerton That differs from what the Administration Guide: Performance says:
"When the number of locks held by any one application reaches this percentage [defined in maxlocks] of the total lock list size, lock escalation will occur for the locks held by that application. Lock escalation also occurs if the lock list runs out of space."
"xixi" <da****@yahoo.com> wrote in message
news:c0*************************@posting.google.co m... i agree, and so why the lock escalated?
Because there are other locks held by your application (which aren't listed
in the db2diag.log escalation warning message) which makes the application's
usage of LOCKLIST exceed MAXLOCKS, and therefore DB2 escalates some row
locks to table locks to free up LOCKLIST.
--
Matt Emmerton "Mark A" <ma@switchboard.net> wrote in message
news:<rh**************@news.uswest.net>... Lock escalation occurs when the TOTAL number of locks held by ALL applications exceeds MAXLOCKS percent of the lock list. <snip> -- Matt Emmerton That differs from what the Administration Guide: Performance says:
"When the number of locks held by any one application reaches this percentage [defined in maxlocks] of the total lock list size, lock escalation will occur for the locks held by that application. Lock escalation also occurs if the lock list runs out of space."
"xixi" <da****@yahoo.com> wrote in message
news:c0*************************@posting.google.co m... i agree, and so why the lock escalated?
Because there are other locks held by your application (which aren't listed
in the db2diag.log escalation warning message) which makes the application's
usage of LOCKLIST exceed MAXLOCKS, and therefore DB2 escalates some row
locks to table locks to free up LOCKLIST.
--
Matt Emmerton This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: xixi |
last post by:
i am using db2 v8.1 windows 64 bit with fp3, i check db2diag.log ,
there is message stating
ADM5502W The escalation of "1540" locks on table "xxx.xxx" to lock
intent "X" was successful.
what...
|
by: xixi |
last post by:
hi, we are using db2 udb v8.1 on 64 bit windows, this message is in
the db2diag.log file
ADM5502W The escalation of "38200" locks on table "xxx.xxx" to lock
intent "X" was successful.
...
|
by: Jane |
last post by:
Our db2diag.log is full of messages like this:
2004-05-31-17.15.10.383766 Instance:tminst1 Node:000
PID:394948(db2agent (TMDB1) 0) TID:1 Appid:GA140956.EF26.03A4B1202647
data management ...
|
by: Bruce Pullen |
last post by:
DB2 v7.2 (FP7 - DB2 v7.1.0.68) on AIX 5.2.0.0.
We're seeing unexpected single row (then commit) insert locking
behaviour.
We're seeing Applications that already hold row-level W locks in...
|
by: db2group88 |
last post by:
we are using db2 udb v8.1 on windows, the configure parameter for
locks is locklist 1000, maxlocks 60, but somehow i still have the
error message
ADM5502W The escalation of "1" locks on table...
|
by: Trent |
last post by:
Hello, all.
I have the following production DB2 environment.
DB2 8.1.4 (fp4) WG edition with 2 production databases on Windows 2003
standard edition.
My first question is regard with...
|
by: kavallin |
last post by:
I receives the following in the db2diag.log file many times / day :
2007-03-05-14.55.24.836553+060 E12415C457 LEVEL: Warning
PID : 2785 TID : 1 PROC :...
|
by: stefan.albert |
last post by:
Hi folks,
we have a little discussion about lock escalation...
What is better for performance: To have an escalation "early" (smaller
locklist) or aviod the escalation with a big lock list?
...
|
by: cburnett |
last post by:
Have a peculiar problem regarding lock escalation. Originally lock escalation was occurring because of an application changing most of the rows in a large table. After setting locksize to table to...
|
by: emmanuelkatto |
last post by:
Hi All, I am Emmanuel katto from Uganda. I want to ask what challenges you've faced while migrating a website to cloud.
Please let me know.
Thanks!
Emmanuel
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Hystou |
last post by:
There are some requirements for setting up RAID:
1. The motherboard and BIOS support RAID configuration.
2. The motherboard has 2 or more available SATA protocol SSD/HDD slots (including MSATA, M.2...
|
by: Hystou |
last post by:
Most computers default to English, but sometimes we require a different language, especially when relocating. Forgot to request a specific language before your computer shipped? No problem! You can...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows...
|
by: isladogs |
last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM).
In this session, we are pleased to welcome a new...
| |