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

DB2 SHOWS PAGE MAP ERROR WHILE RESIZING A LARGE NUMBER OF CONTAINERS
IMMEDIATELY AFTER CREATION OF TABLESPACE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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).
Problem Summary:
**************************************************************** 
* 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.                                     * 
****************************************************************
Local Fix:
Reconnect  the db and  try to resize the containers
available fix packs:
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

Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC87868 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
08.05.2012
18.07.2013
18.07.2013
Problem solved at the following versions (IBM BugInfos)
9.7.FP7
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.7 FixList