Seems like it's a case of lock escalation!!! Lock escalation is a process where row level locks are replaced with table level lock due to the lack of memory allocated to database parameter LOCKLIST. You might want to look at configuring the LOCKLIST and MAXLOCKS parameter. Refer to admin guide for more information.
Originally posted by mickykt
I have been recieving the particular erro in my db2diag.log file for the last 2 days.
Thanks for the reply.
I have a doubt ,how would this lock only happen to a particular table though many othere tables are used equally.The lock is shown only for one table.
I have increased my locklist parameter and am constanly monitoring the logs.
I also wold be greateful if u could give some guide line for having a good database performance,especially the memory usage.
Kindly check your query execution plan using command center. If it takes a tablescan then create appropriate indexes necessary on the required table. After creating indexes execute runstat command on the table so that the new access plan can be generated.
Sometime if your indexes are corrupted, the access plan does not show so, you will have to judge and drop the index and recreate it again. The damaged indexes also locks the table.