DB2 FOR LUW / DB2FORLUW / A50 - DB2

The tool db2ckupgrade evaluates the table status for each table 
defined in a database to ensure no table is in load pending 
state. 
 
If the database has a large number of tables and indexes defined 
and hosts a considerable amount of data this check can take very 
long. 
A DB2 trace with perfcount option (db2trc on -perfcount -t) will 
show a lot of time spend in following functions: 
 
sqlrlAdminGetTabInfo 
sqldGetTableData 
sqldGetTableDataForPermOrTemp 
sqlbReadPageInternal 
sqldGetDataForObjSizes 
sqlbGetObjActualSize 
sqlbDMSGetObjActualSize 
sqldGetIndexObjInfo 
sqldGetDataForTableInfo 
 
This APAR will change the way db2ckupgrade checks the table load 
pending state to improve performance. 
 
The tool db2ckupgrade is run from the installation/CD of the new 
DB2 server copy to which one is upgrading to. However, it is run 
against the downlevel DB2 server which is targeted for upgrade. 
The fix requires both the downlevel DB2 server as well as the 
new DB2 server to be at a fix level mentioned in the 
Recommendation section below.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.5 FixPack 3                               * 
****************************************************************

DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
 DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
 

First fixed in DB2 v10.5 FixPack 3

keiner bekannt / siehe Local-Fix

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

31.07.2013
10.03.2014
10.03.2014