I'm new here. Thought I'd give my opinion on this.

I would also do option 1. I am currently working on doing the same
thing, but in Linux.

You shouldn't won't have to do a redirected restore actually. As long
as the file-systems are the same, you won't have to worry about it.
You can even specify the new physical location of datafiles and
logfiles on the new server in the restore command.

db2look/move is handy if you want to just move one table or start
with an empty database, without dependencies. But as soon as you
start with foreign keys... you're done. There is nothing built in to
db2look or db2move that will help you deal with them (other than that
the alter table add FK commands are at the bottom of the ddl)

Good luck.

Guus

On 31-Aug-05, at 7:58 AM, Maxim Ness wrote:

> Hello DBA's,
>
> Currently we have DB2 8.1 fixpack 6a running of Windows 2000
> server. The
> goal is to transfer the configuration and data to the new windows 2003
> server with DB2 8.1 fixpack 10.
>
> Is there any known issues with fixpack 10 ?
>
> What is the best way to migrate the server ? As far as i can see i
> have 3
> options:
>
> 1. ( Upgrade source DB2 server to fixpack 10 ? ) , do a backup of
> data,
> install DB2 8.1 with fixpack 10 to the destination server and do
> redirected restore.
> 2. Install DB2 8.1 with fixpack 10 to the destination server and do
> redirected restore and move data with db2look/export-load commands.
> Can i
> use db2move ? RTFM says that it is to be used only on workstation.
> 3. Pay to IBM to do the work :)
>
> Thanks in advance.
>
>
>
> ---------------------------------------------------------------------
> PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
> website: http://www.LazyDBA.com
> To unsubscribe: http://www.lazydba.com/unsubscribe.html
>
>


DB2 & UDB email list listserv db2-l LazyDBA home page