I'm getting entries in the windows event log saying "DB2 is performing
lock escalation" which of course is followed by another entrie saying
"The escalation of 'xxxx' locks on table 'SYSIBM .SYSCOLDIST' to
lock
intent 'X' was successful."
I'm assuming these are just warnings about the database making it's
own adjustments, but I thought I'd be sure before sweeping them under
the carpet. Any advice? (DB2 8 Workgroup Edition)

On Aug 7, 10:44 pm, clilush <bill.shan...@gmail.com> wrote:
> I'm getting entries in the windows event log saying "DB2 is performing
> lock escalation" which of course is followed by another entrie saying
> "The escalation of 'xxxx' locks on table 'SYSIBM .SYSCOLDIST' to
> lock
> intent 'X' was successful."
> I'm assuming these are just warnings about the database making it's
> own adjustments, but I thought I'd be sure before sweeping them under
> the carpet. Any advice? (DB2 8 Workgroup Edition)

To minimize lock escalation, run the following command:

db2 update db cfg using locklist 4096

The make sure all users are disconnected from the database for it to
take effect.

The default of 100 (pages) is way too small for an OLTP database. If
you have a data warehouse, and the locks are read locks (S = share)
then leave it at 100 because lock escalation from row to table level
is actually more efficient since there will not be an contention with
multiple share locks.