DB2 FOR LUW / DB2FORLUW / 970 - DB2

If we  create tablespace with large numbers (say 124)  and try 
to resize them after  creation ,it shows error as 
example given below. 
 
db2 "alter tablespace USERSPACE4 RESIZE (all containers 2000K)" 
DB21034E  The command was processed as an SQL statement because 
it was not a valid Command Line Processor command.  During SQL 
processing it 
returned:SQL0259N  Container map for table space is too 
complicated. 
SQLSTATE=54037. 
 
However  ,if we  try  to reconnect the db and resize ,it 
completes resize successfully. 
 
The above problem is not seen in case we create tablespace with 
small number of containers (say 64).

**************************************************************** 
* USERS AFFECTED:                                              * 
* software                                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* if we  create  tablespace  with large number of containers   * 
* and try to resize immediately ,it fails with page map error. * 
*                                                              * 
* However  on  reconnection it can be done without error.      * 
*                                                              * 
* The above error is not seen in case of small number of       * 
* containers.                                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to db2 v9.7 fp7.                                     * 
****************************************************************

Reconnect  the db and  try to resize the containers

DB2 Version 9.7 Fix Pack 7 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 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC87868 
Nachfolger : 

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

08.05.2012
18.07.2013
18.07.2013

9.7.FP7