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

Restore into DB2 replication database

P: n/a
Hi all,

Environment:

DB2 v8.1with fixpack 9 on AIX, SQL bi-directional replication.

Server A: capture process
Server B: capture and apply process

1. Shut down all capture and apply processes. Now I am SURE no more
transactions will take place on either side.
2. Take DB backup for Server B
3. Doing some read/write testing on Server B
4. Finish testing on Server B
5. Restore backup took in step 2 into Server B
6. The data on Server A should be the same as on Server A.

Now, do I HAVE TO do a 'cold' resync from Server A to Server B? Or just
'warm' is enough? 'cause 'cold' sync takes much longer time and uses
lots of space.

Again the same question, where can I find out more info like this? Any
docs or books?

Thanks!

Mar 6 '06 #1
Share this Question
Share on Google+
4 Replies


P: n/a

ibm...@yahoo.com wrote:
Hi all,

Environment:

DB2 v8.1with fixpack 9 on AIX, SQL bi-directional replication.

Server A: capture process
Server B: capture and apply process

1. Shut down all capture and apply processes. Now I am SURE no more
transactions will take place on either side.
2. Take DB backup for Server B
3. Doing some read/write testing on Server B
4. Finish testing on Server B
5. Restore backup took in step 2 into Server B
6. The data on Server A should be the same as on Server A.

Now, do I HAVE TO do a 'cold' resync from Server A to Server B? Or just
'warm' is enough? 'cause 'cold' sync takes much longer time and uses
lots of space.

Again the same question, where can I find out more info like this? Any
docs or books?

Thanks!

Sorry.

"
6. The data on Server B should be the same as on Server A.
"

Mar 6 '06 #2

P: n/a
Here are some observations:

1. If you do a RESTORE of a database you have to start a COLD start of
the CAPTURE otherwise it will give you an error saying this database
has been restored...etc

2. You can do a COLD start and do a Manual Refresh or Sync script which
is basically telling REPLICATION that even though you started the
CAPTURE in COLD don't start replicating the entire table ...only the
changes and from now on.....
cheers....
Shashi Mannepalli
ib****@yahoo.com wrote:
ibm...@yahoo.com wrote:
Hi all,

Environment:

DB2 v8.1with fixpack 9 on AIX, SQL bi-directional replication.

Server A: capture process
Server B: capture and apply process

1. Shut down all capture and apply processes. Now I am SURE no more
transactions will take place on either side.
2. Take DB backup for Server B
3. Doing some read/write testing on Server B
4. Finish testing on Server B
5. Restore backup took in step 2 into Server B
6. The data on Server A should be the same as on Server A.

Now, do I HAVE TO do a 'cold' resync from Server A to Server B? Or just
'warm' is enough? 'cause 'cold' sync takes much longer time and uses
lots of space.

Again the same question, where can I find out more info like this? Any
docs or books?

Thanks!

Sorry.

"
6. The data on Server B should be the same as on Server A.
"


Mar 7 '06 #3

P: n/a

Shashi Mannepalli wrote:
Here are some observations:

1. If you do a RESTORE of a database you have to start a COLD start of
the CAPTURE otherwise it will give you an error saying this database
has been restored...etc

2. You can do a COLD start and do a Manual Refresh or Sync script which
is basically telling REPLICATION that even though you started the
CAPTURE in COLD don't start replicating the entire table ...only the
changes and from now on.....
cheers....
Shashi Mannepalli
ib****@yahoo.com wrote:
ibm...@yahoo.com wrote:
Hi all,

Environment:

DB2 v8.1with fixpack 9 on AIX, SQL bi-directional replication.

Server A: capture process
Server B: capture and apply process

1. Shut down all capture and apply processes. Now I am SURE no more
transactions will take place on either side.
2. Take DB backup for Server B
3. Doing some read/write testing on Server B
4. Finish testing on Server B
5. Restore backup took in step 2 into Server B
6. The data on Server A should be the same as on Server A.

Now, do I HAVE TO do a 'cold' resync from Server A to Server B? Or just
'warm' is enough? 'cause 'cold' sync takes much longer time and uses
lots of space.

Again the same question, where can I find out more info like this? Any
docs or books?

Thanks!

Sorry.

"
6. The data on Server B should be the same as on Server A.
"

Thanks a lot!

In the step 5 of my original post, if I can use 'db2move' instead of
restoring database, do I have to COLD start of CAPTURE?

Mar 7 '06 #4

P: n/a
Check this IBM Guide

ftp://ftp.software.ibm.com/ps/produc...e=db2e0e82.pdf
Bottomline is u cannot avoid writing the manual refresh script....if
that is what your goal is !!!!

cheers...
Shashi Mannepalli

Mar 7 '06 #5

This discussion thread is closed

Replies have been disabled for this discussion.