home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT02782 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 CLP                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2_v97fp10.                                      * 
****************************************************************
Local-Fix:
Lösung
Problem fixed in db2_v97fp10
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
25.06.2014
10.11.2014
10.11.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
9.7.0.10 FixList