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

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

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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".
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem was first fixed in DB2 UDB Version 10.1 fix pack 4.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.12.2013
02.06.2014
02.06.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList