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 IC98108 Status: Geschlossen

DB2PD -DBP NUMBER -EVERYTHING RETURNED "INVALID -DBP SUBOPTION.
PROVIDE DATABASE PARTITION NUMBER."

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
db2pd -dbp number -everything returned "Invalid -dbp suboption. 
Provide database partition number." 
 
For example: 
db2pd -dbp xx -everything 
Invalid -dbp suboption.  Provide database member number. 
... snip ... 
Database Member XXX -- Database SAMPLE -- Active -- 
 
Displayed Database member is not correct.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB version 10.1 fixpack 4.                   * 
****************************************************************
Local-Fix:
use  command   "db2pd -everything -dbp < partitionNumber >  " 
instead of  "db2pd -dbp <partitionNumber> -everything".
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in DB2 UDB Version 10.1 fix pack 4.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.12.2013
02.06.2014
02.06.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.4 FixList