IT32749: MON_GET_CONNECTION REPORTS SOME METRICS AS 0 FOR APPLICATIONS THAT HAVE ONLY CONNECTED TO A DATABASE BUT STAY IDLE

APAR status

• Closed as program error.

Error description

• MON_GET_CONNECTION reports some metrics as 0 for applications
  that have only connected to a database but stay idle (that
  haven't performed any requests).
  
  For example:In one clp session,  connect to a db and do nothing
  else:
  /db2/pviv001 $ db2 connect to xxxxxxx user xxxxxx
  Enter current password for xxxxxx:
  
     Database Connection Information
  
  Database server        = DB2/AIX64 11.1.4.4
  SQL authorization ID   = SPIZA1
  Local database alias   = PVSS001I
  
  In a separete clp window,  query this connection.
  
  APPLICATION_HANDLE   APPNAME              AUTH_ID   
  CONNECTION_START_TIME      RQSTS_COMPLETED_TOTAL
  TOTAL_CONNECT_REQUESTS TOTAL_CONNECT_REQUEST_TIME
  TOTAL_CONNECT_AUTHENTICATIONS TOTAL_CONNECT_AUTHENTICATION_TIME
  PREV_UOW_STOP_TIME         UOW_START_TIME            
  UOW_STOP_TIME
  -------------------- -------------------- ----------
  -------------------------- ---------------------
  ---------------------- --------------------------
  ----------------------------- ---------------------------------
  -------------------------- --------------------------
  --------------------------
                   411 db2bp                SPIZA1    
  2020-03-06-12.37.34.267951                     0                
  0                          0                             0      
  0 -                          2020-03-06-12.37.33.972853
  2020-03-06-12.37.34.278958
    1 record(s) selected.
  
  In this case RQSTS_COMPLETED_TOTAL, TOTAL_CONNECT_REQUESTS,
  TOTAL_CONNECT_REQUEST_TIME, TOTAL_CONNECT_AUTHENTICATIONS,
  TOTAL_CONNECT_AUTHENTICATION_TIME are reported as zero and only
  get updated when the application issues SQL.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ALL                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to Version 11.1 Fixpack 6                            *
  ****************************************************************
  

Problem conclusion

• Problem first fixed in Version 11.1 Fixpack 6
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  DB2 FOR LUW

• Fixed component ID

  DB2FORLUW

Applicable component levels