By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
439,993 Members | 1,984 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 439,993 IT Pros & Developers. It's quick & easy.

rebind after DB2 client upgrade

P: n/a
If I were to upgrade my application development client from V8.1.3 to
V8.1.4 but the (remote) database stays at V8.1.3, should I rebind the
upgraded client's utilities and CLI using @db2ubind.lst and
@db2cli.lst? Or, the rebind is done atomatcaly by a client utility
first execution, for example CLP?

Thanks,
-Eugene
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
Most FixPaks add new bind files to support the client side utilities and
drivers. I think FixPak 4 does have new bind files. You can explicitly
issue the bind using the db2ubind.lst and db2cli.lst or they will
automatically bind the first time the new bind files are needed. However,
the authid doing the first access needs to have BINDADD privilege on the
database.

"Eugene" <eu****@compete.com> wrote in message
news:72**************************@posting.google.c om...
If I were to upgrade my application development client from V8.1.3 to
V8.1.4 but the (remote) database stays at V8.1.3, should I rebind the
upgraded client's utilities and CLI using @db2ubind.lst and
@db2cli.lst? Or, the rebind is done atomatcaly by a client utility
first execution, for example CLP?

Thanks,
-Eugene

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.