DB2 FOR LUW / DB2FORLUW / 970 - DB2

Database manager erroneously reports that a temporary DMS 
tablespace has reached its maximum size, when the reported size 
is in fact a value that is below the documented limit. 
 
For example, for a 32K temporary DMS tablespace, you may 
observe the following error message in db2diag.log: 
 
2010-02-02-07.51.36.600495-360 E62453858A639 LEVEL: Warning 
PID : 86514 TID : 14185 PROC : db2sysc 2 
INSTANCE: bcuaix NODE : 002 DB : xxxxxx 
APPHDL : 0-75 APPID: *N0.bcuaix.100202122336 
AUTHID : BCUAIX 
EDUID : 14185 EDUNAME: db2agntp 2 
FUNCTION: DB2 UDB, buffer pool services, 
sqlbPrepareToGrowLastRange, probe:160 
MESSAGE : ADM6099W Table space "TEMP32K" (ID "2") has reached 
the maxiumum size ("549755813888" bytes) for a tablespace of 
this type and page size. To add more storage to the database, 
add a new table space. 
 
Here, the database manager reports the maximum limit of 512 GB 
was reached. However, DB2 info center states that temporary DMS 
tablespace is always LARGE and should have a 64 TB limit for 
32K pages. 
 
The problem is that database manager incorrectly treats 
temporary DMS tablespaces as REGULAR when they should be 
considered LARGE. 
 
The problem applies to tablespace with page sizes other than 
32K, as well.

USERS AFFECTED: 
=============== 
Customer using version 9.5 and above on all platforms. 
 
PROBLEM DESCRIPTION: 
==================== 
DB2 is treating temporary tablespace as REGULAR tablespace when 
it attempts to grow a temporary tablespace as part of extent 
allocation. Temporary tablespaces should truly be considered as 
LARGE/LONG tablespace. Due to this behavior, DB2 will fail 
stating the maximum capacity is reached when attempting to grow 
the temporary tablespace beyond 512 GB. The true limit for a 
large tablespace is 64 TB.  This APAR will make sure that DB2 
treats a temporary tablespace as a LARGE/LONG tablespace.

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 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
 

Problem is first fixed in version 9.7 Fixpack 4.

not known / see Local fix

forerunner  : APAR is sysrouted TO one or more of the following: IZ82631 
follow-up : 

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

11.08.2010
03.05.2011
19.12.2011

9.7.FP4