Lennart,
We ran into those problems with our V8.2 servers. What we do is create a
32-bit instance to act as a proxy for the 32-bit clients and point all
traffic through to the 64-bit instance from this.
Been doing this with both AIX and Solaris at V8.2 level.
Here's an example of what we do ... db264 (port 50064) is the 64 bit
instance, db232 (port 50032) is the 32-bit instance) -
On db232 -
CATALOG TCPIP NODE DB264 REMOTE hostname SERVER 50064;
CATALOG DATABASE DB1 AT NODE DB264;
The 32-bit clients can then connect to DB1 on port 50032 but the database
will actually be on the 64-bit instance.
We've had to do this for three reasons -
WAS4 : old Type 2 Java drivers (32-bit client only)
32-bit Windows V6.1 clients
TSM is either 32-bit or 64-bit (not both) so can't have a 64-bit V9.5 and
32-bit V8.2 on same box and back up both using TSM
HTH
Phil Nelson
(te*****@scotdb.com)
Lennart wrote:
>
I'm trying to read up on the possibility to migrate a db2 V9.5 server
to 64 bit, and continue running 32 bit application servers (via db2
runtime client, or otherwise). Does anyone have links to this kind of
information? I've google around a bit, and searched the db2 docs
without much success so far? Is it at all possible, what restrictions
apply for such a setup, etc is the kind of questions I would like to
find info about.
Thanx in advance
/Lennart