|
Problem IT03487
|
Status: Closed |
IN A DPF ENVIRONMENT, THE "DB2GCF -S" COMMAND RETURNS OPERABLE STATE FOR NODE NUMBERS 997-999 WHEN THEY ARE IN AVAILABLE STATE |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All DB2 users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 version 10.1.0.5 *
**************************************************************** |
| Local Fix: |
|
| Solution |
Fixed in DB2 version 10.1.0.5 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 30.07.2014
14.07.2015
14.07.2015 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.5
|
 |
