DB2PD – Diagnosing an Application Information


As per the memory structure DB2 has setting for minimum connection pool to be maintained on database level. Following is the command to get more information for the applications which are connected to current database.

Using the -apinfo parameter to capture detailed runtime information about the lock owner and the lock waiter

The following sample output was generated under the same conditions as those for Example
 
venus@boson:/home/venus=>db2pd -apinfo 47 -db pdtestDatabase Partition 0 — Database PDTEST — Active — Up 0 days 00:01:30Application :
Address :                0x0780000001676480
AppHandl [nod-index] :   47       [000-00047]
Application PID :        876558
Application Node Name :  boson
IP Address:              n/a
Connection Start Time :  (1197063450)Fri Dec  7 16:37:30 2007
Client User ID :         venus
System Auth ID :         VENUS
Coordinator EDU ID :     5160
Coordinator Partition :  0
Number of Agents :       1
Locks timeout value :    4294967294 seconds
Locks Escalation :       No
Workload ID :            1
Workload Occurrence ID : 2
Trusted Context :        n/a
Connection Trust Type :  non trusted
Role Inherited :         n/a
Application Status :     UOW-Waiting
Application Name :       db2bp
Application ID :         *LOCAL.venus.071207213730  ClientUserID :           n/a
ClientWrkstnName :       n/a
ClientApplName :         n/a
ClientAccntng :          n/aList of inactive statements of current UOW :
UOW-ID :          2
Activity ID :     1
Package Schema :  NULLID
Package Name :    SQLC2G13
Package Version :
Section Number :  203
SQL Type :        Dynamic
Isolation :       CS
Statement Type :  DML, Insert/Update/Delete
Statement :       insert into pdtest values 99venus@boson:/home/venus =>db2pd -apinfo 46 -db pdtest

Database Partition 0 — Database PDTEST — Active — Up 0 days 00:01:39

Application :
Address :                0x0780000000D77A60
AppHandl [nod-index] :   46       [000-00046]
Application PID :        881102
Application Node Name :  boson
IP Address:              n/a
Connection Start Time :  (1197063418)Fri Dec  7 16:36:58 2007
Client User ID :         venus
System Auth ID :         VENUS
Coordinator EDU ID :     5913
Coordinator Partition :  0
Number of Agents :       1
Locks timeout value :    4294967294 seconds
Locks Escalation :       No
Workload ID :            1
Workload Occurrence ID : 1
Trusted Context :        n/a
Connection Trust Type :  non trusted
Role Inherited :         n/a
Application Status :     Lock-wait
Application Name :       db2bp
Application ID :         *LOCAL.venus.071207213658

ClientUserID :           n/a
ClientWrkstnName :       n/a
ClientApplName :         n/a
ClientAccntng :          n/a

List of active statements :
*UOW-ID :          3
Activity ID :     1
Package Schema :  NULLID
Package Name :    SQLC2G13
Package Version :
Section Number :  201
SQL Type :        Dynamic
Isolation :       CS
Statement Type :  DML, Select (blockable)
Statement :       select * from pdtest

More on Database Support, DBAWorkDatabase support, Database services, Oracle ADF

Advertisements

One Response to “DB2PD – Diagnosing an Application Information”

  1. nice blog keep writing

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: