|
Problem IC76803
|
Status: Closed |
DB2PD -DB DBNAME -APPLICATION CAN NOT SHOW "DECOUPLED" STATUS |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
db2pd -db dbname -application can not show "Decoupled" status if
connection concentrator is enabled. The connection concentrator
is enabled when the value of max_connections is greater than the
value of max_coordagents.
For example:
"db2 list applications show detail" shows the application's
status is "Decoupled" as below(output is snipped):
DB2INST1 db2bp 15
*LOCAL.db2inst1.110601073057 00001 0 0 0
Decoupled Not Collected
SAMPLE
However, "db2pd -db SAMPLE -appl" shows the same application's
status as "ConnectCompleted" as below, which is wrong.
0x07800000016307A0 15 [000-00015] 0 0
ConnectCompleted 0 0 0 0
*LOCAL.db2inst1.110601073057
0 0 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 on LUW V9.7 users. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 V9.7 Fix Pack 6 or subsequent Fix Packs. *
**************************************************************** |
| Local Fix: |
use "db2 list applications show detail" to query the
application's status in connection concentrator enabled
environment. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 V9.7 Fix Pack 6. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 06.06.2011
25.11.2013
25.11.2013 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
