DB2 FOR LUW / DB2FORLUW / 970 - DB2

When you create more than 32768 partition groups, the error 
SQL0269N is expected but does not occur. 
 
Each partition group is assigned a partition map id (pmap_id). 
If 
more than 32768 partition groups are created, the pmap_id 
will be set beyond its 32768 limit. 
The behavior is unknown when the pmap_id exceeds this limit.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW version 9.7 GA who create large numbers of partition * 
* groups.                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When creating more than 32768 partition groups, the          * 
* error SQL0269N  is expected but does not occur.              * 
*                                                              * 
* Each partition group is assigned a partition map id          * 
* (pmap_id).                                                   * 
* If more than 32768 partition groups are created, the pmap_id * 
*                                                              * 
* will be set beyond its 32768 limit.                          * 
*                                                              * 
* DB2 incorrectly allows pmap_id values that are greater than  * 
* 32768 and does not block creating more nodegroups when       * 
* this limit is exceeded.                                      * 
*                                                              * 
* The behavior is unknown when the pmap_id exceeds this limit. * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Create fewer partition groups or upgrade to DB2 Version 9.7  * 
* Fix Pack 1                                                   * 
****************************************************************

No workaround available. 
 
To verify how many partition groups currently exist, issue the 
following query: 
              $ 
db2 select "SUBSTR(DBPGNAME, 1, 15) as PGNAME, 
 
    SUBSTR(OWNER, 1, 10) as OWNER, 
   PMAP_ID, 
  from SYSCAT.DBPARTITIONGROUPS" 
         PGNAME 
 OWNER   PMAP_ID 
--------------- ---------- ------- 
IBMCATGROUP SYSIBM   0 
IBMDEFAULTGROUP SYSIBM  1 
IBMTEMPGROUP SYSIBM   2 
NG2  DB2INST1  3 
NG3  DB2INST1  4 
NG4  DB2INST1  5

DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

The fix restores the validation of the pmap_id and blocks 
creating nodegoups when this limit is exceeded. When creating 
more than 32768 partition groups the correct error message 
(SQL0269N) is returned. 
 
Problem is first fixed in DB2 Version 9.7 Fix Pack 1 and all 
subsequent Fix Packs.

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

22.09.2009
29.12.2009
29.12.2009

9.7.,
9.7.FP1