An Event Monitor will only fire on a deadlock, not a lock-wait.
See earlier suggestions.

> -----Original Message-----
> From: pavan
> [mailto:db2udbdba-ezmlmshield-x66774146.[Email address protected]
> Sent: 27 March 2008 17:02
> To: LazyDBA Discussion
> Subject: RE: capturing lock time out in db2
>
> Gurus,
> Any idea about the overhead that the event monitor to detect
> lock timeout could cause on the db2 database ? How to guage this ?
> Thanks.
>
>
> On Thu, March 27, 2008 4:05 pm, Doug Kostelnik wrote:
> > **A LazyDBA.com subscriber has responded to your lazydba.com post**
> > **LazyDBA.com mail shield has forwarded you this email,
> **and removed
> > any attachments, and kept your email address secret **from this
> > person, and any viruses/trojans.
> > **If you reply to this email, the person will see your
> email address
> > as normal **Anything below this line is the original email text
> >
> >
> >
> > You can setup a database event monitor to capture all locking
> > activities to include the lockor, lockee, and the sql that
> executing for both parties.
> >
> >
> > Douglas Kostelnik
> > Senior Database Administrator/Architect
> >
> >
> >
> > -----Original Message-----
> > From: pavan
> > [Email address protected]
> > Sent: Thursday, March 27, 2008 11:51 AM
> > To: LazyDBA Discussion
> > Subject: capturing lock time out in db2
> >
> >
> > All,
> > I understand that we cannot capture lock time out in
> db2diag.log with
> > a diaglevel of 3 and we do not want to pump it to 4.
> >
> > Can we capture in real time basis the details of a lock time out ?
> > What I am looking for is:
> > 1) capturing the tables involved in a lock time out
> > 2) capturing the sqls involved in a lock time out
> > 3) capturing the application that is responsible for the
> lock time out.
> >
> >
> > Please advise me on if you could implement your idea successfully.
> > I did go through lot of documents but nothing really was helpful.
> >
> >
> > Thanks.
> >
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST
> REPLY To post
> > a dba job: http://jobs.lazydba.com To Subscribe :
> > http://www.LazyDBA.com To unsubscribe:
> > http://www.lazydba.com/unsubscribe.html
> >
> >
> >
> >
> >
> ----------------------------------------------------------------------
> > -- The information transmitted is intended only for the
> person(s) or
> > entity to which it is addressed and may contain confidential and or
> > privileged material and should be treated as a confidential
> AAA Auto
> > Club South communication. If the reader of this message is not the
> > intended recipient, you are hereby notified that your access is
> > unauthorized, and any review, dissemination, distribution,
> or copying
> > of this message including any attachments is strictly prohibited.
> >
> ======================================================================
> > ==
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
> ---------------------------------------------------------------------
> TO REPLY TO EVERBODY , PLEASE CLICK REPLY-ALL, NOT JUST REPLY
> To post a dba job: http://jobs.lazydba.com To Subscribe :
> http://www.LazyDBA.com To unsubscribe:
> http://www.lazydba.com/unsubscribe.html
>
>
>
>
>
>
> E-mail message checked by Spyware Doctor (5.5.0.212) Database
> version: 5.09490 http://www.pctools.com/en/spyware-doctor/





E-mail message checked by Spyware Doctor (5.5.0.212)
Database version: 5.09490
http://www.pctools.com/en/spyware-doctor/

DB2 & UDB email list listserv db2-l LazyDBA home page