I have a DB2 UDB database on an AIX UNIX machine. I would like to know
the queries running against certain tables. There are some applications
outside of the database that do read and update these tables. Some have
incorrect isolation levels that end up locking the tables. How can I
find out what queries are running against a table, and how can I kill
them. This is a development environment and I would hate to bother the
DBA to fix these things. Sometime back the DBA has mentioned to me that
he will give the users access to see these things. I just didnt know
how.
Appreciate your help.
Thanks.
Jay

Jay wrote:
> I have a DB2 UDB database on an AIX UNIX machine. I would like to know
> the queries running against certain tables. There are some applications
> outside of the database that do read and update these tables. Some have
> incorrect isolation levels that end up locking the tables. How can I
> find out what queries are running against a table, and how can I kill
> them. This is a development environment and I would hate to bother the
> DBA to fix these things. Sometime back the DBA has mentioned to me that
> he will give the users access to see these things. I just didnt know
> how.
HE must have been talking about giving you SYSMON privileges so you can
use snapshot table functions.
The easiest way. The easiest way to find out which query goes against
which table is to dump the statement cache and grep for the table names.
You can perform more elaborate schemes. But I'd start there.

Cheers
Serge

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

IOD Conference
http://www.ibm.com/software/data/ond...ness/conf2006/

"Serge Rielau" <srielau@ca.ibm.com> wrote in message
news:4nr28iFbm163U3@individual.net...
> HE must have been talking about giving you SYSMON privileges so you can
> use snapshot table functions.
> The easiest way. The easiest way to find out which query goes against
> which table is to dump the statement cache and grep for the table names.
> You can perform more elaborate schemes. But I'd start there.
>
> Cheers
> Serge
>
> --
> Serge Rielau
> DB2 Solutions Development
> IBM Toronto Lab

I don't believe that you can kill (force) any offending applications with
SYSMON authority.

Mark A wrote:
> "Serge Rielau" <srielau@ca.ibm.com> wrote in message
> news:4nr28iFbm163U3@individual.net...
>> HE must have been talking about giving you SYSMON privileges so you can
>> use snapshot table functions.
>> The easiest way. The easiest way to find out which query goes against
>> which table is to dump the statement cache and grep for the table names.
>> You can perform more elaborate schemes. But I'd start there.
>>
>> Cheers
>> Serge
>>
>> --
>> Serge Rielau
>> DB2 Solutions Development
>> IBM Toronto Lab
>
> I don't believe that you can kill (force) any offending applications with
> SYSMON authority.
>
>
No. But you got to find'em first.

--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab

IOD Conference
http://www.ibm.com/software/data/ond...ness/conf2006/

How would I do that in unix. I mean what is the command to run at the
unix prompt.
Thanks.

Mark A wrote:
> "Serge Rielau" <srielau@ca.ibm.com> wrote in message
> news:4nr28iFbm163U3@individual.net...
> > HE must have been talking about giving you SYSMON privileges so you can
> > use snapshot table functions.
> > The easiest way. The easiest way to find out which query goes against
> > which table is to dump the statement cache and grep for the table names.
> > You can perform more elaborate schemes. But I'd start there.
> >
> > Cheers
> > Serge
> >
> > --
> > Serge Rielau
> > DB2 Solutions Development
> > IBM Toronto Lab
>
> I don't believe that you can kill (force) any offending applications with
> SYSMON authority.