DB2 FOR LUW / DB2FORLUW / A10 - DB2

When using a command like this: 
 
db2pd -db <dbname> -apinfo -active 
 
... it is possible that the "EntryTime" for a statement is shown 
to happen before the "Connection Start Time".    This can cause 
the timing information to be inaccurate. 
 
For example: 
 
Database Partition 0 -- Database SAMPLE -- Active -- Up 221 days 
21:25:24 -- Date 2015-01-05-12.06.56.179853 
 
Application : 
  Address :                0x0780000000FB6E00 
  AppHandl [nod-index] :   9626     [000-09626] 
  TranHdl :                19 
  Application PID :        6619242 
  Application Node Name :  db2inst1 
 
  IP Address:              n/a 
 
  Connection Start Time :  (1420477540)Mon Jan  5 12:05:40 2015 
  Client User ID :         db2admin 
  System Auth ID :         DB2ADMIN 
  Coordinator EDU ID :     15986 
  Coordinator Partition :  0 
  Number of Agents :       1 
  Locks timeout value :    NotSet 
  Locks Escalation :       No 
  Workload ID :            1 
  Workload Occurrence ID : 76220 
  Trusted Context :        n/a 
  Connection Trust Type :  non trusted 
  Role Inherited :         n/a 
  Application Status :     UOW-Executing 
  Application Name :       db2bp 
  Application ID :         *LOCAL.db2inst1.150105170540 
 
  ClientUserID :           n/a 
  ClientWrkstnName :       n/a 
  ClientApplName :         n/a 
  ClientAccntng :          n/a 
 
Database Partition 0 -- Database SAMPLE -- Active -- Up 221 days 
21:25:24 -- Date 2015-01-05-12.06.56.189133 
 
Active Statement List: 
Address            AppHandl [nod-index] UOW-ID     StmtID 
AnchID StmtUID    EffISO      EffLockTOut EffDegree   EntryTime 
StartTime           LastRefTime 
0x070000004B2B44A0 9626     [000-09626] 1          1 
199    785        1           45          0           Mon Jan  5 
12:05:31 Mon Jan  5 12:05:31 Mon Jan  5 12:05:31 
 
 
The EntryTime (and StartTime) are showing 12:05:31, yet the 
connection start time for this application was 9 seconds later 
at 12:05:40.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1, Fixpack 5                       * 
****************************************************************

This problem is more likley to happen the longer the DB2 
instance has been up.   Recycling the DB2 instance 
(db2stop/db2start) on a regular basis (example every 30 days) 
would help alleviate this type of problem from occurring.

First fixed in DB2 Version 10.1, Fixpack 5

see Local Fix

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

27.03.2015
14.07.2015
14.07.2015