home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC97530 Status: Geschlossen

DB2CKUPGRADE FAILS WHEN THERE IS A CERTAIN DEPENDENCY ON SEQUENCE.

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description above.                                 * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 3                       * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
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

Lösung
First fixed in DB2 Version 10.5 Fix Pack 3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
08.11.2013
27.02.2014
27.02.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.3 FixList
10.5.0.3 FixList