DB2 FOR LUW / DB2FORLUW / A50 - DB2

The 'db2gcf -s -i <instance-name> -p <part-number>' command 
reports that the partition is 'Operable' regardless of the 
actual state of the partition in the case where the default 
partition is stopped. The default partition number value is zero 
or the value of the DB2NODE environment variable if set. 
 
The following scenario illustrates this problem. 
 
1. Create a DPF instance with two database partitions. 
$ cat db2nodes.cfg 
0 hostname 0 
1 hostname 1 
 
2. Start the instance, then stop the default partition (0). 
$ db2start 
04/15/2013 11:16:30     1   0   SQL1063N  DB2START processing 
was successful. 
04/15/2013 11:16:31     0   0   SQL1063N  DB2START processing 
was successful. 
SQL1063N  DB2START processing was successful. 
 
$ db2gcf -d -i db2inst1 -p 0 
Instance  : db2inst1 
DB2 Stop : Success 
Member 0 : Success 
 
3. Run db2gcf -s to see the status of the partitions. 
$ db2gcf -s -i db2inst1 -p 0,1 
Instance  : db2inst1 
DB2 State 
Member 0 :  Operable 
Member 1 :  Operable 
 
The results should be: 
Instance  : db2inst1 
DB2 State 
Member 0 :  Operable 
Member 1 :  Available

**************************************************************** 
* USERS AFFECTED:                                              * 
* Users who use db2gcf in Linux and Unix platforms.            * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Please upgrade to DB2 V10.5 FixPack 3 or later.              * 
****************************************************************

N/A

DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

This problem was first fixed in DB2 V10.5 FixPack 3.

keiner bekannt / siehe Local-Fix

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

27.08.2013
24.03.2014
24.03.2014