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 IC64270 Status: Geschlossen

CLI PACKAGES ARE NOT CORRECTLY REBOUND DURING DATABASE UPGRADE

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
CLI packages are not correctly rebound automatically by the 
database upgrade process. 
. 
Due to this issue, catalog contention may occur when executing 
the CLI packages as concurrent implicit rebinds may be running. 
This contention may lead to unexpected lock-waits or deadlocks 
on the DB2 system catalog tables. 
. 
To avoid this contention, this APAR ensures CLI packages will be 
rebound during database upgrade.  However, if the db2rbind 
command is executed after database upgrade, this catalog 
contention will not occur.  Running db2rbind is a documented 
step in the post-upgrade procedure.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All databases upgraded to DB2 Version 9.7 GA or Fix Pack 1   * 
* on Linux, Unix and Windows platforms.                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* During database upgrade, CLI packages are not get rebound    * 
* correctly. So these packages are still invalid after         * 
* database upgrade. This will cause potential system catalog   * 
* concurrency issues such as deadlocks or unexpected           * 
* lock-waits while implicitly rebinding packages.              * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* See local fix.                                               * 
****************************************************************
Local-Fix:
Run the db2rbind command to rebind all packages after database 
upgrade.
verfügbare FixPacks:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
The problem is first fixed in DB2 Version 9.7 Fix Pack 2 and all 
subsequent Fix Packs.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
30.10.2009
14.05.2010
14.05.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP2
Problem behoben lt. FixList in der Version
9.7.0.2 FixList