deadlock

I am running IDS version 9.21.HC4XM on HP_UX B.11.00 Based on onstat -p, there were 2 deadlocks detected: bufwaits lokwaits lockreqs deadlks dltouts ckpwaits compress seqscans 4922980 3521 946949636 2 0 528 231735 368007 I want to find out more about these deadlocks. Does Informix keep a history of deadlocks? Is there a way to find out the following: when a deadlock occured, who involved in the deadlock, who the victim was, what db resources involved in the deadlock? Any information would be appreciated. Thanks! henny

As far as I know, you're out of luck unless perhaps your application is nice enough to record such information for you. Even if it does, there's no good way to determine what process it was deadlocking with - the "winner" never even realizes there was a problem. It would be nice if it did though - that way I wouldn't have to endure hearing someone tell me that a process is deadlocking against itself. ----- Original Message ----- From: <hwinarsoo@verizongni.com> To: <ids@iiug.org> Sent: Thursday, June 12, 2003 3:56 PM Subject: deadlock [1351] > I am running IDS version 9.21.HC4XM on HP_UX B.11.00 > > Based on onstat -p, there were 2 deadlocks detected: > bufwaits lokwaits lockreqs deadlks dltouts ckpwaits compress seqscans > 4922980 3521 946949636 2 0 528 231735 368007 > > I want to find out more about these deadlocks. Does Informix keep a > history of deadlocks? Is there a way to find out the following: > when a deadlock occured, > who involved in the deadlock, > who the victim was, > what db resources involved in the deadlock? > > > Any information would be appreciated. > Thanks! > > henny > > >

Hi You can figure out the deadlock using onstat -g ppfand then look for the records where dlks is more than 0 and then identify the tables involved using sysmaster database. I mean take the partnumber out from that dlk records and run this query against sysmaster databases select dbsname, tabname from systbnames where hex(partnum) matches "*partnum*"which will give you the datbase and table name where deadlocks are happening. As far as the timings are concerned, you need to try to collect the statistics for every hour and doing onstat -z to zero the statistics to see when it ishappening exactly. Hope this helps. Thanks, Vineet --- Danny Wright <dwright@sherwoodfoods.com> wrote: > As far as I know, you're out of luck unless perhaps > your application is nice > enough to record such information for you. > > Even if it does, there's no good way to determine > what process it was > deadlocking with - the "winner" never even realizes > there was a problem. > > It would be nice if it did though - that way I > wouldn't have to endure > hearing someone tell me that a process is > deadlocking against itself. > > ----- Original Message ----- > From: <hwinarsoo@verizongni.com> > To: <ids@iiug.org> > Sent: Thursday, June 12, 2003 3:56 PM > Subject: deadlock [1351] > > > > I am running IDS version 9.21.HC4XM on HP_UX > B.11.00 > > > > Based on onstat -p, there were 2 deadlocks > detected: > > bufwaits lokwaits lockreqs deadlks dltouts > ckpwaits compress seqscans > > 4922980 3521 946949636 2 0 528 > 231735 368007 > > > > I want to find out more about these deadlocks. > Does Informix keep a > > history of deadlocks? Is there a way to find out > the following: > > when a deadlock occured, > > who involved in the deadlock, > > who the victim was, > > what db resources involved in the deadlock? > > > > > > Any information would be appreciated. > > Thanks! > > > > henny > > > > > > > > __________________________________ Do you Yahoo!? Yahoo! Calendar - Free online calendar with sync to Outlook(TM). http://calendar.yahoo.com

--- Vineet Mehrotra <vin_us@yahoo.com> wrote: > Hi You can figure out the deadlock using > onstat -g ppf> and then look for the records where dlks is more > than > 0 and then identify the tables involved using > sysmaster database. I mean take the partnumber out > from that dlk records > and run this query against sysmaster databases > select dbsname, tabname from systbnames > where hex(partnum) matches "*partnum*"> which will give you the datbase and table name where > deadlocks are happening. > > As far as the timings are concerned, you need to try > to collect the statistics for every hour and doing > onstat -z to zero the statistics to see when it is> happening exactly. > > Hope this helps. > > Thanks, > > Vineet > --- Danny Wright <dwright@sherwoodfoods.com> wrote: > > As far as I know, you're out of luck unless > perhaps > > your application is nice > > enough to record such information for you. > > > > Even if it does, there's no good way to determine > > what process it was > > deadlocking with - the "winner" never even > realizes > > there was a problem. > > > > It would be nice if it did though - that way I > > wouldn't have to endure > > hearing someone tell me that a process is > > deadlocking against itself. > > > > ----- Original Message ----- > > From: <hwinarsoo@verizongni.com> > > To: <ids@iiug.org> > > Sent: Thursday, June 12, 2003 3:56 PM > > Subject: deadlock [1351] > > > > > > > I am running IDS version 9.21.HC4XM on HP_UX > > B.11.00 > > > > > > Based on onstat -p, there were 2 deadlocks > > detected: > > > bufwaits lokwaits lockreqs deadlks dltouts > > ckpwaits compress seqscans > > > 4922980 3521 946949636 2 0 > 528 > > 231735 368007 > > > > > > I want to find out more about these deadlocks. > > Does Informix keep a > > > history of deadlocks? Is there a way to find > out > > the following: > > > when a deadlock occured, > > > who involved in the deadlock, > > > who the victim was, > > > what db resources involved in the deadlock? > > > > > > > > > Any information would be appreciated. > > > Thanks! > > > > > > henny > > > > > > > > > > > > > > > > __________________________________ > Do you Yahoo!? > Yahoo! Calendar - Free online calendar with sync to > Outlook(TM). > http://calendar.yahoo.com > __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com