DB2 FOR LUW / DB2FORLUW / 970 - DB2

Every time a given Fixpak issues db2look for the first time, it 
requires the packages to be bound again. 
 
The following output will be shown whenever binding needs to be 
done. 
 
db2look -d sample -o db2look.out 
-- USER is: USER 
-- Output is sent to file: db2look.out 
-- Binding package automatically ... 
-- Bind is successful 
-- Binding package automatically ... 
-- Bind is successful 
 
For example, if two clients at Fixpak 1 and Fixpak 2 run db2look 
against a server, the following behavior will be observed 
 
- Fixpak 1 runs db2look, binding occurs 
- Fixpak 1 runs db2look, no bind occurs 
- Fixpak 2 runs db2look, binding occurs 
- Fixpak 2 runs db2look, no bind occurs 
- Fixpak 1 runs db2look, binding occurs 
- Fixpak 2 runs db2look, binding occurs 
 
This happens because all Fixpaks of the same release share the 
same package name but different timestamp.  The binding occurs 
when the package that exists on the server has a different 
timestamp. 
 
This APAR will introduce unique naming of db2look packages so 
that binding does not need to be done again if it was bound 
originally at some point in time.

**************************************************************** 
* USERS AFFECTED:                                              * 
* DB2 LUW v9.7                                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* BINDING OF PACKAGES OCCURS EVERY TIME A DIFFERENT            * 
* FIXPAKLEVELEXECUTES DB2LOOK                                  * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW v9.7 Fixpak 3                             * 
****************************************************************

- Grant bind privileges to users that run db2look to prevent 
bind authority errors. 
- Ensure all clients that may need to run db2look are at the 
same Fixpak level.

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 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

First fixed in DB2 LUW v9.7 Fixpak 3

- Grant bind privileges to users that run db2look to prevent 
bind authority errors. 
- Ensure all clients that may need to run db2look are at the 
same Fixpak level.

forerunner  : APAR is sysrouted TO one or more of the following: IC69013 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

15.02.2010
27.09.2010
27.09.2010

9.7.