Since these events are random and you need to capture the info as they
happens, you will need to investigate using the event monitor function of
DB2.
You can create an event monitor for locks, start it and then let things go
on.
After you have noticed, or after enough time has elapsed, stop the event
monitor and investigate the output to find out.
If you know when they happen then using snapshots or db2pd command will also
give you what you need.
Regards, Pierre.

-----Message d'origine-----
De : pavan [mailto:db2udbdba-ezmlmshield-x23731876.[Email address protected]
Envoyé : 27 mars 2008 11:51
À : LazyDBA Discussion
Objet : 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


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