LUW generation 8 -> 9.1 or 9.5 experiences?

[Troels Arvin]

Hello,

We have started planning our DB2 generation 8 -9.1/9.5 upgrades, as
April 30 2009 is no longer distant future (ordinary support for DB2
generation 8 on Linux/Unix/Windows==LUW will end on April 30).

We are unsure if it's safe to move directly to version 9.5, or if we
should proceed more cautiously to version 9.1.

So I'm interested in hearing about people's experiences regarding DB2 LUW
migrations from generation 8 to 9.1 or 9.5. (I consider DB2 v. 9.1 and 9.5
as separate generations, given the move from a process-based to a threads-
based model sounds, which sounds like a rather large change to me.)
Especially, I'm interested in hearing about migrations of large and/or
mission critical databases.

--
Regards,
Troels Arvin

[Darin McBride]

Troels Arvin wrote:

We are unsure if it's safe to move directly to version 9.5, or if we
should proceed more cautiously to version 9.1.

If your concern is safety, IBM officially supports the migration of your
data from v8 directly to 9.5. If you like to hold on to a version for as
long as possible before upgrading, 9.5 should have a later end-of-service
date, which means fewer migrations.

Note that 9.5 fp2 is targeted at v8 migrations. That is, the stability and
features should be there to move your systems to 9.5. That probably also
means that DB2 support should be more comfortable with it.

(I consider DB2 v. 9.1 and 9.5
as separate generations, given the move from a process-based to a threads-
based model sounds, which sounds like a rather large change to me.)

So does IBM, it seems, because 9.1 still has new fix packs coming out even
though 9.5 has been released, unlike the difference between 8.1 and 8.2.

[w.l.fischer]

- db2cmd (win) works different than before. Once again this is only a

problem in dev. For unknown reasons (for me) our developers are doing
development from windows (poor bastards :-). There are a small number
of sh scripts for batches and so on, and they have to run these
through cygwin/db2cmd. I'm not familiar with the details, but I think
there is a workaround by setting some db2 environment variable.

I have the same problem under V9.1/cygwin. The connections gets lost
after I connect to the database. The solution is to include the
connect statement in the script. For command line editing, I have to
use the DOS shell (*uargs*).

[Jan M. Nelken]

w.*********@googlemail.com wrote:

I have the same problem under V9.1/cygwin. The connections gets lost
after I connect to the database. The solution is to include the
connect statement in the script. For command line editing, I have to
use the DOS shell (*uargs*).

Just do in cygwin bash shell:

export DB2CLP=**$$**

and get over with it.
Jan M. Nelken

[Jan M. Nelken]

Lennart wrote:

- db2cmd (win) works different than before. Once again this is only a
problem in dev. For unknown reasons (for me) our developers are doing
development from windows (poor bastards :-). There are a small number
of sh scripts for batches and so on, and they have to run these
through cygwin/db2cmd. I'm not familiar with the details, but I think
there is a workaround by setting some db2 environment variable.

For Windows - set environment variable:

DB2CLP=**$$**

and you can use DB2 commands in Windows command prompt (no need for
db2cmd window.
For cygwin, export:

export DB2CLP=**$$**

(you can set in in profile for the user.
Jan M. Nelken