PID/TID is process id/thread id. On windows all db2 edus run in a single
process (they're threads).
For deadlocks, have you looked at the deadlock event monitor? It will
report app, statement text, and lock list for each app involved in the
deadlock...you can use a write to table event monitor if you want to
access the data via SQL.
(I don't know the answer to why/what has changed that would cause you
not to see these in the diag.log).
Mike wrote:
Ok, why does the db2 diag log not reporting deadlocks and escalations
any longer? Something I am doing wrong here? Also in the db2diag.log
what is the difference between and TID and a PID. If I try and trace
the application id of process that locked I do not find it. My guess
is that since these programs make a connection and then disconnect
that it is no longer there. In previous versions I thought I remember
where the log actually showed the application name. This would be very
beneficial to have unless someone can tell me a better way of tracking
down a app that is locking by what was or is the PID/TID. Thanks for
any advice,
Mike
Win2k3
db2 8.1 fp 7a
