|
Problem IC62106
|
Status: Closed |
DB2ADMINOTM.BND MISSING FROM V9.7 CLIENT INSTALL |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
To bind the DB2 utilities the file db2ubind.lst must be bound.
db2ubind.lst references the file db2adminotm.bnd, but this file
was not shipped in client installs. This APAR will result in
the bind file having a new name and db2ubind.lst reference the
new bind file name. This new bind file will be shipped on both
client and server installs.
Note: In v9.7 Fixpak 1, the file db2adminotm.bnd was renamed to
db2_adminotm.bnd but is still only found on the server
installation. The new file will be included in a client
installation in the next Fixpak release |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 LUW v9.7 *
****************************************************************
* PROBLEM DESCRIPTION: *
* DB2ADMINOTM.BND MISSING FROM V9.7 CLIENT INSTALL *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 LUW v9.7 Fixpak 2 *
**************************************************************** |
| Local Fix: |
Please use one of the following options:
1) Bind db2ubind.lst locally on the DB2 server install
2) If you intend on binding db2ubind.lst remotely from a client
or issue a create database command remotely from a client,
please ensure the bind files are copied to the client prior to
issuing the command by following these steps:
- If v9.7 GA, copy db2adminotm.bnd from the server to the
client's bnd directory
- If v9.7 Fixpak 1, copy db2_adminotm.bnd from the server to the
client's bnd directory
On Windows: The "bnd" directory is typically located under
C:\Program Files\IBM\SQLLIB\bnd in the default install location.
On Unix: The "bnd" directory is located under the instance
user's home directory of $INSTHOME/sqllib/bnd.
** Please ensure both the server and client are the same Fixpak
level when copying files. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
First fixed in DB2 LUW v9.7 Fixpak 2 |
| Workaround |
Please use one of the following options:
1) Bind db2ubind.lst locally on the DB2 server install
2) If you intend on binding db2ubind.lst remotely from a client
or issue a create database command remotely from a client,
please ensure the bind files are copied to the client prior to
issuing the command by following these steps:
- If v9.7 GA, copy db2adminotm.bnd from the server to the
client's bnd directory
- If v9.7 Fixpak 1, copy db2_adminotm.bnd from the server to
the
client's bnd directory
On Windows: The "bnd" directory is typically located under
C:\Program Files\IBM\SQLLIB\bnd in the default install location.
On Unix: The "bnd" directory is located under the instance
user's home directory of $INSTHOME/sqllib/bnd.
** Please ensure both the server and client are the same Fixpak
level when copying files. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.07.2009
24.02.2011
24.02.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
