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

Binding after FixPack installation?

P: n/a

I have the following situation:
DB2 V6.1 OS/390 and DB2 V6.1 auf AIX 4.3.3 running the database servers.
A windows NT machine with db2 V7.1.040 FP3 (WR21254) client.

Now I have a JDBC application which crashes when it tries to find out
the primary keys of a table on the AIX db server using getPrimaryKeys on
tables with primary keys (it don't crash with tables without primary keys!).

My first idea is to install a newer fixpack version on the client
machine, e.g. FixPack 10a (WR21331).
The Problem is, that each FixPack installation needs to bind the new
packages of the fixpack into the database server.

The administrators of the db2 servers worry about an influence with the
older clients.

Can someone tell me, if the new fixpack packages overwrites the older
packages of the client version?

Are there any influence with clients on the fp3 level?

Is it possible to install the new packages in a separate collection and
to configure only the one client machine, with the fixpack, to use the
packages in this separate collection?


Nov 12 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.