UDB V8 fp5
Solaris OS...


We are seeing lots and lots of lock escalations in our prod..
There was a crash od DB on last night.. I am thinking it is because of two
many loack escalations..

Any how can you guys give me how to get rid of these lock escalations.?

Please give me a detailed explanation...

Assuming you mean escalation from row lock to table lock:

- Increase locklist db parmameter by a factor of 10.
- Increase maxlocks db parameter to about 60 (percent).

Locklist is the amount of memory allocated to store active locks. When this gets full, escalation occurs. Maxlocks is the percent of the locklist memory that any one application can use before escalation occurs. If 60 does not work, you can increase it more.

Yes, it's about memory usage!

And of course, you can better the situation using PAGE LOCKS instead off row locks. With page locks memory usage is much lower, so escalations occurs no so offen.

But this strategy has drawbacks, too...

Cheers, Bill

each x lock 1st lock uses 512 bytes, othe locks 32 bytes, calculate based on your maxappls .

if your application user maxlock ( % of space used from locklist ) then lock escalations.

either increase locklist ( lock memory) or increase maxlock ( % of lock utilize)



while you getting escalations , get snapshot for DB & lock

db2 get snapshot for database on Dbname > snpdb
no of locks ,how much locklist user , no escalations, time out , based on it increase locklist , or maxlock


db2 get snapshot for locks on DBname > snplck


check which table are escalating

if suspecting any application

get snapshot for lock for application agentid handler



Hope this will help


Let me know , if any questions


Thank You


Lekharaju Ennam

Page locks are not available on DB2 for LUW, only with DB2 for OS/390 and z/OS.