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

db2 database online copy help?

P: n/a
Hi all,

I know this is possible in Oracle but has anyone done it in DB2 and
could you maybe direct me to some documentation or let me know how I
would go about doing it?

In the oracle world you would basically need to do the following:

1. Set tablespace to backup mode
2. Copy associated data files to new directory/system
3. Set tablespace off backup mode

4. Keep doing the above for all the tablespaces.
5. Force a log switch to write an archive log
6. Copy the archive logs over to the new directory/system
7. create a new control file with the new system name etc.
8. bring up the DB.

That was basically it.

In most cases we copied the data files over to a new system via rfc
(scp)

Can you do this or something similar in db2 on AIX?

Thanks,

Kevin

May 5 '06 #1
Share this Question
Share on Google+
5 Replies


P: n/a
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
ke******@yahoo.com wrote:
Hi all,

I know this is possible in Oracle but has anyone done it in DB2 and
could you maybe direct me to some documentation or let me know how I
would go about doing it?

In the oracle world you would basically need to do the following:

1. Set tablespace to backup mode
2. Copy associated data files to new directory/system
3. Set tablespace off backup mode

4. Keep doing the above for all the tablespaces.
5. Force a log switch to write an archive log
6. Copy the archive logs over to the new directory/system
7. create a new control file with the new system name etc.
8. bring up the DB.

That was basically it.

In most cases we copied the data files over to a new system via rfc
(scp)

Can you do this or something similar in db2 on AIX?

Thanks,

Kevin


May 5 '06 #2

P: n/a

hi****@gmail.com wrote:
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
ke******@yahoo.com wrote:
Hi all,

I know this is possible in Oracle but has anyone done it in DB2 and
could you maybe direct me to some documentation or let me know how I
would go about doing it?

In the oracle world you would basically need to do the following:

1. Set tablespace to backup mode
2. Copy associated data files to new directory/system
3. Set tablespace off backup mode

4. Keep doing the above for all the tablespaces.
5. Force a log switch to write an archive log
6. Copy the archive logs over to the new directory/system
7. create a new control file with the new system name etc.
8. bring up the DB.

That was basically it.

In most cases we copied the data files over to a new system via rfc
(scp)

Can you do this or something similar in db2 on AIX?

Thanks,

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

May 5 '06 #3

P: n/a
ke******@yahoo.com wrote:
hi****@gmail.com wrote:
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
ke******@yahoo.com wrote:
Hi all,

I know this is possible in Oracle but has anyone done it in DB2 and
could you maybe direct me to some documentation or let me know how I
would go about doing it?

In the oracle world you would basically need to do the following:

1. Set tablespace to backup mode
2. Copy associated data files to new directory/system
3. Set tablespace off backup mode

4. Keep doing the above for all the tablespaces.
5. Force a log switch to write an archive log
6. Copy the archive logs over to the new directory/system
7. create a new control file with the new system name etc.
8. bring up the DB.

That was basically it.

In most cases we copied the data files over to a new system via rfc
(scp)

Can you do this or something similar in db2 on AIX?

Thanks,

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.

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?
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
May 5 '06 #4

P: n/a
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.

--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
<ke******@yahoo.com> a écrit dans le message de news:
11**********************@e56g2000cwe.googlegroups. com...

hi****@gmail.com wrote:
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
ke******@yahoo.com wrote:
> Hi all,
>
> I know this is possible in Oracle but has anyone done it in DB2 and
> could you maybe direct me to some documentation or let me know how I
> would go about doing it?
>
> In the oracle world you would basically need to do the following:
>
> 1. Set tablespace to backup mode
> 2. Copy associated data files to new directory/system
> 3. Set tablespace off backup mode
>
> 4. Keep doing the above for all the tablespaces.
> 5. Force a log switch to write an archive log
> 6. Copy the archive logs over to the new directory/system
> 7. create a new control file with the new system name etc.
> 8. bring up the DB.
>
> That was basically it.
>
> In most cases we copied the data files over to a new system via rfc
> (scp)
>
> Can you do this or something similar in db2 on AIX?
>
> Thanks,
>
> 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


May 8 '06 #5

P: n/a
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

Pierre Saint-Jacques wrote:
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.

--
Pierre Saint-Jacques
SES Consultants Inc.
514-737-4515
<ke******@yahoo.com> a écrit dans le message de news:
11**********************@e56g2000cwe.googlegroups. com...

hi****@gmail.com wrote:
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
ke******@yahoo.com wrote:
> Hi all,
>
> I know this is possible in Oracle but has anyone done it in DB2 and
> could you maybe direct me to some documentation or let me know how I
> would go about doing it?
>
> In the oracle world you would basically need to do the following:
>
> 1. Set tablespace to backup mode
> 2. Copy associated data files to new directory/system
> 3. Set tablespace off backup mode
>
> 4. Keep doing the above for all the tablespaces.
> 5. Force a log switch to write an archive log
> 6. Copy the archive logs over to the new directory/system
> 7. create a new control file with the new system name etc.
> 8. bring up the DB.
>
> That was basically it.
>
> In most cases we copied the data files over to a new system via rfc
> (scp)
>
> Can you do this or something similar in db2 on AIX?
>
> Thanks,
>
> 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


May 10 '06 #6

This discussion thread is closed

Replies have been disabled for this discussion.