DB2 - Problem description
Problem IC97530 | Status: Closed |
DB2CKUPGRADE FAILS WHEN THERE IS A CERTAIN DEPENDENCY ON SEQUENCE. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
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". | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description above. * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.5 Fix Pack 3 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 Version 10.5 Fix Pack 3 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 08.11.2013 27.02.2014 27.02.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.5.0.3 | |
10.5.0.3 |