we are trying to analyze some situation where we have lock-wait and lock-holders. eg 6888 is the lockholder (uow waiting)
if executing get snapshot for this agentid we see the last statement (delete) and we see that 5 statements have been executed since last commit
if using db2pd -d thebrain -apinfo 6888 we do not see any details/history
Database Partition 0 -- Database THEBRAIN -- Active -- Up 39 days 16:43:01 -- Date 2013-04-10-08.43.59.788141
Address : 0x0000000101AE0080
AppHandl [nod-index] : 6888 [000-06888]
TranHdl : 401
Application PID : 0
Application Node Name : alx00044.cbss.inet
IP Address: 10.104.116.64
Connection Start Time : (1365541248)Tue Apr 9 23:00:48 2013
Client User ID : n/a
System Auth ID : ATHEBRAI
Coordinator EDU ID : 10826
Coordinator Partition : 0
Number of Agents : 1
Locks timeout value : NotSet
Locks Escalation : No
Workload ID : 1
Workload Occurrence ID : 7407
Trusted Context : n/a
Connection Trust Type : non trusted
Role Inherited : n/a
Application Status : UOW-Waiting
Application Name : was702:register
Application ID : 10.104.116.64.51233.130409210048
ClientUserID : n/a
ClientWrkstnName : alx00044.cbss.inet
ClientApplName : n/a
ClientAccntng : n/a
according the doc
Displays the detailed information about applications including the execution of dynamic SQL statements of the current unit of work (UOW), if it is applicable. Available in DB2 V9.5 Fix Pack 1.
we are using db2 ese 9.5 fp9 on p/series
is this option only for uow executing and not for uow waiting (although not committed) ?
anyone used this option before ?
Best Regards, Guy Przytula
Database Software Consultant
Good DBAs are not formed in a week or a month. They are created little by little, day by day. Protracted and patient effort is needed to develop good DBAs.
Spoon feeding : To treat (another) in a way that discourages independent thought or action, as by overindulgence.
DB2 UDB LUW Certified V7-V8-V9-V9.7-V10.1-V10.5 DB Admin - Advanced DBA -Dprop..
Information Server Datastage Certified http://www.infocura.be