|
Problem IC62070
|
Status: Closed |
SNAPSHOT INFO REPORTS A VERY HIGH MAXCOORDAGENTS VALUE. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem 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 Summary: |
DATABASE SNAPSHOT INFO REPORTS A VERY HIGH MAXCOORDAGENTS VALUE.
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: |
|
| available fix packs: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in v9.7 FP1 |
| Workaround |
n/a |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.07.2009
04.02.2010
04.02.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP1
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.1
|
 |
