DB2 FOR LUW / DB2FORLUW / A10 - DB2

Upgrade of DB2 database involves allocation of new pages is 
system catalog tablespace (SYSCATSPACE). Details can be found in 
"Increasing table space and log file sizes before upgrade" 
chapter of KnowledgeCenter . 
 
In case upgrade fails to allocate new pages in SYSCATSPACE, 
upgrade will fail with: 
SQL1704N  Database upgrade failed.  Reason code "17". 
 
This error can be returned in case MAXSIZE limit for SYSCATSPACE 
is reached during the upgrade, which will result in ADM6091W 
error being logged to db2diag.log, e.g. 
FUNCTION: DB2 UDB, buffer pool services, 
sqlbPrepareToGrowLastRange, probe:140 
MESSAGE : ADM6091W  An attempt was made to automatically 
increase the size of 
          auto-resize table space "SYSCATSPACE" (ID "0") but the 
table space's 
          maximum size ("2147483648" bytes) has been reached. 
 
Currently db2ckupgrade doesn't verify MAXSIZE limit for 
SYSCATSPACE before the upgrade and this APAR will add this 
additional check.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 Fix Pack 6                               * 
****************************************************************

Before the upgrade, verify whether MAXSIZE limit for SYSCATSPACE 
is high enough for upgrade to complete. 
In case the error is hit during the upgrade, instance has to be 
downgraded to previous release, backup restored and MAXSIZE 
limit has to adjusted (ALTER TABLESPACE SYSCATSPACE...).

First fixed in DB2 10.1 Fix Pack 6

not known / see Local fix

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

17.10.2016
02.03.2017
02.03.2017