IBM Support

IC66282: BINDING OF PACKAGES OCCURS EVERY TIME A DIFFERENT FIXPAK LEVEL EXECUTES DB2LOOK

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • 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.
    

Local fix

  • - 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.
    

Problem summary

  • ****************************************************************
    * 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                             *
    ****************************************************************
    

Problem conclusion

  • First fixed in DB2 LUW v9.7 Fixpak 3
    

Temporary fix

  • - 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.
    

Comments

APAR Information

  • APAR number

    IC66282

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-02-15

  • Closed date

    2010-09-27

  • Last modified date

    2010-09-27

  • APAR is sysrouted FROM one or more of the following:

    IZ49710

  • APAR is sysrouted TO one or more of the following:

    IC69013

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC66282

Modified date: 27 September 2010