Question & Answer
How can I acquire the bind files (.bnd) that are included for a specific version and fix pack?
Included in every DB2 install image are bind files (sqllib/bnd/*.bnd) containing the packages for various database and CLI utilities. Many of these bind files correspond to utilities that are incorporated into the Runtime client. If you are using a Runtime client with a different release or fixpack version then the database server, then it is often necessary to bind the .bnd files associated with that Runtime client version to the database before it can be used.
When creating a new database that may accept connections from various remote clients which may run these utilities, it is often difficult to track down the .bnd files from each client version.
Suppose you deploy a new database created on DB2 11.1 modpack 3 fixpack3, an application that is executing on a remotely connected client may be running a DB2 Runtime client of version 10.5 fixpack4. If the application attempts to use a utility (such as CLP, Import, Export, etc...) it could generate an SQL0805N error because the package associated with this version of the utility was not bound to the new database. You will have to bind the packages using the bind files from client version.
With this technote, you can download the bind files for any version.
Included in this technote are tar files that contain the .bnd files for the fix packs from Db2 11.5, 11.1, and 10.5.
How to use the tar file:
- Download the tar file to your computer.
- Extract or untar the files to use them using the command:
tar -xvf <tarfilename>
- Locate the subdirectory for the fix pack you wish to bind
- Identify the bind files required and use the DB2 BIND command to bind the packages to your database.
The Related Information section contains a link to the BIND Command syntax.
21 December 2020