1. Take an online backup of the database from source system (include
the logs in the backup)
2. FTP the backup to the destination system
3. Restore the back up on the destination system(redirected restore if
the tablespace containers do not follow the same structure)
4. rollforward logs on the destination system
Hope this helps.
Kums
> 1. Take an online backup of the database from source system (include
> the logs in the backup)
[quoted text clipped - 35 lines]
> >
> > Kevin
Kums,
that's a very similiar idea to the oracle "copy" that I described
except it's using the backup command.
Is there a similar way of just doing a copy? So that you don't have to
have a "dump" space for the backup. Although that isn't all that bad,
could just have a NFS mounted filesystem and dump to it.
Thanks,
Kevin
Serge Rielau - 05 May 2006 22:29 GMT
>> 1. Take an online backup of the database from source system (include
>> the logs in the backup)
[quoted text clipped - 44 lines]
> have a "dump" space for the backup. Although that isn't all that bad,
> could just have a NFS mounted filesystem and dump to it.
Hmm, in Viper you can perform tablespace buck-ups and stitch it back
together on the remote side, but I fail to see where the difference is
between copies and backup/restore? Care to motivate?
Cheers
Serge
PS: Search for my name on www.ibm.com. You'll find a COPY SCHEMA
article. Maybe that'll help?

Signature
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Pierre Saint-Jacques - 08 May 2006 18:52 GMT
Investigate the:
db2relocatedb.
This allows you to take fast OS file system copies ot using flash copies on
ESS or SAN boxes.
Once the data is moved, you use the command on the receiving system with a
config file you build.
The Admin. Guide has all the necessary info.
You can script those, do it once and afte it's only a repeat of the scripts.
HTH, Pierre.

Signature
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
>
>> 1. Take an online backup of the database from source system (include
[quoted text clipped - 49 lines]
>
> Kevin
kebuchan@yahoo.com - 09 May 2006 15:01 GMT
Thanks for your responses.
It seems like this does an "internal" rename. So it seems like you
need to have the files copied over, paths renamed etc. before you run
the script.
Kevin
> Investigate the:
> db2relocatedb.
[quoted text clipped - 65 lines]
> >
> > Kevin