IBM Support

IC67654: TO AVOID ERROR SQL0551, PACKAGES SHOULD GET AUTOMATICALLY BOUND EVEN IF THE USER HAS NO BIND AUTHORITY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If your database does not contain packages that database
    utilities (IMPORT, EXPORT, REORG, the Command Line Processor) or
    CLI (Call Level Interface) require, those packages should be
    automatically bound when you connect to the database.
    The packages that database utilities require are listed in the
    file db2ubind.lst.
    The packages that DB2 CLI requires are listed in the file
    db2cli.lst.
    Database utilities and CLI might require new packages in the
    database after you apply a fix pack to the database server or to
    a database client that connects to the database.
    But if the user as which you connect does not have the authority
    to bind packages in the database, the automatic bind does not
    take place.
    That means that when you do some operation that requires one of
    those packages you could get an error message like:
     SQL0551N  "<username>" does not have the privilege to perform
    operation "BIND" on object "<packagename>".
    
    
    The change that this APAR introduces is to make the automatic
    bind of packages that database utilities and CLI
    happen even if the user as which you connect to the database
    does not have the authority to bind packages to the database.
    
    Note that when connections are coming from a remote instance
    at a level of DB2 that is not the same as the level of the
    server, then packages required to execute the
    application/utility may  not the be the same as those
    that are bound on the server.
    In such a case, the packages will have to be bound from the
    client (this bind can be driven implicitly from the DB2 utility
    or  explicitly via a BIND from the remote client).
    In this case of this remote client bind, the user must still
    have the  required privileges to BIND the package, or the DB2
    will fail with a -805 sqlcode error.
    

Local fix

  • Manually bind the required packages.
    That is, change to the directory which contains the bind files
    (sqllib/bnd), connect to the database as a user with authority
    to bind packages, and run:
     db2 "bind @db2ubind.lst"
     db2 "bind @db2cli.lst"
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of DB2 for Linux, UNIX and Windows, after applying a   *
    * fixpak                                                       *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 Version 9.7 Fix Pack 3 or later fix pack      *
    ****************************************************************
    

Problem conclusion

  • Problem was first fixed in Version 9.7 Fix Pack 3
    

Temporary fix

  • As a workaround, you can manually bind the required packages.
    
    That is, change to the directory which contains the bind files
    
    (sqllib/bnd), connect to the database as a user with authority
    
    to bind packages, and run:
    
    db2 "bind @db2ubind.lst"
    
    db2 "bind @db2cli.lst"
    

Comments

APAR Information

  • APAR number

    IC67654

  • 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-04-06

  • Closed date

    2011-01-31

  • Last modified date

    2011-01-31

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

    IZ73666

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R950 PSN

       UP

  • R970 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.7","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
31 January 2011