DB2 FOR LUW / DB2FORLUW / A10 - DB2

In a DPF environment, if there are database partitions with a 
node number in the 997-999 range, then the "db2gcf -s" command 
will erroneously return "Operable" state instead of "Available" 
when the database partition is online. 
 
For example, in the following environment both database 
partitions 0 and 999 are online: 
 
$ db2pd -alldbp - 
 
Database Member 0 -- Active -- Up 0 days 00:41:24 -- Date 
2014-07-28-13.20.38.351215 
 
Database Member 999 -- Active -- Up 0 days 00:41:24 -- Date 
2014-07-28-13.20.38.389945 
 
However, the "db2gcf -s" command when run against database 
partition 999 returns "Operable": 
 
$ db2gcf -s -p 999 -i db2inst 
 
Instance  : db2inst 
DB2 State 
Member 999 :  Operable 
 
If we run the same db2gcf command against database partition 0, 
it returns the correct state(Available): 
 
$ db2gcf -s -p 0 -i db2inst 
 
Instance  : db2inst 
DB2 State 
Member 0 :  Available

**************************************************************** 
* USERS AFFECTED:                                              * 
* All DB2 users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.0.5                              * 
****************************************************************

Fixed in DB2 version 10.1.0.5

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

30.07.2014
14.07.2015
14.07.2015