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

V7 client and V8 client on same machine

P: n/a
Helpful folks,

I am in the process of upgrading our company to V8. The steps I have
outlined are as follows:

1) Upgrade all clients to latest V7 fixpack
2) Upgrade test server to latest v7 fixpack
3) Upgrade prod server to latest v7 fixpack
4) migrate test server to V8
5) Upgrade developers client workstations to V8
5a) developers test major applications for V8 compatabilites
6) migrate prod server to v8
7) Upgade all non-developer clients to v8

The problem occurs during step 5a. While the test server is at v8 and
developer workstations are at v8, and the prod server is at v7, the
developers will have a need to run tools and test emergency code fixes
against the prod server. The v8client-to-v7server incompatabilites
will make this impossible.
My question is, can the developer workstations be configured such that
they can easily 'toggle' back and forth between a v8 client and a v7
client, without having to uninstall/reinstall db2 client components?

Any feedback would be greatly appreciated.

Sean
Nov 12 '05 #1
Share this Question
Share on Google+
5 Replies


P: n/a
On Linux and UNIX, v7 and v8 clients can coexist on the same machine.

On Windows, the safest way to do this is to have separate, bootable
Windows partitions - one with the v7 client, and one with the v8
client, and reboot before using one or the other.

Sean C. wrote:
Helpful folks,

I am in the process of upgrading our company to V8. The steps I have
outlined are as follows:

1) Upgrade all clients to latest V7 fixpack
2) Upgrade test server to latest v7 fixpack
3) Upgrade prod server to latest v7 fixpack
4) migrate test server to V8
5) Upgrade developers client workstations to V8
5a) developers test major applications for V8 compatabilites
6) migrate prod server to v8
7) Upgade all non-developer clients to v8

The problem occurs during step 5a. While the test server is at v8 and
developer workstations are at v8, and the prod server is at v7, the
developers will have a need to run tools and test emergency code fixes
against the prod server. The v8client-to-v7server incompatabilites
will make this impossible.
My question is, can the developer workstations be configured such that
they can easily 'toggle' back and forth between a v8 client and a v7
client, without having to uninstall/reinstall db2 client components?

Any feedback would be greatly appreciated.

Sean


Nov 12 '05 #2

P: n/a
We are having the same exact issue...
We have a V7 OS 390 DB2 server and V8 server Linux UDB server and users need
the ability to connect to both
of them from their NT workstattions. V8 Windows client is not compatible
with V7 OS 390 DB2 server (thru V7 DB2 connect). Every once in a while we
keep doing uninstall/reinstall betwenn ver 8 client & ver 7 client which is
really
really ridiculous.

"Blair Adamache" <ba*******@2muchspam.yahoo.com> wrote in message
news:br**********@hanover.torolab.ibm.com...
On Linux and UNIX, v7 and v8 clients can coexist on the same machine.

On Windows, the safest way to do this is to have separate, bootable
Windows partitions - one with the v7 client, and one with the v8
client, and reboot before using one or the other.

Sean C. wrote:
Helpful folks,

I am in the process of upgrading our company to V8. The steps I have
outlined are as follows:

1) Upgrade all clients to latest V7 fixpack
2) Upgrade test server to latest v7 fixpack
3) Upgrade prod server to latest v7 fixpack
4) migrate test server to V8
5) Upgrade developers client workstations to V8
5a) developers test major applications for V8 compatabilites
6) migrate prod server to v8
7) Upgade all non-developer clients to v8

The problem occurs during step 5a. While the test server is at v8 and
developer workstations are at v8, and the prod server is at v7, the
developers will have a need to run tools and test emergency code fixes
against the prod server. The v8client-to-v7server incompatabilites
will make this impossible.
My question is, can the developer workstations be configured such that
they can easily 'toggle' back and forth between a v8 client and a v7
client, without having to uninstall/reinstall db2 client components?

Any feedback would be greatly appreciated.

Sean

Nov 12 '05 #3

P: n/a
Why not just leave your clients on V7 until after all servers have
been upgraded to V8? V7 client should work perfectly fine connecting
to V8 Server. So what I am saying is do your upgrade as follows.

1) Upgrade all clients to latest V7 fixpack
2) Upgrade test server to latest v7 fixpack
3) Upgrade prod server to latest v7 fixpack
4) migrate test server to V8
5) developers test major applications for V8 compatabilites
6) migrate prod server to v8
7) Upgrade developers client workstations to V8
8) Upgade all non-developer clients to v8
db*****@yahoo.com (Sean C.) wrote in message news:<2f**************************@posting.google. com>...
Helpful folks,

I am in the process of upgrading our company to V8. The steps I have
outlined are as follows:

1) Upgrade all clients to latest V7 fixpack
2) Upgrade test server to latest v7 fixpack
3) Upgrade prod server to latest v7 fixpack
4) migrate test server to V8
5) Upgrade developers client workstations to V8
5a) developers test major applications for V8 compatabilites
6) migrate prod server to v8
7) Upgade all non-developer clients to v8

The problem occurs during step 5a. While the test server is at v8 and
developer workstations are at v8, and the prod server is at v7, the
developers will have a need to run tools and test emergency code fixes
against the prod server. The v8client-to-v7server incompatabilites
will make this impossible.
My question is, can the developer workstations be configured such that
they can easily 'toggle' back and forth between a v8 client and a v7
client, without having to uninstall/reinstall db2 client components?

Any feedback would be greatly appreciated.

Sean

Nov 12 '05 #4

P: n/a
Thanks for all the useful feedback. One of the details I left out, is
that some of the 'clients' that will be talking to the db server are
application servers. This is the functionality that the developers
will need to test, running their workstation as an application server
against the database. I would of course like to upgrade all the
application servers to the v8 client, but as Spencer implies, perhaps
this is not a critical step. I will probably leave that as a follow up
item, and perhaps convince one developer to be the v8 testing dupe, so
that only his workstation will need to worry about
uninstalling/reinstalling client code as needed, and have him test
each application server functionality one-by-one.
Thanks again folks.
Nov 12 '05 #5

P: n/a
Thanks for all the useful feedback. One of the details I left out, is
that some of the 'clients' that will be talking to the db server are
application servers. This is the functionality that the developers
will need to test, running their workstation as an application server
against the database. I would of course like to upgrade all the
application servers to the v8 client, but as Spencer implies, perhaps
this is not a critical step. I will probably leave that as a follow up
item, and perhaps convince one developer to be the v8 testing dupe, so
that only his workstation will need to worry about
uninstalling/reinstalling client code as needed, and have him test
each application server functionality one-by-one.
Thanks again folks.
Nov 12 '05 #6

This discussion thread is closed

Replies have been disabled for this discussion.