home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC73753 Status: Closed

SQLECREA FROM REMOTE CLIENT IS NOT AUTOMATICALLY BINDING SERVER-SIDE
UTILITY PACKAGES

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
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.
Problem Summary:
**************************************************************** 
* 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                                * 
****************************************************************
Local Fix:
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
available fix packs:
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

Solution
This APAR fix will ensure that the server-side packages get 
bound. 
Problem was first fixed in Version 9.7 Fix Pack 4
Workaround
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
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
10.01.2011
02.05.2011
02.05.2011
Problem solved at the following versions (IBM BugInfos)
9.7.,
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList