home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT02782 Status: Closed

"LIST DBPARTITIONNUMS" ONLY RETURNS ONE NODE IN A
MULTI-PARTITIONED DATABASE ENVIRONMENT

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
A partitioned database environment. where everything is working 
fine, but when the "list dbpartitionnums" is issued, only one 
node is listed. 
 
Specifically, in the partitioned database environment, there is 
NODE0001 on a physical machine and NODE0002 on another physical 
machine, and the two nodes are defined in the db2nodes.cfg file. 
 
Originally, one node group was defined and it was defined on 
node 1 only. Using the "list dbpartitinums" command, it only 
returned node 1.  it seems that this returned result is 
incorrect. It is supposed to return both 1 and 2.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 CLP                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2_v97fp10.                                      * 
****************************************************************
Local Fix:
Solution
Problem fixed in db2_v97fp10
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.06.2014
10.11.2014
10.11.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.10 FixList