DB2 FOR LUW / DB2FORLUW / A10 - DB2

When db2ckupgrade is run from v10 install image on a lower level 
and the database contains dependencies to an invalid sequence, 
db2ckupgrade will fail. 
 
 
Example output from the db2ckupgrade log file: 
--------------------------------------------- 
 
Version of DB2CKUPGRADE being run: VERSION "10.1" 
 
 Database: "TEST" 
 
 Warning! Found package(s) with sequence dependencies but the 
package binder has no explicit USAGE privilege on that sequence 
and has no DATAACCESS authority granted. Rebinding those 
packages after upgrade may cause a failure due to security 
changes in DB2 V10 (Galileo). 
 
Before continuing with the upgrade the package binder must be 
granted either an explicit (or implicit via role hierarchy) 
USAGE privilege on the sequence or DATAACCESS database 
authority. To grant the explicit USAGE privilege execute 
statements below. Please contact IBM support for more 
information. 
 
 GRANT USAGE ON SEQUENCE "DBGUYS2 "."SEQNBR" TO USER DBGUYS2 
 
DBT5518W  The db2ckupgrade utility completed with one or more 
warnings but the database can still be upgraded. Log file: 
"/tmp/chkupdate_test-2013-02-07-b.log".

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 3                       * 
****************************************************************

DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
 DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
 

First fixed in DB2 Version 10.1 Fix Pack 3

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC97530 
Nachfolger : 

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

19.03.2013
09.12.2013
09.12.2013