Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Paulo Rafael Padilla Velazquez asked how to monitor a table where deadlocks occur. Ravi Vijay pointed to sysmaster tables sysprofile, syssesprof and sysptprof and an article. Mike Magie said to find the table's partnum with oncheck -pt and run onstat -g ppf for that partnum, reading the dlk column. Paulo thanked them.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hi,
Is it possible to monitor a table where dead lock is occurring?
thanks in advance
↪ replying to PAULO RAFAEL PADILLA VELAZQUEZ
ravi vijay — — source: IIUG Forums & Mailing Lists
Hi
Other than onstat -p output, these are some of the sysmaster table that
provides the additional information regarding the locks/deadlocks:
- *sysprofile*: Contains the total number of deadlocks detected which
corresponds to the deadlks column in the *onstat -p* command output
- *syssesprof*: Contains the number of deadlocks detected per individual
database session
- *sysptprof: Contains the number of deadlocks detected per individual
table*
This article could be of help to you regarding monitoring deadlock
situations:
http://www.ibm.com/developerworks/db2/library/techarticle/dm-0701herber/index.ht
ml
Thanks
Ravi
On 6/20/08, PAULO RAFAEL PADILLA VELAZQUEZ <rafaelpadilla@grupomayan.com>
wrote:
>
> Hi,
>
> Is it possible to monitor a table where dead lock is occurring?
>
> thanks in advance
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
↪ replying to PAULO RAFAEL PADILLA VELAZQUEZ
MIKE MAGIE — — source: IIUG Forums & Mailing Lists
You can run onstat -g ppf <partnum> to determine the deadlocks for the
specific table. Locate the partum in a # of ways but an easy one is just run
oncheck -pt <database>:<table> and look for:
Partition partnum 49283138
Partition lockid 49283138
If they both match it is a non-fragged table - run onstat -g ppf 49283138 and
look at the dlk column. If the partnums do not match the table is fragged, but
you will see all of the frags partnumbers in the oncheck output. If the tabls
is fragged there will be an easier solution than this one, but if not, this
one works.
MM
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.