home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC64270 Status: Closed

CLI PACKAGES ARE NOT CORRECTLY REBOUND DURING DATABASE UPGRADE

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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.
available fix packs:
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

Solution
The problem is first fixed in DB2 Version 9.7 Fix Pack 2 and all 
subsequent Fix Packs.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.10.2009
14.05.2010
14.05.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList