db2 archive log shipping

[adeelsanaullah]

Hi,
I have Db2 8.1.1.152 FixPack 17 on AIX using SAP with DB2. we wanted to have a DR site. we are backing our production using TSM. we just restored the filesystem and later the DB2 data on DR site. every thing seemed to work fine. now we want to have online DR, for this we are shipping archive logs from production to DR site. but if we say
db2 rollforward db <dbname> to end of logs and complete
then this DR DB2 starts creating archive logs. but we want to keep shipping archive logs from production to DR, and then again do rollforward. for this reason we tried
after complete we will
db2rfpen on dbname
this command will again bring it in rollforward pending state.

is there any other way that we can do, that archive logs keep shipping and we dont have to keep our db in rollforward pending state. or if we it is not in rollforward pending state, it should not create its own archive logs instead wait for the logs coming from production site.
please advise soon
adeelsanaullah gmail com

[vijay2082]

Hi,

Probably you are having a DR site by using the log shipping technology. Use below command to rollforward your database and keep it in rollforward pending mode.

1) Once your batch job runs and log file are shipped to DR server go to step 2

2) use below command to rollforward the database through the logs from step 1

db2 "rollforwar d db <db_name> to eng of logs"

Now to go to step 1 > and then to step 2 ....you will have a database which will be in sync with your production as long as you have all log files form step1.

If your production database is unavailable and you want to make your DR database up, then move the exisitng logs form primary to the DR site and use below command

db2 "rollforwar d db <db_name> to eng of logs and complete"

Above command will apply the existing logs to the database and open your database for read/write activity. Also your database at DR site will start archiving logs as well and will act as standlone active database.


You can also trying using the HADR feature form the IBM form db2 udb databases that will take care of log apply and automatic failover as and when required.

Cheers, Vijay