DB2 FOR LUW / DB2FORLUW / A50 - DB2

Db2's rebind utility, db2rbind, doesn't rebind inoperative 
packages, i.e, packages marked with valid='X' in 
syscat.packages. 
Currently db2rbind only rebinds valid (valid='Y') and invalid 
packages 
(valid='N').   This leaves packages that are inoperative 
(valid='X') 
that still need to be rebound - and may end up rebinding 
implicitly 
which can cause locking issues at runtime. 
This APAR corrects the db2rbind utility by ensuring db2rbind 
rebinds inoperative packages as well if the "resolve any" option 
is chosen (noting that 'resolve conservative' will not 
successfully 
rebind inoperative packages) 
 
Specifically: 
 
Unchanged: 
 
- db2rbind <db_name> -l <logfile> -r conservative 
will continue to rebind only invalid packages. 
 
- db2rbind <db_name> -l <logfile> all -r conservative 
will continue to rebind valid and invalid packages. 
 
Changes: 
 
- db2rbind <db_name> -l <logfile> -r any 
will now rebind invalid and inoperative packages 
 
- - db2rbind <db_name> -l <logfile> all -r any 
will now rebind all packages: valid, invalid and 
inoperative packages.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All users using db2rbind                                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 for LUW Version 10.5 fix pack 7               * 
****************************************************************

The inoperative packages can be explicitly rebound.

Fixed in DB2 for LUW Version 10.5 fix pack 7

keiner bekannt / siehe Local-Fix

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

06.08.2015
22.01.2016
22.01.2016