DB2 FOR LUW / DB2FORLUW / B10 - DB2

The problem happens on DPF environments. In order to hit this
problem, user has to introduce gap in the storage group file.
Way to introduce gap is deletion of entry from the middle of the
file:

$ db2 "CREATE STOGROUP HIGHEND1 ON '$HOME'"
$ db2 "CREATE STOGROUP HIGHEND2 ON '$HOME'"
$ db2 "DROP STOGROUP HIGHEND1"

After commands above, the storage group file does not contain
valid entry for storage group HIGHEND1. Next, once user tries to
add partition it fails:

$ db2start dbpartitionnum 2 add dbpartitionnum HOSTNAME db2debug
port 2 without tablespaces

01/23/2017 11:08:15     2   0   SQL1483N  Add database partition
server  processing for database partition server "2" failed.
Information returned for the error includes SQLCODE "-902",
SQLSTATE "5800", and message tokens "".
SQL1483N  Add database partition server  processing for database
partition server "2" failed. Information returned for the error
includes SQLCODE "-902", SQLSTATE "5800", and message tokens "".
SQLSTATE=5UA02


In the db2diag.log we see entries like:

2017-01-23-11.08.15.880319-300 I85255A812           LEVEL:
Severe
PID     : 42991858             TID : 3343           PROC :
db2sysc 2
INSTANCE: bastarma             NODE : 002           DB   :
SAMPLE
APPHDL  : 2-53                 APPID: *N2.bastarma.170123160813
AUTHID  : BASTARMA             HOSTNAME: db2debug
EDUID   : 3343                 EDUNAME: db2agent (instance) 2
FUNCTION: DB2 UDB, buffer pool services,
sqlbReadStorageGroupEntry, probe:21
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic
error detected"
         DIA8501C A buffer pool logic error has occurred.
DATA #1 : String, 49 bytes
Invalid flavour while reading storage group files
DATA #2 : unsigned integer, 8 bytes
0
DATA #3 : unsigned integer, 8 bytes
0
DATA #4 : Storage Group ID, PD_TYPE_SQLB_STORAGEGROUP_ID, 8
bytes
0

2017-01-23-11.08.15.884876-300 I86881A814           LEVEL:
Severe
PID     : 42991858             TID : 3343           PROC :
db2sysc 2
INSTANCE: bastarma             NODE : 002           DB   :
SAMPLE
APPHDL  : 2-53                 APPID: *N2.bastarma.170123160813
AUTHID  : BASTARMA             HOSTNAME: db2debug
EDUID   : 3343                 EDUNAME: db2agent (instance) 2
FUNCTION: DB2 UDB, buffer pool services, sqlbReadStorageGroup,
probe:1678
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic
error detected"
         DIA8501C A buffer pool logic error has occurred.
DATA #1 : String, 38 bytes
Error reading from storage group files
DATA #2 : Storage Group ID, PD_TYPE_SQLB_STORAGEGROUP_ID, 8
bytes
1
DATA #3 : Pointer, 8 bytes
0x0700000051144000
DATA #4 : Pointer, 8 bytes
0x07800000019f2779

2017-01-23-11.08.15.885517-300 I87696A751           LEVEL:
Severe
PID     : 42991858             TID : 3343           PROC :
db2sysc 2
INSTANCE: bastarma             NODE : 002           DB   :
SAMPLE
APPHDL  : 2-53                 APPID: *N2.bastarma.170123160813
AUTHID  : BASTARMA             HOSTNAME: db2debug
EDUID   : 3343                 EDUNAME: db2agent (instance) 2
FUNCTION: DB2 UDB, buffer pool services,
sqlbReadStorageGroupTable, probe:1984
MESSAGE : ZRC=0x87020002=-2029912062=SQLB_BPSE "Debug logic
error detected"
         DIA8501C A buffer pool logic error has occurred.
DATA #1 : String, 38 bytes
Failed to read the storage group table
DATA #2 : Pointer, 8 bytes
0x07800000019f2779
DATA #3 : Pointer, 8 bytes
0x0700000051144000

****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to v11.1 FP2 or later                                *
****************************************************************

To workaround the problem, user has to create dummy storage
group to fill gap:

db2 "CREATE STOGROUP HIGHEND3 ON '$HOME'"

Afterwards, the gap is filled and add partition works fine:

$ db2start dbpartitionnum 2 add dbpartitionnum HOSTNAME db2debug
port 2 without tablespaces

01/24/2017 10:58:48     2   0   SQL1489I  The add database
partition server  operation was successful. The new database
partition server "2" is active.
SQL1489I  The add database partition server  operation was
successful. The new database partition server "2" is active.

not known / see Local fix

forerunner  : IT18988 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

02.10.2017
13.10.2017
13.10.2017