LI74635: SNAPSHOT INFO REPORTS A VERY HIGH MAXCOORDAGENTS VALUE.

DB2 Version 9.5 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• Database snapshot can report a very high value for MaxCoord
  agents in the database snapshot as follows:
  
                Database Snapshot
  
  Database name                              = XXXX
  Database path =
  /d/ny001idb00/d1/ibmdb2/nytxt370/nytxt370/NODE0001/SQL00002/
  <snip>
  
  Maximum coordinating agents                = 4294967295
  
  
  In a DPF env following query also reports this behavior.
  
  select dec(DBPARTITIONNUM,3) as DP# ,int(CONNECTIONS_TOP) as
  con_top
  ,dec(COORD_AGENTS_TOP,11) ca_top ,int(AGENTS_TOP) as agt_top
  ,int(TOTAL_CONS) as tot_con_inst_strt ,int(TOTAL_SEC_CONS) as
  tot_sa_con
  ,int(APPLS_CUR_CONS) as active_con ,int(APPLS_IN_DB2) as
  active_ca
  ,int(NUM_ASSOC_AGENTS) as #_sa FROM SYSIBMADM.SNAPDB order by 1
  
  DP# CON_TOP CA_TOP AGT_TOP TOT_CON_INST_STRT TOT_SA_CON
  ACTIVE_CON
  ACTIVE_CA #_SA
  ----- ----------- ------------- ----------- -----------------
  ----------- ----------- ----------- -----------
  1. 300 4294967295. 189 391481 50347 50 5 58
  2. 111 4294967294. 134 327966 316624 21 0 8
  3. 102 4294967295. 99 149553 138207 9 0 8
  4. 91 4294967293. 84 149854 138244 9 0 6
  5. 91 4294967295. 86 149571 138223 9 0 5
  
    5 record(s) selected.
  
  
  This seem to occur after the database is activated and some
  activity has happened against the db.
  

Local fix

Problem summary

• DATABASE SNAPSHOT INFO REPORTS A VERY HIGH MAXCOORDAGENTS VALUE.
  
  ERROR DESCRIPTION:
  
  Database snapshot can report a very high value for MaxCoord
  agents in the database snapshot as follows:
  
                Database Snapshot
  
  Database name                              = XXXX
  Database path =
  /d/ny001idb00/d1/ibmdb2/nytxt370/nytxt370/NODE0001/SQL00002/
  <snip>
  
  Maximum coordinating agents                = 4294967295
  
  
  In a DPF env following query also reports this behavior.
  
  select dec(DBPARTITIONNUM,3) as DP# ,int(CONNECTIONS_TOP) as
  con_top
  ,dec(COORD_AGENTS_TOP,11) ca_top ,int(AGENTS_TOP) as agt_top
  ,int(TOTAL_CONS) as tot_con_inst_strt ,int(TOTAL_SEC_CONS) as
  tot_sa_con
  ,int(APPLS_CUR_CONS) as active_con ,int(APPLS_IN_DB2) as
  active_ca
  ,int(NUM_ASSOC_AGENTS) as #_sa FROM SYSIBMADM.SNAPDB order by 1
  
  DP# CON_TOP CA_TOP AGT_TOP TOT_CON_INST_STRT TOT_SA_CON
  ACTIVE_CON
  ACTIVE_CA #_SA
  ----- ----------- ------------- ----------- -----------------
  ----------- ----------- ----------- -----------
  1. 300 4294967295. 189 391481 50347 50 5 58
  2. 111 4294967294. 134 327966 316624 21 0 8
  3. 102 4294967295. 99 149553 138207 9 0 8
  4. 91 4294967293. 84 149854 138244 9 0 6
  5. 91 4294967295. 86 149571 138223 9 0 5
  
    5 record(s) selected.
  
  
  This seem to occur after the database is activated and some
  activity has happened against the db.
  

Problem conclusion

• First fixed in v9.5 FP5
  Users Affected: ALL
  Defect: wsdbu00550671
  

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:

  IC62070

Fix information

• Fixed component name

  DB2 EDE LINUX

• Fixed component ID

  5724N7604

Applicable component levels

• R950 PSY

     UP