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

DB2 UPGRADE DATABASE MIGHT FAIL WITH SQL1704N RC 17 IF MAXSIZE LIMIT FOR
SYSCATSPACE IS HIT DURING THE UPGRADE (ADM6091W)

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
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.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.1 Mod 2 Fix Pack 2 or higher               *
****************************************************************
Local Fix:
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...).
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT17527 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.08.2017
24.10.2017
24.10.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)