DB2 FOR LUW / DB2FORLUW / 970 - DB2

Using the sqlecrea() administrative API from a remote DB2 client 
to create a new database is not automatically binding the 
server-side DB2 utility packages.  These packages are typically 
created by binding @db2ubind.lst. 
 
The sqlecrea() API will bind the client-side utility packages, 
however if an action is required directly on the server once the 
database is created, that action might fail with an SQL0805N 
(package was not found) error since the server-side packages 
were not created automatically.

**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Using the sqlecrea() administrative API from a remote DB2    * 
* client to create a new database is not automatically binding * 
* the server-side DB2 utility packages.  These packages are    * 
* typically created by binding @db2ubind.lst.                  * 
*                                                              * 
*                                                              * 
*                                                              * 
* The sqlecrea() API will bind the client-side utility         * 
* packages, however if an action is required directly on the   * 
* server once the database is created, that action might fail  * 
* with an SQL0805N (package was not found) error since the     * 
* server-side packages were not created automatically.         * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v9.7, Fixpak 4                                * 
****************************************************************

Bind the utility packages manually on the server by going into 
the sqllib/bnd directory on the server, and issuing these 
commands: 
 
db2 connect to <dbname> 
db2 bind @db2ubind.lst blocking all grant public 
db2 terminate

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
 

This APAR fix will ensure that the server-side packages get 
bound. 
Problem was first fixed in Version 9.7 Fix Pack 4

Bind the utility packages manually on the server by going into 
the sqllib/bnd directory on the server, and issuing these 
 
 
commands: 
 
db2 connect to <dbname> 
db2 bind @db2ubind.lst blocking all grant public 
db2 terminate

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

10.01.2011
02.05.2011
02.05.2011

9.7.,
9.7.FP4