Hello,

I have a user who regularly runs a query which blocks a lot of other
queries. The query is initiated from SSIS (SQL Server Integration
Services) on another host. The DB2 instance is version 8.1.

According to the user, the query doesn't perform any DROP TABLE/CREATE
TABLE/... DDL-like actions. But it seems to perform a RUNSTATS at the
time when I'm called for help.

At http://troels.arvin.dk/db/db2/locking/systables/ there's information
about the query blocking work for several others. The lock which seems to
cause trouble is this one:

Lock Name = 0x00000002000000000000000054
Lock Attributes = 0x00000002
Release Flags = 0xC0000000
Lock Count = 255
Hold Count = 0
Lock Object Name = 2
Object Type = Table
Tablespace Name = SYSCATSPACE
Table Schema = SYSIBM
Table Name = SYSTABLES
Mode = X

How to proceed? Is it RUNSTATS which locks SYSIBM.SYSTABLES? - If so: Is
there a way to decrease catalog locking in particular cases, and/or in
general?

--
Regards,
Troels Arvin <troels@arvin.dk>
http://troels.arvin.dk/